Pasaffe logging can't be enabled in pasaffe-import-gpass

Bug #991143 reported by Marc Deslauriers
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Pasaffe
Fix Released
Undecided
Unassigned
pasaffe (Ubuntu)
Fix Released
Undecided
Marc Deslauriers
Precise
Fix Released
Undecided
Marc Deslauriers
Quantal
Fix Released
Undecided
Marc Deslauriers

Bug Description

Although pasaffe_lib/gpassfile.py contains logging statements, logging can't be turned on when using the pasaffe-import-gpass script. This makes debugging import failures difficult.

Changed in pasaffe:
status: New → Fix Committed
Changed in pasaffe (Ubuntu):
status: New → Confirmed
assignee: nobody → Marc Deslauriers (mdeslaur)
Changed in pasaffe (Ubuntu Precise):
status: New → Confirmed
assignee: nobody → Marc Deslauriers (mdeslaur)
Changed in pasaffe:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pasaffe - 0.17-0ubuntu1

---------------
pasaffe (0.17-0ubuntu1) quantal; urgency=low

  * New upstream release
   - Add command-line option to specify default database
   - Don't save database specified on command line as default
   - Properly handle entries that have no URL specified (LP: #980608)
   - Fix logging in pasaffe-import scripts so we can debug failures
     (LP: #991143)
   - Correctly strip gpass database padding (LP: #991204)
   - Properly handle unicode characters with optparse (LP: #983210)
 -- Marc Deslauriers <email address hidden> Thu, 03 May 2012 20:37:15 -0400

Changed in pasaffe (Ubuntu Quantal):
status: Confirmed → Fix Released
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

SRU Request:

[Impact]
logging cannot be enabled when using the command line tools. This prevents properly debugging issues, such as the issue in LP: #991204.

[Development Fix]
Quantal has been fixed by updating to version 0.17 that contains the fix for this issue

[Stable Fix]
See attached patch for minimal fix for this issue.

[Test Case]
1- Launch pasaffe-import-gpass on a gpass database with the -vv switch

[Regression Potential]
This is an obvious fix, and if it's incorrect it would not prevent Pasaffe from working since it only affects the command line tools

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello Marc, or anyone else affected,

Accepted pasaffe into precise-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in pasaffe (Ubuntu Precise):
status: Confirmed → Fix Committed
tags: added: verification-needed
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

I confirm the package in -proposed enables proper logging.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pasaffe - 0.16-0ubuntu1.1

---------------
pasaffe (0.16-0ubuntu1.1) precise-proposed; urgency=low

  * debian/patches/lp980608.patch: Don't print an error if trying to open a
    URL when none is set in an entry. (LP: #980608)
  * debian/patches/lp991143.patch: add option to turn on debugging when
    using the pasaffe-import-* scripts. (LP: #991143)
  * debian/patches/lp991204.patch: properly strip gpass database padding.
    (LP: #991204)
  * debian/patches/lp983210.patch: Properly handle unicode chars with
    optparse. (LP: #983210)
 -- Marc Deslauriers <email address hidden> Thu, 03 May 2012 20:13:13 -0400

Changed in pasaffe (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.