Bug 489104 – net-analyzer/wireshark-1.11.0 links against old installed libraries on upgrade

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Kalin KOZHUHAROV 2013-10-23 07:25:57 UTC]

I updated to net-analyzer/wireshark-1.11.0 on a few different systems and they all ended with old libraries linked. Re-emerging it solved the problem.

...
<<<          dir /usr/share/doc/wireshark-1.10.2
<<<          dir /usr/lib/wireshark/plugins/1.10.2
>>> Regenerating /etc/ld.so.cache...
>>> Original instance of package unmerged safely.
 * NOTE: To run wireshark as normal user you have to add yourself to
 * the wireshark group. This security measure ensures that only trusted
 * users are allowed to sniff your traffic.
>>> net-analyzer/wireshark-1.11.0 merged.
>>> Regenerating /etc/ld.so.cache...

 * Messages for package net-analyzer/wireshark-1.11.0:

 * NOTE: To run wireshark as normal user you have to add yourself to
 * the wireshark group. This security measure ensures that only trusted
 * users are allowed to sniff your traffic.
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

!!! existing preserved libs:
>>> package: net-analyzer/wireshark-1.11.0
 *  - /usr/lib/libwiretap.so.3
 *  - /usr/lib/libwiretap.so.3.0.2
 *      used by /usr/lib/libwireshark.so.0.0.0 (net-analyzer/wireshark-1.11.0)
 *  - /usr/lib/libwsutil.so.3
 *  - /usr/lib/libwsutil.so.3.0.0
Use emerge @preserved-rebuild to rebuild packages using these libraries

Probably related bugs 391251, 255642, 349782

Hmm, do we need a tracker bug "Packages linking to old libraries on upgrade"?

[Comment 1 Jeroen Roovers (RETIRED) 2013-10-24 15:09:58 UTC]

Created attachment 361796 [details, diff]
wireshark-1.11.0-oldlibs.patch

Could you please test this patch:

1a) Either wait an hour or so and re-sync the portage tree (I added epatch_user
    to the ebuilds) and save this patch in
    </etc/portage/patches/net-analyzer/wireshark-1.11.0>.
1b) Apply the attached patch yourself in the ebuild.
2) Downgrade to net-analyzer/wireshark-1.10.2
3) Again upgrade to net-analyzer/wireshark-1.11.0

[Comment 2 Kalin KOZHUHAROV 2013-10-24 15:54:24 UTC]

Hmm, I just tried, saw the patch being applied in epatch_user, but got the same final result (i.e. linked to the old libraries it seems)... or ...

Actually looking at that output, I start wondering if it is not a bug in portage. How can I make sure that those libraries are from the old package?
Because:
...
!!! existing preserved libs:
>>> package: net-analyzer/wireshark-1.11.0
 *  - /usr/lib64/libwsutil.so.3
 *  - /usr/lib64/libwsutil.so.3.0.0
 *  - /usr/lib64/libwiretap.so.3
 *  - /usr/lib64/libwiretap.so.3.0.2
 *      used by /usr/lib64/libwireshark.so.0.0.0 (net-analyzer/wireshark-1.11.0)
Use emerge @preserved-rebuild to rebuild packages using these libraries
$ equery b  /usr/lib64/libwsutil.so.3.0.0 
 * Searching for /usr/lib64/libwsutil.so.3.0.0 ... 
net-analyzer/wireshark-1.11.0 (/usr/lib64/libwsutil.so.3.0.0)
$ equery b  /usr/lib64/libwiretap.so.3.0.2
 * Searching for /usr/lib64/libwiretap.so.3.0.2 ... 
net-analyzer/wireshark-1.11.0 (/usr/lib64/libwiretap.so.3.0.2)
$ equery k wireshark
* Checking net-analyzer/wireshark-1.11.0 ...
   1006 out of 1006 files passed

So it seems like portage is mistakingly thinking those are preserved libraries?

[Comment 3 Jeroen Roovers (RETIRED) 2013-10-24 16:12:10 UTC]

(In reply to Kalin KOZHUHAROV from comment #2)
> Hmm, I just tried, saw the patch being applied in epatch_user, but got the
> same final result (i.e. linked to the old libraries it seems)... or ...

Please attach the entire 1.11.0 build log to this bug report.

> How can I make sure that those libraries are from the old package?
> Because:

The preserved libraries are "owned" by the new version of the installed package.

[Comment 4 Kalin KOZHUHAROV 2013-10-24 17:43:40 UTC]

Sorry, it was me being sloppy/tired :-|

I emerged it a few times to realize I had the patch in the wrong directory and it wasn't applied. I moved it and repeated the test 1.10.2 -> 1.11.0 and all is fine now.

Not sure if this is to go upstream or not, but may be it is not Gentoo specific.
Thanks for the quick fix!

[Comment 5 Jeroen Roovers (RETIRED) 2013-10-25 13:33:26 UTC]

(In reply to Kalin KOZHUHAROV from comment #4)
> Thanks for the quick fix!

Thank you for testing. The patch is in the tree with 1.11.0-r1.