Dear wanna-build team, Could you please clarify what is the status on this issue? (And, if applicable, what are the blockers?) Thanks, Lucas On 06/06/13 at 23:37 +0200, Christoph Egger wrote: > Hi! > > Gerfried Fuchs <rhonda@deb.at> writes: > > So let me re-iterate my question: what is needed to get autobuilding > > working for both wheezy-backports and squeeze-backports-sloppy, what is > > the specific pain part involved in getting this done, and how can one > > help to improve it that we won't have the same painful moments again for > > jessie? > > wheezy-backports should be building just fine on kfreebsd-* (I have > several successfull logs there as well. as for squeeze-backports-sloppy, > there's some technality to be fixed [0]. So as far as wanna-build is > involved everything's in place apart buildd-admins not having these > suites configured [1]. > > Christoph > > [1] > buildd admins: you need to have a schroot config in > /etc/schroot/chroot.d with name > squeeze-backports-sloppy-${arch}-sbuild and in ~buildd/.builddrc add > squeeze-backports-sloppy to squeeze-backports (aptitude, upload to > backports-master) and wheezy-backports to experimental (aptitude, > upload to ftp-master). That should be it. > > [0] > We have a rather strict limit on length of mount-points and therefore > need to keep CHROOT_NAME short. that's done for $normal by replacing > kfreebsd-amd64 with ka in the name and adding an alias. Unfortunately > that's not enough for squeeze-backports-sloppy-$something. > > I can not, trivially, shorten backports-sloppy with the same trick > because setup scripts parse $CHROOT_NAME to add sources.list entries > and need the full 'backports-sloppy' substring. changing to > $CHROOT_ALIAS fails as well because the parsing gets confused by the > '-' in kfreebsd-amd64. > -- > 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 > Debian Developer | Lisp Hacker | CaCert Assurer
Attachment:
signature.asc
Description: Digital signature