Re: Pushing a bunch of packages to jessie-backports
On 11/27/2015 11:31 AM, Piotr Ożarowski wrote:
>> Will do. FYI, I'm still waiting for the removal of
>> python-repoze.{what,what-plugins,who-plugins}, which is blocking the
>> migration of Keystone, and which therefore makes my efforts useless
>> (there's no point of uploading OpenStack without keystone). So for the
>> moment, my uploads are stalled.
>
> what's blocking you with sphinx?
I don't want to upload it if I can't upload the rest at the same time.
> you realize some packages will have to go though NEW and sphinx is one of them?
Yes. Which is why I asked (on the backports list) the backports FTP
masters what they thought was best for the upload.
Though there's no way to make it happen correctly without having some
breakage due to NEW at some point. There's too many interactions and
inter-dependencies.
>> (build-)dependencies are satisfied, yes. Though I don't think I actually
>> need to upload in a specific order: I can push all at once if it is
>> within a single dak run (if I'm wrong here, let me know).
>
> if you upload A that doesn't have to go through NEW and new B that A build
> depends on, A is broken.
> (if all of them will end up in NEW, ftp-masters will take care of that)
What you give above as an example is too simplistic. It works for basic
cases, but not here, with all of what I want to upload, and already
existing packages in jessie-backports.
That's one of the multiple breakage that the NEW queue brings. There's
unfortunately no way to fix that for this kind of complex uploads with
inter-dependencies and updates of existing packages. The only way,
unfortunately, is to have the NEW queue processed fast enough by the FTP
masters.
Reply to: