Jakub Wilk <jw...@debian.org> writes: > * Оlе Ѕtrеісhеr <debian-de...@liska.ath.cx>, 2014-08-14, 10:08: >>>> I've uploaded a package to contrib [1], that needs a non-free package >>>> (pgplot5) as build dependency. While it builds nicely on my local pbuilder >>>> (after adding non-free), it fails to build on the buildds [2]. >>>This is bug #690282. >> >> Hmm, so how do I build the remaining archs? I could do some on a >> quemu-users... > > I don't think we want package built on QEMU in the archive.
Why? > i386 packages can be built in a chroot. For anything else, you can ask on a > porters' mailing list[0]; although it might not be worth the effort. Since I am not a DD yet, this would mean that I have to ask for access to all porter boxes, build the binaries, and then ask my sponsor to upload them. And to repeat this for every new version. Since I already know how long it usually takes in Debian for steps like these (f.e. the package in question took four months until it passed NEW), I doubt that this is a prtactable solution. >> if I do this once, do I have to do this always (otherwise the package would >> not migrate due to missing builds)? > > That's right. The package won't migrate to testing it it's out of date on a > release architecture. This at the end leads to the situation that the package will be build only for those platforms which I would count as worthwile -- so limiting to linux-i386 and linux-x86. Quite far from a perfect solution, but OK. Best Ole -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/874mxft10l....@news.ole.ath.cx
