Arch Linux

Please read this before reporting a bug:

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#58459 - [js52] manual intervention needed for /usr/lib/

Attached to Project: Arch Linux
Opened by nl6720 (nl6720) - Friday, 04 May 2018, 17:53 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 04 May 2018, 21:30 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 13
Private No


When upgrading extra/js52 from 52.7.3-1 to 52.7.3-2, I get this error:

error: failed to commit transaction (conflicting files)
js52: /usr/lib/ exists in filesystem
Errors occurred, no packages were upgraded.

pacman -Qo /usr/lib/
error: No package owns /usr/lib/

/usr/lib/ is part of the js52 52.7.3-2 package, but not of js52 52.7.3-1 .
Most likely the symlink was created by "ldconfig.service".

Additional info:
* package version(s)
* config and/or log files etc.
js52 52.7.3-2

Steps to reproduce:
pacman -Syu

This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Friday, 04 May 2018, 21:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  See news item.
Comment by Herman Yanush (Sheogorath) - Friday, 04 May 2018, 18:05 GMT
I've just removed it:
sudo mv /usr/lib/ /usr/lib/
Comment by nl6720 (nl6720) - Friday, 04 May 2018, 18:16 GMT
While removing the file is a solution, I don't think I should be expected to do that. It's the person who packaged js52 that screwed up, not me, so he should fix it not me.
Comment by Eli Schwartz (eschwartz) - Friday, 04 May 2018, 18:25 GMT
How do you expect it to be fixed, then? The package deadlocks on a file conflict long before it can delete the symlink for you in a pre-upgrade script.

The only real solution is to create a news post telling people they need to delete it manually first. Which you already know to do.
Comment by Noah (Euphoria42) - Friday, 04 May 2018, 18:38 GMT
I fixed this by renaming /usr/lib/ to /usr/lib/ and proceeding to upgrade. Seeing as this package is required by gnome, would a news post be in order to notify needing manual intervention? Or would we just hope people find there way to the pacman page on the arch wiki?
Comment by nl6720 (nl6720) - Friday, 04 May 2018, 18:39 GMT
A news post would be a proper solution.

I think there was one time this kind of situation was solved without manual intervention, but maybe I'm mistaken...
Comment by Eli Schwartz (eschwartz) - Friday, 04 May 2018, 18:48 GMT
One time, upstream released a soname upgrade that coincided with the symlink fix. So manual intervention was not needed. This is not the case here.