http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c1 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org --- Comment #1 from Dominique Leuenberger --- FTR: this starts with implementing the 'dist-upgrade' role in PK/zypp -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c3 --- Comment #3 from Dominique Leuenberger --- (In reply to Bernhard Wiedemann from comment #2)

could be made zypper dup --no-recommends --no-allow-vendor-change

nope - it should follow your pre-setup configuration from /etc/zypp.conf - nothing more, nothing less of course 'pkcon' can take any number of arbitrary parameters in plus: but the PK/zypp backend must not set any such values -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c5 --- Comment #5 from Dominique Leuenberger --- (In reply to Bernhard Wiedemann from comment #4)

unfortunately, /etc/zypp/zypp.conf does not allow to configure no-recommends only for upgrades, but not for newly installed packages

That is not up to PK to fix - please file a feature request against libzypp for that -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c6 Code Struct changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |codestruct@posteo.org --- Comment #6 from Code Struct --- I got use the Packman Repository which is recommended if one wants to use some Multimedia packages. What is the recommended way to get security patches? I currently use: $ zypper refresh $ zypper dup --no-allow-vendor-change $ zypper dup --no-allow-vendor-change --from "Packman Repository" Is this correct? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 Frank Kruger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger@mailbox.org -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1093693 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 Oliver Kurz changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1090505 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c8 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sonichedgehog_hyperblast00@ | |yahoo.com --- Comment #8 from Wolfgang Bauer --- *** Bug 1098922 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 Sébastien GUÉRIN changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastien.guerin.news@gmail | |.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c10 John Shand changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jshand2013@gmail.com --- Comment #10 from John Shand --- this would also be brilliant for KDE/Plasma -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c12 --- Comment #12 from simon izor --- "I got use the Packman Repository which is recommended if one wants to use some Multimedia packages. What is the recommended way to get security patches? I currently use: $ zypper refresh $ zypper dup --no-allow-vendor-change $ zypper dup --no-allow-vendor-change --from "Packman Repository" Is this correct?" zypper dup is all you really need to do. It will refresh repos marked as autorefresh and --no-allow-vendor-change is default in Tumbleweed now. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c14 --- Comment #14 from Aleksey Kontsevich ---

Removing it altogether would cripple the GNOME Software which I find quite useful. Consider patching PackageKit's source code instead so its' upgrade-system functionality would either use zypper dup or throw error message like "sorry, openSUSE Tumbleweed's zypper dup is not supported yet". Thank you in advance.

And good to add something like "Update package list" button to rescan available packages which is not available with 'zypper dup' message. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 Michele Cherici changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |one@contezero.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c17 --- Comment #17 from Michele Cherici --- (In reply to Wolfgang Bauer from comment #16)

Apparently this has been implemented now: https://lists.opensuse.org/opensuse-factory/2019-02/msg00485.html https://build.opensuse.org/request/show/676261

I think that KDE Plasma applet for software updates should be modified to support the new behavior: https://build.opensuse.org/package/show/openSUSE%3AFactory/plasma5-pk-update... https://build.opensuse.org/package/view_file/openSUSE:Factory/plasma5-pk-upd... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c19 --- Comment #19 from Mircea Kitsune --- (In reply to Wolfgang Bauer from comment #18)

Yes, I suppose we can drop that patch (that disabled installing updates on Tumbleweed) now again.

I would really appreciate that! I've completely disabled the software updates applet since that change, as it literally made the updater useless on Tumbleweed. I'd like to be able to enable it once more, and to use the applet instead of running 'zypper dup' manually from the console whenever I happen to remember "maybe it's time to check if there are new updates again". -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c21 --- Comment #21 from Wolfgang Bauer --- (In reply to Michele Cherici from comment #20)

But I've found a misbehavior, plasma5-pk-updates want to update packages with a vendor change, so it does not respect the zypp.conf default value solver.allowVendorChange = false

