As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Can't you just run systemctl disable servicename to stop it from starting on reboot?
On 10/06/2014 08:58 AM, Freek de Kruijf wrote:
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
* alanbortu alanbortu@gmail.com [10-06-14 18:46]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Can't you just run systemctl disable servicename to stop it from starting on reboot?
On 10/06/2014 08:58 AM, Freek de Kruijf wrote:
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBAgAGBQJUMxudAAoJEM66EOTZRH6+XrsP/RqJmPvVktWdUdJYRH81FS/q 4gm01e1tNLxhQRRiuQS+1r2w/OUG/BAkWhYP5Qh88ovjS0pIzfTOVqXJ6K1mnvIn IwgqOP7unFG5rCSCzmmNBL5FdtgW9NYpgQsTTbrm98Zqlvf6kmwD5aCtKCc7sc9j nvrGjSagRVsVEjNMdNQ7BvR/CLdkmBg0gh03qaBcIVqNvYuiY5pTBlDaWaIWnETH EkjNQ0Zqzd943M2g4PZsJpdkpfovx9eSnHBzer3t9aiammjWSMVGJHplxiMvWMgg F7YKd/w3HFHlbpZOgQXKEUykebIMiFBbZkSgZO/Pbqbik1RrjSrRS22N9ZJwo4WL PUXvcSEgJlK8peaNsy6r7MM5bCnmHgRotk7WvqEXq1FXAIHXyWCUCwdtVgWneylR 00J8YJ0bSZExeIwMCqbdIUDn8XQlkVmZwBF8tt+UltEcjBYFzfb1Jc/n1hCgeEfr W3C6UdBMI98Gl7Ak86E8dm3oAF27772quYs8aSPhxSSjhAokW0rlYkM/9e/d/gvD b/yizIx07KRuq/e784yvVnfbpF741kbFdApUxPmFOYEJ59xgfDzhTbB4L/aUuFmT YQeHEExlMHVzBc4e0fLMNGNSGu+mz41egKy01BCHX30Yyjr+VRoGRvxb6nM/IgMk VLb8YeCWn8hiMOdKEXsG =SfbG -----END PGP SIGNATURE-----
No, it is a "static" service, but it is possible to: rpm -e PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE apper
On 10/06/2014 10:09 PM, Patrick Shanahan wrote:
- alanbortu alanbortu@gmail.com [10-06-14 18:46]:
Can't you just run systemctl disable servicename to stop it from starting on reboot?
On 10/06/2014 08:58 AM, Freek de Kruijf wrote:
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
No, it is a "static" service, but it is possible to: rpm -e PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE apper
Okay thanks, good to know. I don't have it installed on my system so couldn't check it out. IIRC you can also disable via the services manager in the KDE settings.
* alanbortu alanbortu@gmail.com [10-07-14 06:10]:
On 10/06/2014 10:09 PM, Patrick Shanahan wrote:
- alanbortu alanbortu@gmail.com [10-06-14 18:46]:
Can't you just run systemctl disable servicename to stop it from starting on reboot?
On 10/06/2014 08:58 AM, Freek de Kruijf wrote:
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
No, it is a "static" service, but it is possible to: rpm -e PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE apper
Okay thanks, good to know. I don't have it installed on my system so couldn't check it out. IIRC you can also disable via the services manager in the KDE settings.
I believe not, but if possible, I would really like to know. I do not see that option!
On Tue, 7 Oct 2014 08:00:32 -0400 Patrick Shanahan paka@opensuse.org wrote:
- alanbortu alanbortu@gmail.com [10-07-14 06:10]:
Okay thanks, good to know. I don't have it installed on my system so couldn't check it out. IIRC you can also disable via the services manager in the KDE settings.
I believe not, but if possible, I would really like to know. I do not see that option!
I'll note that packagekitd is not running on my system, though it is installed.
In KDE:
Configure Desktop --> Startup and Shutdown --> Service Manager
and uncheck the box for Apper. (In my opinion, that should be the default)
Also:
Right click on the tray, select "System Tray Settings" and uncheck the box for "Software Updater". (Note that if enabled, Software Updater still works, even if Apper is not running; that's why I think turning off Apper should be the default).
If packagekitd is running, those changes won't stop it. But after a reboot, it won't run Presumably, if you start Apper from the menus, that will again start packagekitd.
The settings for Gnome are harder to find, and require that you install "dconf-editor". I don't remember where to look (the path is a bit obscure), and I'm not currently logged into Gnome so I can't look for it.
* Neil Rickert nrickert@ameritech.net [10-07-14 09:27]:
On Tue, 7 Oct 2014 08:00:32 -0400 Patrick Shanahan paka@opensuse.org wrote:
- alanbortu alanbortu@gmail.com [10-07-14 06:10]:
Okay thanks, good to know. I don't have it installed on my system so couldn't check it out. IIRC you can also disable via the services manager in the KDE settings.
I believe not, but if possible, I would really like to know. I do not see that option!
I'll note that packagekitd is not running on my system, though it is installed.
In KDE:
Configure Desktop --> Startup and Shutdown --> Service Manager
and uncheck the box for Apper. (In my opinion, that should be the default)
Also:
Right click on the tray, select "System Tray Settings" and uncheck the box for "Software Updater". (Note that if enabled, Software Updater still works, even if Apper is not running; that's why I think turning off Apper should be the default).
If packagekitd is running, those changes won't stop it. But after a reboot, it won't run Presumably, if you start Apper from the menus, that will again start packagekitd.
The settings for Gnome are harder to find, and require that you install "dconf-editor". I don't remember where to look (the path is a bit obscure), and I'm not currently logged into Gnome so I can't look for it.
Tks, I hadn't realized that those particular options were available. Guess I didn't see the need to look previous :^). After removing subject apps, those options aren't visible.
Op 07-10-14 om 04:09 schreef Patrick Shanahan:
- alanbortu alanbortu@gmail.com [10-06-14 18:46]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Can't you just run systemctl disable servicename to stop it from starting on reboot?
On 10/06/2014 08:58 AM, Freek de Kruijf wrote:
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBAgAGBQJUMxudAAoJEM66EOTZRH6+XrsP/RqJmPvVktWdUdJYRH81FS/q 4gm01e1tNLxhQRRiuQS+1r2w/OUG/BAkWhYP5Qh88ovjS0pIzfTOVqXJ6K1mnvIn IwgqOP7unFG5rCSCzmmNBL5FdtgW9NYpgQsTTbrm98Zqlvf6kmwD5aCtKCc7sc9j nvrGjSagRVsVEjNMdNQ7BvR/CLdkmBg0gh03qaBcIVqNvYuiY5pTBlDaWaIWnETH EkjNQ0Zqzd943M2g4PZsJpdkpfovx9eSnHBzer3t9aiammjWSMVGJHplxiMvWMgg F7YKd/w3HFHlbpZOgQXKEUykebIMiFBbZkSgZO/Pbqbik1RrjSrRS22N9ZJwo4WL PUXvcSEgJlK8peaNsy6r7MM5bCnmHgRotk7WvqEXq1FXAIHXyWCUCwdtVgWneylR 00J8YJ0bSZExeIwMCqbdIUDn8XQlkVmZwBF8tt+UltEcjBYFzfb1Jc/n1hCgeEfr W3C6UdBMI98Gl7Ak86E8dm3oAF27772quYs8aSPhxSSjhAokW0rlYkM/9e/d/gvD b/yizIx07KRuq/e784yvVnfbpF741kbFdApUxPmFOYEJ59xgfDzhTbB4L/aUuFmT YQeHEExlMHVzBc4e0fLMNGNSGu+mz41egKy01BCHX30Yyjr+VRoGRvxb6nM/IgMk VLb8YeCWn8hiMOdKEXsG =SfbG -----END PGP SIGNATURE-----
No, it is a "static" service, but it is possible to: rpm -e PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE apper
I tried, but is was wrong. Should it be
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
? Thanks André
* A. den Oudsten AdenOudsten@wxs.nl [10-07-14 08:11]:
Op 07-10-14 om 04:09 schreef Patrick Shanahan:
- alanbortu alanbortu@gmail.com [10-06-14 18:46]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Can't you just run systemctl disable servicename to stop it from starting on reboot?
On 10/06/2014 08:58 AM, Freek de Kruijf wrote:
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBAgAGBQJUMxudAAoJEM66EOTZRH6+XrsP/RqJmPvVktWdUdJYRH81FS/q 4gm01e1tNLxhQRRiuQS+1r2w/OUG/BAkWhYP5Qh88ovjS0pIzfTOVqXJ6K1mnvIn IwgqOP7unFG5rCSCzmmNBL5FdtgW9NYpgQsTTbrm98Zqlvf6kmwD5aCtKCc7sc9j nvrGjSagRVsVEjNMdNQ7BvR/CLdkmBg0gh03qaBcIVqNvYuiY5pTBlDaWaIWnETH EkjNQ0Zqzd943M2g4PZsJpdkpfovx9eSnHBzer3t9aiammjWSMVGJHplxiMvWMgg F7YKd/w3HFHlbpZOgQXKEUykebIMiFBbZkSgZO/Pbqbik1RrjSrRS22N9ZJwo4WL PUXvcSEgJlK8peaNsy6r7MM5bCnmHgRotk7WvqEXq1FXAIHXyWCUCwdtVgWneylR 00J8YJ0bSZExeIwMCqbdIUDn8XQlkVmZwBF8tt+UltEcjBYFzfb1Jc/n1hCgeEfr W3C6UdBMI98Gl7Ak86E8dm3oAF27772quYs8aSPhxSSjhAokW0rlYkM/9e/d/gvD b/yizIx07KRuq/e784yvVnfbpF741kbFdApUxPmFOYEJ59xgfDzhTbB4L/aUuFmT YQeHEExlMHVzBc4e0fLMNGNSGu+mz41egKy01BCHX30Yyjr+VRoGRvxb6nM/IgMk VLb8YeCWn8hiMOdKEXsG =SfbG -----END PGP SIGNATURE-----
No, it is a "static" service, but it is possible to: rpm -e PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE apper
I tried, but is was wrong. Should it be
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
That will remove the listed packages. If the packages are not installed, they will not run so that disables PackageKit which you wanted to do. Note that this requires removing apper as it requires PackageKit. I use zypper rather than apper so do not miss it.
Another approach, root password is requested after restarting KDE. You can just deny/cancell the password request and PackageKit/apper will not be running. But you must do this every time you restart KDE.
I prefer the first choice as one can always reinstall the removed apps.
On Tue, 2014-10-07 at 14:09 +0200, A. den Oudsten wrote:
Op 07-10-14 om 04:09 schreef Patrick Shanahan:
- alanbortu alanbortu@gmail.com [10-06-14 18:46]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Can't you just run systemctl disable servicename to stop it from starting on reboot?
On 10/06/2014 08:58 AM, Freek de Kruijf wrote:
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBAgAGBQJUMxudAAoJEM66EOTZRH6+XrsP/RqJmPvVktWdUdJYRH81FS/q 4gm01e1tNLxhQRRiuQS+1r2w/OUG/BAkWhYP5Qh88ovjS0pIzfTOVqXJ6K1mnvIn IwgqOP7unFG5rCSCzmmNBL5FdtgW9NYpgQsTTbrm98Zqlvf6kmwD5aCtKCc7sc9j nvrGjSagRVsVEjNMdNQ7BvR/CLdkmBg0gh03qaBcIVqNvYuiY5pTBlDaWaIWnETH EkjNQ0Zqzd943M2g4PZsJpdkpfovx9eSnHBzer3t9aiammjWSMVGJHplxiMvWMgg F7YKd/w3HFHlbpZOgQXKEUykebIMiFBbZkSgZO/Pbqbik1RrjSrRS22N9ZJwo4WL PUXvcSEgJlK8peaNsy6r7MM5bCnmHgRotk7WvqEXq1FXAIHXyWCUCwdtVgWneylR 00J8YJ0bSZExeIwMCqbdIUDn8XQlkVmZwBF8tt+UltEcjBYFzfb1Jc/n1hCgeEfr W3C6UdBMI98Gl7Ak86E8dm3oAF27772quYs8aSPhxSSjhAokW0rlYkM/9e/d/gvD b/yizIx07KRuq/e784yvVnfbpF741kbFdApUxPmFOYEJ59xgfDzhTbB4L/aUuFmT YQeHEExlMHVzBc4e0fLMNGNSGu+mz41egKy01BCHX30Yyjr+VRoGRvxb6nM/IgMk VLb8YeCWn8hiMOdKEXsG =SfbG -----END PGP SIGNATURE-----
No, it is a "static" service, but it is possible to: rpm -e PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE apper
I tried, but is was wrong. Should it be
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
? Thanks André
Why would you do rpm -e instead of zypper rm? I don't get it.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-07 18:24, Shawn W Dunn wrote:
On Tue, 2014-10-07 at 14:09 +0200, A. den Oudsten wrote:
Op 07-10-14 om 04:09 schreef Patrick Shanahan:
I tried, but is was wrong. Should it be
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
Why would you do rpm -e instead of zypper rm? I don't get it.
Why would you do zypper rm instead of rpm -e? I don't get it :-)
It is like using libreoffice to print a label with the "buy milk" which you stick on the freezer. Yes, sure, you can do it. But why? Just pick a piece of paper and a pen, less resources needed.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
"Carlos E. R." robin.listas@telefonica.net writes:
On 2014-10-07 18:24, Shawn W Dunn wrote:
On Tue, 2014-10-07 at 14:09 +0200, A. den Oudsten wrote:
Op 07-10-14 om 04:09 schreef Patrick Shanahan:
I tried, but is was wrong. Should it be
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
Why would you do rpm -e instead of zypper rm? I don't get it.
Why would you do zypper rm instead of rpm -e? I don't get it :-)
zypper rm resolves dependencies, rpm -e doesn't.
Andreas.
On Wed, 8 Oct 2014 09:19, Andreas Schwab <schwab@...> wrote:
"Carlos E. R." robin.listas@telefonica.net writes:
On 2014-10-07 18:24, Shawn W Dunn wrote:
On Tue, 2014-10-07 at 14:09 +0200, A. den Oudsten wrote:
Op 07-10-14 om 04:09 schreef Patrick Shanahan:
I tried, but is was wrong. Should it be
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
Why would you do rpm -e instead of zypper rm? I don't get it.
Why would you do zypper rm instead of rpm -e? I don't get it :-)
zypper rm resolves dependencies, rpm -e doesn't.
Bzzzt! Rpm does handle dependencies, but only from the view point of the package that rpm has been called to handle.
Recommends, Suggests, and Pattern on the other hand are ignored by rpm.
To ignore dependencies, rpm has to be called with "--nodeps".
For most of such unclear cases I look at what "zypper rm -u {package}" suggests and then use "rpm -e" to remove what I select.
If there are "special cases" where a package can not be removed without zypper getting ugly on me, I either install the package with "rpm -u --justdb {package}" or, if that is impossible, I remove the executable and or readable bits from the file(s) in question to get my peace.
Then again, I use Linux systems since 1996, and I am capable to repair my system in the case I got it unuseable.
- Yamaban.
Yamaban foerster@lisas.de writes:
On Wed, 8 Oct 2014 09:19, Andreas Schwab <schwab@...> wrote:
"Carlos E. R." robin.listas@telefonica.net writes:
On 2014-10-07 18:24, Shawn W Dunn wrote:
On Tue, 2014-10-07 at 14:09 +0200, A. den Oudsten wrote:
Op 07-10-14 om 04:09 schreef Patrick Shanahan:
I tried, but is was wrong. Should it be
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
Why would you do rpm -e instead of zypper rm? I don't get it.
Why would you do zypper rm instead of rpm -e? I don't get it :-)
zypper rm resolves dependencies, rpm -e doesn't.
Bzzzt! Rpm does handle dependencies,
handle != resolve.
Andreas.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-08 09:19, Andreas Schwab wrote:
"Carlos E. R." <> writes:
Why would you do rpm -e instead of zypper rm? I don't get it.
Why would you do zypper rm instead of rpm -e? I don't get it :-)
zypper rm resolves dependencies, rpm -e doesn't.
Not exactly. rpm does check that dependencies are met, but it does not "solve" them deciding what to download. It just bails out, which is safe.
Why would you need to _solve_ dependencies when the intention is to just remove a package, not replace it with another? :-)
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
"Carlos E. R." robin.listas@telefonica.net writes:
Why would you need to _solve_ dependencies when the intention is to just remove a package, not replace it with another? :-)
??? You cannot remove the package without resolving dependencies.
Andreas.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-08 12:18, Andreas Schwab wrote:
"Carlos E. R." <> writes:
Why would you need to _solve_ dependencies when the intention is to just remove a package, not replace it with another? :-)
??? You cannot remove the package without resolving dependencies.
Of course you can >:-)
Anyway, rpm checks that dependencies are fulfilled. It just does not "solve" them. It bails out. Safe enough.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
"Carlos E. R." robin.listas@telefonica.net writes:
On 2014-10-08 12:18, Andreas Schwab wrote:
"Carlos E. R." <> writes:
Why would you need to _solve_ dependencies when the intention is to just remove a package, not replace it with another? :-)
??? You cannot remove the package without resolving dependencies.
Of course you can >:-)
No, you cannot.
Andreas.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-08 12:58, Andreas Schwab wrote:
"Carlos E. R." <> writes:
On 2014-10-08 12:18, Andreas Schwab wrote:
"Carlos E. R." <> writes:
Why would you need to _solve_ dependencies when the intention is to just remove a package, not replace it with another? :-)
??? You cannot remove the package without resolving dependencies.
Of course you can >:-)
No, you cannot.
- --nodeps
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
"Carlos E. R." robin.listas@telefonica.net writes:
On 2014-10-08 12:58, Andreas Schwab wrote:
"Carlos E. R." <> writes:
On 2014-10-08 12:18, Andreas Schwab wrote:
"Carlos E. R." <> writes:
Why would you need to _solve_ dependencies when the intention is to just remove a package, not replace it with another? :-)
??? You cannot remove the package without resolving dependencies.
Of course you can >:-)
No, you cannot.
--nodeps
You don't need rpm to shoot yourself in the foot.
Andreas.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-08 14:01, Andreas Schwab wrote:
"Carlos E. R." <> writes:
On 2014-10-08 12:58, Andreas Schwab wrote:
"Carlos E. R." <> writes:
On 2014-10-08 12:18, Andreas Schwab wrote:
"Carlos E. R." <> writes:
Why would you need to _solve_ dependencies when the intention is to just remove a package, not replace it with another? :-)
??? You cannot remove the package without resolving dependencies.
Of course you can >:-)
No, you cannot.
--nodeps
You don't need rpm to shoot yourself in the foot.
(Hint: look at the smiley above)
By doing what was suggested here:
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
you are not shooting any foot. The rpm command is smart enough to verify that dependencies are satisfied; if not, it will simply refuse, unless you force it to go ahead. It does not solve dependencies, but it checks them.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
"Carlos E. R." carlos.e.r@opensuse.org writes:
you are not shooting any foot. The rpm command is smart enough to verify that dependencies are satisfied;
And if they fail, rinse, repeat, ...
It does not solve dependencies, but it checks them.
But zypper does. In one go.
Andreas.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-08 16:24, Andreas Schwab wrote:
"Carlos E. R." carlos.e.r@opensuse.org writes:
you are not shooting any foot. The rpm command is smart enough to verify that dependencies are satisfied;
And if they fail, rinse, repeat, ...
It does not solve dependencies, but it checks them.
But zypper does. In one go.
Yes, absolutely. But you do not need all that to remove a few packages. In my case, doing it with zypper takes about five minutes of the clock, whereas rpm ends in seconds.
Thus what I say is that using zypper for removing a package or two is an overkill, and just as safe, not more.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
2014-10-08 11:39 GMT-03:00 Carlos E. R. carlos.e.r@opensuse.org:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-08 16:24, Andreas Schwab wrote:
"Carlos E. R." carlos.e.r@opensuse.org writes:
you are not shooting any foot. The rpm command is smart enough to verify that dependencies are satisfied;
And if they fail, rinse, repeat, ...
It does not solve dependencies, but it checks them.
But zypper does. In one go.
Yes, absolutely. But you do not need all that to remove a few packages. In my case, doing it with zypper takes about five minutes of the clock, whereas rpm ends in seconds.
Thus what I say is that using zypper for removing a package or two is an overkill, and just as safe, not more.
I prefer this "zypper rm -u YYY" as it also removes packages installed only because package YYY installed it, so less garbage in my system.
regards
Luiz
* Luiz Fernando Ranghetti elchevive68@gmail.com [10-08-14 10:49]:
2014-10-08 11:39 GMT-03:00 Carlos E. R. carlos.e.r@opensuse.org:
On 2014-10-08 16:24, Andreas Schwab wrote:
"Carlos E. R." carlos.e.r@opensuse.org writes:
you are not shooting any foot. The rpm command is smart enough to verify that dependencies are satisfied;
And if they fail, rinse, repeat, ...
It does not solve dependencies, but it checks them.
But zypper does. In one go.
Yes, absolutely. But you do not need all that to remove a few packages. In my case, doing it with zypper takes about five minutes of the clock, whereas rpm ends in seconds.
Thus what I say is that using zypper for removing a package or two is an overkill, and just as safe, not more.
I prefer this "zypper rm -u YYY" as it also removes packages installed only because package YYY installed it, so less garbage in my system.
You may prefer that and that may be the most prudent method, but zypper, nor anything else, is not infallible and certainly does *not* know about applications you may have installed not from zypper/rpm. But rpm will also be a problem then.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-08 16:47, Luiz Fernando Ranghetti wrote:
2014-10-08 11:39 GMT-03:00 Carlos E. R. <>:
I prefer this "zypper rm -u YYY" as it also removes packages installed only because package YYY installed it, so less garbage in my system.
True, but be careful: this feature is little tested. Check the proposal before accepting, just in case.
It is a nice feature.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
* Shawn W Dunn sfalken@opensuse.org [10-07-14 12:25]:
On Tue, 2014-10-07 at 14:09 +0200, A. den Oudsten wrote:
Op 07-10-14 om 04:09 schreef Patrick Shanahan:
- alanbortu alanbortu@gmail.com [10-06-14 18:46]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Can't you just run systemctl disable servicename to stop it from starting on reboot?
On 10/06/2014 08:58 AM, Freek de Kruijf wrote:
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBAgAGBQJUMxudAAoJEM66EOTZRH6+XrsP/RqJmPvVktWdUdJYRH81FS/q 4gm01e1tNLxhQRRiuQS+1r2w/OUG/BAkWhYP5Qh88ovjS0pIzfTOVqXJ6K1mnvIn IwgqOP7unFG5rCSCzmmNBL5FdtgW9NYpgQsTTbrm98Zqlvf6kmwD5aCtKCc7sc9j nvrGjSagRVsVEjNMdNQ7BvR/CLdkmBg0gh03qaBcIVqNvYuiY5pTBlDaWaIWnETH EkjNQ0Zqzd943M2g4PZsJpdkpfovx9eSnHBzer3t9aiammjWSMVGJHplxiMvWMgg F7YKd/w3HFHlbpZOgQXKEUykebIMiFBbZkSgZO/Pbqbik1RrjSrRS22N9ZJwo4WL PUXvcSEgJlK8peaNsy6r7MM5bCnmHgRotk7WvqEXq1FXAIHXyWCUCwdtVgWneylR 00J8YJ0bSZExeIwMCqbdIUDn8XQlkVmZwBF8tt+UltEcjBYFzfb1Jc/n1hCgeEfr W3C6UdBMI98Gl7Ak86E8dm3oAF27772quYs8aSPhxSSjhAokW0rlYkM/9e/d/gvD b/yizIx07KRuq/e784yvVnfbpF741kbFdApUxPmFOYEJ59xgfDzhTbB4L/aUuFmT YQeHEExlMHVzBc4e0fLMNGNSGu+mz41egKy01BCHX30Yyjr+VRoGRvxb6nM/IgMk VLb8YeCWn8hiMOdKEXsG =SfbG -----END PGP SIGNATURE-----
No, it is a "static" service, but it is possible to: rpm -e PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE apper
I tried, but is was wrong. Should it be
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
? Thanks André
Why would you do rpm -e instead of zypper rm? I don't get it.
Old habits die hard :^). zypper rm would be more appropriate, but neither are *wrong* and both accomplish the task at hand.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-07 18:39, Patrick Shanahan wrote:
Old habits die hard :^). zypper rm would be more appropriate, but neither are *wrong* and both accomplish the task at hand.
Zypper in my case takes minutes *before* attempting any removal, which is actually done by rpm in the end. That is, zypper first downloads the repository metadata, then computes what to do, then it mandates rpm to do it.
Just call rpm yourself and be done, instantly.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Tue, 07 Oct 2014, 18:44:33 +0200, Carlos E. R. wrote:
On 2014-10-07 18:39, Patrick Shanahan wrote:
Old habits die hard :^). zypper rm would be more appropriate, but neither are *wrong* and both accomplish the task at hand.
Zypper in my case takes minutes *before* attempting any removal, which is actually done by rpm in the end. That is, zypper first downloads the repository metadata, then computes what to do, then it mandates rpm to do it.
Just call rpm yourself and be done, instantly.
unless you also want to get those packages removed which got pulled in as a package required by the one to be removed now. This is where "zypper rm -u" really _can_ help a lot ;)
HTH, cheers.
l8er manfred
* Manfred Hollstein mhollstein@t-online.de [10-07-14 13:17]:
On Tue, 07 Oct 2014, 18:44:33 +0200, Carlos E. R. wrote:
On 2014-10-07 18:39, Patrick Shanahan wrote:
Old habits die hard :^). zypper rm would be more appropriate, but neither are *wrong* and both accomplish the task at hand.
Zypper in my case takes minutes *before* attempting any removal, which is actually done by rpm in the end. That is, zypper first downloads the repository metadata, then computes what to do, then it mandates rpm to do it.
Just call rpm yourself and be done, instantly.
unless you also want to get those packages removed which got pulled in as a package required by the one to be removed now. This is where "zypper rm -u" really _can_ help a lot ;)
Indeed, "zypper rm -u PackageKit" offers to remove 23 packages including apper and the afore mentioned. Much more complete, doesn't leave the crumbs laying about.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-07 22:17, Patrick Shanahan wrote:
- Manfred Hollstein <> [10-07-14 13:17]:
Just call rpm yourself and be done, instantly.
unless you also want to get those packages removed which got pulled in as a package required by the one to be removed now. This is where "zypper rm -u" really _can_ help a lot ;)
Indeed, "zypper rm -u PackageKit" offers to remove 23 packages including apper and the afore mentioned. Much more complete, doesn't leave the crumbs laying about.
And potentially very dangerous.
Just you slip a bit on carelessness, and you wipe the entire system just as happily. That feature is little tested.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Wed, 2014-10-08 at 00:53 +0200, Carlos E. R. wrote:
On 2014-10-07 22:17, Patrick Shanahan wrote:
- Manfred Hollstein <> [10-07-14 13:17]:
Just call rpm yourself and be done, instantly.
unless you also want to get those packages removed which got pulled in as a package required by the one to be removed now. This is where "zypper rm -u" really _can_ help a lot ;)
Indeed, "zypper rm -u PackageKit" offers to remove 23 packages including apper and the afore mentioned. Much more complete, doesn't leave the crumbs laying about.
And potentially very dangerous.
Just you slip a bit on carelessness, and you wipe the entire system just as happily. That feature is little tested.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
And that is why we are making btrfs default :)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-10-08 02:12, Roger Luedecke wrote:
On Wed, 2014-10-08 at 00:53 +0200, Carlos E. R. wrote:
And potentially very dangerous.
Just you slip a bit on carelessness, and you wipe the entire system just as happily. That feature is little tested.
And that is why we are making btrfs default :)
LOL.
Not on my machines >:-p
Ok, I'll bite. Let's suppose I shoot my own foot by removing an awful lot. To make this interesting, I might have removed crucial components for YaST.
So, I have btrfs on root, so I can "undo". They say :-)
If YaST was not destroyed, maybe there is some module that helps me to undo the removal. If it was destroyed, maybe there is a rescue disk that has some module to click and tell it to restore my main system.
Do those two modules exist? Documented, easy to use?
And there are complications. /var/log is not restored, I understand. What about /var/lib/rpm/*?
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Tue, 7 Oct 2014 18:24, Shawn W Dunn <sfalken@...> wrote:
On Tue, 2014-10-07 at 14:09 +0200, A. den Oudsten wrote:
Op 07-10-14 om 04:09 schreef Patrick Shanahan:
- alanbortu <alanbortu@...> [10-06-14 18:46]:
Can't you just run systemctl disable servicename to stop it from starting on reboot?
On 10/06/2014 08:58 AM, Freek de Kruijf wrote:
Op maandag 6 oktober 2014 14:45:21 schreef A. den Oudsten:
As soon as I start my Laptop, as well as my dektop, PackageKit is running to update. In both cases it is not possible to stop PackageKit to stop, it is blocked by pid 8993. Restart does not help. André den Oudsten
You may try to stop and disable packagekit.service in systemd using systemctl. I did that and still could use apper to update the system. Don't how this behaves after a reboot.
No, it is a "static" service, but it is possible to: rpm -e PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE apper
I tried, but is was wrong. Should it be
rpm -e PackageKitd PackageKitd-backend-zypp PackageKitd-branding-openSUSE apper
Why would you do rpm -e instead of zypper rm? I don't get it.
Because zypper looks deeper into dependencies and recomments, and will, based on that in some cases more or less try to remove your whole system instead of just the package you want to be removed.
In my case, I did a "zypper al '*PackageKit*' '*packagekit*' 'apper'" on the second try of installing beta1 to avoid even installing that piece of software. My box runs much better without. zypper and rpm are enough for most of my needs, for anything else, there is yast.
- Yamaban.
--
-
A. den Oudsten -
alanbortu -
Andreas Schwab -
Carlos E. R. -
Carlos E. R. -
Freek de Kruijf -
Luiz Fernando Ranghetti -
Manfred Hollstein -
Neil Rickert -
Patrick Shanahan -
Roger Luedecke -
Shawn W Dunn -
Yamaban