Having no EMAIL environment variable set makes quickly release fail
Bug #418369 reported by
Rick Spencer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Quickly |
Fix Released
|
Medium
|
Unassigned |
Bug Description
if you do not have an EMAIL set in your .baschrc file, then even if you have pgp keys set, quickly release fails. This is because dpkg-buildpackage falls back to the users local machine user name, which does not match the email set for the pgp key, and thus the whole thing bombs.
I suppose release.py could check if the EMAIL variable is set, and if not go ahead and use the users email as an environment variable when making the dpkg-buildpackage call.
Related branches
Changed in quickly: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I agree. I'll do this evening.
So, if EMAIL is empty, I'll try to take the preferred email of LP account (as release command has this info).
Just for the information, did it crashed gracefully?