Hi, On Wed, Aug 08, 2012 at 02:01:47PM +0200, Alexander Reichle-Schmehl wrote: > > * Andreas Tille <[email protected]> [120807 08:57]: > > > it seems that some binary packages for arches were autobuilded for a > > package in contrib even if they should not (because of its non-free > > dependencies). I would like you to remove beast-doc for the > > following architectures: > > > > armel > > armhf > > ia64 > > kfreebsd-amd64 > > kfreebsd-i386 > > mips > > mipsel > > powerpc > > s390 > > s390x > > sparc > > > > ATTENTION: The package beast-doc is also builded from the beast package. > > The removal above is for the binary package which was created from the > > source beast-mcmc. Sorry for the confusion. > > Uhm... I'm confused. Or dak is, or we both are.
I guess the cause of the confusion is http://qa.debian.org/excuses.php?package=beast-mcmc I have no idea why beast-doc is listed there - but beast-mcmc-lib vanished after you closed #681957. I had some hope that this would help as well for beast-doc. > The current state is: > > tolimar@franck:~$ dak ls beast-doc > beast-doc | 0.7.4-4 | testing | all > beast-doc | 0.7.4-4 | unstable | all > beast-doc | 1.6.2-1 | unstable/contrib | all > > So we can't remove it from the named architectures, as it's arch any > (which makes sense, as it is a doc package). So, and if I understand > correctly, you want the beast-doc/1.6.2-1 to be removed, correct? Yes. Due to the name space conflict (#679394) the doc package which is created by beast-mcmc source is now named beast-mcmc-doc and beast-doc version 1.6.2-* should not exist (neither arch any nor arch all). > I think we might need help from a ftp-master here; it appears I can only > remove both package (0.7.4-4 as well ass 1.6.2-1). May be it helps that the beast-doc in question resides in contrib? Sorry for the confusion Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
