FS#52564 - [glm] Update fails because of conflicting files when updating from vrtsion 0.9.8.3-1.

Attached to Project: Community Packages
Opened by Andreas (G33KatWork) - Monday, 16 January 2017, 03:21 GMT
Last edited by Antonio Rojas (arojas) - Monday, 16 January 2017, 08:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:
Update fails because of conflicting files when updating from vrtsion 0.9.8.3-1.

Error output:
error: failed to commit transaction (conflicting files)
glm: /usr/lib64 exists in filesystem
glm: /usr/lib64/cmake/glm/glmConfig.cmake exists in filesystem
glm: /usr/lib64/cmake/glm/glmConfigVersion.cmake exists in filesystem
glm: /usr/lib64/cmake/glm/glmTargets.cmake exists in filesystem
glm: /usr/lib64/pkgconfig/glm.pc exists in filesystem
Errors occurred, no packages were upgraded.

Steps to reproduce:
> pacman -Sy glm
This task depends upon

Closed by  Antonio Rojas (arojas)
Monday, 16 January 2017, 08:11 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#52563 
Comment by Christoph Haag (haagch) - Monday, 16 January 2017, 07:15 GMT
You shouldn't use pacman -Sy glm, rather pacman -Syu; pacman -S glm

Anyway, the problem is that glm installs cmake files in /usr/lib64. /usr/lib64 should be a symlink to /usr/lib, if it should exist at all.

There's been a cmake problem now and then that it installed various files into /usr/lib64 and cmake -DCMAKE_INSTALL_LIBDIR=lib did help. I just tried it and it installs the cmake files in /usr/lib, but then I never really had that problem with cmake in the first place.
Comment by Antoine (saveman71) - Monday, 16 January 2017, 07:19 GMT
I had the problem with pacman -Syu as well fyi. I think what Andreas meant is that it's reproducible with pacman -S glm

I did pacaur -Syu --ignore glm, then pacaur -Syu and I still have the problem.

Should we wait for a package update, or is there anything we can do in the meantime?
Comment by Neros (Neros) - Monday, 16 January 2017, 07:34 GMT
I have the exact same issue.

I think we can say it's confirmed.
Comment by Kevin (xhavok87) - Monday, 16 January 2017, 08:03 GMT
Also running into the same issue.

resolving dependencies...
looking for conflicting packages...

Packages (1) glm-0.9.8.3-3

Total Installed Size: 12.19 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
glm: /usr/lib64 exists in filesystem
Errors occurred, no packages were upgraded.

Loading...