PackageKit installed on MicroOS
Hi, New question; I have both KDE and Gnome installed on my system to be able to test them both. However if I try to remove PackageKit it also wants to remove the following patterns/packages: The following 6 packages are going to be REMOVED: PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE patterns-microos-desktop-gnome patterns-microos-desktop-kde plasma5-pk-updates Why is PackageKit installed by default by both the Gnome and KDE desktop and what do we need it for? Updates and upgrades are done within transactional-update and are automatically initialised by transactional-update.timer. Is it safe to remove it from my system, plus should we also remove it from the KDE/Gnome patterns? BR, Syds
On Wed, 2020-12-02 at 21:58 +0100, Syds Bearda wrote:
Hi,
New question; I have both KDE and Gnome installed on my system to be able to test them both. However if I try to remove PackageKit it also wants to remove the following patterns/packages:
The following 6 packages are going to be REMOVED: PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE patterns-microos-desktop-gnome patterns-microos-desktop-kde plasma5-pk-updates
Why is PackageKit installed by default by both the Gnome and KDE desktop and what do we need it for? Updates and upgrades are done within transactional-update and are automatically initialised by transactional-update.timer.
Is it safe to remove it from my system, plus should we also remove it from the KDE/Gnome patterns?
In GNOME, PackageKit is a key requirement for gnome-software, which is our intended tool for installing flatpaks. So no, it's not safe to remove from your system unless you don't want a graphical way of installing user applications. I believe for KDE it's equally important for discover, which does the equivalent job to gnome-software for that DE. That said, the PackageKit-backend-zypp is extraneous and I'm certainly open to submissions that loosen the coupling between that backend and the PackageKit core. Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
Hi, Am Donnerstag, 3. Dezember 2020, 11:26:39 CET schrieb Richard Brown:
On Wed, 2020-12-02 at 21:58 +0100, Syds Bearda wrote:
Hi,
New question; I have both KDE and Gnome installed on my system to be able to test them both. However if I try to remove PackageKit it also wants to remove the following patterns/packages:
The following 6 packages are going to be REMOVED: PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE patterns-microos-desktop-gnome patterns-microos-desktop-kde plasma5-pk-updates
Why is PackageKit installed by default by both the Gnome and KDE desktop and what do we need it for? Updates and upgrades are done within transactional-update and are automatically initialised by transactional-update.timer.
Is it safe to remove it from my system, plus should we also remove it from the KDE/Gnome patterns?
In GNOME, PackageKit is a key requirement for gnome-software, which is our intended tool for installing flatpaks.
So no, it's not safe to remove from your system unless you don't want a graphical way of installing user applications.
I believe for KDE it's equally important for discover, which does the equivalent job to gnome-software for that DE.
No, Discover's PackageKit backend is entirely optional and not installed on MicroOS at all. The reason that PackageKit is pulled with the MicroOS KDE pattern at all is because of plasma5-pk-updates, which is mostly just for showing that updates are available at this point (as installation is broken).
That said, the PackageKit-backend-zypp is extraneous and I'm certainly open to submissions that loosen the coupling between that backend and the PackageKit core.
If PackageKit-backend-zypp is extraneous, there's no backend left which makes PackageKit itself (well, packagekitd) absolutely useless. Cheers, Fabian
Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team
Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer _______________________________________________ openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
Hi, On Thu, Dec 3, 2020, at 11:36, Fabian Vogt wrote:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:26:39 CET schrieb Richard Brown:
On Wed, 2020-12-02 at 21:58 +0100, Syds Bearda wrote:
Hi,
New question; I have both KDE and Gnome installed on my system to be able to test them both. However if I try to remove PackageKit it also wants to remove the following patterns/packages:
The following 6 packages are going to be REMOVED: PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE patterns-microos-desktop-gnome patterns-microos-desktop-kde plasma5-pk-updates
Why is PackageKit installed by default by both the Gnome and KDE desktop and what do we need it for? Updates and upgrades are done within transactional-update and are automatically initialised by transactional-update.timer.
Is it safe to remove it from my system, plus should we also remove it from the KDE/Gnome patterns?
Ah thanks for the clarification, I thought PackageKit was necessary for just zypper in/rm/up/dup from Gnome Software/ Discover, but since zypper isn't accessible without transactional-update in MicroOS, I thought it could be removed, didn't know it was also necessary for those GUI installers to work at all. I was just surprised that when I typed zypper ref by mistake I had to wait for PackageKit to finish.
In GNOME, PackageKit is a key requirement for gnome-software, which is our intended tool for installing flatpaks.
So no, it's not safe to remove from your system unless you don't want a graphical way of installing user applications.
I believe for KDE it's equally important for discover, which does the equivalent job to gnome-software for that DE.
No, Discover's PackageKit backend is entirely optional and not installed on MicroOS at all. The reason that PackageKit is pulled with the MicroOS KDE pattern at all is because of plasma5-pk-updates, which is mostly just for showing that updates are available at this point (as installation is broken).
That said, the PackageKit-backend-zypp is extraneous and I'm certainly open to submissions that loosen the coupling between that backend and the PackageKit core.
If PackageKit-backend-zypp is extraneous, there's no backend left which makes PackageKit itself (well, packagekitd) absolutely useless.
Cheers, Fabian
Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team
Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer _______________________________________________ openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
Hi, Am Donnerstag, 3. Dezember 2020, 11:54:37 CET schrieb Syds Bearda:
Hi,
On Thu, Dec 3, 2020, at 11:36, Fabian Vogt wrote:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:26:39 CET schrieb Richard Brown:
On Wed, 2020-12-02 at 21:58 +0100, Syds Bearda wrote:
Hi,
New question; I have both KDE and Gnome installed on my system to be able to test them both. However if I try to remove PackageKit it also wants to remove the following patterns/packages:
The following 6 packages are going to be REMOVED: PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE patterns-microos-desktop-gnome patterns-microos-desktop-kde plasma5-pk-updates
Why is PackageKit installed by default by both the Gnome and KDE desktop and what do we need it for? Updates and upgrades are done within transactional-update and are automatically initialised by transactional-update.timer.
Is it safe to remove it from my system, plus should we also remove it from the KDE/Gnome patterns?
Ah thanks for the clarification, I thought PackageKit was necessary for just zypper in/rm/up/dup from Gnome Software/ Discover, but since zypper isn't accessible without transactional-update in MicroOS, I thought it could be removed, didn't know it was also necessary for those GUI installers to work at all.
At least for Discover it's not, so if you don't use GNOME Software you could safely uninstall PackageKit. There's no important package in the "going to be REMOVED:" list, except for the patterns. If you uninstall those, future "zypper rm" calls with "--clean-deps" will try to also remove necessary packages and you won't benefit from new changes to the patterns. I'm planning to drop the PackageKit dependency of patterns-microos-desktop-kde with the next submission. Cheers, Fabian
I was just surprised that when I typed zypper ref by mistake I had to wait for PackageKit to finish.
In GNOME, PackageKit is a key requirement for gnome-software, which is our intended tool for installing flatpaks.
So no, it's not safe to remove from your system unless you don't want a graphical way of installing user applications.
I believe for KDE it's equally important for discover, which does the equivalent job to gnome-software for that DE.
No, Discover's PackageKit backend is entirely optional and not installed on MicroOS at all. The reason that PackageKit is pulled with the MicroOS KDE pattern at all is because of plasma5-pk-updates, which is mostly just for showing that updates are available at this point (as installation is broken).
That said, the PackageKit-backend-zypp is extraneous and I'm certainly open to submissions that loosen the coupling between that backend and the PackageKit core.
If PackageKit-backend-zypp is extraneous, there's no backend left which makes PackageKit itself (well, packagekitd) absolutely useless.
Cheers, Fabian
Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team
Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer _______________________________________________ openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
_______________________________________________ openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
On Thu, Dec 3, 2020 at 6:04 AM Fabian Vogt
Hi,
Am Donnerstag, 3. Dezember 2020, 11:54:37 CET schrieb Syds Bearda:
Hi,
On Thu, Dec 3, 2020, at 11:36, Fabian Vogt wrote:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:26:39 CET schrieb Richard Brown:
On Wed, 2020-12-02 at 21:58 +0100, Syds Bearda wrote:
Hi,
New question; I have both KDE and Gnome installed on my system to be able to test them both. However if I try to remove PackageKit it also wants to remove the following patterns/packages:
The following 6 packages are going to be REMOVED: PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE patterns-microos-desktop-gnome patterns-microos-desktop-kde plasma5-pk-updates
Why is PackageKit installed by default by both the Gnome and KDE desktop and what do we need it for? Updates and upgrades are done within transactional-update and are automatically initialised by transactional-update.timer.
Is it safe to remove it from my system, plus should we also remove it from the KDE/Gnome patterns?
Ah thanks for the clarification, I thought PackageKit was necessary for just zypper in/rm/up/dup from Gnome Software/ Discover, but since zypper isn't accessible without transactional-update in MicroOS, I thought it could be removed, didn't know it was also necessary for those GUI installers to work at all.
At least for Discover it's not, so if you don't use GNOME Software you could safely uninstall PackageKit. There's no important package in the "going to be REMOVED:" list, except for the patterns. If you uninstall those, future "zypper rm" calls with "--clean-deps" will try to also remove necessary packages and you won't benefit from new changes to the patterns.
I'm planning to drop the PackageKit dependency of patterns-microos-desktop-kde with the next submission.
I've been working on making PackageKit work with transactional-updates[1], but I'm currently blocked on Ignaz's PR that provides a C++ library to manage this[2]. I'm pretty sure I can get PackageKit working as expected soon afterward for MicroOS. [1]: https://code.opensuse.org/microos/libdnf-plugin-txnupd [2]: https://github.com/openSUSE/transactional-update/pull/31 -- 真実はいつも一つ!/ Always, there's only one truth!
-- Syds Bearda *@syds.eu On Thu, Dec 3, 2020, at 12:57, Neal Gompa wrote:
On Thu, Dec 3, 2020 at 6:04 AM Fabian Vogt
wrote: Hi,
Am Donnerstag, 3. Dezember 2020, 11:54:37 CET schrieb Syds Bearda:
Hi,
On Thu, Dec 3, 2020, at 11:36, Fabian Vogt wrote:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:26:39 CET schrieb Richard Brown:
On Wed, 2020-12-02 at 21:58 +0100, Syds Bearda wrote:
Hi,
New question; I have both KDE and Gnome installed on my system to be able to test them both. However if I try to remove PackageKit it also wants to remove the following patterns/packages:
The following 6 packages are going to be REMOVED: PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE patterns-microos-desktop-gnome patterns-microos-desktop-kde plasma5-pk-updates
Why is PackageKit installed by default by both the Gnome and KDE desktop and what do we need it for? Updates and upgrades are done within transactional-update and are automatically initialised by transactional-update.timer.
Is it safe to remove it from my system, plus should we also remove it from the KDE/Gnome patterns?
Ah thanks for the clarification, I thought PackageKit was necessary for just zypper in/rm/up/dup from Gnome Software/ Discover, but since zypper isn't accessible without transactional-update in MicroOS, I thought it could be removed, didn't know it was also necessary for those GUI installers to work at all.
At least for Discover it's not, so if you don't use GNOME Software you could safely uninstall PackageKit. There's no important package in the "going to be REMOVED:" list, except for the patterns. If you uninstall those, future "zypper rm" calls with "--clean-deps" will try to also remove necessary packages and you won't benefit from new changes to the patterns.
I'm planning to drop the PackageKit dependency of patterns-microos-desktop-kde with the next submission.
I've been working on making PackageKit work with transactional-updates[1], but I'm currently blocked on Ignaz's PR that provides a C++ library to manage this[2]. I'm pretty sure I can get PackageKit working as expected soon afterward for MicroOS.
[1]: https://code.opensuse.org/microos/libdnf-plugin-txnupd [2]: https://github.com/openSUSE/transactional-update/pull/31
Do we have to move away from zypper to DNF for that to work with transactional-updates?
-- 真実はいつも一つ!/ Always, there's only one truth!
On Thu, Dec 3, 2020 at 7:05 AM Syds Bearda
-- Syds Bearda *@syds.eu
On Thu, Dec 3, 2020, at 12:57, Neal Gompa wrote:
On Thu, Dec 3, 2020 at 6:04 AM Fabian Vogt
wrote: Hi,
Am Donnerstag, 3. Dezember 2020, 11:54:37 CET schrieb Syds Bearda:
Hi,
On Thu, Dec 3, 2020, at 11:36, Fabian Vogt wrote:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:26:39 CET schrieb Richard Brown:
On Wed, 2020-12-02 at 21:58 +0100, Syds Bearda wrote: > Hi, > > New question; I have both KDE and Gnome installed on my system to be > able to test them both. However if I try to remove PackageKit it also > wants to remove the following patterns/packages: > > The following 6 packages are going to be REMOVED: > PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE > patterns-microos-desktop-gnome patterns-microos-desktop-kde > plasma5-pk-updates > > Why is PackageKit installed by default by both the Gnome and KDE > desktop and what do we need it for? Updates and upgrades are done > within transactional-update and are automatically initialised by > transactional-update.timer. > > Is it safe to remove it from my system, plus should we also remove it > from the KDE/Gnome patterns?
Ah thanks for the clarification, I thought PackageKit was necessary for just zypper in/rm/up/dup from Gnome Software/ Discover, but since zypper isn't accessible without transactional-update in MicroOS, I thought it could be removed, didn't know it was also necessary for those GUI installers to work at all.
At least for Discover it's not, so if you don't use GNOME Software you could safely uninstall PackageKit. There's no important package in the "going to be REMOVED:" list, except for the patterns. If you uninstall those, future "zypper rm" calls with "--clean-deps" will try to also remove necessary packages and you won't benefit from new changes to the patterns.
I'm planning to drop the PackageKit dependency of patterns-microos-desktop-kde with the next submission.
I've been working on making PackageKit work with transactional-updates[1], but I'm currently blocked on Ignaz's PR that provides a C++ library to manage this[2]. I'm pretty sure I can get PackageKit working as expected soon afterward for MicroOS.
[1]: https://code.opensuse.org/microos/libdnf-plugin-txnupd [2]: https://github.com/openSUSE/transactional-update/pull/31
Do we have to move away from zypper to DNF for that to work with transactional-updates?
As far as I know, there's not a good way to do this with libzypp, but I've also been doing work all over the place in openSUSE because folks have asked me to help make it possible to use DNF everywhere after someone else in the community asked if the openSUSE could switch to DNF package manager stack[3]. As shown in that thread, even upstream projects are unhappy with openSUSE's Zypper package manager. So a lot of my work lately has been to work with the upstream DNF project to support the needs of the SUSE distributions, though currently I'm focused on openSUSE since that's what I can work with. [3]: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/G... -- 真実はいつも一つ!/ Always, there's only one truth!
Hi, Am Donnerstag, 3. Dezember 2020, 12:04:54 CET schrieb Fabian Vogt:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:54:37 CET schrieb Syds Bearda:
Hi,
On Thu, Dec 3, 2020, at 11:36, Fabian Vogt wrote:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:26:39 CET schrieb Richard Brown:
On Wed, 2020-12-02 at 21:58 +0100, Syds Bearda wrote:
Hi,
New question; I have both KDE and Gnome installed on my system to be able to test them both. However if I try to remove PackageKit it also wants to remove the following patterns/packages:
The following 6 packages are going to be REMOVED: PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE patterns-microos-desktop-gnome patterns-microos-desktop-kde plasma5-pk-updates
Why is PackageKit installed by default by both the Gnome and KDE desktop and what do we need it for? Updates and upgrades are done within transactional-update and are automatically initialised by transactional-update.timer.
Is it safe to remove it from my system, plus should we also remove it from the KDE/Gnome patterns?
Ah thanks for the clarification, I thought PackageKit was necessary for just zypper in/rm/up/dup from Gnome Software/ Discover, but since zypper isn't accessible without transactional-update in MicroOS, I thought it could be removed, didn't know it was also necessary for those GUI installers to work at all.
At least for Discover it's not, so if you don't use GNOME Software you could safely uninstall PackageKit. There's no important package in the "going to be REMOVED:" list, except for the patterns. If you uninstall those, future "zypper rm" calls with "--clean-deps" will try to also remove necessary packages and you won't benefit from new changes to the patterns.
I'm planning to drop the PackageKit dependency of patterns-microos-desktop-kde with the next submission.
I tried that and it works as expected: PackageKit isn't pulled in anymore and discover still works fine. It shows up with a "Nothing installed" page though, which looks a bit weird and obviously there aren't any update notifications anymore. Now I'd like to have PackageKit installed by default, but optional, but that's only possible without solver.onlyrequires on, which is forced off by MicroOS and thus not an option. Thoughts? Cheers, Fabian
Cheers, Fabian
I was just surprised that when I typed zypper ref by mistake I had to wait for PackageKit to finish.
In GNOME, PackageKit is a key requirement for gnome-software, which is our intended tool for installing flatpaks.
So no, it's not safe to remove from your system unless you don't want a graphical way of installing user applications.
I believe for KDE it's equally important for discover, which does the equivalent job to gnome-software for that DE.
No, Discover's PackageKit backend is entirely optional and not installed on MicroOS at all. The reason that PackageKit is pulled with the MicroOS KDE pattern at all is because of plasma5-pk-updates, which is mostly just for showing that updates are available at this point (as installation is broken).
That said, the PackageKit-backend-zypp is extraneous and I'm certainly open to submissions that loosen the coupling between that backend and the PackageKit core.
If PackageKit-backend-zypp is extraneous, there's no backend left which makes PackageKit itself (well, packagekitd) absolutely useless.
Cheers, Fabian
Regards,
openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
_______________________________________________ openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
Hi all, What about using this new app Souk as the preferred GUI to install flatpaks. No more need for either Gnome Software or Discover. Only thing it would miss is the system updates. But I think that would be better suited with a notification from the standard email for a new snapshot. https://www.omgubuntu.co.uk/2020/12/souk-flatpak-app-store-for-linux Cheers, Syds On Thu, Dec 3, 2020, at 16:09, Fabian Vogt wrote:
Hi,
Am Donnerstag, 3. Dezember 2020, 12:04:54 CET schrieb Fabian Vogt:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:54:37 CET schrieb Syds Bearda:
Hi,
On Thu, Dec 3, 2020, at 11:36, Fabian Vogt wrote:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:26:39 CET schrieb Richard Brown:
On Wed, 2020-12-02 at 21:58 +0100, Syds Bearda wrote:
Hi,
New question; I have both KDE and Gnome installed on my system to be able to test them both. However if I try to remove PackageKit it also wants to remove the following patterns/packages:
The following 6 packages are going to be REMOVED: PackageKit PackageKit-backend-zypp PackageKit-branding-openSUSE patterns-microos-desktop-gnome patterns-microos-desktop-kde plasma5-pk-updates
Why is PackageKit installed by default by both the Gnome and KDE desktop and what do we need it for? Updates and upgrades are done within transactional-update and are automatically initialised by transactional-update.timer.
Is it safe to remove it from my system, plus should we also remove it from the KDE/Gnome patterns?
Ah thanks for the clarification, I thought PackageKit was necessary for just zypper in/rm/up/dup from Gnome Software/ Discover, but since zypper isn't accessible without transactional-update in MicroOS, I thought it could be removed, didn't know it was also necessary for those GUI installers to work at all.
At least for Discover it's not, so if you don't use GNOME Software you could safely uninstall PackageKit. There's no important package in the "going to be REMOVED:" list, except for the patterns. If you uninstall those, future "zypper rm" calls with "--clean-deps" will try to also remove necessary packages and you won't benefit from new changes to the patterns.
I'm planning to drop the PackageKit dependency of patterns-microos-desktop-kde with the next submission.
I tried that and it works as expected: PackageKit isn't pulled in anymore and discover still works fine. It shows up with a "Nothing installed" page though, which looks a bit weird and obviously there aren't any update notifications anymore.
Now I'd like to have PackageKit installed by default, but optional, but that's only possible without solver.onlyrequires on, which is forced off by MicroOS and thus not an option.
Thoughts?
Cheers, Fabian
Cheers, Fabian
I was just surprised that when I typed zypper ref by mistake I had to wait for PackageKit to finish.
In GNOME, PackageKit is a key requirement for gnome-software, which is our intended tool for installing flatpaks.
So no, it's not safe to remove from your system unless you don't want a graphical way of installing user applications.
I believe for KDE it's equally important for discover, which does the equivalent job to gnome-software for that DE.
No, Discover's PackageKit backend is entirely optional and not installed on MicroOS at all. The reason that PackageKit is pulled with the MicroOS KDE pattern at all is because of plasma5-pk-updates, which is mostly just for showing that updates are available at this point (as installation is broken).
That said, the PackageKit-backend-zypp is extraneous and I'm certainly open to submissions that loosen the coupling between that backend and the PackageKit core.
If PackageKit-backend-zypp is extraneous, there's no backend left which makes PackageKit itself (well, packagekitd) absolutely useless.
Cheers, Fabian
Regards,
openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
_______________________________________________ openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
On Wed, 2020-12-09 at 22:18 +0100, Syds Bearda wrote:
Hi all,
What about using this new app Souk as the preferred GUI to install flatpaks. No more need for either Gnome Software or Discover.
Only thing it would miss is the system updates. But I think that would be better suited with a notification from the standard email for a new snapshot.
https://www.omgubuntu.co.uk/2020/12/souk-flatpak-app-store-for-linux
Cheers, Syds
I'm certainly interested in that instead of gnome-software Do you know if it supports fwupd/firmware updates?
On Thu, Dec 10, 2020 at 4:36 AM Richard Brown
On Wed, 2020-12-09 at 22:18 +0100, Syds Bearda wrote:
Hi all,
What about using this new app Souk as the preferred GUI to install flatpaks. No more need for either Gnome Software or Discover.
Only thing it would miss is the system updates. But I think that would be better suited with a notification from the standard email for a new snapshot.
https://www.omgubuntu.co.uk/2020/12/souk-flatpak-app-store-for-linux
Cheers, Syds
I'm certainly interested in that instead of gnome-software
Do you know if it supports fwupd/firmware updates?
It is only for Flatpaks. It handles nothing else. -- 真実はいつも一つ!/ Always, there's only one truth!
On Wed, 2020-12-09 at 22:18 +0100, Syds Bearda wrote:
Hi all,
What about using this new app Souk as the preferred GUI to install flatpaks. No more need for either Gnome Software or Discover.
Only thing it would miss is the system updates. But I think that would be better suited with a notification from the standard email for a new snapshot.
https://www.omgubuntu.co.uk/2020/12/souk-flatpak-app-store-for-linux
Cheers, Syds
On Thu, Dec 3, 2020, at 16:09, Fabian Vogt wrote:
Hi,
Am Donnerstag, 3. Dezember 2020, 12:04:54 CET schrieb Fabian Vogt:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:54:37 CET schrieb Syds Bearda:
Hi,
On Thu, Dec 3, 2020, at 11:36, Fabian Vogt wrote:
Hi,
Am Donnerstag, 3. Dezember 2020, 11:26:39 CET schrieb Richard Brown:
On Wed, 2020-12-02 at 21:58 +0100, Syds Bearda wrote: > Hi, > > New question; I have both KDE and Gnome installed on my > system to be > able to test them both. However if I try to remove > PackageKit it also > wants to remove the following patterns/packages: > > The following 6 packages are going to be REMOVED: > PackageKit PackageKit-backend-zypp PackageKit-branding- > openSUSE > patterns-microos-desktop-gnome patterns-microos- > desktop-kde > plasma5-pk-updates > > Why is PackageKit installed by default by both the Gnome > and KDE > desktop and what do we need it for? Updates and upgrades > are done > within transactional-update and are automatically > initialised by > transactional-update.timer. > > Is it safe to remove it from my system, plus should we > also remove it > from the KDE/Gnome patterns?
Ah thanks for the clarification, I thought PackageKit was necessary for just zypper in/rm/up/dup from Gnome Software/ Discover, but since zypper isn't accessible without transactional-update in MicroOS, I thought it could be removed, didn't know it was also necessary for those GUI installers to work at all.
At least for Discover it's not, so if you don't use GNOME Software you could safely uninstall PackageKit. There's no important package in the "going to be REMOVED:" list, except for the patterns. If you uninstall those, future "zypper rm" calls with "--clean-deps" will try to also remove necessary packages and you won't benefit from new changes to the patterns.
I'm planning to drop the PackageKit dependency of patterns- microos-desktop-kde with the next submission.
I tried that and it works as expected: PackageKit isn't pulled in anymore and discover still works fine. It shows up with a "Nothing installed" page though, which looks a bit weird and obviously there aren't any update notifications anymore.
Now I'd like to have PackageKit installed by default, but optional, but that's only possible without solver.onlyrequires on, which is forced off by MicroOS and thus not an option.
Thoughts?
Cheers, Fabian
Cheers, Fabian
I was just surprised that when I typed zypper ref by mistake I had to wait for PackageKit to finish.
In GNOME, PackageKit is a key requirement for gnome- software, which is our intended tool for installing flatpaks.
So no, it's not safe to remove from your system unless you don't want a graphical way of installing user applications.
I believe for KDE it's equally important for discover, which does the equivalent job to gnome-software for that DE.
No, Discover's PackageKit backend is entirely optional and not installed on MicroOS at all. The reason that PackageKit is pulled with the MicroOS KDE pattern at all is because of plasma5-pk-updates, which is mostly just for showing that updates are available at this point (as installation is broken).
That said, the PackageKit-backend-zypp is extraneous and I'm certainly open to submissions that loosen the coupling between that backend and the PackageKit core.
If PackageKit-backend-zypp is extraneous, there's no backend left which makes PackageKit itself (well, packagekitd) absolutely useless.
Cheers, Fabian
Regards,
openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
_______________________________________________ openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
_______________________________________________ openSUSE Kubic mailing list -- kubic@lists.opensuse.org To unsubscribe, email kubic-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org
-- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
participants (4)
-
Fabian Vogt
-
Neal Gompa
-
Richard Brown
-
Syds Bearda