[opensuse] Mysterious zypper update
I just tried (but did not execute) a zypper up on my 12.3 system. The unusual thing is that nvidia-gfxG03-kmp-desktop, which is currently installed, is listed both under packages that 'will NOT be installed' as well as 'NEW packages are going to be installed'. Hmm. There are a few kernel packages that are also listed in both places. I don't dare do an update at this time. Anyone else see this? I have only the basic 12.3 repos defined. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-05-13 07:44 (GMT+0200) Roger Oberholtzer composed:
I just tried (but did not execute) a zypper up on my 12.3 system. The unusual thing is that nvidia-gfxG03-kmp-desktop, which is currently installed, is listed both under packages that 'will NOT be installed' as well as 'NEW packages are going to be installed'. Hmm. There are a few kernel packages that are also listed in both places.
I don't dare do an update at this time. Anyone else see this? I have only the basic 12.3 repos defined.
I've often seen zypper report a particular package both will and will not be installed in the same operation. I normally ignore such reports. Maybe you can spot a difference using zypper's -v option. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer [13.05.2013 07:44]:
I just tried (but did not execute) a zypper up on my 12.3 system. The unusual thing is that nvidia-gfxG03-kmp-desktop, which is currently installed, is listed both under packages that 'will NOT be installed' as well as 'NEW packages are going to be installed'. Hmm. There are a few kernel packages that are also listed in both places.
I don't dare do an update at this time. Anyone else see this? I have only the basic 12.3 repos defined.
When you have "multiversion" enabled for zypp (in /etc/zypp/zypp.conf), you have this as an effect. For example, you have nvidia-gfxG03-kmp-desktop-319.17_k3.7.10_1.1-12.1 in your system. When you do a "zypper up", and the latest version of nvidia-gfxG03-kmp-desktop has a version beginning with 319.17_k3.7.10_1.1, the package will not be updated. When the latest version is newer than 319.17_k3.7.10_1.1 (like 319.17_k3.7.10_1.4), the package will be installed. Also, when you use Tumbleweed, you are used to see that the kernel is not updated though a newer version is available, you have to trigger it manually. Except for the cases where patches for the kernel are available, then you get the newest version... HTH, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2013-05-13 at 11:03 +0200, Werner Flamme wrote:
Roger Oberholtzer [13.05.2013 07:44]:
I just tried (but did not execute) a zypper up on my 12.3 system. The unusual thing is that nvidia-gfxG03-kmp-desktop, which is currently installed, is listed both under packages that 'will NOT be installed' as well as 'NEW packages are going to be installed'. Hmm. There are a few kernel packages that are also listed in both places.
I don't dare do an update at this time. Anyone else see this? I have only the basic 12.3 repos defined.
When you have "multiversion" enabled for zypp (in /etc/zypp/zypp.conf), you have this as an effect.
My /etc/zypp/zypp.conf is whatever gets installed in 12.3. I see these relevant lines: multiversion = provides:multiversion(kernel) multiversion.kernels = latest,latest-1,running Which seems reasonable. Thinking that the rpm listed more than once were for different versions, I added the -v option, which reports: The following package updates will NOT be installed: kernel-desktop 3.7.10-1.4.1 kernel-desktop-devel 3.7.10-1.4.1 kernel-devel 3.7.10-1.4.1 nvidia-gfxG03-kmp-desktop 319.17_k3.7.10_1.1-12.1 The following NEW packages are going to be installed: kernel-desktop 3.7.10-1.4.1 kernel-desktop-devel 3.7.10-1.4.1 kernel-devel 3.7.10-1.4.1 nvidia-gfxG03-kmp-desktop 319.17_k3.7.10_1.1-12.1 So it is not listing the one it will keep as not being upgraded, and the new one as a new one to install. That may be what it is thinking, but it is not what it is reporting. I really do not want to hose my system... Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[13.05.2013 11:18] [Roger Oberholtzer]:
On Mon, 2013-05-13 at 11:03 +0200, Werner Flamme wrote:
Roger Oberholtzer [13.05.2013 07:44]:
I just tried (but did not execute) a zypper up on my 12.3 system. The unusual thing is that nvidia-gfxG03-kmp-desktop, which is currently installed, is listed both under packages that 'will NOT be installed' as well as 'NEW packages are going to be installed'. Hmm. There are a few kernel packages that are also listed in both places.
I don't dare do an update at this time. Anyone else see this? I have only the basic 12.3 repos defined.
When you have "multiversion" enabled for zypp (in /etc/zypp/zypp.conf), you have this as an effect.
My /etc/zypp/zypp.conf is whatever gets installed in 12.3. I see these relevant lines:
multiversion = provides:multiversion(kernel)
multiversion.kernels = latest,latest-1,running
Which seems reasonable. Thinking that the rpm listed more than once were for different versions, I added the -v option, which reports:
The following package updates will NOT be installed: kernel-desktop 3.7.10-1.4.1 kernel-desktop-devel 3.7.10-1.4.1 kernel-devel 3.7.10-1.4.1 nvidia-gfxG03-kmp-desktop 319.17_k3.7.10_1.1-12.1
This tries to tell you that packages with the version given are available, and that they are not installed *as* *update*.
The following NEW packages are going to be installed: kernel-desktop 3.7.10-1.4.1 kernel-desktop-devel 3.7.10-1.4.1 kernel-devel 3.7.10-1.4.1 nvidia-gfxG03-kmp-desktop 319.17_k3.7.10_1.1-12.1
This tries to tell you that packages with the version given are available, and that they will be installed as *additional* *package*. If you issue "rpm -q kernel-desktop" after (as example) kernel-desktop-3.7.10-1.4.1 has been installed, you will see output like # rpm -q kernel-desktop kernel-desktop-3.7.10-1.1.1 kernel-desktop-3.7.10-1.4.1 So you did not install an upgrade, since that would mean to replace the old package with the new one, but you installed an additional package instead. Both packages are installed in your system and should produce selectable entries in your grub (or lilo or ...) configuration. If you disable the "multiversion" line in /etc/zypp/zypp.conf (by putting a # in the first column), the behaviour will change to the behaviour that was standard before openSUSE 11.1 (AFAIR), where a newly installed kernel replaces the old one.
So it is not listing the one it will keep as not being upgraded, and the new one as a new one to install. That may be what it is thinking, but it is not what it is reporting.
I really do not want to hose my system...
Why would you? I love this multiversion thing, because now I can update my kernel, but the system can run on. I do so with my 20+ SLES11 at work, and there is no problem to reboot them when they are not needed so urgently, like "next weekend". With SLES9, the new kernel replaced the old, and you should reboot the system soon after patching. After several years, it became possible to install multiple kernels with SLES9 too, by downloading them manually into /tmp/newkern followed by "rpm -i /tmp/newkern/*rpm && rm -rf /tmp/newkern". At that time, YaST would do a "rpm -U" instead, thus replacing the old kernel with the new one. Zypper was not born then ;-) BTW, if you don't trust zypper to do the updates, you still can use YaST for this purpose. In the graphical interface, you have the "versions" tab (down right) when you click on one package (up right). Here you select the versions you want to install, and you get the dependencies straightened out at once. In the ncurses interface, you'll have to search the menus where the "version" info is available, but you can also see it here when you select a package. Plus, you can see the "installation summary" before the patches are applied, and you will see that your system ist not going to be hosed ;-) Regards, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2013-05-13 at 20:25 +0200, Werner Flamme wrote:
Why would you? I love this multiversion thing, because now I can update my kernel, but the system can run on. I do so with my 20+ SLES11 at work, and there is no problem to reboot them when they are not needed so urgently, like "next weekend". With SLES9, the new kernel replaced the old, and you should reboot the system soon after patching.
I like the multiversion feature as well. Is it just that there is a difference between what zypper is trying to tell me and what it is actually saying. Your description is based on information you have outside what zypper reported. Perhaps zypper should explicitly list RPMs that will be kept because of multiversioning. I have done the update and all is well. Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[14.05.2013 08:07] [Roger Oberholtzer]:
On Mon, 2013-05-13 at 20:25 +0200, Werner Flamme wrote:
Why would you? I love this multiversion thing, because now I can update my kernel, but the system can run on. I do so with my 20+ SLES11 at work, and there is no problem to reboot them when they are not needed so urgently, like "next weekend". With SLES9, the new kernel replaced the old, and you should reboot the system soon after patching.
I like the multiversion feature as well. Is it just that there is a difference between what zypper is trying to tell me and what it is actually saying. Your description is based on information you have outside what zypper reported. Perhaps zypper should explicitly list RPMs that will be kept because of multiversioning.
I have done the update and all is well.
Yes, I do not use only zypper, I use rpm as well. And sometimes YaST, but that's when some updates become hairy, like when a new KDE version is out, and some package is not available with the new version number. When you think that zypper should give more or other info, try <https://features.opensuse.org/> or open a bug. You need a login, but at least developers know that something is missing, and maybe it becomes realized :-) Regards, Werner -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Felix Miata -
Roger Oberholtzer -
Werner Flamme