https://bugs.kde.org/show_bug.cgi?id=461385
--- Comment #56 from gaetano giunta <[email protected]> --- > We need as for zypper an option "automatically answer yes for the acceptance > of a license" Just to be clear - in my case, I do get shown the EULA by Discover in a popup dialog, and I click to accept it. It's just that this acceptance does not seem to be taken into account / forwarded to the appropriate component, and the updates do not install. If I get it right, what is needed is to fix how Discover communicates to Zypper "the user did accepted the license", which is not necessarily the same as "always answer yes for licenses", as the latter probably would preclude the eula being shown at all? (and I'd rather be asked and have to accept manually rather than blanket-accepting anything) > With openSUSE I do not use Discover. > I use the services : "os-update" and "update-system-flatpaks" I never heard of those - are they daemon-style services or GUI apps? OT opinion: as a complete newcomer to Suse and KDE, I found the KDE system settings apps mostly a breeze to use, but have been quite baffled by the apparent redundancy and overlap between the two (or more) "system management layers". It seems that YaST does duplicates a lot of the System Settings functionality, and there is no clear distinction of when to use one vs the other. In fact, in some cases, functionality is available on both sides, but only one side works (f.e. after install I could not manage to get new locales/translations set up via KDE, but I could via YaST...). This is of course not an ideal situation - and funnily similar to the "control panel" experience in Windows ;-) I know that Suse has now deprecated YaST in favour of Cokpit, so going forward there is probably going to be a lot of churn (with KDE having to remove all its integrations with YaST) to still end up with two separate management systems :-( Looking at the issue tracker for Discover, I realised how complicated its job is - having to deal with multiple sources/types of installation packages (flatpack vs. native) but also multiple backends (dnf vs. apt vs. zypper). I don't have any specific suggestions for how to improve that, but it does seem that the developers have set themselves up for a very complicated task. I wonder if focusing on perfect integration on a single distro would be a more fruitful approach... -- You are receiving this mail because: You are watching all bug changes.
