On Tue, 26 Jul 2016 13:52:55 +0200 Jens Reyer <[email protected]> wrote:
> On 26.07.2016 13:31, Andrey Gursky wrote: > > Hi, > > > > I was about to rebuild wine-development 1.9.14 locally and it failed > > due to the dependency on debhelper (>= 9.20160702), which is still > > 9.20160403 in Stretch. No problem, I've updated this package. But how > > have you managed to let buildd automatically build wine-development for > > Stretch with a broken dependency? > > The packages are built in unstable, where debhelper 9.20160702 already > was. However debhelper was/is set to remain 20 days in unstable > (contrary to the usual 5 days) before migrating to testing (stretch). Aha, that makes all clear. > I still think it's better to use new tools as soon as possible, in order > to find possible bugs. In this case there was a new debhelper feature > requested by a wine user who, like you, had issues with the -tools packages. Fully agreed. Once, I discovered very soon an issue with a debhelper update. Reported it [1], but instead to fix it, people since 4(!) years still suffer from it. Though it's not a bug but a dilemma like issue, thus making other people happy. > The current debhelper hopefully migrates to stretch on July 29th. Regards, Andrey [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677876 _______________________________________________ pkg-wine-party mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-wine-party
