Hi, folks. For QA purposes, I wanted to get some clarification on the current status of package management and updating on KDE.
It seems that recently dnfdragora-gui was added to the KDE spin. This has at least one, obvious, unfortunate consequence: when booting KDE live, there's a completely out-of-place (because it's in full color, while every other KDE systray icon is in black-and-white) permanent 'notification' icon for 'dnfdragora-updater', which doesn't seem to be of any use in a live environment.
Beyond this: what's the actual intended shape of package management and updates on KDE now? Is dnfdragora supposed to be responsible for all of it, or is...some other thing...supposed to handle updating, and dnfdragora is only supposed to be there for installing / removing?
As a reminder, this release criterion is in effect at Beta:
"The installed system must be able to download and install updates with the default graphical package manager in all release-blocking desktops."
and this one at Final:
"Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image."
So it'd be good to have the story here clear and be sure the criteria are met ASAP.
Thanks!
On Tue, 2017-05-09 at 13:19 -0700, Adam Williamson wrote:
Hi, folks. For QA purposes, I wanted to get some clarification on the current status of package management and updating on KDE.
It seems that recently dnfdragora-gui was added to the KDE spin. This has at least one, obvious, unfortunate consequence: when booting KDE live, there's a completely out-of-place (because it's in full color, while every other KDE systray icon is in black-and-white) permanent 'notification' icon for 'dnfdragora-updater', which doesn't seem to be of any use in a live environment.
Beyond this: what's the actual intended shape of package management and updates on KDE now? Is dnfdragora supposed to be responsible for all of it, or is...some other thing...supposed to handle updating, and dnfdragora is only supposed to be there for installing / removing?
As a reminder, this release criterion is in effect at Beta:
"The installed system must be able to download and install updates with the default graphical package manager in all release-blocking desktops."
and this one at Final:
"Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image."
So it'd be good to have the story here clear and be sure the criteria are met ASAP.
Thanks!
I've now checked an installed system; it seems like *both* dnfdragora and the previous update manager are checking for updates. I saw a '48 updates available' message pop up above the dnfdragora icon, and there's also the 'up-arrow-in-a-circle' icon, with the tooltip:
Software Updates You have 48 new updates
This probably isn't what's intended, is it?
On Tue, May 9, 2017 at 4:41 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Tue, 2017-05-09 at 13:19 -0700, Adam Williamson wrote:
Hi, folks. For QA purposes, I wanted to get some clarification on the current status of package management and updating on KDE.
It seems that recently dnfdragora-gui was added to the KDE spin. This has at least one, obvious, unfortunate consequence: when booting KDE live, there's a completely out-of-place (because it's in full color, while every other KDE systray icon is in black-and-white) permanent 'notification' icon for 'dnfdragora-updater', which doesn't seem to be of any use in a live environment.
Beyond this: what's the actual intended shape of package management and updates on KDE now? Is dnfdragora supposed to be responsible for all of it, or is...some other thing...supposed to handle updating, and dnfdragora is only supposed to be there for installing / removing?
As a reminder, this release criterion is in effect at Beta:
"The installed system must be able to download and install updates with the default graphical package manager in all release-blocking desktops."
and this one at Final:
"Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image."
So it'd be good to have the story here clear and be sure the criteria are met ASAP.
Thanks!
I've now checked an installed system; it seems like *both* dnfdragora and the previous update manager are checking for updates. I saw a '48 updates available' message pop up above the dnfdragora icon, and there's also the 'up-arrow-in-a-circle' icon, with the tooltip:
Software Updates You have 48 new updates
This probably isn't what's intended, is it?
(CC'ing Bjorn Esser, maintainer of dnfdragora in Fedora)
Most likely not. The "dnfdragora-gui" package needs to be renamed to "dnfdragora-updater" and then removed from the default install in favor of "dnfdragora" itself, since we switched to rich dependencies to correctly install the libyui things. "dnfdragora-gui" will need to be provided by "dnfdragora" so that the rich deps still resolve as expected.
Neal Gompa wrote:
"dnfdragora-gui" will need to be provided by "dnfdragora" so that the rich deps still resolve as expected.
The rich deps don't actually mention dnfdragora at all, only libyui/libyui-mga and qt5-qtbase-gui/gtk3/ncurses-libs. I think the name dnfdragora-gui can just go away, or more likely be Obsoleted/Provided by dnfdragora-updater.
Kevin Kofler
On Tue, May 9, 2017 at 6:38 PM, Kevin Kofler kevin.kofler@chello.at wrote:
Neal Gompa wrote:
"dnfdragora-gui" will need to be provided by "dnfdragora" so that the rich deps still resolve as expected.
The rich deps don't actually mention dnfdragora at all, only libyui/libyui-mga and qt5-qtbase-gui/gtk3/ncurses-libs. I think the name dnfdragora-gui can just go away, or more likely be Obsoleted/Provided by dnfdragora-updater.
If we move the "dnfdragora-gui" name to "dnfdragora", then the kickstarts don't need to be adjusted again.
-
Adam Williamson -
Kevin Kofler -
Neal Gompa