Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#64588 - [lockdev] No package owns /usr/lib/liblockdev.so.1
Attached to Project:
Community Packages
Opened by nl6720 (nl6720) - Wednesday, 20 November 2019, 13:04 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:01 GMT
Opened by nl6720 (nl6720) - Wednesday, 20 November 2019, 13:04 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:01 GMT
|
DetailsDescription:
After installing lockdev, there is /usr/lib/liblockdev.so.1 that is not tracked by pacman. The /usr/lib/liblockdev.so.1 -> liblockdev.so.1.0.3 symlink gets created by ldconfig. Please add the symlink to the package. Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any lockdev 1.0.3_1.6-5 Steps to reproduce: pacman -Qo /usr/lib/liblockdev.so.1 |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:01 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/lockdev/issues/1
Saturday, 25 November 2023, 20:01 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/lockdev/issues/1
Comment by Buggy McBugFace (bugbot) -
Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.