You are not logged in.
sudo pacman -Syu
:: Synchronizing package databases...
testing is up to date
core is up to date
extra 1806.5 KiB 775K/s 00:02 [----------------------] 100%
community-testing is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: packagekit: requires pacman<4.2.0
Last edited by Dmitrii (2014-12-19 23:46:45)
Offline
"Works" for me on my 32-bit Arch with [testing] repos enabled. pacman automatically got downgraded back to 4.1.2-7:
$ sudo pacman -S packagekit
resolving dependencies...
looking for conflicting packages...
Package (2) Old Version New Version Net Change Download Size
core/pacman 4.2.0-1 4.1.2-7 -0.53 MiB
community/packagekit 0.7.6-12 6.90 MiB 0.87 MiB
Total Download Size: 0.87 MiB
Total Installed Size: 10.60 MiB
Net Upgrade Size: 6.37 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages ...
packagekit-0.7.6-12-i686 894.8 KiB 1916K/s 00:00 [###################################] 100%
(2/2) checking keys in keyring [###################################] 100%
(2/2) checking package integrity [###################################] 100%
(2/2) loading package files [###################################] 100%
(2/2) checking for file conflicts [###################################] 100%
(2/2) checking available disk space [###################################] 100%
(1/2) downgrading pacman [###################################] 100%
(2/2) installing packagekit [###################################] 100%
Optional dependencies for packagekit
networkmanager
It has been flagged out-of-date for almost exactly a year: https://www.archlinux.org/packages/comm … ackagekit/ :-)
Offline
I am getting same exact thing as OP. On both my computers.
Offline
On my computer, it just downgraded pacman, as kerol has shown in his post above.
Offline
sudo pacman -Syu
"Works" for me on my 32-bit Arch with [testing] repos enabled. pacman automatically got downgraded back to 4.1.2-7:
$ sudo pacman -S packagekit
OP is trying to update his system, not install packagekit.
Obviously you are not going to be able to update to pacman4.2 while you have packages installed that depend on pacman4.1. Either uninstall packagekit or wait for an updated version that depends on pacman4.2.
Offline
Workaround
pacman -R python-packagekit packagekit
Offline
Why does this come up every single time pacman has an update? Obviously if packagekit requires pacman < 4.2, you won't be able to install pacman 4.2 while packagekit is installed. Not rocket science.
Edit, ok, I was thinking of package-query, which causes problems every time.
Last edited by Scimmia (2014-12-19 23:27:49)
Offline
No workaround on my part yet. Removed both and still a no go.But I'm just going to uncomment Testing for now and downgrade. That should be the safer and better route for I myself.
Offline
It's marked as SOLVED.. but I wonder, where is the solution?
Offline
Solution is to either wait for a new version of packagekit to appear before upgrading or uninstall packagekit and upgrade without it.
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
Solution is to either wait for a new version of packagekit to appear before upgrading or uninstall packagekit and upgrade without it.
Thanks a lot.
What I did and worked for me is to remove yaourt and package-query. After that Syu that will automatically install latest pacman. Now Syu gonna work but I lost yaourt for now..
Offline
fsckd wrote:Solution is to either wait for a new version of packagekit to appear before upgrading or uninstall packagekit and upgrade without it.
Thanks a lot.
What I did and worked for me is to remove yaourt and package-query. After that Syu that will automatically install latest pacman. Now Syu gonna work but I lost yaourt for now..
Just run pacman-db-upgrade and then pacman -S yaourt package-query.
Last edited by WinterSoldier53 (2014-12-21 23:04:59)
Offline
Why is this marked as solved? It is far from solved
Last edited by gps1539 (2014-12-23 05:28:33)
Offline
Offline
A fix/workaround (you decide) for me was to uninstall yaourt and packagekit, then run pacman -Syuu to upgrade
As an alternative aur helper I installed pacaur, which is working well so far.
Offline
Solution is to either wait for a new version of packagekit to appear before upgrading or uninstall packagekit and upgrade without it.
per the link in jasonwryan's post, that may be a very long wait.
Offline
A fix/workaround (you decide) for me was to uninstall yaourt and packagekit, then run pacman -Syuu to upgrade
As an alternative aur helper I installed pacaur, which is working well so far.
You're making the same mistake I made earlier in this thread. Packagekit has nothing to do with yaourt, that's package-query.
Offline
Why is this not in the testing area? The 4.2.0 pacman is still in testing. No wonder there are conflicts.
Offline
Why is this not in the testing area? The 4.2.0 pacman is still in testing. No wonder there are conflicts.
Apparently the moderators are collectively overindulging in holiday cheer. Nice catch.
Moving to Testing.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Awebb wrote:Why is this not in the testing area? The 4.2.0 pacman is still in testing. No wonder there are conflicts.
Apparently the moderators are collectively overindulging in holiday cheer. Nice catch.
Moving to Testing.
Heh, I was rather aiming at the OP, who could have solved his urge to create a thread by understanding that testing is involved.
Happy holidays!
Offline
It seems package-query requires pacman <4.2, but this can be changed so that package-query uses pacman 4.2.
Here is the real solution:
https://translate.googleusercontent.com … JLImgg1XYQ
Last edited by gururise (2014-12-24 19:45:39)
Offline
The "real" solution is the same thing that applies to every AUR package that depends on an official package: rebuild it.
Also, package-query is not packagekit, which is what this thread is actually about...
Offline
Also package-query has been updated in the last couple of days to support pacman 4.2
Offline
Tried to make packagekit work with pacman 4.2 : https://github.com/piernov/PackageKit/tree/pacman-4.2
It compiles, can list packages and updates, can install packages but cannot do updates. I don't know if it worked before.
I'm not a good programmer and I don't know how GLib, PackageKit, Pacman work so don't put too much hope there. (for example I don't know where I should use g_return_if_fail() )
Offline
it's likely the arch backend for packagekit broke over the past year, might be fun having a look.
Arch i686 on Phenom X4 | GTX760
Offline