Package: libpng12-0
Version: 1.2.8rel-4
Severity: important

The latest version of libpng12-0 includes a shlibs bump with only this
changelog entry:

  * libpng12-0.shlibs: bump the shlibs version.

I have compared the symbol tables from libpng12-0_1.2.8rel-4 and
libpng12-0_1.2.8rel-1.  There are *no* symbols exported by -4 that were not
already in -1.  Indeed, as we both know there are a number of symbols that
were *removed*, but that should have no impact on the shlibs: any binary
built against -4 *will* work with -1, so the shlibs should not have been
changed from their previous value.

Not only is this shlibs bump wrong, though, it is very, very inopportune.
The shlibs bump coincides with a change in the source package name, and
libpng12-0 has now taken over the libpng source package from libpng10-0.

The shlibs bump means that all packages built against the newest libpng12-0
must wait for libpng12-0 to be updated in testing before they can reach
testing.

The source package name change means that all packages that depend on
libpng10-0 must be removed from testing before the new version of libpng12-0
can reach testing.

There are a number of packages in both sets, which means that all those
packages must be ready to go into testing *at the same time* as libpng.

I've filed this bug at severity: serious, but that doesn't even begin to
describe the personal hell that this transition is going to cause the
release team right now.  Unless there is a very good reason for the shlibs
bump which I have overlooked, please revert it ASAP.

-- 
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/

Attachment: signature.asc
Description: Digital signature

Reply via email to