Launchpad itself

PPA Build Uploads Failing

Asked by Edgemaster

I've had a number of PPA builds that have completed successfully, but have all failed the upload stage with
```
DEBUG Considering changefile 62407/ubuntu/camlp5_6.12-1~ppa1_amd64.changes
DEBUG Finding fresh policy
INFO Processing upload camlp5_6.12-1~ppa1_amd64.changes
ERROR Unhandled exception processing upload
INFO Upload was rejected:
INFO Unhandled exception processing upload: sequence item 0: expected string, exceptions.SystemError found
INFO Committing the transaction and any mails associated with this upload.
```

I've no idea what's wrong...

https://launchpad.net/~grand-edgemaster/+archive/ubuntu/coq-ocaml42/+build/6692572

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
Last query:
Last reply:
Revision history for this message
Best Colin Watson (cjwatson) said : 		#1

This was a regression caused by a production upgrade of apt on the builder manager system. We reverted it and retried the affected builds, including yours. Sorry for the inconvenience.

Revision history for this message
David Bartley (dtbartle) said : 		#2

I'm also seeing the same error trying to upload to a private PPA, but the error comes via email.

Revision history for this message
Colin Watson (cjwatson) said : 		#3

This only happens on manual uploads if you tried to upload binaries, which is disallowed in any case; Launchpad only accepts source-only uploads.

Revision history for this message
David Bartley (dtbartle) said : 		#4

Yes, that was the problem. It would be nice if the error message could be improved.

Revision history for this message
Colin Watson (cjwatson) said : 		#5

Indeed. https://code.launchpad.net/~cjwatson/launchpad/archiveuploader-binary-error/+merge/247872 addresses part of this, but the rest will require sorting out an updated build of python-apt for our production systems. I have an item in our internal task tracker to sort this out, although right now the buggy error message is the only significant consequence so it's not quite at the top of my priority list ...

Revision history for this message
Edgemaster (grand-edgemaster) said : 		#6

Thanks Colin Watson, that solved my question.