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#42601 - [pacman] pacman --noconfirm does not handle multiple package providers very well.

Attached to Project: Pacman
Opened by Yichao Yu (yuyichao) - Wednesday, 29 October 2014, 17:59 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 29 October 2014, 23:36 GMT
Task Type Bug Report
Category Packages: Core
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:
Pacman does not install the correct packages in the following situation.

a1: provides a; conflicts a
a2: provides a; conflicts a
b1: provides b; conflicts b; depends a1
b2: provides b; conflicts b; depends a2

When running

$ pacman --noconfirm -S a1 b

Depend on the order appears in the database. pacman may install b2 a2 instead of b1 a1 if b2 is in from of b1. The same behavior can be seen when a1/2, b1/2's are the same package with different version requirements.

This situation can be caused by compiling packages in chroot that are linked to two versions of a library with different ABIs.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Loading...