[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Accepted backports not showing up in the archive|PTS?



On Fri, 31 Mar 2017 08:05:47 +0100
Neil Williams <codehelp@debian.org> wrote:

> On Thu, 30 Mar 2017 11:48:24 +0200
> Mattia Rizzolo <mattia@debian.org> wrote:
> 
> > On Thu, Mar 30, 2017 at 10:44:28AM +0100, Neil Williams wrote:  
> > > https://lists.alioth.debian.org/pipermail/pkg-linaro-lava-devel/Week-of-Mon-20170327/000849.html
> > > Tue Mar 28 19:49:15 UTC 2017
> > > Does not show up here:
> > > https://tracker.debian.org/pkg/lava-coordinator
> > > 
> > > This backport does not have to go through NEW as it is updating an
> > > existing backport (to fix
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789551 which
> > > appears as a result of
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858835)
> > > 
> > > Typically, this would have shown up by now. Is there a problem
> > > with backports and the archive?    
> > 
> > The hint is in the subject:
> > *ACCEPTED into  jessie-backports->backports-policy*
> > 
> > It's not going to NEW, but in period of freeze _all_ backports
> > upload goes to a policy queue and need manual approval from
> > backports masters.
> > 
> > You'll get another accepted email when it passes that stup.  
> 
> Any idea how long that will take? The reason for the backport is that
> installations of affected packages fail completely due to the backport
> of python-lockfile being made without a corresponding backport of
> python-daemon and then lava-coordinator. This isn't a feature
> enhancement bug, it would be RC if it happened in unstable. We are
> seeing continued reports of breakage from users attempting
> installations.
> 
> Also, could the policy be published please? How close is it to the
> freeze policy of the release team? Why was the policy introduced?

Further, is there a location from which pending backports can be
downloaded? Packages in the NEW queue appear in the incoming archive
but these backports are not included. Without an understanding of why
these packages are delayed, I need to be able to offer the backports to
users directly to fix their installations. I can offer lava-coordinator
because I did that backport, I'm unable to find the python-daemon
backport uploaded by Andreas. Just having that .deb somewhere would be
very useful.

-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

Attachment: pgpqrxIo4Z3xJ.pgp
Description: OpenPGP digital signature


Reply to: