http://bugzilla.opensuse.org/show_bug.cgi?id=1154973 http://bugzilla.opensuse.org/show_bug.cgi?id=1154973#c1 Nathaniel Graham changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pointedstick@zoho.com --- Comment #1 from Nathaniel Graham --- IMO the problem here is mostly a matter of communication. If installing or removing a package truly does require the installation of pending updates first, this must be communicated to the user so they can decide whether they're ready to install the updates. That communication must be done both via the pkcon CLI and also using the API, so that software center apps like Discover and GNOME Software can present an appropriate message to the user. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1154973 http://bugzilla.opensuse.org/show_bug.cgi?id=1154973#c2 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com Component|libzypp |GNOME Assignee|zypp-maintainers@suse.de |gnome-bugs@suse.de --- Comment #2 from Fabian Vogt --- zypper does not have this behaviour, so reassigning to PackageKit. There are some (related?) fixes in the latest version of PackageKit, but it had to be reverted as it caused a severe regression. It would be interesting to know whether the same issue also happens on Leap (older PK and different libzypp upgrade mode). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1154973 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1154973 http://bugzilla.opensuse.org/show_bug.cgi?id=1154973#c7 --- Comment #7 from Fabian Vogt --- (In reply to Jonathan Kang from comment #6)

It's mainly about when to set and reset upgradeMode.

Running "pkcon update" leads to calling get-updates and update-packages. A list of update candidates will be passed from get-updates to update-packages.

* If upgradeMode is set in get-updates and reset to FALSE when it's done, update-packages won't be able to perform a dup-like action in Tumbleweed. * If upgradeMode is set in get-updates and not reset when finished, removing/ installing packages will lead to a full dup-style system upgrade in Tumbleweed. * We can try to set upgradeMode in update-packages, but update-packages is responsible for updating specific packages and upgrading the whole system.

I see two options: a) A hack: Let get-updates a fake "this-is-a-dup" package as marker which is passed to update-packages later. b) Just not support update-packages on its own on TW. Picking out just a few packages from a new snapshot is not guaranteed to work anyway. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1154973 http://bugzilla.opensuse.org/show_bug.cgi?id=1154973#c9 --- Comment #9 from Fabian Vogt --- (In reply to Jonathan Kang from comment #8)

Emm. One of the problems in the zypp backend is many methods like install-packages, install-files and remove-packages calls solver.resolvePool. So as long as upgradeMode is set to TRUE and not reset in time, calling those methods leads to a full system upgrade in Tumbleweed.

I understand that. Why not set the upgrade mode correctly before each transaction? Having a timer is a really ugly hack with disastrous consequences, which this report clearly shows. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1154973 http://bugzilla.opensuse.org/show_bug.cgi?id=1154973#c11 --- Comment #11 from Fabian Vogt --- (In reply to Jonathan Kang from comment #10)

(In reply to Fabian Vogt from comment #9)

...

I understand that. Why not set the upgrade mode correctly before each transaction? Having a timer is a really ugly hack with disastrous consequences, which this report clearly shows.

It's mainly because the way PackageKit works doesn't give zypp backend too much information about what's really happening. For example: "pkcon get-updates" calls get-updates where upgradeMode is set and reset after it's finished. While "pkcon update" calls get-updates and update-packages. As upgradeMode is set and reset in get-updates, resolvPool in updates-packages is run under upgradeMode is FALSE, which makes "pkcon update" unable to do a dup-style update.

Which means the two options I suggested in comment 7 would work just fine, wouldn't they? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1154973 Jonathan Kang changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gnome-bugs@suse.de |songchuan.kang@suse.com -- You are receiving this mail because: You are on the CC list for the bug.