Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 674136

Summary: dev-qt/qtwebengine depends on app-arch/snappy
Product: Gentoo Linux Reporter: Mark Locascio <malocascio>
Component: Current packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED CANTFIX    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info app-arch/snappy

Description Mark Locascio 2018-12-30 21:24:05 UTC
Created attachment 559054 [details]
emerge --info app-arch/snappy

I recently started getting this message after emerge:

!!! existing preserved libs:
>>> package: app-arch/snappy-1.1.7
 *  - /usr/lib64/libsnappy.so.1
 *  - /usr/lib64/libsnappy.so.1.1.7
 *      used by /usr/lib64/libQt5WebEngineCore.so.5 (preserved)
 *      used by /usr/lib64/libQt5WebEngineCore.so.5.11.3 (preserved)

I don't recall ever installing snappy, so I'm not sure why this is a thing, but sure enough, /usr/lib64/libsnappy.so.1 and /usr/lib64/libsnappy.so.1.1.7 both exist.

Furthermore, 'equery belongs /usr/lib64/libsnappy.so.1' and 'equery belongs /usr/lib64/libsnappy.so.1.1.7' both don't find any packages.

So, I emerged app-arch/snappy, then removed it. Both processes looked fine, but those two files remain. No package collisions were reported on merge, and portage reports those two files, in addition to libsnappy.so, which DOES seem to be properly removed.

>>> Installing (1 of 1) app-arch/snappy-1.1.7::gentoo
 * checking 15 files for package collisions
>>> Merging app-arch/snappy-1.1.7 to /
--- /usr/
--- /usr/lib64/
>>> /usr/lib64/libsnappy.so.1 -> libsnappy.so.1.1.7
>>> /usr/lib64/libsnappy.so -> libsnappy.so.1
...
>>> /usr/lib64/libsnappy.so.1.1.7
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2018-12-30 22:15:11 UTC
dev-qt/qtwebengine properly depends on app-arch/snappy, so perhaps the problem will go away when you uninstall dev-qt/qtwebengine. In any case, there is no bug here. Please use our forums, mailing lists and IRC channels for support next time.