[opensuse-factory] PackageKit and libzypp locks
Hi all, Is it just me, or does PackageKit (Or rather, pk-backend-zypp in this case) not respect libzypp package locks at all? I noticed this earlier today when Apper's updater applet attempted to install a locked (non-installed) "recommended" dependency after an update to one of the base packages (patterns-openSUSE-enhanced_base_opt, I think) whereas both YaST and zypper behaved as expected by not marking locked packages/dependencies for update/installation. Is this behavior by design, or am I encountering a bug in the PackageKit(-backend) here? Regards, -F. Moukayed. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/02/13 14:48, Fadi Moukayed wrote:
Hi all,
Is it just me, or does PackageKit (Or rather, pk-backend-zypp in this case) not respect libzypp package locks at all? I noticed this earlier today when Apper's updater applet attempted to install a locked (non-installed) "recommended" dependency after an update to one of the base packages (patterns-openSUSE-enhanced_base_opt, I think) whereas both YaST and zypper behaved as expected by not marking locked packages/dependencies for update/installation.
Is this behavior by design, or am I encountering a bug in the PackageKit(-backend) here?
Regards, -F. Moukayed. PackageKit refusing to die is a nuisance when you are trying to use zypper. My solution is to explicitly kill the PID and mv /usr/lib/packagekitd out of the way. Regards Sid.
-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Sid Boyce
PackageKit refusing to die is a nuisance when you are trying to use zypper. My solution is to explicitly kill the PID and mv /usr/lib/packagekitd out of the way.
I accomplish the same in a different manner and do not have to worry about killing processes: zypper -v rm `rpm -qa|grep -i packagekit` but this also removes apper, PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE apper libpackagekit-glib2-14 libpackagekit-qt2-2 -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 12.02.2013 16:15, schrieb Sid Boyce:
On 12/02/13 14:48, Fadi Moukayed wrote:
Hi all,
Is it just me, or does PackageKit (Or rather, pk-backend-zypp in this case) not respect libzypp package locks at all? I noticed this earlier today when Apper's updater applet attempted to install a locked (non-installed) "recommended" dependency after an update to one of the base packages (patterns-openSUSE-enhanced_base_opt, I think) whereas both YaST and zypper behaved as expected by not marking locked packages/dependencies for update/installation.
Is this behavior by design, or am I encountering a bug in the PackageKit(-backend) here?
Regards, -F. Moukayed. PackageKit refusing to die is a nuisance when you are trying to use zypper. My solution is to explicitly kill the PID and mv /usr/lib/packagekitd out of the way.
And this has nothing to do with the question asked Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/02/13 15:35, Stephan Kulow wrote:
Am 12.02.2013 16:15, schrieb Sid Boyce:
On 12/02/13 14:48, Fadi Moukayed wrote:
Hi all,
Is it just me, or does PackageKit (Or rather, pk-backend-zypp in this case) not respect libzypp package locks at all? I noticed this earlier today when Apper's updater applet attempted to install a locked (non-installed) "recommended" dependency after an update to one of the base packages (patterns-openSUSE-enhanced_base_opt, I think) whereas both YaST and zypper behaved as expected by not marking locked packages/dependencies for update/installation.
Is this behavior by design, or am I encountering a bug in the PackageKit(-backend) here?
Regards, -F. Moukayed. PackageKit refusing to die is a nuisance when you are trying to use zypper. My solution is to explicitly kill the PID and mv /usr/lib/packagekitd out of the way. And this has nothing to do with the question asked
Greetings, Stephan
One of the evils of snapshot reading - too many lists and too many emails. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 12.02.2013 15:48, schrieb Fadi Moukayed:
Hi all,
Is it just me, or does PackageKit (Or rather, pk-backend-zypp in this case) not respect libzypp package locks at all? I noticed this earlier today when Apper's updater applet attempted to install a locked (non-installed) "recommended" dependency after an update to one of the base packages (patterns-openSUSE-enhanced_base_opt, I think) whereas both YaST and zypper behaved as expected by not marking locked packages/dependencies for update/installation.
Locks as in /etc/zypp/locks? If you know a way to reproduce it, I might check - it's hard to imagine but possible that PK is using a zypp API that is buggy, which the other tools don't use. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Yes, I realize I may have worded myself a bit poorly, but as you said,
I meant locks as in /etc/zypp/locks.
I'm not at the machine where it happened, but it was a stock install
of RC1 with KDE, and the only change I made was removing+locking a few
packages (zsh, joe) during install (The entries for these locks were
correctly placed in /etc/zypp/locks and were visible in YaST after
install). The problem cropped up when a new version of
patterns-openSUSE-enhanced_base_opt (Which incidentally recommends the
aforementioned packages) entered factory, and for some reason Apper
thought it was ok to pull & install the locked dependencies along with
the update for patterns-openSUSE-enhanced_base_opt (I'm fairly sure I
didn't see the locked packages in the update notification).
I will try to reproduce this with a simpler test case when I get back,
but from what I've seen, it looks like it's something
pk(-backend-zypp?)-specific, since other libzypp consumers (YaST,
zypper) behave correctly in this case and don't pull in locked
dependencies.
Regards,
-F. Moukayed.
2013/2/12 Stephan Kulow
Am 12.02.2013 15:48, schrieb Fadi Moukayed:
Hi all,
Is it just me, or does PackageKit (Or rather, pk-backend-zypp in this case) not respect libzypp package locks at all? I noticed this earlier today when Apper's updater applet attempted to install a locked (non-installed) "recommended" dependency after an update to one of the base packages (patterns-openSUSE-enhanced_base_opt, I think) whereas both YaST and zypper behaved as expected by not marking locked packages/dependencies for update/installation.
Locks as in /etc/zypp/locks? If you know a way to reproduce it, I might check - it's hard to imagine but possible that PK is using a zypp API that is buggy, which the other tools don't use.
Greetings, Stephan
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Fadi Moukayed -
Patrick Shanahan -
Sid Boyce -
Stephan Kulow