On Sun, Aug 04, 2013 at 07:14:04PM +0200, Thorsten Alteholz wrote: > > > On Sun, 4 Aug 2013, Julien Cristau wrote: > >>Ok, but was does that mean for my package. Isn't it allowed to let a > >>non-free package depend on another non-free package anymore? > >> > >It's allowed, it just won't be autobuilt. > > Hmm, the package already has this XS-Autobuild stuff in > debian/control. The buildd even tries to build it, but complains > that a dependency is not available. But that could not be true!? > > Or do I interpret this message wrong: > mgltools-sff (= 1.5.7~rc1~cvs.20130519-2) build-depends on missing: > - mgltools-bhtree
It was not given to the buildd. This is a check where the Build-Depends are checked against what is in the Packages' files, before the buildd tries it. This is done using edos-distcheck. The difference is that there used to be 1 Packages files that give the buildds access to what's in incoming that contained all architectures and contained main, contrib and non-free. Those are now all seperate files like the normal archive. The buildds themself should now all also be configured to have a deb-src line for non-free, but only have a deb line for main and contrib. So even if we moved it out of the BD-Uninstallable state, it wouldn't get build. I'm not sure what policy that the debian.org hosts have for installing and running non-free software, but I understand that this is problematic, and I think we should at least ask DSA first before doing so. Kurt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
