re-run importer / fix cloud-init import failure

Asked by Scott Moser


  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

 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

English Edit question
Launchpad itself Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Max Bowsher (maxb) said :

I don't think it's branch write access that is the key here, but rather the rights to execute the SourcePackage.setBranch method over the API.

The importer user ~package-import seems to have lost the rights to execute SourcePackage.setBranch in relation to distroseries that are not open for upload.

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.

Revision history for this message
William Grant (wgrant) said :

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.

Revision history for this message
William Grant (wgrant) said :

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.

To post a message you must log in.