Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 674136 - dev-qt/qtwebengine depends on app-arch/snappy
Summary: dev-qt/qtwebengine depends on app-arch/snappy
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2018-12-30 21:24 UTC by Mark Locascio
Modified: 2018-12-30 22:15 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

emerge --info app-arch/snappy (snappyinfo.txt,6.02 KB, text/plain)
2018-12-30 21:24 UTC, Mark Locascio

Note You need to log in before you can comment on or make changes to this bug.
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/
 *  - /usr/lib64/
 *      used by /usr/lib64/ (preserved)
 *      used by /usr/lib64/ (preserved)

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

Furthermore, 'equery belongs /usr/lib64/' and 'equery belongs /usr/lib64/' 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, 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/ ->
>>> /usr/lib64/ ->
>>> /usr/lib64/
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.