[Bug 845487] Re: Debian source publication checks have broken

Clint Byrum clint at fewbar.com
Tue Sep 13 18:27:12 UTC 2011


Excerpts from Stefano Rivera's message of Tue Sep 13 13:39:35 UTC 2011:
> > any ideas? Leaving them in the queues for now.
> Bah, that'd be carelessness on my part when preparing them on a Debian box. If you want to clear them from the queues, I can re-do the uploads.
> 

Thought that might be it.

All 3 rejected.. upload and I'll take a look ASAP.

> -- 
> You received this bug notification because you are a member of Ubuntu
> Stable Release Updates Team, which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/845487
> 
> Title:
>   Debian source publication checks have broken
> 
> Status in “ubuntu-dev-tools” package in Ubuntu:
>   Fix Released
> Status in “ubuntu-dev-tools” source package in Lucid:
>   Fix Committed
> Status in “ubuntu-dev-tools” source package in Maverick:
>   Fix Committed
> Status in “ubuntu-dev-tools” source package in Natty:
>   Fix Committed
> 
> Bug description:
>   This morning, the Launchpad developers ran an SQL query to convert
>   Pending source publications in Debian to Published.  The reason they
>   were Pending was that the program used to import Debian was the same
>   as that used to initially import Ubuntu into Launchpad, and that
>   initial import needed to set everything to Pending so that the first
>   publisher run would work.  However, this was inappropriate for
>   representing the state of the Debian archive, so things are now being
>   changed over to Published.  Some newly-created records will still be
>   created as Pending until the next Launchpad deployment.
> 
>   This change has broken ubuntu-dev-tools, because there are some bits
>   of code that assume that Debian publications will always be Pending
>   and not Published.
> 
>   Internally, Launchpad has this:
> 
>   active_publishing_status = (
>       PackagePublishingStatus.PENDING,
>       PackagePublishingStatus.PUBLISHED,
>       )
> 
>   ... and to be honest I think that's probably correct for most of the
>   stuff ubuntu-dev-tools is doing, regardless of whether it's looking at
>   Debian or Ubuntu; it would make ubuntu-dev-tools effectively more
>   responsive if it didn't have to wait for a publisher run before
>   noticing that a package version exists in Ubuntu, for example.
> 
>   Unfortunately, you can't pass multiple statuses in one API call (bug
>   845486).  I suppose this either leaves us making multiple calls or
>   asking for all statuses and filtering afterwards.
> 
>   == SRU Justification ==
>   Breaks anything that looks for Debian source records in launchpad, such as requestsync in --lp mode.
> 
>   == SRU Test Case ==
>   Only in maverick or lucid: manage-credentials create -c ubuntu-dev-tools -l 2
>   Try to sync a package: requestsync --lp ibid
>   Good: Continues with usual sync process
>   Bad: E: The package 'ibid' does not exist in the Debian primary archive in 'sid'
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/845487/+subscriptions

-- 
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/845487

Title:
  Debian source publication checks have broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/845487/+subscriptions




More information about the universe-bugs mailing list