glibc_2.3.6-6_i386.changes REJECTED
Hi,
This is a reject of the new -bin packages (both of them).
The issues with the -bin package are that it may cause upgrade problems, both
in that upgrading from existing libc's may result in a broken system between
the new libc6 being unpacked and the new libc-bin being installed (ldconfig
not being available), and that when you have a new glibc from upstream, you may
have problems with the new ldconfig (etc) requiring symbols from the new glibc,
and ensuring they're installed correctly.
Note that libc-bin should probably also be Essential: yes, and its
Depends: should be upgraded to Pre-Depends: to work correctly.
Note that libc-bin was split out of the package previously and had to
be reverted due to breakage; see:
glibc (2.1.2-12) frozen unstable; urgency=low
* The "Cardboard Messiah" release.
...
* Kill $(libc)-bin.
...
-- Joel Klecker <debian-glibc@lists.debian.org> Wed, 26 Jan 2000 16:44:12 -0800
glibc (2.1.2-11) unstable; urgency=low
* The "If it ain't broke, you're not tryin'" release.
* Split out $(libc)-bin and libnss1-compat.
* Split debian/rules into debian/package-rules/*.
$(libc-bin):
- Install db_* programs as glibcdb_*.
- Move zic, zdump, locale, localedef, getent here.
- Use alternatives for db_*. (closes:Bug#50311,#50341)
...
-- Joel Klecker <debian-glibc@lists.debian.org> Sat, 25 Dec 1999 09:54:29 -0800
This probably needs some discussion on -devel and some trial runs in
experimental to avoid breakage.
(Note that "Priority: required" and "Essential: yes" are essentially
synonyms -- required should only be used for essential packages and
things they depend on; so the usual rules for introducing a new essential
package should probably be applied -- namely, talk about it on -devel
first. See the last paragraph of s3.8 _Essential packages_ in -policy)
Sorry about that :-/
Cheers,
aj
===
If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.
Reply to: