branch source builder fails to build unsigned packages, but doesn't see the problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu CI Engine |
Fix Released
|
High
|
Francis Ginther | ||
Ubuntu CI Services |
Fix Released
|
High
|
Francis Ginther |
Bug Description
I have foolishly created my .changes without signing it and submitted it to the airline for processing. Looking at the bsb logs I see:
INFO:__main__:The PPA is: ppa:pwlars/
INFO:root:Upload to the ppa: ppa:pwlars/
INFO:root:
INFO:root:
INFO:root:
$USER not set, will use login information.
Checking signature on .changes
gpg: fatal: can't create directory `/nonexistent/
secmem usage: 0/0 bytes in 0/0 blocks of pool 0/32768
Error in finding signature verification status.
Checking signature on .dsc
Checking signature on .dsc
gpg: fatal: can't create directory `/nonexistent/
secmem usage: 0/0 bytes in 0/0 blocks of pool 0/32768
Error in finding signature verification status.
Uploading to ppa (via ftp to ppa.launchpad.net):
Uploading bash_4.
Uploading bash_4.
Uploading bash_4.
Successfully uploaded packages.
Somehow, I think we need to have it check that it's signed, or apparently it will just get ignored in the ppa.
tags: | added: airline |
Changed in ubuntu-ci-services-itself: | |
assignee: | nobody → Francis Ginther (fginther) |
Changed in uci-engine: | |
assignee: | nobody → Francis Ginther (fginther) |
importance: | Undecided → High |
status: | New → Fix Released |
Francis, what did we decide to do with this? I thought we were going to have the CLI check to see if they were signed?