Hello. Not sure if this is really a problem or if it’s working as it should. Here’s what I’ve done:
Installed OpenSUSE 11.4 from live KDE USB.
Ran sudo zypper dup to update the base install.
Added the tumbleweed and packman tumbleweed repos.
Ran sudo zypper dup again, which changed lots of providers to tumbleweed.
After a reboot, I noticed kernel version was still the old one (2.6.37 I think).
Did sudo zypper dup --from tumbleweed, which updated kernel to the expected version (3.0.0).
The “problem” is that I was under the impression that sudo zypper dup should be sufficient for switching to tumbleweed (both from forum posts and the current wiki article). Why did I have to add --from tumbleweed to update the kernel (and some other packages that I don’t remember)?
Also, if I now try to do a simple sudo zypper dup, I get this:
[qbd@linux-yxhh ~]$ sudo zypper dup
root's password:
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 NEW packages are going to be installed:
kernel-default kernel-default-devel preload-kmp-default
The following packages are going to be upgraded:
btrfsprogs hugin kdebase4-openSUSE kdebase4-runtime-branding-openSUSE kdebase4-workspace-branding-openSUSE kdelibs4-branding-openSUSE kdm-branding-openSUSE kio_sysinfo
kio_sysinfo-branding-openSUSE libsoup-2_4-1 preload
The following packages are going to change vendor:
btrfsprogs obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE
kdebase4-openSUSE obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE
kdebase4-runtime-branding-openSUSE obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE
kdebase4-workspace-branding-openSUSE obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE
kdelibs4-branding-openSUSE obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE
kdm-branding-openSUSE obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE
kio_sysinfo obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE
kio_sysinfo-branding-openSUSE obs://build.opensuse.org/openSUSE:Tumbleweed -> openSUSE
11 packages to upgrade, 3 new, 8 to change vendor.
Overall download size: 57.0 MiB. After the operation, additional 148.7 MiB will be used.
Continue? [y/n/?] (y):
Should I do this and change several providers back to OpenSUSE, or is something funky going on with my installs? My current repos are:
That does indeed remove the provider changes (and makes perfect sense based on my understanding of repos and tumbleweed), but from reading the forum the general accepted approach seems to be to leave priorities alone. Certainly it should be mentioned in the wiki if it’s necessary!
The explanation lies in the versions. At this point in time the versions are:
btrfsprogs is 0.19-17.18.1 in updates-opensuse and 0.19-5.47.1 in Tumbleweed, so zypper should go for vendor openSUSE
kdebase4-openSUSE is 11.4-33.40.1 in updates-opensuse (+ a patch) and 11.4-2.1 in Tumbleweed so zypper should go for vendor openSUSE
I didn’t check the others, presumably there’s an explanation for them too.
The point is that the even priority (of 99) and a plain zypper dup gives the correct result. The change of these packages to opensuse-updates is actually an upgrade. I don’t understand why the lesser versions exist in the Tumbleweed repo, but it is interesting that the wiki recommendations stand up in this instance.
Ah that explains it, thanks for that observation :). Would you also happen to know why the kernel did not get updated initially using only zypper dup? Actually I have another kernel question, as after running zypper dup again I got another kernel ending in “-default”. Initially I had just one ending in “-desktop”, but now both are presented as choices when booting. What’s the difference, and which one should be used?
Regrading the reversion of RPMs: I’m no longer sure I was right. Maybe there actually was an error in the repositories that caused the reversion of RPMs from Tumbleweed to opensuse-updates. See posts numbered 18 through 21 on this thread: New packages in Tumbleweed - how do I get to know about them? It works both ways though.
Regarding why the kernel needed a double run of zypper dup: I have seen instances where if there is a large bunch of packages to upgrade, they are sequenced into several groups. That’s not unusual. Maybe that’s what happened. But It’s just a thought, not a definitive explanation.
There are several packages currently in openSUSE update which have higher version numbers than in Tumbleweed (kio-sysinfo).
For quite some time I used Tumbleweed like a “stable” distro, not thinking much about updates but just applying them. Everything just worked, often I simply trusted the update applet to do the right thing. But in the last days I have the feeling that there are inconsistencies creeping in, or alternatively, that I do no longer understand the interdependencies between the different repos used for a “Tumbleweed” system ;).
> There are several packages currently in openSUSE update which have
> higher version numbers than in Tumbleweed (kio-sysinfo).
Yes, and that is to be expected. Packages will flow from one repo to
another as they get updated for various reasons. This is totally normal.
> For quite some
> time I used Tumbleweed like a “stable” distro, not thinking much about
> updates but just applying them. Everything just worked, often I simply
> trusted the update applet to do the right thing. But in the last days I
> have the feeling that there are inconsistencies creeping in, or
> alternatively, that I do no longer understand the interdependencies
> between the different repos used for a “Tumbleweed” system ;).
But it should be still “just working”, right? The fact that packages are
changing repos is correct.
So please don’t worry, it’s expected, and all is well.
