On Mon, Jul 17, 2006 at 05:06:49PM +0000, Marc Brockschmidt <[EMAIL PROTECTED]> wrote: > (...) > Etch will carry 4.0 as version number.
Just out of curiosity, what is the rationale behind the major version change ? > (...) > And these release goals currently: > - - LSB 3.1 compatibility > - - SELinux support > - - pervasive ipv6 support > - - pervasive LFS (large files) support > - - new python framework > - - NFS v4 support I'd like to add this one: - Remove mozilla That involves rebuilding all packages that depend on mozilla against xulrunner. Bug #370436 is tracking the progress. While talking about release, I got bitten by #377418 which I'm pretty sure, on top of being a problem with all mozilla-based packages (thunderbird, firefox, xulrunner, mozilla), is something that is probably present on a lot of packages: those using uname in their build system. The problem here is that the buildd in question is running a 64bit kernel while building 32bit binaries. The same problem would happen if building i386 binaries on amd64 buildds. Now my question is: could these bugs be treated ignore-etch ? It's indeed RC, but is it release blocker that all packages in etch can be built this way ? If it is the case, someone with an amd64 or a sparc64 or anything that can do bi-arch should try to build the whole archive to find those packages that have the problem. Cheers, Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]