The only change to the symbols in 2.26.1 is one dropped internal symbol
(_bfd_*) and the soname change itself. It's appropriate to restore
binary compatibility by providing both -2.26.1- and -2.26- names on
disk.
I've uploaded this to yakkety as 2.26.1-1ubuntu2 and will do the same
for xenial-updates - we definitely don't want to do an soname transition
in SRU.
** Changed in: binutils (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Also affects: binutils (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1603137
Title:
libbfd changed name without transition
Status in binutils package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in binutils source package in Xenial:
New
Status in linux source package in Xenial:
Invalid
Bug description:
the latest binutils update in xenial to 2.26.1-1ubuntu1~16.04 changed the
name of the libbfd library from: libbfd-2.26-system.so to
libbfd-2.26.1-system.so
This apparently happened without transitioning all dependencies.
For example it broke the perf tool from the linux-tools-common package as it
is still linked against the old libbfd name.
To reproduce run "perf" with linux >= 4.4.0-24.43 and binutils
2.26.1-1ubuntu1~16.04 and you get an cannot open libbfd-2.26-system.so
error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1603137/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
