Merge lp:~james-w/pkgme/clean-maintainer into lp:pkgme
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Jonathan Lange | ||||
Approved revision: | 107 | ||||
Merged at revision: | 110 | ||||
Proposed branch: | lp:~james-w/pkgme/clean-maintainer | ||||
Merge into: | lp:pkgme | ||||
Diff against target: |
115 lines (+57/-2) 4 files modified
pkgme/info_elements.py (+15/-0) pkgme/tests/test_info_elements.py (+29/-0) pkgme/tests/test_package_files.py (+1/-1) pkgme/tests/test_script.py (+12/-1) |
||||
To merge this branch: | bzr merge lp:~james-w/pkgme/clean-maintainer | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jonathan Lange | Approve | ||
Review via email: mp+108591@code.launchpad.net |
Commit message
Ensure the maintainer value will always be accepted by dpkg.
Description of the change
Hi,
Daniel reported in https:/
a failure as the maintainer info in the changelog was not recognised.
The docs say that the backend should provide the info in the accepted format,
but it's pretty easy for pkgme to fix up anything that isn't in that format
to get a working package.
I don't really see a downside to this, as if the backend provides something
valid this code shouldn't change it, and if they provide something invalid
the other choice is to fail, which isn't helpful to users.
There's a drive-by here to fix a test-isolation issue I found while running
with DEBEMAIL set in the environment. If it's set and invalid then those
tests fail as they run debuild which will fail. The fix actually means that
debuild would no longer fail, but being explicit about the isolation would
seem to be a good idea.
Thanks,
James
Well done. The code looks clean to me and it certainly fixes the issue I ran into.