Erm, "solver.allowVendorChange" has no influence on "zypper dup" either, there's "solver.dupAllowVendorChange" for that. No idea if that option would work here though... (I don't use Tumbleweed) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c23 --- Comment #23 from Michele Cherici --- I've done more tests and the problem does not happens always. Steps to replicate with Tumbleweed 20190219 snapshot: - use plasma5-pk-updates without patch https://build.opensuse.org/package/view_file/openSUSE:Factory/plasma5-pk-upd... - verify that the installed version of sddm package is 0.18.0-6.1 from OSS repository (if the version is 0.18.0-8.1 than downgrade it) - updater applet should show the available update for sddm package (0.18.0-8.1 from http://download.opensuse.org/update/tumbleweed/) - do the update for sddm from the applet - after the update the applet will show to you the available updates that require a vendor change (it shows the same updates available with the command zypper dup --allow-vendor-change) - if you reboot, the updater applet shows no updates available (so it uses the right solver now) It seems that after the package update from Tumbleweed repository the applet wrongly refresh the list of available updates and do not respect the solver.dupAllowVendorChange = false config Please let me know if someone else is able to replicate the problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c25 Stasiek Michalski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |hellcp@mailbox.org --- Comment #25 from Stasiek Michalski --- There is a bunch of stuff I want to answer here, so stay with me: (In reply to Dominique Leuenberger from comment #1)

FTR: this starts with implementing the 'dist-upgrade' role in PK/zypp

