FS#55756 - [gcc][gcc-libs-multilib] should not be co-installable

Attached to Project: Community Packages
Opened by Oliver Mangold (omangold) - Tuesday, 26 September 2017, 16:25 GMT
Last edited by Balló György (City-busz) - Wednesday, 24 January 2018, 05:54 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The gcc package has a dependency on gcc-libs=7.2.0-3 (which is normally provided by the package with that name):

Name : gcc
Version : 7.2.0-3
Depends On : gcc-libs=7.2.0-3 binutils>=2.28 libmpc

But when one wants to install gcc-libs-multilib instead of gcc-libs (which of course conflict), it doesn't work, because the version doesn't match:

Name : gcc-libs-multilib
Version : 7.2.0-1
Provides : gcc-libs=7.2.0-1
Conflicts With : gcc-libs

Additional info:
* package version(s)
gcc 7.2.0-3
gcc-libs 7.2.0-3
gcc-libs-multilib 7.2.0-1

Steps to reproduce:
try to install gcc and gcc-libs-multilib via pacman
This task depends upon

Closed by  Balló György (City-busz)
Wednesday, 24 January 2018, 05:54 GMT
Reason for closing:  Fixed
Comment by Allan McRae (Allan) - Tuesday, 26 September 2017, 23:07 GMT
Reopened - there needs to be a fix to the gcc-multilib set of packages to prevent situations like this.
Comment by Eli Schwartz (eschwartz) - Wednesday, 27 September 2017, 00:05 GMT
Hmm, true. Just because people really should read the multilib page and install multilib-devel doesn't mean the package dependencies aren't broken. :o


Should gcc conflict with gcc-libs-multilib then -- IIRC pacman will reject a package which provides a conflicting pkgname (unless the package itself is the one which provides and conflicts X), so you cannot have gcc-libs-multilib conflict with gcc or it will reject gcc-multilib as well.
Comment by Oliver Mangold (omangold) - Wednesday, 27 September 2017, 06:12 GMT
I agree that the dependency system should help with detecting this issue better. By the way it is not clear to me which info on multilib I should have read to avoid the mistake. This?

https://wiki.archlinux.org/index.php/Multilib

Doesn't say anything about it. Also I guess people are considering multilib to be something simple enough to not have to read any docs about it.
Comment by Eli Schwartz (eschwartz) - Wednesday, 27 September 2017, 15:33 GMT Comment by Balló György (City-busz) - Wednesday, 24 January 2018, 05:54 GMT

Loading...