Re: synching non-free packages for sarge
firstname.lastname@example.org (Aaron M. Ucko) writes:
> Goswin von Brederlow <email@example.com> writes:
>> One problem with this is that for non-free packages it is unclear if
>> it is even allowed to build them. Ofhand I know of one (pine) which
> Right, I well understand why the autobuilders stick to main.
>> It would be nice to have a list of packages in contrib/non-free that
>> may legally be autobuild and that can be autobuild with free software
> Agreed, though buildd maintainers should of course still have the
> right to limit their machines to main.
Sure but I would hope main+contrib would be default.
>> I scheduled bsdgames-nonfree for build on magix (inofficial mipsel
>> buildd). Its currently building k3d and bsdgames-nonfree will be next.
> Thanks, though as I mentioned elsewhere in the thread, I'm more
> concerned about the existing outdated binaries for arm and mips than
> the lack of a mipsel binary, which may become out of date and hard to
> update down the road.
>From the multibuild wanna-build log:
| >> unstable mips: take bsdgames-nonfree 2.16-1
| unstable non-free mips bsdgames-nonfree 2.16-1
A mips build is on its way now too.