On Fri, Apr 14, 2006 at 03:03:31AM -0700, Jeroen van Wolffelaar wrote: > Hi maintainers, > > Sorry, but I'm going to reject this package. > > 1) You're adding a new package directly to unstable, instead of first to > experimental.
The first point has already been discussed, let's see other ones. > 2) Glibc is currently RC buggy, and it'd really really be better to just get > an RC bugfree glibc in testing asap without all kinds of new changes Which RC bug? The one that was triggered by a change in libstdc++ and could have been reassigned to it? Or the one about locales that became RC today? > 3) The locales-all package is 52MB, 275MB installed size. That's a factor 10 > more than the wishlist (!) bug requestiong the package says. To top this > off, it's also arch:any, so multiplying the required archive space by quite > a factor. I'd encourage you to ensure the binary blogs in question are > architecture neutral, and also look critically at why this package needs to > be so huge, for 'just' the compiled locales. There are 380 locales > supported in unstable atm, and the text representations take 6.8M? An easy > optimalisation is already making sure the 850kB or so LC_COLLATE files of > utf-8 locales to be shared amongst each of the UTF-8 locales. Fixed in SVN, here is the relevant changelog entry: * Preserve hard links when compiling the locales-all package, this reduces package size by a factor of 3. Thanks to Jeroen van Wolffelaar for noticing. > 4) You ask packages which previously depend on locales to now depend on > locales|generated-locales, why not simply let locales-all provide locales? Fixed in SVN, here is the relevant changelog entry: * Let locales-all Provides: locales instead of a virtual generated-locales package. This is requested by Jeroen van Wolffelaar to allow this new package enter unstable. Packages which Build-Depends on locales are likely to FTBFS if locales-all is installed, this dependency will be fixed in a later release. Please let me know if something else needs to be fixed. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]