You are not logged in.
Can packagekit and python-packagekit sensibly be uninstalled without any consequences for most users? Since packagekit has just been dropped it would seem that there will be a need to do so? On the arch mailing list Ike Devolder sent a post today "I just dropped packagekit and its dependencies."
Last edited by mcloaked (2014-12-27 17:29:57)
Mike C
Offline
Can packagekit and python-packagekit sensibly be uninstalled without any consequences for most users?
packagekit is only required for the integrated package managers of e.g. gnome, mate and qt (apper). It may force useres of those desktop environments to use pacman directly instead of a nice GUI, but that should be all.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Thanks progandy - I have deleted the two packagekit packages I had from my machine - I can't even remember installing them so I doubt I'd ever have needed them!
Mike C
Offline
My solution to the problem was:
pacman -R packagekit gnome-packagekit
pacman -Syu
Offline
And my solution is
IgnorePkg = pacman
I love my gnome-packagekit updater thingymajig. Plus PkgBrowser hasn't been updated yet and I need that too.
Offline
No longer a [testing] issue, moving to AUR Issues...
Stickying until this blows over.
Offline
Hi, I am having the same issue but I haven't properly understood what is going on. How do the two solutions differ?
Also, the error message says:
error: failed to prepare transaction (could not satisfy dependencies)
:: packagekit: requires pacman<4.2.0
but
$ pacman --version
.--. Pacman v4.1.2 - libalpm v8.0.2
/ _.-' .-. .-. .-. Copyright (C) 2006-2013 Pacman Development Team
\ '-. '-' '-' '-' Copyright (C) 2002-2006 Judd Vinet
'--'
This program may be freely redistributed under
the terms of the GNU General Public License.
so it seems I have an appropriate version of pacman installed.
Thanks a lot in advance for the help!
Last edited by lucacerone (2014-12-30 12:36:10)
Offline
You are trying to update to a new pacman version. packagekit is not compatible with it and has been removed from the repos. You should remove it from your system then update.
Offline
Thanks Allan,
I didn't notice that there is a page 1 in the thread, reading it it is much clearer now!
(as mentioned in other post uninstalling packagekit and gnome-packagekit fixed the issue for me)
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() )
I did prepare a similar patch and sent it to the mailing list:
http://lists.freedesktop.org/archives/p … 26342.html
Same issues, though...
ArchLinux - make it simple & lightweight
Offline
Plus PkgBrowser hasn't been updated yet and I need that too.
PkgBrowser is now updated, has to be rebuilt while having Pacman 4.2 installed.
Offline
For any KDE users having problems, do the following:
Remove apper, packagekit-qt2 & packagekit.
sudo pacman -R apper packagekit-qt2 packagekit
Then you can upgrade with:
sudo pacman -Syu
Then update the pacman database like so:
sudo pacman-db-upgrade
done.
Offline
PkgBrowser is now updated, has to be rebuilt while having Pacman 4.2 installed.
Yes, I've already noticed and updated pacman and pkgbrowser two days ago. Now I'm using kalu instead of gnome-packagekit, seems to work nicely so far.
Offline
I found three orphaned packages (packagekit, python-packagekit, python2-dbus ) and removed them.
pacman-db-upgrade
System back to normal now.
Last edited by dwillar (2015-01-01 18:40:12)
Offline
Check this page, where I found the solution and sorted it out.
https://forum.manjaro.org/index.php?topic=19287.0
In the terminal as root I entered the following and now it works fine for me:
# pacman -Sdd pacman
Maybe you'll have to run an upgrade of the DB
# pacman-db-upgrade
and then enter th etwo lines below
# Pacman -Syy
# pacman Syu
Hope this helps you as well.
Cheers
Last edited by Verocheque (2015-01-03 19:50:34)
Offline
Check this page, where I found the solution and sorted it out.
https://forum.manjaro.org/index.php?topic=19287.0As root I entered the following in the terminal and now it works fine for me:
# pacman -Sdd pacman
# Pacman -Syy
# pacman Syu
Hope this helps you as well.
Cheers
This really isn't a good solution as you now have packagekit installed without its dependencies.
As stated earlier in this thread the solution is to remove packagekit from your system.
Offline
For the time being, this can be a workaround :
Just edit your "pacman.conf" and ignore the "pacman" update.
Steps to accomplish the above:
1. sudo nano /etc/pacman.conf [Return]
2. Go to the line which says "IgnorePkg"
3. Add IgnorePkg = pacman
4. Ctrl + X >> Y >> [Return]
Done.
Last edited by isank (2015-01-08 17:59:50)
Offline
For the time being, this can be a solution :
Just edit your "pacman.conf" and ignore the "pacman" update.
Steps to accomplish the above:
1. sudo nano /etc/pacman.conf [Return]
2. Go to the line which says "IgnorePkg"
3. Add IgnorePkg = pacman
4. Ctrl + X >> Y >> [Return]Done.
Not a solution at all; a "workaround" and an ill-advised one at that.
Offline
isank wrote:For the time being, this can be a solution :
Just edit your "pacman.conf" and ignore the "pacman" update.
Steps to accomplish the above:
1. sudo nano /etc/pacman.conf [Return]
2. Go to the line which says "IgnorePkg"
3. Add IgnorePkg = pacman
4. Ctrl + X >> Y >> [Return]Done.
Not a solution at all; a "workaround" and an ill-advised one at that.
Sir, can you please tell me that why do you think it is ill-advised?
Because I have mentioned "for the time being", that means till packagekit gets an update or so, and till then ignoring the update of pacman is not harmful.
Last edited by isank (2015-01-08 18:03:21)
Offline
Where to start? First, partial upgrades are unsupported, and holding back the single most important package on your system makes no sense anyway. Secondly, to do so for an unsupported package (packagekit) is just arse backwards. Third, packagekit has been updated so none of this is necessary anyway.
Offline
... "for the time being", that means till packagekit gets an update or so.
It has been updated. It was updated over a week ago. This nonsense is not needed. This thread is solved.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Where to start? First, partial upgrades are unsupported, and holding back the single most important package on your system makes no sense anyway. Secondly, to do so for an unsupported package (packagekit) is just arse backwards. Third, packagekit has been updated so none of this is necessary anyway.
Point taken, but then why the error is still the same when firing the command
sudo pacman -Syu
Offline
isank wrote:... "for the time being", that means till packagekit gets an update or so.
It has been updated. It was updated over a week ago. This nonsense is not needed. This thread is solved.
Point taken, but then why the error is still the same when firing the command
sudo pacman -Syu
Offline
Pacman does not update AUR packages, that's why. Remove the old packagekit, upgrade your system, then rebuild/install the new packagekit.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Pacman does not update AUR packages, that's why. Remove the old packagekit, upgrade your system, then rebuild/install the new packagekit.
Okay, thanks for the help.
But guys do you seriously think this is the way to tell that a post is wrong or not worth (nonsense/ill-advised etc), actually I am saying this because I am a newbie wanting to start my contribution to open source community, and on my very first post I get this, well this might be the way you guys are big players of this field, I don't know.
Offline