re-run importer / fix cloud-init import failure
Hi,
That was a result of me (smoser) having fought it at some point in the past and likely caused the failure.
So, xnox wiped history, with the intent of having the importer re-run cleanly from data in the archive.
the result is failure seen at
http://
It seems in "clean re-import" mode, the importer needs the ability to write to branches like lp:ubuntu/maverick/$PACKAGE , but those branches are now read-only.
Can someone please help to get this fixed specifically for cloud-init , and is there a possible generic fix ? It seems like many packages with fialed importer state might be very happy to have importer run from scratch.
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- 2013-08-14
- Last reply:
- 2013-08-28
This question was reopened
| Max Bowsher (maxb) said : | #1 |
I don't think it's branch write access that is the key here, but rather the rights to execute the SourcePackage.
The importer user ~package-import seems to have lost the rights to execute SourcePackage.
It needs to be able to do this to be able to back-populate official package branches.
I think that fixing this is going to require a code change to Launchpad.
| William Grant (wgrant) said : | #2 |
I've fixed this class of error. It was broken by the recently tightened restrictions on uploads to obsolete series, so I've enabled obsolete series uploads to the Ubuntu primary archive. cloud-init reimported cleanly.
Package imports that haven't succeeded in a long time might still fail because they can't set official branches for obsolete release pockets, but they are far less common.
| William Grant (wgrant) said : | #3 |
s/obsolete release pockets/stable release pockets/
Can you help with this problem?
Provide an answer of your own, or ask Scott Moser for more information if necessary.
