I did an update and ended up with Tumbleweed. I do not know how it got in the repository list. Anyway I deleted the “Factory” repository and got my internet and sound back. But it is still booting as Tumbleweed. Cam anyone give me plain and clear instructions to recover my Leap without using an installation media since I am not sure if I have the installation USB that I used a year or so ago to install it? Is there an easy was to recover my Leap? Thanks in advance for any useful advice.
Actually, I see that there is now a Leap 42.2. It might be just as easy to upgrade to 42.2? What is the easiest way to do that?
Leap 42.2 is only at beta. I assume you do not want to go and test a beta release at the moment you are not even sure whatyou have now.
To check if you have still repos that do not belong to Leap 42.2 we need of course your repos list
zypper lr -d
And it could be that you are running Leap 42.2. You can check that with
cat /etc/os-release
And when you are indeed running Leap 42.2 and not Tumbleweed, it could be that only the text in the Grub menu is wrong. Maybe check in YaST >System > Bootloader what it says.
As always, backup your system first if you value the system, although in your case I’d guess that if your system becomes borked, you would still be able to install a new LEAP from scratch but using the existing /home directory to preserve your personal files (Apps would have to be re-installed).
Verify all your enabled repos are LEAP. You can use the “zypper lr -d” command henk provided to inspect. You may want to also disable all absolutely unnecessary repos to be most safe, and disable any remaining with the following command. Disabling does not remove, only inactivates the repo so you only need to re-enable later.
zypper mr --disable *repo_id_or_number*
Perform a “distribution upgrade” with the following command
zypper dup
If you disabled any repos in the first step, you can now re-enable and update packages from those with a normal update.
zypper update
As henk described, 42.2 is only in testing mode. Unless you want a system with the breakage normally associated with a developing system, you’ll want to be running 42.1.
You only do such a thing when you are sure your repo list is OK. Are you sure?
You are not that new here, but you seem not to know about the all important CODE tags while posting computer code here.
Please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.
Notwithstanding the poor layout, I tried to interprete your listing. In general it looks OK to me, but
Why are several Debug and Source repos Enabled? Are you debugging the OSS and non-OSS software? Disable them when you are not sure that you need them.
You have the OSS repo two times (#3 and #6), delete one of them.
You might want to post your bettered list here for comment before you do the next step.
The next step would be indeed a
zypper dup
to replace all packages you may still have from some conflicting repos you have removed earlier (thus we do not know much about them).
Again, you might want to post here what packages that zypper dup wants to install, so people can check that with you.
Then, to get your multi-media packages again from Packman, a
Yes, you succeeded in making a mess of it. But as we do not know exactly what you did as well as with the repos, as well as with that “I did an update”, we hardly can explain exactly what you did wrong.
BTW an expression as “I did an update” is not very informative. It is just an English language expression giving a vague impression of what you thought you did. Real information is exactly what you did: zypper something or YaST > …, or whatever.
The following 31 patterns are going to be downgraded:
apparmor apparmor_opt base enhanced_base enhanced_base_opt fonts fonts_opt games imaging imaging_opt kde kde_games kde_imaging kde_internet kde_multimedia
kde_office kde_plasma kde_utilities kde_utilities_opt kde_yast multimedia multimedia_opt non_oss non_oss_opt office office_opt sw_management
sw_management_kde x11 x11_opt yast2_basis
The following product is going to be downgraded:
"openSUSE Tumbleweed"
The following 2 packages are going to be reinstalled:
libtiff5 libtiff5-32bit
The following 3 packages are going to change architecture:
file-magic noarch -> x86_64
sharutils-lang noarch -> x86_64
tcsh-lang noarch -> x86_64
The following 4 packages are going to change vendor:
libopencv2_4 http://packman.links2linux.de -> openSUSE
libsoxr0 http://packman.links2linux.de -> openSUSE
libstreamanalyzer0 http://packman.links2linux.de -> openSUSE
libxml++-2_6-2 openSUSE -> http://packman.links2linux.de
6 packages to upgrade, 1765 to downgrade, 24 new, 2 to reinstall, 73 to remove, 4 to change vendor, 3 to change arch.
Overall download size: 382.6 MiB. Already cached: 638.1 MiB. After the operation, 23.7 MiB will be freed.
**Continue? [y/n/? shows all options] (y): **
Will this get me there safely? Thank you for your help. Truly appreciated.
It seems that I am there. Thanks to all who responded. If I run into any glitches that I cannot figure out I will be back. LOL (resulting from the dup) I think I may have cleaned some things up doing this. Not sure yet.
So be very carefull in using zypper dup in the future. In fact, do not use it when updateing your Leap. Use zypper patch (for the standard Update repos) or zypper up for updating from all repos (that includes the zypper patch). Only use zypper dup when you want to repeat the “switch to Packman” and then of course including the --from option.
