Fabian, On Wed, Oct 25, 2006 at 06:49:15AM -0700, Fabian Fagerholm wrote:
> Format: 1.7 > Date: Thu, 19 Oct 2006 23:26:02 +0300 > Source: cyrus-sasl-2.1 > Binary: libsasl2-2 cyrus-sasl-2.1-bin libsasl2 libsasl2-2-dev sasl2-bin > libsasl2-dev libsasl2-2-modules-gssapi-mit libsasl2-modules-gssapi-heimdal > libsasl2-2-modules-otp cyrus-sasl-2.1-doc libsasl2-modules-sql > libsasl2-2-modules-sql libsasl2-modules libsasl2-2-modules > Architecture: source i386 all > Version: 2.1.22-0~pre01 > Distribution: experimental > Urgency: low > Maintainer: Fabian Fagerholm <[EMAIL PROTECTED]> > Changed-By: Fabian Fagerholm <[EMAIL PROTECTED]> > Description: > cyrus-sasl-2.1-bin - Administration programs for SASL users database > cyrus-sasl-2.1-doc - Documentation for Cyrus SASL library and utilities > libsasl2 - Authentication abstraction library > libsasl2-2 - Authentication abstraction library > libsasl2-2-dev - Development files for SASL authentication abstraction > library > libsasl2-2-modules - Pluggable Authentication Modules for SASL > libsasl2-2-modules-gssapi-mit - Pluggable Authentication Modules for SASL > (GSSAPI) > libsasl2-2-modules-otp - Pluggable Authentication Modules for SASL (OTP) > libsasl2-2-modules-sql - Pluggable Authentication Modules for SASL (SQL) > libsasl2-dev - Development files for SASL authentication abstraction library > libsasl2-modules - Pluggable Authentication Modules for SASL > libsasl2-modules-gssapi-heimdal - Pluggable Authentication Modules for SASL > (GSSAPI) > libsasl2-modules-sql - Pluggable Authentication Modules for SASL (SQL) > sasl2-bin - Administration programs for SASL users database Er, I'm happy to see that this version is now available in experimental, but why have you changed the names of *all* the packages, *including* the source package? This is totally unnecessary archive churn and archive bloat -- the only one of these packages whose name should change when there's an soname change is that of the library itself, so all the rest of these are just going to cause confusion in the bts, bloat on users systems and in the archive with unnecessary packages, and unnecessary transitions in the future, either when someone agrees that the packages are misnamed or the next time that you change the names to keep up with soname changes in the library! I do not think the package should be allowed into etch (or unstable) in this condition. If you want to fix up the library package name, that's one thing, and I can concede that this qualifies as a bugfix. Renaming *all* the packages, and renaming the source package, is quite another thing, and totally inappropriate in a package that's frozen for release. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
