Pasaffe logging can't be enabled in pasaffe-import-gpass
Bug #991143 reported by
Marc Deslauriers
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_
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 |
tags: |
added: verification-done removed: verification-needed |
To post a comment you must log in.
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