[opensuse-factory] PackageKit, zypper and friends... Multi-repositories!
Dear all, I'm experiencing a small problem here (GNOME/PackageKit) and I seek guidance... If I had a repository which contains modified versions of packages already distributed in openSUSE and set it with higher priority so those packages are installed through 'zypper dup' all seems to go ok. As long as I use zypper update, it doesn't bring me any problems. The only problem is that PackageKit seems not to understand this multi-repository setups and is always complaining that there are updates, and eventually if I install such updates it just ignores repository priority and installs the stuff I don't want installed. This behaviour as led me to disable PackageKit agent on GNOME. Though this isn't much of a big deal for me, if we try to get users to install repositories like the ones I am using, this can lead to erratic behaviour from PackageKit. From my understanding this can be a bit bad karma and tackles the functionality that openSUSE offers, specially when it's repository based. Any thoughts on how to go around this behaviour from PackageKit? I apologize if this isn't the right list for such question. Nelson -- nelson marques nmo.marques@gmail.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
ma., 14.02.2011 kl. 19.29 +0000, skrev Nelson Marques:
Dear all,
I'm experiencing a small problem here (GNOME/PackageKit) and I seek guidance...
If I had a repository which contains modified versions of packages already distributed in openSUSE and set it with higher priority so those packages are installed through 'zypper dup' all seems to go ok. As long as I use zypper update, it doesn't bring me any problems.
The only problem is that PackageKit seems not to understand this multi-repository setups and is always complaining that there are updates, and eventually if I install such updates it just ignores repository priority and installs the stuff I don't want installed. This behaviour as led me to disable PackageKit agent on GNOME.
Though this isn't much of a big deal for me, if we try to get users to install repositories like the ones I am using, this can lead to erratic behaviour from PackageKit. From my understanding this can be a bit bad karma and tackles the functionality that openSUSE offers, specially when it's repository based.
Any thoughts on how to go around this behaviour from PackageKit?
I apologize if this isn't the right list for such question.
Nelson
-- nelson marques nmo.marques@gmail.com
I think this is covered in https://bugzilla.novell.com/show_bug.cgi?id=637764 //Bjørn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/14/2011 08:29 PM, Nelson Marques wrote:
Dear all,
I'm experiencing a small problem here (GNOME/PackageKit) and I seek guidance...
If I had a repository which contains modified versions of packages already distributed in openSUSE and set it with higher priority so those packages are installed through 'zypper dup' all seems to go ok. As long as I use zypper update, it doesn't bring me any problems.
The only problem is that PackageKit seems not to understand this multi-repository setups and is always complaining that there are updates, and eventually if I install such updates it just ignores repository priority and installs the stuff I don't want installed. This behaviour as led me to disable PackageKit agent on GNOME.
PackageKit applet was supposed to display only the patches the distribution issues as maintenance, and not just updated packages. It was the community who complained loudly because they wanted to use it as a replacement for a build service repository RSS reader. The problem is that whoever added that code, added his own "solver in 2 lines" ie: comparing arches and versions manually. I am giving it a look so that finding the updated packages uses ZYpp sat-solver system update method to find candidates, and I will probably make showing packages optional, and I hope coolo disables it by default. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Tirsdag den 15. februar 2011 10:51:22 skrev Duncan Mac-Vicar P.:
PackageKit applet was supposed to display only the patches the distribution issues as maintenance, and not just updated packages.
It was the community who complained loudly because they wanted to use it as a replacement for a build service repository RSS reader.
The problem is that whoever added that code, added his own "solver in 2 lines" ie: comparing arches and versions manually.
I am giving it a look so that finding the updated packages uses ZYpp sat-solver system update method to find candidates, and I will probably make showing packages optional, and I hope coolo disables it by default.
Sounds excellent! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/15/2011 10:54 AM, Martin Schlander wrote:
Tirsdag den 15. februar 2011 10:51:22 skrev Duncan Mac-Vicar P.:
PackageKit applet was supposed to display only the patches the distribution issues as maintenance, and not just updated packages.
It was the community who complained loudly because they wanted to use it as a replacement for a build service repository RSS reader.
The problem is that whoever added that code, added his own "solver in 2 lines" ie: comparing arches and versions manually.
I am giving it a look so that finding the updated packages uses ZYpp sat-solver system update method to find candidates, and I will probably make showing packages optional, and I hope coolo disables it by default.
Sounds excellent!
May be you can test http://download.opensuse.org/repositories/home:/dmacvicar/openSUSE_Factory/ PackageKit and give me some feedback? It still shows packages and patches, however, it does not use a handcrafted logic to find candidates but ZYpp solver, therefore it should respect "zypper up" no-uninstall, vendor policies, locks, etc. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Tirsdag den 15. februar 2011 12:35:13 skrev Duncan Mac-Vicar P.:
May be you can test http://download.opensuse.org/repositories/home:/dmacvicar/openSUSE_Factory/ PackageKit and give me some feedback?
It still shows packages and patches, however, it does not use a handcrafted logic to find candidates but ZYpp solver, therefore it should respect "zypper up" no-uninstall, vendor policies, locks, etc.
Sounds much better, though I agree that the ideal case is only patches by default - with package updates as an option. I will test it. But I've added your repo but there's no packagekit there (yet). I guess it's down to publishing and mirror syncing lag. But "thankfully" my currently broken (K)PK will notify me when there's a vendor change update in your repo >:-) ... I told it to check every hour. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
;) If any experiences of problems with packagekit, kpackagekit or updater applet are wanted to read about - I can try to offer some links to so tagged threads in the forums http://forums.opensuse.org/tags/packagekit.html ... and there are more untagged postings to find via Google http://www.google.de/search?q=site%3Aforums.openSUSE.org+packagekit http://www.google.de/search?q=site%3Aforums.openSUSE.org+kpackagekit http://www.google.de/search?hl=en&q=site%3Aforums.openSUSE.org+updater+applet or via internal search /;) I wish you a lot of success! Martin (pistazienfresser) -- - Martin Seidler - openSUSE profile: https://users.opensuse.org/show/pistazienfresser -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 15 February 2011 13:32:22 Martin Schlander wrote:
Tirsdag den 15. februar 2011 12:35:13 skrev Duncan Mac-Vicar P.:
May be you can test http://download.opensuse.org/repositories/home:/dmacvicar/openSUSE_Factor y/ PackageKit and give me some feedback?
It still shows packages and patches, however, it does not use a handcrafted logic to find candidates but ZYpp solver, therefore it should respect "zypper up" no-uninstall, vendor policies, locks, etc.
Sounds much better, though I agree that the ideal case is only patches by default - with package updates as an option.
I will test it. But I've added your repo but there's no packagekit there (yet). I guess it's down to publishing and mirror syncing lag.
But "thankfully" my currently broken (K)PK will notify me when there's a vendor change update in your repo >:-) ... I told it to check every hour.
It's not published yet, but you can download it with osc getbinaries. You might need to --force it to keep the PackageKit-branding-openSUSE which is not in version 0.6.12 in Duncan's repo. Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/15/2011 03:15 PM, Will Stephenson wrote:
It's not published yet, but you can download it with osc getbinaries. You might need to --force it to keep the PackageKit-branding-openSUSE which is not in version 0.6.12 in Duncan's repo.
Anyway it may be I removed some functions that were used in another place so the package may be broken. I am cleaning up more code and adding the feature for disabling packages and I will post another package) -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 15 February 2011 15:29:59 Duncan Mac-Vicar P. wrote:
On 02/15/2011 03:15 PM, Will Stephenson wrote:
It's not published yet, but you can download it with osc
getbinaries. You
might need to --force it to keep the PackageKit-branding-openSUSE which is not in version 0.6.12 in Duncan's repo.
Anyway it may be I removed some functions that were used in another place so the package may be broken. I am cleaning up more code and adding the feature for disabling packages and I will post another package)
The build I just installed makes kpackagekit spam dbus (dbus-daemon 100% cpu), not sure why yet. Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Will Stephenson write:
On Tuesday 15 February 2011 15:29:59 Duncan Mac-Vicar P. wrote:
On 02/15/2011 03:15 PM, Will Stephenson wrote:
It's not published yet, but you can download it with osc
getbinaries. You
might need to --force it to keep the PackageKit-branding-openSUSE which is not in version 0.6.12 in Duncan's repo.
Anyway it may be I removed some functions that were used in another place so the package may be broken. I am cleaning up more code and adding the feature for disabling packages and I will post another package)
The build I just installed makes kpackagekit spam dbus (dbus-daemon 100% cpu), not sure why yet.
Will
You can debug it if you run packagekitd --disable-timer --verbose to observe dbus you can use dbus-monitor
-- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex
-- Josef Reidinger Appliance Toolkit team maintainer of perl-Bootloader, yast2-bootloader and parts of webyast and SLMS -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/15/2011 03:45 PM, Will Stephenson wrote:
The build I just installed makes kpackagekit spam dbus (dbus-daemon 100% cpu), not sure why yet.
My package was broken so packagekitd would not start. I guess it is a bug in KPackageKit that if it can't connect it goes in a smap loop? The new built one should be fixed. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/15/2011 01:32 PM, Martin Schlander wrote:
Tirsdag den 15. februar 2011 12:35:13 skrev Duncan Mac-Vicar P.:
May be you can test http://download.opensuse.org/repositories/home:/dmacvicar/openSUSE_Factory/ PackageKit and give me some feedback?
It still shows packages and patches, however, it does not use a handcrafted logic to find candidates but ZYpp solver, therefore it should respect "zypper up" no-uninstall, vendor policies, locks, etc.
Sounds much better, though I agree that the ideal case is only patches by default - with package updates as an option.
I will test it. But I've added your repo but there's no packagekit there (yet). I guess it's down to publishing and mirror syncing lag.
Now you can disable packages as well, just create /etc/PackageKit/ZYpp.conf and set: [Updates] HidePackages=true Once it is tested enough I will submit to Factory and upstream. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, 2011-02-15 at 12:35 +0100, Duncan Mac-Vicar P. wrote:
It still shows packages and patches, however, it does not use a handcrafted logic to find candidates but ZYpp solver, therefore it should respect "zypper up" no-uninstall, vendor policies, locks, etc.
Ooh ! :-) finally the love from a zypp afficionado to do the other half of fixing the zypp PK backend :-) I'd love to read the diff, as no doubt would Zhang Qiang, hopefully you fixed some of the create-a-new-iterator-to-check-end type problems that were in there too ? :-) Thanks, Michael. -- michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/15/2011 04:25 PM, Michael Meeks wrote:
On Tue, 2011-02-15 at 12:35 +0100, Duncan Mac-Vicar P. wrote:
It still shows packages and patches, however, it does not use a handcrafted logic to find candidates but ZYpp solver, therefore it should respect "zypper up" no-uninstall, vendor policies, locks, etc.
Ooh ! :-) finally the love from a zypp afficionado to do the other half of fixing the zypp PK backend :-)
I'd love to read the diff, as no doubt would Zhang Qiang, hopefully you fixed some of the create-a-new-iterator-to-check-end type problems that were in there too ? :-)
https://build.opensuse.org/package/view_file?file=use-system-solve.patch&package=PackageKit&project=home%3Admacvicar&srcmd5=3cebc65db4b3f54f22feff58a4e79c75 There is some noise in the patch as my emacs has trailing whitespace removal :-/ The interesting part is: zypp_get_package_updates If choosing the update candidates would be as easy as looking for bigger versions of the same arch, why would we have a solver at all? :-) I haven't fixed anything else, just s/handcrafted candidate logic/doSystemUpdate/ and added an option to hide packages from the list on /etc/PackageKit/ZYpp.conf. There is other stuff to clean up. Sometimes the sat:: classes are used without a reason (those are the low level ones) solvable->getAttribute(ATTRIBUT_FOO) is unneeded when you have package.foo() and stuff like that. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi Duncan, On Tue, 2011-02-15 at 17:03 +0100, Duncan Mac-Vicar P. wrote:
If choosing the update candidates would be as easy as looking for bigger versions of the same arch, why would we have a solver at all? :-)
Looks nice :-) I'm no zypp expert and only skimmed it quickly, but AFAIR we spent a while sucking state out of zypp by doing magic like 'doUpdate()' and then discarding the results having sucked the consequences out. I assume we don't leave any global update state lying around after getting the list of updates, that would conflict with a subsequent operation.
There is other stuff to clean up. Sometimes the sat:: classes are used without a reason (those are the low level ones)
Quite :-) it'd be lovely to have a blast of a handful of hours from a zypp API familiar person to clean the whole thing up. Great start though; thanks ! Hopefully Zhang can merge it, ATB, Michael. -- michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/16/2011 06:44 PM, Michael Meeks wrote:
Looks nice :-) I'm no zypp expert and only skimmed it quickly, but AFAIR we spent a while sucking state out of zypp by doing magic like 'doUpdate()' and then discarding the results having sucked the consequences out. I assume we don't leave any global update state lying around after getting the list of updates, that would conflict with a subsequent operation.
That is a good point. If I introduced that bug, it can be solved easily by saving and restoring the solver state before get_updates and at the end. Duncan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Tirsdag den 15. februar 2011 12:35:13 skrev Duncan Mac-Vicar P.:
May be you can test http://download.opensuse.org/repositories/home:/dmacvicar/openSUSE_Factory/ PackageKit and give me some feedback?
I got your packages with 'osc getbinaries home:dmacvicar PackageKit openSUSE_Factory i586' Added a plaindir repo with and vendor changed to it using sw_single. Leaving me with the following packages installed: cb400f@linux-2rly:~> rpm -qa | grep -i packagekit kpackagekit-0.6.3.3-4.1.i586 libpackagekit-glib2-14-0.6.12-7.1.i586 PackageKit-gstreamer-plugin-0.6.12-7.1.i586 PackageKit-branding-upstream-0.6.12-7.1.i586 libpackagekit-qt14-0.6.12-7.1.i586 PackageKit-gtk-module-0.6.12-7.1.i586 PackageKit-0.6.12-7.1.i586 PackageKit-browser-plugin-0.6.12-7.1.i586 The good news is that (K)PK no longer wants me to break my system with vendor change updates. Unfortunately there are some bad news too :-( 1) KPK shows two updates where 'zypper lu' only shows one. I'm unsure if KPK is showing the same update twice or showing rpm _and_ deltarpm or something. See the screenshot, maybe you can figure out what it's doing: http://opensuse-guide.org/tmp/kpk-duncan.png Clicking Apply in KPK only installs _one_ patch. 2) packagekitd refuses to go away and let me do anything package related after it has been awokened from its slumber. I can't even kill it via zypper: linux-2rly:/home/cb400f # zypper lu PackageKit is blocking zypper. This happens if you have an updater applet or other software management application using PackageKit running. Tell PackageKit to quit? [yes/no] (no): yes PackageKit is still running (probably busy). Try again? [yes/no] (no): yes PackageKit is still running (probably busy). Try again? [yes/no] (no): The only way I can use zypper or yast after KPK/packagekitd has been invoked in a session is by manually running 'killall packagekitd' it would seem. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/16/2011 12:39 PM, Martin Schlander wrote:
The good news is that (K)PK no longer wants me to break my system with vendor change updates.
Great.
Unfortunately there are some bad news too :-(
1) KPK shows two updates where 'zypper lu' only shows one. I'm unsure if KPK is showing the same update twice or showing rpm _and_ deltarpm or something. See the screenshot, maybe you can figure out what it's doing: http://opensuse-guide.org/tmp/kpk-duncan.png
Clicking Apply in KPK only installs _one_ patch.
Yes. Well, PK get-updates in our ZYpp backend is not exactly zypper lu, but it first show patches.where(:needed => true), then add zypper lu minus packages that were contained in the patch already. It seems that this last part is not working then (the package should not be shown). I will look into it.
2) packagekitd refuses to go away and let me do anything package related after it has been awokened from its slumber.
Ok, this is different. Can you inspect pk_zypp_backend.log to know what it is doing? or PackageKit.log -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Onsdag den 16. februar 2011 12:43:40 skrev Duncan Mac-Vicar P.:
On 02/16/2011 12:39 PM, Martin Schlander wrote:
2) packagekitd refuses to go away and let me do anything package related after it has been awokened from its slumber.
Ok, this is different. Can you inspect pk_zypp_backend.log to know what it is doing? or PackageKit.log
My /var/log/pk_backend_zypp is 10(!) megabytes, after only playing with it a couple of hrs this morning. It has a lot of MediaHandler stuff, other than that nothing particularly stands out to me. You can get the entire file here if you want. http://opensuse-guide.org/tmp/pk_backend_zypp My /var/log/pk_backend_zypp-1 (log from yesterday using the standard (k)pk of 11.4rc1), has similar size and content however. I don't have any PackageKit.log in /var/log/ or anything else that looks PK related. Dunno if it might be hiding elsewhere. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/16/2011 01:29 PM, Martin Schlander wrote:
Onsdag den 16. februar 2011 12:43:40 skrev Duncan Mac-Vicar P.:
On 02/16/2011 12:39 PM, Martin Schlander wrote:
2) packagekitd refuses to go away and let me do anything package related after it has been awokened from its slumber.
Ok, this is different. Can you inspect pk_zypp_backend.log to know what it is doing? or PackageKit.log
My /var/log/pk_backend_zypp is 10(!) megabytes, after only playing with it a couple of hrs this morning. It has a lot of MediaHandler stuff, other than that nothing particularly stands out to me. You can get the entire file here if you want. http://opensuse-guide.org/tmp/pk_backend_zypp
My /var/log/pk_backend_zypp-1 (log from yesterday using the standard (k)pk of 11.4rc1), has similar size and content however.
I see in the log that ProductFileReader is called everytime a url is touched. This is caused by RepoFileReader.cc:100 in repositories_in_stream who does a useless logging: MIL << info << endl; Where a bug in RepoInfo::baseUrls (related to Dominik's code for mirrorlists) does a replace of macros all the time (stuff like $distver), however, this replace is done even if there is nothing to replace. Something to fix in libzypp. Then the solver is pretty verbose in pk_backend_log. Michael, may be we can control the log level also with /etc/PackageKit/ZYpp.conf? -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/16/2011 02:01 PM, Duncan Mac-Vicar P. wrote:
Where a bug in RepoInfo::baseUrls (related to Dominik's code for mirrorlists) does a replace of macros all the time (stuff like $distver), however, this replace is done even if there is nothing to replace.
I have fixed this in git. The changes file looks like this: ------------------------------------------------------------------- Wed Feb 16 14:24:27 UTC 2011 - dmacvicar@suse.de - Do not look for $releasever 's value if there is no variable in the url: parses product file again and again - version 8.12.2 (10) If you want to test how bad it spams the log now, take libzypp from zypp:Head project. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Onsdag den 16. februar 2011 13:29:30 skrev Martin Schlander:
Onsdag den 16. februar 2011 12:43:40 skrev Duncan Mac-Vicar P.:
On 02/16/2011 12:39 PM, Martin Schlander wrote:
2) packagekitd refuses to go away and let me do anything package related after it has been awokened from its slumber.
I poked at it some more. And this only made the situation worse or more confusing at least. It seems: Sometimes packagekitd releases package management on its own after a minute or two - without needing to use the hammer. But not always. Sometimes packagekitd can be told to quit via zypper, but most times it can't. Telling sw_single to quit packagekitd seems to work everytime however (tried four different times, all successful). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 02/16/2011 02:11 PM, Martin Schlander wrote:
Onsdag den 16. februar 2011 13:29:30 skrev Martin Schlander:
Onsdag den 16. februar 2011 12:43:40 skrev Duncan Mac-Vicar P.:
On 02/16/2011 12:39 PM, Martin Schlander wrote:
2) packagekitd refuses to go away and let me do anything package related after it has been awokened from its slumber.
I poked at it some more. And this only made the situation worse or more confusing at least. It seems:
Sometimes packagekitd releases package management on its own after a minute or two - without needing to use the hammer. But not always.
Sometimes packagekitd can be told to quit via zypper, but most times it can't.
Telling sw_single to quit packagekitd seems to work everytime however (tried four different times, all successful).
zypper checks for packagekit like this: $ dbus-send --system --dest=org.freedesktop.DBus --type=method_call --print-reply --reply-timeout=200 / org.freedesktop.DBus.NameHasOwner string:org.freedesktop.PackageKit then does: $ dbus-send --system --dest=org.freedesktop.PackageKit --type=method_call /org/freedesktop/PackageKit org.freedesktop.PackageKit.SuggestDaemonQuit then checks again after a while. Any yast wizdars here to tell what yast does? Or some other suggestions? -- cheers, jano Ján Kupec Appliances team ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz ---------------------------------------------------------(EOF)---
On 02/16/2011 04:03 PM, Jano Kupec wrote:
then does: $ dbus-send --system --dest=org.freedesktop.PackageKit --type=method_call /org/freedesktop/PackageKit org.freedesktop.PackageKit.SuggestDaemonQuit
then checks again after a while.
Any yast wizdars here to tell what yast does? Or some other suggestions?
LOL may be YaST is doing 'killall -9 packagekitd' :-) Duncan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Mittwoch, 16. Februar 2011, 14:11:53 schrieb Martin Schlander:
Sometimes packagekitd releases package management on its own after a minute or two - without needing to use the hammer. But not always.
Sometimes packagekitd can be told to quit via zypper, but most times it can't.
For me this always works, yet not as expected. But maybe it can shed a light on what does not work. If zypper asks whether it should tell packagkitd to quit and one chooses "yes" one almost always gets the message that it failed. No matter how often one enters yes again to try again, it will always fail. However, if one aborts zypper with CTRL+C after the first attempt which according to zypper fails and immediately after that restarts zypper up or whatever packagekitd is not reported by zypper to still block anything. So the "fail" is not really a fail. Maybe zypper itself somehow prevents packagekitd from quitting until zypper itself was quit. Another question for me is whether after zypper or YaST quit packagekitd the notifiers like kpackagekit still work, i.e. do their checks. I have a feeling that this is not the case. Sven -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (10)
-
Bjørn Lie -
Duncan Mac-Vicar P. -
Jano Kupec -
Josef Reidinger -
Martin Schlander -
Michael Meeks -
Nelson Marques -
pistazienfresser (see profile) -
Sven Burmeister -
Will Stephenson