On 2017-08-01 08:17, Ralf Treinen wrote:
> Hello,
>
> On Mon, Jul 31, 2017 at 07:30:22PM +0300, Niko Tyni wrote:
> > On Mon, Jul 31, 2017 at 04:16:25PM +0200, Mattia Rizzolo wrote:
> > > On Thu, Jul 27, 2017 at 03:15:14PM +0200, Aurelien Jarno wrote:
> > > > > 1. upload to stretch, upgrade wuiet to stretch
> > > >
> > > > I plan to upgrade wuiet to stretch during debconf, but not before. Note
> > > > anyway that going through stretch means waiting for the next point
> > > > release.
> > >
> > > I don't believe waiting for the next point release would be so bad
> > > anyway. It probably means less than 2 months, this change waited for
> > > quite longer…
> > > Also, couldn't you install it from stretch-pu?
> > >
> > > > > 3. upload to stretch-bpo, upgrade wuiet to stretch
> > > >
> > > > That also works and might be faster. It means we need to try to keep as
> > > > much as possible the interface unchanged to not get any breakage.
> > >
> > > That, and it would need be kept up to date in backports to comply with
> > > backport's rules.
> > >
> > >
> > > Overall I think that 1 is the best choice for everything, but then it
> > > comes down to Ralf's willingness to take out the fixing commit and to a
> > > stable update (and RM acceptance of it), and pkg-perl's willingness to
> > > wait for the next point release.
> >
> > Oh, we aren't in any particular hurry though I'd obviously like it to
> > happen early enough for buster :) There's also #867081 to fix before we
> > can reinstate the versioned Provides in perl anyway.
>
> OK, I will go for the next stretch point release. Cheers -Ralf.
Ok, thanks. For the record, wuiet.d.o the machine behind buildd.d.o now
runs stretch.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
