It doesnt seem alpm is implemented, dont know if that is ever gonna happen.
]]>And your contribution to the problem's solution is what, ANOKNUSA?
Every time there's a Pacman upgrade, the forums balloon with inane complaints about third-party wrappers blocking upgrades, and this somehow being an Arch problem. The answer is always the same: Either wait for the third party to update, or don't use such packages. And anyone using [testing] is expected to take full responsibility for any issues they run into, and understand how the dependency chain works; that's just how it is. If one isn't prepared to accept that, one shouldn't use [testing], as was stated in the second post in this thread.
Useful information: That's my contribution. Though in retrospect I should have posted it the first time around.
]]>First i call
sudo pacman -S packagekit
Answer "NO" on question about upgrading pacman first. Then system upgrade packagekit and pacman.
sudo pacman -Syu
works now ok.
]]>Absolutely none of this is a problem with Pacman. Period.
EDIT: Packagekit isn't even a GNOME dependency, so there's really no reason to even post this on these forums.
I am now versed on the fact that the devs say this is not a pacman problem, but rather a packagekit problem, as I filled the original bug report on it against pacman. But it was, originally, a definite problem with upgrading to the latest pacman for anyone that had this installed. Fortunately, the packagekit maintainer was fairly quick to fix the problem of packagekit depending on an older version of pacman. I was merely pointing out and confirming to the person that I replied to that the new version is definitely on at least some repo or mirror somewhere because I was able to install it twice so that the poster might be encouraged to try again and doublecheck his commands or choose a different mirror or something. Sorry, if I offended you.
]]>EDIT: Packagekit isn't even a GNOME dependency, so there's really no reason to even post this on these forums.
]]>I tried to update to packagekit 0.7.6-6 64 bit so I could fix this pacman issue but apparently it's not in the repos anymore? Can't even download it directly. Is there an issue with it?
Thanks!
Just checked it on the packages page, it shows up for me. Also, just did a 'sudo pacman -S packagekit' and reinstalled it.
]]>Thanks!
]]>The above bug was closed as "not a pacman bug". Proper report has been filled for the package that depends on pacman < 4.1.0 (PackageKit):
https://bugs.archlinux.org/task/34557
NOTE
The mantainer of package-query has been contacted by email, as this package belongs to the AUR.
Sorry about that. That was the first bug report I've done and I guess I thought about it backwards. I see that the new packagekit is in the repos now. I'll try again in the morning when I get back to my machine. Thanks.
[EDIT] Updated to new packagekit and new pacman successfully.
]]>NOTE
The mantainer of package-query has been contacted by email, as this package belongs to the AUR.
package-query-git has already been updated for the new 4.1 API/ABI. I think that the stable version will follow as soon as pacman 4.1 hits the stable repo and leavers the testing stage.
]]>https://bugs.archlinux.org/task/34557
NOTE
The mantainer of package-query has been contacted by email, as this package belongs to the AUR.
I can confirm the same issue here.
resolving dependencies... looking for inter-conflicts... error: failed to prepare transaction (could not satisfy dependencies) :: packagekit: requires pacman<4.1.0
[EDIT] Bug report filed.
For the people that ended up here and want to know more about this issue, here is the link:
]]>