Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#49934 - Files flagged as conflicting though owned by llvm37-libs 3.7.1-1

Attached to Project: Pacman
Opened by Jack LaSota (Jack_LaSota) - Monday, 04 July 2016, 03:15 GMT
Last edited by Allan McRae (Allan) - Monday, 04 July 2016, 03:48 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture arm
Severity Low
Priority Normal
Reported Version 5.0.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
Installing xorg-server, /usr/lib/LLVMgold.so and some other files are listed as conflicting, but are owned by another pacman package.

Steps to Reproduce:
Ran sudo pacman -S xorg-server
When prompted to chose from 5 available libgl providers, chose mesa-libgl (the default). When prompted to chose from 2 available xf86-input-driver providers, chose xf86-input-libinput.
It complained of conflicting files:
/usr/lib/LLVMgold.so
/usr/lib/bfd-plugins/LLVMgold.so
/usr/lib/libLLVM.so
/usr/lib/libLTO.so

Ran pacman -Qo /usr/lib/LLVMgold.so
It said "/usr/lib/LLVMgold.so is owned by llvm37-libs 3.7.1-1"

This is on an almost-fresh Arch Linux ARM, installed on a Raspberry Pi 3 B as directed here: https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-3
A complete pacman.log for this machine is attached. I have not installed anything using something besides pacman.
   pacman.log (6.7 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Monday, 04 July 2016, 03:48 GMT
Reason for closing:  Not a bug
Comment by Allan McRae (Allan) - Monday, 04 July 2016, 03:30 GMT
You have files conflicting (two packages have the same file). Pacman reports the conflict. What is the issue here?
Comment by Jack LaSota (Jack_LaSota) - Monday, 04 July 2016, 03:46 GMT
This says that for it to complain in that case instead of just sharing the files between the packages is a bug:
https://wiki.archlinux.org/index.php/pacman#.22Failed_to_commit_transaction_.28conflicting_files.29.22_error
"The problem is usually trivial to solve. A safe way is to first check if another package owns the file (pacman -Qo /path/to/file). If the file is owned by another package, file a bug report."
Comment by Allan McRae (Allan) - Monday, 04 July 2016, 03:48 GMT
Ah - file a bug report for your distribution.
Comment by Jack LaSota (Jack_LaSota) - Monday, 04 July 2016, 04:00 GMT
What makes you think this is an Arch Linux ARM bug and not a Pacman bug? If I'm going to file a bug report with them, I have to have some justification so they don't close it as upstream because at face value this looks like a Pacman bug.
Comment by Allan McRae (Allan) - Monday, 04 July 2016, 04:16 GMT
Having /usr/lib/libLLVM.so in xf86-input-libinput is a bug at their end.
Comment by Jack LaSota (Jack_LaSota) - Monday, 04 July 2016, 04:35 GMT
Shouldn't a package manager work the same whether files are included in packages for good reasons or bad ones? Or is their specification of xf86-input-libinput somehow not just wrong, but invalid?
Comment by Allan McRae (Allan) - Monday, 04 July 2016, 04:48 GMT
The package manager does work the same. It has seen two packages want to own a file. That is not allowed, so it reported a conflict.
Comment by Jack LaSota (Jack_LaSota) - Monday, 04 July 2016, 05:02 GMT
Oh. Got it, thanks.

Loading...