Arch Linux

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!
Tasklist

FS#38108 - gcc 4.8.2-6 in testing has conflicting file /usr/lib/libiberty.a owned by package binutils-multilib

Attached to Project: Arch Linux
Opened by Mirco Tischler (mirco) - Wednesday, 11 December 2013, 22:16 GMT
Last edited by Allan McRae (Allan) - Thursday, 12 December 2013, 00:04 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Additional info:
* gcc 4.8.2-6 and binutils-multilib 2.23.2-3
Steps to reproduce:

# pacman -Syu
...
Packages (3):

Name Old Version New Version Net Change

testing/gcc 4.8.2-5 4.8.2-6 0,95 MiB
testing/gcc-fortran 4.8.2-5 4.8.2-6 0,04 MiB
testing/gcc-libs 4.8.2-5 4.8.2-6 0,05 MiB

Total Installed Size: 91,07 MiB
Net Upgrade Size: 1,04 MiB

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

# pacman -Qo /usr/lib/libiberty.a
/usr/lib/libiberty.a is owned by binutils-multilib 2.23.2-3
This task depends upon

Closed by  Allan McRae (Allan)
Thursday, 12 December 2013, 00:04 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Wednesday, 11 December 2013, 22:27 GMT
You need to enable [multilib-testing] if you enable [testing].
Comment by patrick (potomac) - Wednesday, 11 December 2013, 22:30 GMT
I think it's normal, if you have multilib packages then you should use "gcc-multilib" package instead of the normal version of "gcc" package

https://wiki.archlinux.org/index.php/Arch64_FAQ#Multilib_repository
Comment by Mirco Tischler (mirco) - Wednesday, 11 December 2013, 23:02 GMT
Alright, I did enable [multilib-testing] and install gcc-multilib and the conflict is gone now. But that's because gcc-multilib is still at 4.8.2-5 for me and https://www.archlinux.org/packages/multilib-testing/x86_64/gcc-multilib/ shows gcc-multilib 4.8.2-6 is owning /usr/lib/libiberty.a as well, so I expect the conflict again when 4.8.2-6 hits my mirror of [multilib-testing].

Thanks
Comment by Mirco Tischler (mirco) - Wednesday, 11 December 2013, 23:04 GMT
It looks like binutils and binutils-multilib 2.24-1 from the testing repos don't own libiberty.a anymore so the conflict will resolve itself once these packages hit my mirrors. Maybe these dependencies should be made more explicit?

Loading...