From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-ext4@vger.kernel.org
Subject: libcom_err DSO version bump needed for 1.42?
Date: Wed, 15 Aug 2012 17:48:12 -0400 [thread overview]
Message-ID: <k0h5eu$f6u$1@ger.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
Hi,
I noticed when trying to upgrade my e2fsprogs RPM set from a 1.41.12ish
release to a 1.42.3ish release only e2fsprogs and e2fsprogs-libs got
upgraded and libcom_err didn't get upgraded despite there being ABI
differences between 1.41.12 and 1.42.3. This results in the following
type of error:
# e2fsck
e2fsck: symbol lookup error: e2fsck: undefined symbol: set_com_err_gettext
# mke2fs
mke2fs: symbol lookup error: mke2fs: undefined symbol: set_com_err_gettext
This appears to be due to the addition of set_com_err_gettext() (in
4259052093da329907e255b11bf3e799872828c7) during the 1.42 development
cycle.
Since this addition introduces an ABI incompatibility in libcom_err,
isn't the process supposed to be to increase the SO's version so that
the tools find the proper version of the library and also so that it
gets upgraded accordingly by RPM with it's autoprovides/requires bits?
Cheers,
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next reply other threads:[~2012-08-15 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 21:48 Brian J. Murrell [this message]
2012-08-16 1:47 ` libcom_err DSO version bump needed for 1.42? Theodore Ts'o
2012-08-16 12:01 ` Brian J. Murrell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='k0h5eu$f6u$1@ger.gmane.org' \
--to=brian@interlinx.bc.ca \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).