[Bug 783885] New: "zypper dup" steps back to older version ?!
https://bugzilla.novell.com/show_bug.cgi?id=783885 https://bugzilla.novell.com/show_bug.cgi?id=783885#c0 Summary: "zypper dup" steps back to older version ?! Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: koenig@linux.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- I noticed that "zypper dup" on a fully updated 12.2 with some additional repos wants to downgrade some packages back to main opensuse repos. why ? # zypper dup Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... The following package is going to be upgraded: yast2-vm The following packages are going to be downgraded: flash-player flash-player-gnome flash-player-kde4 gparted gparted-lang kvm libcap-ng0 libcelt051-0 libcgroup-devel libcgroup1 libcgroup1-32bit libnetcontrol0 libspice-server1 libvdeplug3 libvirt libvirt-client libvirt-python lxc lxc-devel python-SpiceClientGtk python-virtinst qemu qemu-linux-user qemu-tools tv-common v4l-conf v4l-tools virt-manager virt-utils virt-viewer virtualbox virtualbox-guest-kmp-desktop virtualbox-guest-tools virtualbox-guest-x11 virtualbox-host-kmp-desktop virtualbox-qt vm-install xen xen-doc-html xen-doc-pdf xen-kmp-desktop xen-libs xen-tools The following packages are going to change vendor: gparted obs://build.opensuse.org/home:oddball33 -> openSUSE gparted-lang obs://build.opensuse.org/home:oddball33 -> openSUSE kvm obs://build.opensuse.org/Virtualization -> openSUSE ... qemu obs://build.opensuse.org/Virtualization -> openSUSE qemu-linux-user obs://build.opensuse.org/Virtualization -> openSUSE qemu-tools obs://build.opensuse.org/Virtualization -> openSUSE virt-manager obs://build.opensuse.org/Virtualization -> openSUSE virt-utils obs://build.opensuse.org/Virtualization -> openSUSE ... yast2-vm obs://build.opensuse.org/Virtualization -> openSUSE so this tries to downgrade gparted from 0.13.1-3.1 to 0.12.1-2.1.2 # zypper se -s gparted Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+---------------------+---------+--------------+--------+------------------ v | gparted | package | 0.12.1-2.1.2 | x86_64 | oss-122-gwdg v | gparted | package | 0.12.1-2.1.2 | i586 | oss-122-gwdg v | gparted | package | 0.12.1-2.1.2 | x86_64 | oss-122 v | gparted | package | 0.12.1-2.1.2 | i586 | oss-122 i | gparted | package | 0.13.1-3.1 | x86_64 | (System Packages) v | gparted-lang | package | 0.12.1-2.1.2 | noarch | oss-122-gwdg v | gparted-lang | package | 0.12.1-2.1.2 | noarch | oss-122 i | gparted-lang | package | 0.13.1-3.1 | noarch | (System Packages) and qemu from 1.2.0-122.5 to some 1.1.* # zypper se -s qemu Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+----------------------------+------------+---------------------------+--------+---------------- v | qemu | package | 1.1.1-3.9.1 | x86_64 | update-122-gwdg v | qemu | package | 1.1.1-3.9.1 | i586 | update-122-gwdg v | qemu | package | 1.1.0-3.6.1 | x86_64 | oss-122-gwdg v | qemu | package | 1.1.0-3.6.1 | i586 | oss-122-gwdg i | qemu | package | 1.2.0-122.5 | x86_64 | Virtualization v | qemu | package | 1.1.1-3.9.1 | x86_64 | update-122 v | qemu | package | 1.1.0-3.6.1 | x86_64 | oss-122 v | qemu | package | 1.2.0-122.5 | i586 | Virtualization v | qemu | package | 1.1.1-3.9.1 | i586 | update-122 v | qemu | package | 1.1.0-3.6.1 | i586 | oss-122 why does "zypper dup" ignore non-opensuse repos and downgrades such packages back to older versions of OS repos ?? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=783885 https://bugzilla.novell.com/show_bug.cgi?id=783885#c kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |zypp-maintainers@forge.prov |ovo.novell.com |o.novell.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=783885 https://bugzilla.novell.com/show_bug.cgi?id=783885#c1 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Michael Andres <ma@suse.com> 2012-10-15 15:42:30 CEST --- DUP is not a version-update! DUP (roughly) re-installs the system taking the packages from the enabled repos. Thus DUP will change vendor and downgrade packages if needed. This is different from UP, which will try to keep arch and vendor of the installed package and just update to a newer version. If gparted-0.13.1 is not provided by any enabled repo, the version is unwanted and DUP will pick one from the available repos (downgrading it). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=783885 https://bugzilla.novell.com/show_bug.cgi?id=783885#c2 --- Comment #2 from Harald Koenig <koenig@linux.de> 2012-10-15 17:18:31 UTC --- (In reply to comment #1)
If gparted-0.13.1 is not provided by any enabled repo, the version is unwanted and DUP will pick one from the available repos (downgrading it).
agreed for the [bad] example of gparted, whose source repo was not enabled. but what about the planed downgrade of qemu from 1.2.0-122.5 back to 1.1.1-3.9.1 from the openSUSE repo? here, version 1.2.0-* *is* available from an active repo "Virtualization" as "zypper search -s qemu" showed: $ zypper lr Virtualization Alias : Virtualization Name : Virtualization URI : http://download.opensuse.org/repositories/Virtualization/openSUSE_12.2/ Enabled : Yes Priority : 99 Auto-refresh : On Keep Packages : Off Type : rpm-md GPG Check : On GPG Key URI : Path Prefix : Parent Service : MD Cache Path : /var/cache/zypp/raw/Virtualization -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=783885 https://bugzilla.novell.com/show_bug.cgi?id=783885#c3 --- Comment #3 from Michael Andres <ma@suse.com> 2012-10-16 10:04:52 CEST --- Could be due to repo prioriy if the openSUSE repo is above '99'. Could be qemu-1.2.0 would raise a conflict, which can be avoided using the minor version. Maybe because one of the packages quemu depends on can not be updated to it's latest version or is downgraded. (Could be a solver bug.) If the DUP is not yet performed, you can try to lock the installed quemu-1.2.0 (zypper al quemu) and check whether this raises additional conflicts in DUP, or if the solver can be forced into a solution keeping quemu. If you suspect a bug or think the solver could have been smarter, I'd need a solver testcase to investigate. If the DUP is not yet performed: zypper dup --debug-solver. If the DUP is already done zypper saved a testcase /var/log/updateTestcase-<date> -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=783885 https://bugzilla.novell.com/show_bug.cgi?id=783885#c4 --- Comment #4 from Harald Koenig <koenig@linux.de> 2012-10-16 08:20:45 UTC --- (In reply to comment #3)
Could be due to repo prioriy if the openSUSE repo is above '99'.
yes it is: $ zypper lr -P | grep -v No # | Alias | Name | Enabled | Refresh | Priority ---+-------------------+--------------------+---------+---------+--------- 45 | update-122-gwdg | update-122-gwdg | Yes | Yes | 15 26 | non-oss-122-gwdg | non-oss-122-gwdg | Yes | Yes | 60 32 | oss-122-gwdg | oss-122-gwdg | Yes | Yes | 60 5 | Virtualization | Virtualization | Yes | Yes | 99 14 | google-chrome | google-chrome | Yes | Yes | 99 15 | google-earth | google-earth | Yes | Yes | 99 25 | non-oss-122 | non-oss-122 | Yes | Yes | 99 27 | nvidia | nvidia | Yes | Yes | 99 31 | oss-122 | oss-122 | Yes | Yes | 99 37 | s122-debug | s122-debug | Yes | Yes | 99 44 | update-122 | update-122 | Yes | Yes | 99 but for "UP" version is more important than priority.
Could be qemu-1.2.0 would raise a conflict, which can be avoided using the minor version. Maybe because one of the packages quemu depends on can not be updated to it's latest version or is downgraded.
(Could be a solver bug.)
If the DUP is not yet performed, you can try to lock the installed quemu-1.2.0 (zypper al quemu) and check whether this raises additional conflicts in DUP, or if the solver can be forced into a solution keeping quemu.
I won't do the DUP anyway (it's only for checking if newer versions on non-suse repos are available, typically I don't want to get them all -- exceptions prove the rule...). so: after locking qemu, DUP still suggests the following without any conflict msgs: Computing distribution upgrade... The following packages are going to be upgraded: MozillaFirefox MozillaThunderbird akonadi akregator bootsplash-branding-openSUSE branding-openSUSE dynamic-wallpaper-branding-openSUSE emacs emacs-info emacs-nox emacs-x11 gfxboot-branding-openSUSE gimp-branding-openSUSE gnuplot grub2-branding-openSUSE iscsitarget-kmp-desktop iscsitarget-kmp-xen kaddressbook kde4-kgreeter-plugins kdebase4-workspace kdebase4-workspace-devel kdebase4-workspace-ksysguardd kdebase4-workspace-liboxygenstyle kdebase4-workspace-plasma-calendar kdebase4-workspace-plasma-engine-akonadi kdelibs4-branding-openSUSE kdepim4 kdm kdm-branding-openSUSE kernel-debug-devel kernel-default-devel kernel-desktop kernel-desktop-devel kernel-devel kernel-source kernel-syms kernel-xen kernel-xen-devel kmail knode knotes kontact korganizer ksplash-qml-branding-openSUSE ksplashx-branding-openSUSE kwin libgudev-1_0-0 libgudev-1_0-0-32bit libgudev-1_0-devel libkdepim4 libquvi-scripts libudev-devel libudev0 libudev0-32bit mozilla-kde4-integration plymouth-branding-openSUSE python-kdebase4 susegreeter-branding-openSUSE typelib-1_0-GUdev-1_0 udev wallpaper-branding-openSUSE xemacs xemacs-info xemacs-packages xemacs-packages-info xfce4-splash-branding-openSUSE yast2-qt-branding-openSUSE yast2-vm The following packages are going to be downgraded: flash-player flash-player-gnome flash-player-kde4 gparted gparted-lang kvm libcap-ng0 libcelt051-0 libcgroup-devel libcgroup1 libcgroup1-32bit libnetcontrol0 libspice-server1 libvdeplug3 libvirt libvirt-client libvirt-python lxc lxc-devel python-SpiceClientGtk python-virtinst qemu qemu-linux-user qemu-tools tv-common v4l-conf v4l-tools virt-manager virt-utils virt-viewer virtualbox virtualbox-guest-kmp-desktop virtualbox-guest-tools virtualbox-guest-x11 virtualbox-host-kmp-desktop virtualbox-qt vm-install xen xen-doc-html xen-doc-pdf xen-kmp-desktop xen-libs xen-tools The following packages are going to change vendor: ... qemu obs://build.opensuse.org/Virtualization -> openSUSE qemu-linux-user obs://build.opensuse.org/Virtualization -> openSUSE qemu-tools obs://build.opensuse.org/Virtualization -> openSUSE ...
If you suspect a bug or think the solver could have been smarter, I'd need a solver testcase to investigate.
If the DUP is not yet performed: zypper dup --debug-solver. If the DUP is already done zypper saved a testcase /var/log/updateTestcase-<date>
will attach... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=783885 https://bugzilla.novell.com/show_bug.cgi?id=783885#c5 --- Comment #5 from Harald Koenig <koenig@linux.de> 2012-10-16 08:36:31 UTC --- (In reply to comment #4)
(In reply to comment #3)
Could be due to repo prioriy if the openSUSE repo is above '99'.
yes it is:
$ zypper lr -P | grep -v No # | Alias | Name | Enabled | Refresh | Priority ---+-------------------+--------------------+---------+---------+--------- 45 | update-122-gwdg | update-122-gwdg | Yes | Yes | 15 26 | non-oss-122-gwdg | non-oss-122-gwdg | Yes | Yes | 60 32 | oss-122-gwdg | oss-122-gwdg | Yes | Yes | 60 5 | Virtualization | Virtualization | Yes | Yes | 99 14 | google-chrome | google-chrome | Yes | Yes | 99 15 | google-earth | google-earth | Yes | Yes | 99 25 | non-oss-122 | non-oss-122 | Yes | Yes | 99 27 | nvidia | nvidia | Yes | Yes | 99 31 | oss-122 | oss-122 | Yes | Yes | 99 37 | s122-debug | s122-debug | Yes | Yes | 99 44 | update-122 | update-122 | Yes | Yes | 99
but for "UP" version is more important than priority.
Could be qemu-1.2.0 would raise a conflict, which can be avoided using the minor version. Maybe because one of the packages quemu depends on can not be updated to it's latest version or is downgraded.
(Could be a solver bug.)
If the DUP is not yet performed, you can try to lock the installed quemu-1.2.0 (zypper al quemu) and check whether this raises additional conflicts in DUP, or if the solver can be forced into a solution keeping quemu.
I won't do the DUP anyway (it's only for checking if newer versions on non-suse repos are available, typically I don't want to get them all -- exceptions prove the rule...).
so: after locking qemu, DUP still suggests the following without any conflict msgs:
Computing distribution upgrade...
The following packages are going to be upgraded: MozillaFirefox MozillaThunderbird akonadi akregator bootsplash-branding-openSUSE branding-openSUSE dynamic-wallpaper-branding-openSUSE emacs emacs-info emacs-nox emacs-x11 gfxboot-branding-openSUSE gimp-branding-openSUSE gnuplot grub2-branding-openSUSE iscsitarget-kmp-desktop iscsitarget-kmp-xen kaddressbook kde4-kgreeter-plugins kdebase4-workspace kdebase4-workspace-devel kdebase4-workspace-ksysguardd kdebase4-workspace-liboxygenstyle kdebase4-workspace-plasma-calendar kdebase4-workspace-plasma-engine-akonadi kdelibs4-branding-openSUSE kdepim4 kdm kdm-branding-openSUSE kernel-debug-devel kernel-default-devel kernel-desktop kernel-desktop-devel kernel-devel kernel-source kernel-syms kernel-xen kernel-xen-devel kmail knode knotes kontact korganizer ksplash-qml-branding-openSUSE ksplashx-branding-openSUSE kwin libgudev-1_0-0 libgudev-1_0-0-32bit libgudev-1_0-devel libkdepim4 libquvi-scripts libudev-devel libudev0 libudev0-32bit mozilla-kde4-integration plymouth-branding-openSUSE python-kdebase4 susegreeter-branding-openSUSE typelib-1_0-GUdev-1_0 udev wallpaper-branding-openSUSE xemacs xemacs-info xemacs-packages xemacs-packages-info xfce4-splash-branding-openSUSE yast2-qt-branding-openSUSE yast2-vm
The following packages are going to be downgraded: flash-player flash-player-gnome flash-player-kde4 gparted gparted-lang kvm libcap-ng0 libcelt051-0 libcgroup-devel libcgroup1 libcgroup1-32bit libnetcontrol0 libspice-server1 libvdeplug3 libvirt libvirt-client libvirt-python lxc lxc-devel python-SpiceClientGtk python-virtinst qemu qemu-linux-user qemu-tools tv-common v4l-conf v4l-tools virt-manager virt-utils virt-viewer virtualbox virtualbox-guest-kmp-desktop virtualbox-guest-tools virtualbox-guest-x11 virtualbox-host-kmp-desktop virtualbox-qt vm-install xen xen-doc-html xen-doc-pdf xen-kmp-desktop xen-libs xen-tools
The following packages are going to change vendor: ... qemu obs://build.opensuse.org/Virtualization -> openSUSE qemu-linux-user obs://build.opensuse.org/Virtualization -> openSUSE qemu-tools obs://build.opensuse.org/Virtualization -> openSUSE ...
If you suspect a bug or think the solver could have been smarter, I'd need a solver testcase to investigate.
If the DUP is not yet performed: zypper dup --debug-solver. If the DUP is already done zypper saved a testcase /var/log/updateTestcase-<date>
will attach...
does not work: Local File Too Large Local file uploads must not exceed 10 MB in size. checking "BigFile: Big File - Stored locally and may be purged" does not help :-( $ ll -h /tmp/zypper.solverTestCase.tar.gz -rw-r--r-- 1 root root 24M Oct 16 10:24 /tmp/zypper.solverTestCase.tar.gz -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=783885 https://bugzilla.novell.com/show_bug.cgi?id=783885#c6 --- Comment #6 from Michael Schröder <mls@suse.com> 2012-10-16 11:03:44 UTC --- UP uses repo priorities like DUP does. It doesn't simply look at the version. -- 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