Not necessarily, but it will need to be implemented for Leap anyway. Now that Ludwig pushed for releasever this also will be easier, but not the easiest considering our repos tend to change repo names and links and other associated data depending on installation, we should instead ship a file with repos that defines all the values properly (that's also associated with zypper bug which causes it to change names and other values of repos by itself). (In reply to Fabian Vogt from comment #7)

While "pkcon get-distro-upgrades" seems to be implemented, it always returns an empty set of changes.

Changing priority to "major" as this can lead to broken updates as the usual graphical applets and updaters are not aware of this.

Packagekit's method for that is implemented only to check product.d for possible upgrades, we do not ship that data in product.d anymore. Precise specification of this was written few years ago: https://old-en.opensuse.org/Product_Management/Code11/Upgrade I also suggested improvements to that method: https://lists.opensuse.org/opensuse-factory/2019-01/msg00032.html (In reply to Michele Cherici from comment #23)

I've done more tests and the problem does not happens always.

Steps to replicate with Tumbleweed 20190219 snapshot: - use plasma5-pk-updates without patch https://build.opensuse.org/package/view_file/openSUSE:Factory/plasma5-pk- updates/0001-Hide-option-to-install-updates-on-Tumbleweed.patch?expand=1 - verify that the installed version of sddm package is 0.18.0-6.1 from OSS repository (if the version is 0.18.0-8.1 than downgrade it) - updater applet should show the available update for sddm package (0.18.0-8.1 from http://download.opensuse.org/update/tumbleweed/) - do the update for sddm from the applet - after the update the applet will show to you the available updates that require a vendor change (it shows the same updates available with the command zypper dup --allow-vendor-change) - if you reboot, the updater applet shows no updates available (so it uses the right solver now)

It seems that after the package update from Tumbleweed repository the applet wrongly refresh the list of available updates and do not respect the solver.dupAllowVendorChange = false config

Please let me know if someone else is able to replicate the problem.

That is more or less intended behaviour from the pov of showing updates, solver there isn't switched to doUpgrade, performs simulated doUpdate, which causes it to only show updates that would be performed if product package wasn't at newer release in resolvables list (basically shows updates as if they were in :Update repo). Obviously we want to keep both possibilities open, :Update, albeit rarely is still used for critical TW updates. Fixable, but not system breaking. As for PackageKit allowing for vendor change, that's libzypp bug. On switching solver mode to Upgrade, it doesn't inherit options from doUpgrade solver (even though it __should__ be the same solver behaviour). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c27 --- Comment #27 from Stasiek Michalski --- (In reply to Michele Cherici from comment #26)

...

(In reply to Michele Cherici from comment #23)

...

I've done more tests and the problem does not happens always.

Steps to replicate with Tumbleweed 20190219 snapshot: - use plasma5-pk-updates without patch https://build.opensuse.org/package/view_file/openSUSE:Factory/plasma5-pk- updates/0001-Hide-option-to-install-updates-on-Tumbleweed.patch?expand=1 - verify that the installed version of sddm package is 0.18.0-6.1 from OSS repository (if the version is 0.18.0-8.1 than downgrade it) - updater applet should show the available update for sddm package (0.18.0-8.1 from http://download.opensuse.org/update/tumbleweed/) - do the update for sddm from the applet - after the update the applet will show to you the available updates that require a vendor change (it shows the same updates available with the command zypper dup --allow-vendor-change) - if you reboot, the updater applet shows no updates available (so it uses the right solver now)

It seems that after the package update from Tumbleweed repository the applet wrongly refresh the list of available updates and do not respect the solver.dupAllowVendorChange = false config

Please let me know if someone else is able to replicate the problem.

That is more or less intended behaviour from the pov of showing updates, solver there isn't switched to doUpgrade, performs simulated doUpdate, which causes it to only show updates that would be performed if product package wasn't at newer release in resolvables list (basically shows updates as if they were in :Update repo). Obviously we want to keep both possibilities open, :Update, albeit rarely is still used for critical TW updates. Fixable, but not system breaking.

As for PackageKit allowing for vendor change, that's libzypp bug. On switching solver mode to Upgrade, it doesn't inherit options from doUpgrade solver (even though it __should__ be the same solver behaviour).

The problem is not related to :Update repository, I've added it to the steps list because it's easier to repoduce the problem. The problem happens also if you update another package from a different repository, I've reproduced the bug with a package update form my home repo.

It seems that libzypp use the right solver (dupAllowVendorChange = false) for the first package update, than it refresh the list of available packages but it uses dupAllowVendorChange = true

Hm, I will try to reproduce it, but overall list of updates will not always be 1:1 to what packagekit will end up doing during actual update. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c29 Hadrien Grasland changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grasland@lal.in2p3.fr --- Comment #29 from Hadrien Grasland --- Just wanted to point out that the --allow-vendor -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c31 --- Comment #31 from Wolfgang Bauer --- (In reply to Michele Cherici from comment #28)

With snapshot 20190224 I've found a new problem while trying to update with plasma5-pk-updates The update in not executed and a notification appears: "You've to agree/decline a license" But the notification only contain the error message so you cannot advance with the update.

AFAIK, plasma5-pk-updates just doesn't support showing license agreements to the user. That was not a problem so far, as IIANM they were disabled in PackageKit's zypp backend itself anyway after they caused it to just hang. See https://bugs.freedesktop.org/show_bug.cgi?id=89651 and bug#908730 here. So apparently this got fixed meanwhile? We'd have the very same problem in Leap then... No idea if that change will be in 15.x, but certainly 16.x I suppose. (although the one or two packages that require a license agreement wouldn't get updated that often there of course, if at all) Would you care to file a new bug report about this please? (against KDE Workspace) Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c33 --- Comment #33 from Wolfgang Bauer ---

plasma5-pk-updates has not showed the license agreement to me, it has only showed the notification with the error message.

I think that in this case the problem is not the applet

It is a problem with the applet (I think), because the applet doesn't have any code to show the license agreement (I think).

but the Mesa-dri-nouveau package and how the license agreement is handled by zypper. Why zypper show the license agreement and the user have to accept it?

That has been done by the Mesa/Xorg package maintainers because there were (and probably still are) big problems with nouveau. The biggest one was that QtWebEngine crashed very often, we patched it to use software rendering only on nouveau to avoid that though.

That license was already accepted when the package was installed the first time, so why the license is showed for every update?

Well, handling this with a license agreement is probably not the best way. That's a packaging "problem" though.

This happened to me only for the Mesa-dri-nouveau package, Flash player does not require a license agreement for updates.

Flash player has been dropped from the distribution years ago. I think the only other package that requires a license agreement is AdobeICCProfiles. All of that is quite unrelated to this bug report though... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c35 --- Comment #35 from Stasiek Michalski --- (In reply to Michele Cherici from comment #34)

...

All of that is quite unrelated to this bug report though...

Bug title is 'PackageKit should use "zypper dup" instead of "zypper up" on Tumbleweed'. I've listed some misbehavior that happens when "zypper dup" is used form plasma5-pk-update though PackageKit so they are related to this bug report IMHO.

Anyway up to now nobody else have replied confirming the problems that I've found in my Tumbleweed installations, so it's possible that there is something wrong with my setup.

That is a bug in pk implementation of plasma-pk-update, not pk-backend-zypp, I would recommend reporting this to KDE upstream, not here. It is our fault that we have EULA agreements on update, but there is a valid reason for keeping it there, as mentioned before. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c37 --- Comment #37 from Wolfgang Bauer --- PS, for completeness: PackageKit in Leap (up to 15.1 at least) does indeed have license agreements disabled: https://build.opensuse.org/package/view_file/openSUSE:Leap:15.1:Update/Packa... This patch has been removed in Tumbleweed recently so license agreements are necessary again. https://build.opensuse.org/request/show/661478 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c38 --- Comment #38 from Michele Cherici --- (In reply to Stasiek Michalski from comment #35)

(In reply to Michele Cherici from comment #34)

...

...

All of that is quite unrelated to this bug report though...

Bug title is 'PackageKit should use "zypper dup" instead of "zypper up" on Tumbleweed'. I've listed some misbehavior that happens when "zypper dup" is used form plasma5-pk-update though PackageKit so they are related to this bug report IMHO.

Anyway up to now nobody else have replied confirming the problems that I've found in my Tumbleweed installations, so it's possible that there is something wrong with my setup.

That is a bug in pk implementation of plasma-pk-update, not pk-backend-zypp, I would recommend reporting this to KDE upstream, not here. It is our fault that we have EULA agreements on update, but there is a valid reason for keeping it there, as mentioned before.

I've rolled back mesa to previous version (18.3.2) to replicate the update "with license confirmation", but this time I've used pkcon command line to do the update: pkcon update the result has been a pkcon crash (without showing the license). I've repeated the same command a second time and it has showed the license agreement but it crashed after user input. I've repeated "pkcon update" a third time and it worked without crash. It seems that also pkcon has some problem when there is an EULA to show, or it's also possible that the crashes are not related, I don't know, I rarely use pkcon. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c40 --- Comment #40 from Wolfgang Bauer --- (In reply to Aleksey Kontsevich from comment #39)

What it the problem to add --auto-agree-with-licenses to zypper dup command?

What does zypper have to do with it? This is about PackageKit. (and no, PackageKit does *not* run zypper) And the crash with pkcon should be reported separately as well. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c42 --- Comment #42 from Jonathan Kang --- (In reply to Wolfgang Bauer from comment #33)

...

plasma5-pk-updates has not showed the license agreement to me, it has only showed the notification with the error message.

I think that in this case the problem is not the applet

It is a problem with the applet (I think), because the applet doesn't have any code to show the license agreement (I think).

Agreeded. gpk-update-viewer which is the "applet" in GNOME environment. And it handles the EULAs nicely with the latest fixes. -- You are receiving this mail because: You are on the CC list for the bug.

Please report a new bug against that UI then, thanks :D Think it related to this bug as well: pkcon get-updates

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c54 Aleksey Kontsevich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #54 from Aleksey Kontsevich --- (In reply to Stasiek Michalski from comment #51) +

pkcon refresh now also shows these 251 packages which were updated long time ago. Only running these commands twice, solves the problem which is VERY inconvenient.

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c56 --- Comment #56 from Aleksey Kontsevich --- (In reply to Aleksey Kontsevich from comment #55)

...

pkcon update -y

...

pkcon refresh solves issue temporarily only till next updates available.

Now even above does not help. :) Please fix! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c58 Cristiano Guadagnino changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |criguada+opensuse@gmail.com --- Comment #58 from Cristiano Guadagnino --- Created attachment 818962 --> http://bugzilla.opensuse.org/attachment.cgi?id=818962&action=edit Screenshot shows the problem with the Software Updates widget in KDE I have to confirm the bug reported by Michele Cherici: I've always felt uncomfortable updating Tumbleweed by using the Software Updates widget in KDE, but yesterday I decided to give it a spin. After the first update, the widget presented me immediately with another batch of updates, which I found unusual. So I checked by using the usual "zypper dup", which found no updates. After a bit of investigation, I found the reason: I have configured zypper not to offer updates when the update would imply a change of vendors (solver.dupAllowVendorChange = false), but the widget apparently does not follow the same criteria and presents me with updates involving vendor change. At the time of the problem I was on Tumbleweed 20190916 I believe. In the attached screenshot (sorry, it is in the Italian language) you can see that 'zypper dup' show no updates, while the widget shows 50 updates. You can also see that the first proposed package update (bubblewrap) could actually be updated by changing the vendor from openSUSE-Tubleweed-Oss to home:opensuseitalia (which shouldn't be allowed). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1030829 http://bugzilla.opensuse.org/show_bug.cgi?id=1030829#c60 --- Comment #60 from Aleksey Kontsevich --- (In reply to Michele Cherici from comment #59)

Hi Cristiano, I've developed a KDE plasmoid for openSUSE Tumbleweed that uses zypper as backend (inside a screen session) and it can handle both EULA agreements and interactive package conflicts resolution, if you want to try it you can find more info at this page: https://www.contezero.com/linux/kde-plasma-software-updater-opensuse- tumbleweed

openSUSE Build Service project page: https://build.opensuse.org/package/show/home:alucardx:plasma/tw-updater- plasmoid

Thanks, could be installed from here as well: https://software.opensuse.org/package/tw-updater-plasmoid?search_term=tw-upd... -- You are receiving this mail because: You are on the CC list for the bug.