[Bug 1205456] New: patch "openSUSE-SLE-15.4-2022-2969" conflicts with packman packages
https://bugzilla.suse.com/show_bug.cgi?id=1205456 Bug ID: 1205456 Summary: patch "openSUSE-SLE-15.4-2022-2969" conflicts with packman packages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance@opensuse.org Reporter: martin.wilck@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 862909 --> https://bugzilla.suse.com/attachment.cgi?id=862909&action=edit screenshot from gpk-update-viewer Patch openSUSE-SLE-15.4-2022-2969 breaks updating Leap 15.4 because of a conflict with libswresample. The graphical update tool gpk-update-viewer runs into an error that unexperienced users might not understand. "zypper patch --with-optional" would install the patch, changing a bunch of ffmpeg and avcodec related packages from Packman to SUSE LLC, which is most probably not what the users want. "zypper update" skips these updates instead. It is unclear to me why these conflicts are in the patch meta data. It's obviously possible to update the other packages (non-ffmpeg) without breaking any package-level dependencies. Several users have posted about this in the Forum: https://www.opensuse-forum.de/thread/65990-softwareaktualisierung-funktionie... https://forums.opensuse.org/showthread.php/574888-openSUSE-SLE-15-4-2022-296... Is there a deeper reason for creating this artificial conflict? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 https://bugzilla.suse.com/show_bug.cgi?id=1205456#c1 --- Comment #1 from Marcus Meissner <meissner@suse.com> --- (the respective ffmpeg update was released Oct 26th) The problem here is more that there is overlap between the packagelists between OpenSUSE SLE imports and Packman. Application of the SUSE patch would require a vendor change (flipping all the binaries from Packman over to the SUSE ones). This is a bit messy. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 https://bugzilla.suse.com/show_bug.cgi?id=1205456#c2 --- Comment #2 from Martin Wilck <martin.wilck@suse.com> --- (In reply to Marcus Meissner from comment #1)
Application of the SUSE patch would require a vendor change (flipping all the binaries from Packman over to the SUSE ones).
And this is what users who have the packman packages installed probably don't want. I just wonder about those conflicts. Are they necessary to make the patch work? The biggest issue IMO is that this breaks the graphical updater in a way that's non-obvious to apprentice users. It leaves people like my wife or my daughter totally clueless. Even for me as experienced user it was non-obvious if I could simply deselect this patch and be good (besides ffmpeg, the patchinfo mentioned a lot of KDE updates that I wouldn't want to miss). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 https://bugzilla.suse.com/show_bug.cgi?id=1205456#c4 --- Comment #4 from Martin Wilck <martin.wilck@suse.com> --- Thanks. Summing up, 1 All zypp patches conflict with all package versions younger than the packages contained in them 2 There is overlap between the packagelists between OpenSUSE SLE imports and Packman => "zypper patch" will never work reliably on systems that enable 3rd party repositiories. 3 gpk-update-viewer builds upon zypper's patch functionality => Forget about gpk-update-viewer on Leap Together with 4 packman is necessary for a lot users to perform every-day tasks and 5 gpk-update-viewer is a prominent part of the GNOME desktop and is (afaik) the only way in which ordinary users can install updates without becoming root this has quite a negative impact on the overall user experience. The "this is how it is" kind of answers in this bug make me realize that this isn't going to change. I suppose it's a WONTFIX then. A bit sad, but whatever. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 https://bugzilla.suse.com/show_bug.cgi?id=1205456#c5 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ohering@suse.com --- Comment #5 from Marcus Meissner <meissner@suse.com> --- correction: zypper patch breaks when the two repos present packages with the same name, but a different version-release scheme. I still see a need to somehow fix this, but I currently do not know how. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 https://bugzilla.suse.com/show_bug.cgi?id=1205456#c6 --- Comment #6 from Marcus Meissner <meissner@suse.com> --- Olaf, as one packman representative, any ideas here. only thing I can think of is if packman would have a higher version for the ffmpeg library packages. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 https://bugzilla.suse.com/show_bug.cgi?id=1205456#c8 --- Comment #8 from Olaf Hering <ohering@suse.com> --- I think libzypp could become smarter and consider the vendor in addition to the version. In other words, either offer a replace, or leave the installed package alone. Other than that, do not create patches for packages which will 100% come from 3rd party repos. This certainly reveals an unrelated issue: the openSUSE.org:openSUSE:Leap:15.4:Update does not provide the sources for 4.4-150400.3.2.1, it does apparently link to 4.4-150400.1.13 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 https://bugzilla.suse.com/show_bug.cgi?id=1205456#c11 --- Comment #11 from Martin Wilck <martin.wilck@suse.com> --- Another option, at least for users of the packagekit-related tools, would be to base libzypp's packagekit backend on "update" rather than "patch" functionality. In view of comment 4, "patch" is generally broken on systems that enable 3rd party repos, which I suppose is the majority of Leap installations. No idea whether that can be easily done, though. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 https://bugzilla.suse.com/show_bug.cgi?id=1205456#c12 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #12 from Olaf Hering <ohering@suse.com> --- I fixed it in prjconf, lets see how it behaves in the future. env -i /usr/bin/zypper versioncmp 1 1a 1 is older than 1a -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 https://bugzilla.suse.com/show_bug.cgi?id=1205456#c13 --- Comment #13 from Olaf Hering <ohering@suse.com> --- Maybe not... env -i /usr/bin/zypper versioncmp 1.2.3 1a.2.4 1.2.3 is newer than 1a.2.4 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205456 https://bugzilla.suse.com/show_bug.cgi?id=1205456#c14 --- Comment #14 from Olaf Hering <ohering@suse.com> --- The solution is in place since last week: Release: %sle_version.<CI_CNT>.string.<B_CNT> The _link files already contain 'cicount="add"'. As a result CI_CNT will be always higher. 'string' can not be part of the "sle_version" or the "CI_CNT" item. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com