Ubuntu
jade package

libsp1: Changed ABI without soname change

Bug #11410 reported by Debian Bug Importer
4
Affects Status Importance Assigned to Milestone
jade (Debian)
Fix Released
Unknown
jade (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Automatically imported from Debian bug report #286945 http://bugs.debian.org/286945

See original description
Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #286945 http://bugs.debian.org/286945

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Thu, 23 Dec 2004 08:22:33 +0100
From: Lionel Elie Mamane <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: libsp1: Changed ABI without soname change

Package: libsp1
Version: 1.3.4-1.2.1-42
Severity: grave

Machine one:

ii libsp1 1.3.4-1.2.1-28 Runtime library for James Clark's SP suite

master@tofu:~$ readelf -s /usr/lib/libsp.so.1|grep __ti16OutputByteStream
  1203: 0020c888 8 OBJECT GLOBAL DEFAULT 20 __ti16OutputByteStream

Machine two:

ii libsp1 1.3.4-1.2.1-42 Runtime library for James Clark's SP suite

lmamane@topaz:/usr/src/backports/pdns/pdns-2.9.16$ readelf -s /usr/lib/libsp.so.1|grep __ti16OutputByteStream

This is an incompatible ABI change, and warrants a soname change. As a
result, jade doesn't work anymore on machine two, since it was linked
against an older version of libps1, that had the __ti16OutputByteStream
symbol.

-- System Information:
Debian Release: 3.0
  APT prefers unstable
  APT policy: (400, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-signal.dos
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libsp1 depends on:
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libgcc1 1:3.4.3-1 GCC support library
ii libstdc++5 1:3.3.5-2 The GNU Standard C++ Library v3

-- no debconf information

Revision history for this message
In , Neil Roeth (neil-debian) wrote : Bug#286945: libsp1: Changed ABI without soname change

On Dec 23, Lionel Elie Mamane (<email address hidden>) wrote:
 > Package: libsp1
 > Version: 1.3.4-1.2.1-42
 > Severity: grave
 >
 > Machine one:
 >
 > ii libsp1 1.3.4-1.2.1-28 Runtime library for James Clark's SP suite
 >
 > master@tofu:~$ readelf -s /usr/lib/libsp.so.1|grep __ti16OutputByteStream
 > 1203: 0020c888 8 OBJECT GLOBAL DEFAULT 20 __ti16OutputByteStream
 >
 > Machine two:
 >
 > ii libsp1 1.3.4-1.2.1-42 Runtime library for James Clark's SP suite
 >
 > lmamane@topaz:/usr/src/backports/pdns/pdns-2.9.16$ readelf -s /usr/lib/libsp.so.1|grep __ti16OutputByteStream
 >
 > This is an incompatible ABI change, and warrants a soname change. As a
 > result, jade doesn't work anymore on machine two, since it was linked
 > against an older version of libps1, that had the __ti16OutputByteStream
 > symbol.

Jade has had a dependency on libsp1 >= -30 since -30, so how did you get jade
-42 installed with libsp1 -28? You are correct that an ABI change should be
handled with a different soname, however: (1) the only package affected is
jade, which has dependencies to prevent this, (2) it will not affect anyone
upgrading from woody to sarge since -28 was in woody, and the newer versions
of jade will force an upgrade to a version of libsp1 >= -30, and (3) it's darn
close to the sarge release to be making a soname change that doesn't really
affect anyone who installs normally, i.e., in a way that the dependencies
would take care of the problem. Do you really think this should be a release
critical bug? I'd be more inclined to change this if I had reports that there
were other programs that need the old libsp1 ABI as well as programs that need
the new one.

--
Neil Roeth

Revision history for this message
In , Lionel Elie Mamane (lionel-mamane) wrote :

On Thu, Dec 23, 2004 at 07:31:23AM -0500, Neil Roeth wrote:
> On Dec 23, Lionel Elie Mamane (<email address hidden>) wrote:
>> Package: libsp1
>> Version: 1.3.4-1.2.1-42
>> Severity: grave

>> Machine one:
>>
>> ii libsp1 1.3.4-1.2.1-28 Runtime library for James Clark's SP suite

>> master@tofu:~$ readelf -s /usr/lib/libsp.so.1|grep __ti16OutputByteStream
>> 1203: 0020c888 8 OBJECT GLOBAL DEFAULT 20 __ti16OutputByteStream

>> Machine two:

>> ii libsp1 1.3.4-1.2.1-42 Runtime library for James Clark's SP suite

>> lmamane@topaz:/usr/src/backports/pdns/pdns-2.9.16$ readelf -s /usr/lib/libsp.so.1|grep __ti16OutputByteStream

>> This is an incompatible ABI change, and warrants a soname change. As a
>> result, jade doesn't work anymore on machine two, since it was linked
>> against an older version of libps1, that had the __ti16OutputByteStream
>> symbol.

> Jade has had a dependency on libsp1 >= -30 since -30, so how did you
> get jade -42 installed with libsp1 -28?

It is the other way round: jade 1.2.1-28 with libsp1 1.3.4-1.2.1-42.

> You are correct that an ABI change should be handled with a
> different soname, however: (1) the only package affected is jade,
> which has dependencies to prevent this,

The old jade doesn't have it; if you want to go the "but jade is the
only package depending on libsp1 anyway" route, you need the newer
libsp1 to conflict with the older jade, too.

And it then, it still breaks programs people have self-compiled, and I
don't think we should call this acceptable.

> (2) it will not affect anyone upgrading from woody to sarge since
> -28 was in woody, and the newer versions of jade will force an
> upgrade to a version of libsp1 >= -30,

It will affect them if they have locally compiled programs against
libsp1.

> and (3) it's darn close to the sarge release to be making a soname
> change

(That's another story altogether.)

> that doesn't really affect anyone who installs normally, i.e., in a
> way that the dependencies would take care of the problem.

Upgrading only libsp1, the dependencies don't take care of it.

> Do you really think this should be a release critical bug?

Yes, but if you disagree, I won't fight it.

> I'd be more inclined to change this if I had reports that there were
> other programs that need the old libsp1 ABI as well as programs that
> need the new one.

That's the crux of my argument: Users may have such programs that are
not in Debian, e.g. locally compiled or even locally written.

--
Lionel

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 23 Dec 2004 07:31:23 -0500
From: Neil Roeth <email address hidden>
To: Lionel Elie Mamane <email address hidden>, <email address hidden>
Subject: Bug#286945: libsp1: Changed ABI without soname change

On Dec 23, Lionel Elie Mamane (<email address hidden>) wrote:
 > Package: libsp1
 > Version: 1.3.4-1.2.1-42
 > Severity: grave
 >
 > Machine one:
 >
 > ii libsp1 1.3.4-1.2.1-28 Runtime library for James Clark's SP suite
 >
 > master@tofu:~$ readelf -s /usr/lib/libsp.so.1|grep __ti16OutputByteStream
 > 1203: 0020c888 8 OBJECT GLOBAL DEFAULT 20 __ti16OutputByteStream
 >
 > Machine two:
 >
 > ii libsp1 1.3.4-1.2.1-42 Runtime library for James Clark's SP suite
 >
 > lmamane@topaz:/usr/src/backports/pdns/pdns-2.9.16$ readelf -s /usr/lib/libsp.so.1|grep __ti16OutputByteStream
 >
 > This is an incompatible ABI change, and warrants a soname change. As a
 > result, jade doesn't work anymore on machine two, since it was linked
 > against an older version of libps1, that had the __ti16OutputByteStream
 > symbol.

Jade has had a dependency on libsp1 >= -30 since -30, so how did you get jade
-42 installed with libsp1 -28? You are correct that an ABI change should be
handled with a different soname, however: (1) the only package affected is
jade, which has dependencies to prevent this, (2) it will not affect anyone
upgrading from woody to sarge since -28 was in woody, and the newer versions
of jade will force an upgrade to a version of libsp1 >= -30, and (3) it's darn
close to the sarge release to be making a soname change that doesn't really
affect anyone who installs normally, i.e., in a way that the dependencies
would take care of the problem. Do you really think this should be a release
critical bug? I'd be more inclined to change this if I had reports that there
were other programs that need the old libsp1 ABI as well as programs that need
the new one.

--
Neil Roeth

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 23 Dec 2004 13:42:11 +0100
From: Lionel Elie Mamane <email address hidden>
To: Neil Roeth <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#286945: libsp1: Changed ABI without soname change

On Thu, Dec 23, 2004 at 07:31:23AM -0500, Neil Roeth wrote:
> On Dec 23, Lionel Elie Mamane (<email address hidden>) wrote:
>> Package: libsp1
>> Version: 1.3.4-1.2.1-42
>> Severity: grave

>> Machine one:
>>
>> ii libsp1 1.3.4-1.2.1-28 Runtime library for James Clark's SP suite

>> master@tofu:~$ readelf -s /usr/lib/libsp.so.1|grep __ti16OutputByteStream
>> 1203: 0020c888 8 OBJECT GLOBAL DEFAULT 20 __ti16OutputByteStream

>> Machine two:

>> ii libsp1 1.3.4-1.2.1-42 Runtime library for James Clark's SP suite

>> lmamane@topaz:/usr/src/backports/pdns/pdns-2.9.16$ readelf -s /usr/lib/libsp.so.1|grep __ti16OutputByteStream

>> This is an incompatible ABI change, and warrants a soname change. As a
>> result, jade doesn't work anymore on machine two, since it was linked
>> against an older version of libps1, that had the __ti16OutputByteStream
>> symbol.

> Jade has had a dependency on libsp1 >= -30 since -30, so how did you
> get jade -42 installed with libsp1 -28?

It is the other way round: jade 1.2.1-28 with libsp1 1.3.4-1.2.1-42.

> You are correct that an ABI change should be handled with a
> different soname, however: (1) the only package affected is jade,
> which has dependencies to prevent this,

The old jade doesn't have it; if you want to go the "but jade is the
only package depending on libsp1 anyway" route, you need the newer
libsp1 to conflict with the older jade, too.

And it then, it still breaks programs people have self-compiled, and I
don't think we should call this acceptable.

> (2) it will not affect anyone upgrading from woody to sarge since
> -28 was in woody, and the newer versions of jade will force an
> upgrade to a version of libsp1 >= -30,

It will affect them if they have locally compiled programs against
libsp1.

> and (3) it's darn close to the sarge release to be making a soname
> change

(That's another story altogether.)

> that doesn't really affect anyone who installs normally, i.e., in a
> way that the dependencies would take care of the problem.

Upgrading only libsp1, the dependencies don't take care of it.

> Do you really think this should be a release critical bug?

Yes, but if you disagree, I won't fight it.

> I'd be more inclined to change this if I had reports that there were
> other programs that need the old libsp1 ABI as well as programs that
> need the new one.

That's the crux of my argument: Users may have such programs that are
not in Debian, e.g. locally compiled or even locally written.

--
Lionel

Revision history for this message
In , Neil Roeth (neil-debian) wrote : Bug#286945: fixed in jade 1.2.1-43
Download full text (3.2 KiB)

Source: jade
Source-Version: 1.2.1-43

We believe that the bug you reported is fixed in the latest version of
jade, which is due to be installed in the Debian FTP archive:

jade_1.2.1-43.diff.gz
  to pool/main/j/jade/jade_1.2.1-43.diff.gz
jade_1.2.1-43.dsc
  to pool/main/j/jade/jade_1.2.1-43.dsc
jade_1.2.1-43_i386.deb
  to pool/main/j/jade/jade_1.2.1-43_i386.deb
libsp1-dev_1.3.4-1.2.1-43_i386.deb
  to pool/main/j/jade/libsp1-dev_1.3.4-1.2.1-43_i386.deb
libsp1_1.3.4-1.2.1-43_i386.deb
  to pool/main/j/jade/libsp1_1.3.4-1.2.1-43_i386.deb
sp_1.3.4-1.2.1-43_i386.deb
  to pool/main/j/jade/sp_1.3.4-1.2.1-43_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Neil Roeth <email address hidden> (supplier of updated jade package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed, 29 Dec 2004 07:12:29 -0500
Source: jade
Binary: jade libsp1 sp libsp1-dev
Architecture: source i386
Version: 1.2.1-43
Distribution: unstable
Urgency: high
Maintainer: Neil Roeth <email address hidden>
Changed-By: Neil Roeth <email address hidden>
Description:
 jade - James Clark's DSSSL Engine
 libsp1 - Runtime library for James Clark's SP suite
 libsp1-dev - James Clark's SP suite, developer support
 sp - James Clark's SGML parsing tools
Closes: 221735 270109 286945
Changes:
 jade (1.2.1-43) unstable; urgency=high
 .
   * RC bug fix: Make libsp1 conflict with jade earlier than 1.2.1-30 to
     avoid problem where old version of jade fails to run because of
     changes in libsp1. Better way to do this would be new soname, etc.,
     but that would be a drastic change to make so close to the sarge
     release (this situation has existed for almost two years with no prior
     report of problems). Other, non-Debian programs compiled locally
     against old version of libsp1 might have problems. Best solution for
     those is to convert to the OpenSP version of these programs, since
     that is the successor to this old, no longer updated suite of
     programs. (closes: #286945)
   * Use patch supplied by Andreas Jochens to allow compiling with g++ 3.4
     (closes: #221735, #270109)
Files:
 5e9723a16c3ad6845229895f26ae22cc 645 text optional jade_1.2.1-43.dsc
 ab80f2052199e308fa655a63d20f3905 365434 text optional jade_1.2.1-43.diff.gz
 ec9313a9342fdb2a09cac8f83ec2bc48 175078 text optional sp_1.3.4-1.2.1-43_i386.deb
 9984743694782f98b3022d56f6a04804 1394762 libs optional libsp1_1.3.4-1.2.1-43_i386.deb
 2478bd73b1f8a223b89f30d8c1cb2cdc 1706806 libdevel optional libsp1-dev_1.3.4-1.2.1-43_i386.deb
 3f37ee320e2f41da08700e51b1eada48 319556 text optional jade_1.2.1-43_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFB01lz6j+skPrutKkRAjw+AKDG1VvHCixeVQFq5erKBPQnh...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (3.4 KiB)

Message-Id: <email address hidden>
Date: Wed, 29 Dec 2004 22:02:12 -0500
From: Neil Roeth <email address hidden>
To: <email address hidden>
Subject: Bug#286945: fixed in jade 1.2.1-43

Source: jade
Source-Version: 1.2.1-43

We believe that the bug you reported is fixed in the latest version of
jade, which is due to be installed in the Debian FTP archive:

jade_1.2.1-43.diff.gz
  to pool/main/j/jade/jade_1.2.1-43.diff.gz
jade_1.2.1-43.dsc
  to pool/main/j/jade/jade_1.2.1-43.dsc
jade_1.2.1-43_i386.deb
  to pool/main/j/jade/jade_1.2.1-43_i386.deb
libsp1-dev_1.3.4-1.2.1-43_i386.deb
  to pool/main/j/jade/libsp1-dev_1.3.4-1.2.1-43_i386.deb
libsp1_1.3.4-1.2.1-43_i386.deb
  to pool/main/j/jade/libsp1_1.3.4-1.2.1-43_i386.deb
sp_1.3.4-1.2.1-43_i386.deb
  to pool/main/j/jade/sp_1.3.4-1.2.1-43_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Neil Roeth <email address hidden> (supplier of updated jade package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed, 29 Dec 2004 07:12:29 -0500
Source: jade
Binary: jade libsp1 sp libsp1-dev
Architecture: source i386
Version: 1.2.1-43
Distribution: unstable
Urgency: high
Maintainer: Neil Roeth <email address hidden>
Changed-By: Neil Roeth <email address hidden>
Description:
 jade - James Clark's DSSSL Engine
 libsp1 - Runtime library for James Clark's SP suite
 libsp1-dev - James Clark's SP suite, developer support
 sp - James Clark's SGML parsing tools
Closes: 221735 270109 286945
Changes:
 jade (1.2.1-43) unstable; urgency=high
 .
   * RC bug fix: Make libsp1 conflict with jade earlier than 1.2.1-30 to
     avoid problem where old version of jade fails to run because of
     changes in libsp1. Better way to do this would be new soname, etc.,
     but that would be a drastic change to make so close to the sarge
     release (this situation has existed for almost two years with no prior
     report of problems). Other, non-Debian programs compiled locally
     against old version of libsp1 might have problems. Best solution for
     those is to convert to the OpenSP version of these programs, since
     that is the successor to this old, no longer updated suite of
     programs. (closes: #286945)
   * Use patch supplied by Andreas Jochens to allow compiling with g++ 3.4
     (closes: #221735, #270109)
Files:
 5e9723a16c3ad6845229895f26ae22cc 645 text optional jade_1.2.1-43.dsc
 ab80f2052199e308fa655a63d20f3905 365434 text optional jade_1.2.1-43.diff.gz
 ec9313a9342fdb2a09cac8f83ec2bc48 175078 text optional sp_1.3.4-1.2.1-43_i386.deb
 9984743694782f98b3022d56f6a04804 1394762 libs optional libsp1_1.3.4-1.2.1-43_i386.deb
 2478bd73b1f8a223b89f30d8c1cb2cdc 1706806 libdevel optional libsp1-dev_1.3.4-1.2.1-43_i386...

Read more...

Revision history for this message
Matt Zimmerman (mdz) wrote :

      jade | 1.2.1-43 | http://archive.ubuntu.com hoary/main Packages

Bug Watch Updater (bug-watch-updater)
Changed in jade:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.