On 24/05/10 at 22:27 +0200, Andreas Barth wrote: > Re the long term perspectives, Jakub Wilk has contacted Lucas Nussbaum > about testing all our packages in unstable and see which are affected > by this bug, and then filling bugs as appropriate. Once we know how > many packages are affected, we then can encourage people to fix the > bugs with their next uploads. As soon as the number of affected > packages is acceptable, we then can turn on LINENO on dash again. > Otherwise this is now directly negativly affecting all of our ongoing > and planned transitions.
Hi, I've just done an archive rebuild. 459 packages failed. 340 are new failures (they didn't fail two weeks ago). I've attached the full list of new failures. Filtering out failures that don't seem caused by this change (with grep -v -e GCC_ERROR -e BUILDDEPS -e LD_ERROR -e globus -e cc1d -e autopoint -e dpkg-gencontrol -e epstopdf), I'm down to a maximum of 160 failures possibly caused by this change. How do you want to proceed? Should I file bugs on all those packages, or wait until a "fixed" dash is uploaded? IMHO, the most reasonable option is to keep the current package as is, to change the shell in the buildd chroots to bash temporarily, and to file those bugs as RC. That way, people can easily test and fix them, and the buildds are not affected. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
