[Bug 1204467] New: Update fail
http://bugzilla.opensuse.org/show_bug.cgi?id=1204467 Bug ID: 1204467 Summary: Update fail Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs@suse.de Reporter: creamsoda.e2@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 862258 --> http://bugzilla.opensuse.org/attachment.cgi?id=862258&action=edit Update Error Hello! Due to the fact that some one update (package) does not want to be updated, all other packages are not updated at once. There may be 100 updates, but because 1 update is not installed, the remaining 99 are not installed. Please make sure that those packages that can (99) be updated. This problem has been haunting me ever since version 12.1. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204467 Ruslan Romanyuk <creamsoda.e2@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Update fail |[Feature] Update fail OS|openSUSE Leap 15.4 |Windows 10 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204467 http://bugzilla.opensuse.org/show_bug.cgi?id=1204467#c1 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Andreas.Stieger@gmx.de Component|Upgrade Problems |libzypp Assignee|screening-team-bugs@suse.de |zypp-maintainers@suse.de QA Contact|jsrain@suse.com |qa-bugs@suse.de Severity|Normal |Enhancement --- Comment #1 from Andreas Stieger <Andreas.Stieger@gmx.de> --- No, updating all other packages could lead to unexpected problems that are worse. By principle of least surprise this should be bubbled to the user to resolve. This returns a valid solution on a stock problem: $ zypper in --dry-run plymouth{,-lang} Find out what blocks the update and resolve that. Assiging to libzypp maintainers to close. I believe all transactions that have any conflict or ambiguity should only proceed if we have have a user-informed resolution, or bail out. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204467 http://bugzilla.opensuse.org/show_bug.cgi?id=1204467#c2 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |GNOME Assignee|zypp-maintainers@suse.de |gnome-bugs@suse.de --- Comment #2 from Michael Andres <ma@suse.com> --- Basically right. Nevertheless I tentatively forward it to the PackageKit maintainers because AFAIK the desktop updater applets are using PK. In case of doubt please forward it to the applet maintainer. The resolver does not only report problems, it also offers potential solutions. Those solutions often tell more about the nature of the problem, than the problem description alone. I don't know if PK forwards the solution texts as well. If PK does, the maintainer of the applet should perhaps display them together with the problem. OTOH - I don't know what the applet or PK is executing here. A plain 'update' job (like zypper up) will never cause any problem reports. It simply and silently updates whatever is possible. This is intended for situations like this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204467 http://bugzilla.opensuse.org/show_bug.cgi?id=1204467#c3 Yifan Jiang <yfjiang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gnome-bugs@suse.de, | |yfjiang@suse.com Assignee|gnome-bugs@suse.de |songchuan.kang@suse.com --- Comment #3 from Yifan Jiang <yfjiang@suse.com> --- Jonathan, it is like another example for PK dependency handling you were working on. So I am putting it in your queue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204467 http://bugzilla.opensuse.org/show_bug.cgi?id=1204467#c4 --- Comment #4 from Jonathan Kang <songchuan.kang@suse.com> --- (In reply to Michael Andres from comment #2)
The resolver does not only report problems, it also offers potential solutions. Those solutions often tell more about the nature of the problem, than the problem description alone. I don't know if PK forwards the solution texts as well.
This is still a missing feature in PackageKit.
OTOH - I don't know what the applet or PK is executing here. A plain 'update' job (like zypper up) will never cause any problem reports. It simply and silently updates whatever is possible. This is intended for situations like this.
I assume "zypper up" may report the same conflict in his system. However the zypper does provide potential solutions, so that this can be resolved. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1204467 http://bugzilla.opensuse.org/show_bug.cgi?id=1204467#c5 --- Comment #5 from Ruslan Romanyuk <creamsoda.e2@gmail.com> --- I'm very happy to have received feedback from the SUSE team. Thank you and wish you all the best! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com