| 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 [details] 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-funktioniert-seit-heute-nicht-mehr/ https://forums.opensuse.org/showthread.php/574888-openSUSE-SLE-15-4-2022-2969-vs-Packman-conflicts Is there a deeper reason for creating this artificial conflict?