Welcome to the Pacman bug tracker. Please search the current bugs and feature requests before filing a new one! Use advanced search and select "Search in Comments".

* Please select the correct category and version.
* Write a descriptive summary, background info, and provide a reproducible test case whenever possible.

FS#34552 - pacman fails to upgrade, unmet dependencies

Attached to Project: Pacman
Opened by Sidney Kline (sidneyk) - Monday, 01 April 2013, 16:43 GMT
Last edited by Dave Reisner (falconindy) - Monday, 01 April 2013, 18:02 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version 4.1.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No


Summary and Info:
pacman fails to upgrade to 4.1.0-1 in testing, unmet dependencies with packagekit.

Steps to Reproduce:
Attempt to upgrade with sudo pacman -Syu. Suggests to upgrade pacman first to 4.1.0-1. Accepting to upgrade pacman fails with the following error:

resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: packagekit: requires pacman<4.1.0
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 01 April 2013, 18:02 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Not a pacman bug -- bother the maintainers of the respective packages.
Comment by Daniel Wallace (gtmanfred) - Monday, 01 April 2013, 16:47 GMT
my bad, thought it was package-query

Comment by Lucas Cano (canolucas) - Monday, 01 April 2013, 17:50 GMT
@Daniel Wallace, both of them require pacman < 4.1

i get:

:: package-query: requires pacman<4.1
:: packagekit: requires pacman<4.1.0

i'm using the i686 package set
Comment by Dave Reisner (falconindy) - Monday, 01 April 2013, 18:02 GMT
This is a problem with the specific packages which rely on an explicit version of pacman. It is not a pacman bug.
Comment by Lucas Cano (canolucas) - Monday, 01 April 2013, 18:13 GMT
@falconindy, With all due respect sir (:)), this is still an issue.

Can this bug be moved to the arch bugs? Or a new one needs to be filled?

Thanks for the moderation.
Comment by Dave Reisner (falconindy) - Monday, 01 April 2013, 18:17 GMT
Open bugs against *specific* packages *in the official repos* (that is, not from the AUR) which are affected by this.
Comment by Pablo Lezaeta (Jristz) - Monday, 01 April 2013, 18:24 GMT
fill the same bug but againt packagekit (this one on the repos)

package-query is on AUR, then e-mail the maintainer