FS#67861 - [tigervnc] fails to update - /usr/sbin exists in filesystem (owned by filesystem)

Attached to Project: Community Packages
Opened by David C. Rankin (drankinatty) - Wednesday, 09 September 2020, 23:28 GMT
Last edited by freswa (frederik) - Thursday, 10 September 2020, 13:01 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 19
Private No

Details

Description:

Attempting system update (pacman -Syu) fails due to tigervnc. pacman output is:

(7/7) checking for file conflicts [######################################] 100%
error: failed to commit transaction (conflicting files)
tigervnc: /usr/sbin exists in filesystem (owned by filesystem)
Errors occurred, no packages were upgraded.

There is no note at archlinux.org on manual intervention needed.

Additional info:
* package version(s) -- tigervnc-1.11.0-1-x86_64

Steps to reproduce:

Have earlier version of tigervnc installed, and attempt system update.
This task depends upon

Closed by  freswa (frederik)
Thursday, 10 September 2020, 13:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  tigervnc-1.11.0-2
Comment by Valentín Casanova (Genstar) - Wednesday, 09 September 2020, 23:40 GMT
An earlier version installed is not needed to duplicate this bug. I've removed the package and installed it again. Still the same.

/usr/sbin is owned by the Arch Linux base filesystem, so I don't know why tigervnc tries to create it's own /usr/sbin.
Comment by Doug Newgard (Scimmia) - Wednesday, 09 September 2020, 23:40 GMT
Obviously not even test-installed. Sergej?
Comment by loqs (loqs) - Thursday, 10 September 2020, 00:00 GMT
@drankinatty does the package produced by rebuilding the package with the attached PKGBUILD.diff work?
Comment by Hexhu (hexhu) - Thursday, 10 September 2020, 00:20 GMT
Can confirm. `pacman -Sy tigervnc` consistently fails with `tigervnc: /usr/sbin exists in filesystem`
Comment by Hexhu (hexhu) - Thursday, 10 September 2020, 00:41 GMT
@loqs your patch works and tigervnc v1.11.0 gets installed. Thanks!
Comment by Eli Schwartz (eschwartz) - Thursday, 10 September 2020, 01:31 GMT
In upstream commit https://github.com/TigerVNC/tigervnc/commit/1af1cfdf8709dd1a5574efa19fb4f0e68a98021e#diff-5257b0445ad1f985acf062f6589461df a new file got added, and installed to CMAKE_INSTALL_SBINDIR, which defaults to "sbin" and on Arch must be "bin".

The package doesn't even install during the post-build lint checks and should therefore never have been released...
Comment by Sergej Pupykin (sergej) - Thursday, 10 September 2020, 07:08 GMT
should be fixed
Comment by Pascal Ernster (hardfalcon) - Thursday, 10 September 2020, 07:11 GMT
tigervnc-1.11.0-2-x86_64 works for me.
Comment by Levente Polyak (anthraxx) - Thursday, 10 September 2020, 09:23 GMT
Errors like this must have been visible during extra-x86_64-build post step.
Please take the time to read log output, packages are automatically installed as a test step into the chroot, which must have failed as well.

Loading...