[Bug 208694] New: YaST does not allow package downgrading if patches were applied
https://bugzilla.novell.com/show_bug.cgi?id=208694 Summary: YaST does not allow package downgrading if patches were applied Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: kkaempf@novell.com ReportedBy: rguenther@novell.com QAContact: jsrain@novell.com CC: sh@novell.com If you start with a 10.1 install and apply current online-updates you get a xorg patch. If you then install xorg7 from an external source (openSUSE) you can not downgrade to xorg 6.9 again without re-installing. This is because the applied patch imposes requirements on library versions, but those are not available for downgrading. So downgrading to the available 10.1 packages fails and there is no way ignoring the patch dependencies or uninstalling the patch. I believe this (interaction of patches with dependencies) is a design issue and is not easy to fix (other than by providing a "ignore this dependency" from the Yast sw management module and allowing to re-apply a patch). Still this is a quite severe issue, as requiring a re-install of the complete system in this case is not acceptable. [but unsupported external install, yadayada, so Critial priority only] Note this problem is in openSUSE 10.2, too, I believe. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208694 kkaempf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com, visnov@novell.com AssignedTo|kkaempf@novell.com |sh@novell.com ------- Comment #1 from kkaempf@novell.com 2006-10-03 11:16 MST ------- Actually, the dependencies work as designed. The patch serves as a warrant for the fix. Installing the patch ensures that the fix is - and stays - applied. The bug you're seeing here is YaSTs inability to delete the patch. Deletion of the patch would then remove the warrant and allow package downgrade. Use "rug rm -t patch ..." as a workaround. Reassign to Stefan to allow patch deletion in YaST UI. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208694 sh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #2 from sh@novell.com 2006-10-04 09:10 MST ------- I can easily allow patch deletion in the UI. Currently it is artificially disabled - mostly for historical reasons, because the old package manager didn't support deleting patches at all. For ZYPP this had been undecided IIRC. If a user deletes a patch, I assume only the patch meta data will be deleted, but all packages that came with the patch will remain the same. Wouldn't users expect to downgrade to the status before they applied the patch in that case? I know we (currently?) can't do that and that it would be very hard to support that - keeping track of RPM DB history and so on. But I fear if we offer to delete patches users will think to have been mislead if the same package versions are still there after deleting a patch. Somebody better prepare an SDB article or an OpenSUSE wiki page to explain what is going on in that case... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208694 sh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kmachalkova@novell.com AssignedTo|sh@novell.com |gs@novell.com Status|ASSIGNED |NEW ------- Comment #3 from sh@novell.com 2006-10-04 09:31 MST ------- Patches can now be selected for deletion in the Qt package selector. -> Gabi / Katharina for y2-ncurses -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208694 kmachalkova@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|gs@novell.com |kmachalkova@novell.com Status|NEW |ASSIGNED ------- Comment #4 from kmachalkova@novell.com 2006-10-07 08:54 MST ------- I'll take this one, since Gabi is away next week -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208694 gs@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #5 from gs@novell.com 2006-10-11 03:40 MST ------- I had a look at the problem. I now have enabled the deletion of patches for Ncurses package selector, too (will be provided with yast2-ncurses-2.13.46). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208694 Richard Guenther <rguenther@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Found By|Other |Development -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com