[opensuse] Upgrading OpenSuSE and repos
Hello - I am still trying to track down and understand why my attempt to upgrade OpenSuSE Leap 42.3 to OpenSuSE Leap 15.0 has failed. After using an OpenSuSE installation DVD, to do an in place upgrade, my system was working partially OK but there were some problems with the plasma widgets and tools and and I was advised to try and do a zypper dup to fix those issues. That worked until I tried to do some further installation of some additional software and then I lost the ability to do anything with KDE. Both the keyboard and mouse no longer work at the point the login prompts are shown. I can SSH in to the system, and from that perspective everything seems to be working OK, services I want to run are running etc. Using the QT version of YaST, from an SSH shell, I have discovered that the repositories that YaST is using are still pointing at the 42.3 versions, so I suspect I now have a mixed bag of software from both the 42.3 and the 15.0 repos. Doing another zypper dup simply tells me there is nothing to update however... So I am wondering, could/should I go in to /etc/zypp/repos.d and change all the BaseURL references for the repositories from 42.3 to 15.0 (or perhaps to $releasever )? Seems like I could, but I am guessing.... And then I would think doing a zypper dup (or zypper dup --$releasever 15.0 ) might insure I have a consistent system? And this all begs another question, why weren't my repository definitions updated when I used the OpenSuSE installation DVD to upgrade my system? Marc... -- Linux Counter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Marc Chamberlin composed on 2019-01-18 21:45 (UTC-0800): ...
I have discovered that the repositories that YaST is using are still pointing at the 42.3 versions, so I suspect I now have a mixed bag of software from both the 42.3 and the 15.0 repos. Doing another zypper dup simply tells me there is nothing to update however...
That's because of the inane choice of release versions, from 13.x to 42.x to 15.x. There is nothing to update according to the package management system when there are bigger version numbers in 42.3 repos than those in 15.0 repos, which is many if not most.
So I am wondering, could/should I go in to /etc/zypp/repos.d and change all the BaseURL references for the repositories from 42.3 to 15.0 (or perhaps to $releasever )? Seems like I could, but I am guessing.... And then I would think doing a zypper dup (or zypper dup --$releasever 15.0 ) might insure I have a consistent system?...
I've done lots of successful dups from oldLeap to newerLeap, and 13.1 and 13.2 to Leap. The process begins by changing e.g. all instances of 42.3 in /etc/zypp/repos.d/*repo to 15.0. sed -i 's/42.3/15.0/g' /etc/zypp/repos.d/*repo That followed by zypper dup might fix you up. For your situation, various solver.dupAllow* options may require adjustment for a full fixup, either in /etc/zypp/zypp.conf or on your zypper cmdline. I'd try first as-is, then check to see what old packages might be left over zypper --no-refresh se -si | grep 'tem Pac' | grep -v plication before deciding on a next step. Zypper has a --dry-run option you might want to check out. man zypper -- Evolution as taught in public schools is religion, not science. 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
On 19/01/2019 07.36, Felix Miata wrote:
Marc Chamberlin composed on 2019-01-18 21:45 (UTC-0800): ...
I have discovered that the repositories that YaST is using are still pointing at the 42.3 versions, so I suspect I now have a mixed bag of software from both the 42.3 and the 15.0 repos. Doing another zypper dup simply tells me there is nothing to update however...
That's because of the inane choice of release versions, from 13.x to 42.x to 15.x. There is nothing to update according to the package management system when there are bigger version numbers in 42.3 repos than those in 15.0 repos, which is many if not most.
zypper dup doesn't care. Zypper up does.
So I am wondering, could/should I go in to /etc/zypp/repos.d and change all the BaseURL references for the repositories from 42.3 to 15.0 (or perhaps to $releasever )? Seems like I could, but I am guessing.... And then I would think doing a zypper dup (or zypper dup --$releasever 15.0 ) might insure I have a consistent system?...
I've done lots of successful dups from oldLeap to newerLeap, and 13.1 and 13.2 to Leap. The process begins by changing e.g. all instances of 42.3 in /etc/zypp/repos.d/*repo to 15.0.
sed -i 's/42.3/15.0/g' /etc/zypp/repos.d/*repo
That followed by zypper dup might fix you up.
I concur.
For your situation, various solver.dupAllow* options may require adjustment for a full fixup, either in /etc/zypp/zypp.conf or on your zypper cmdline. I'd try first as-is, then check to see what old packages might be left over
zypper --no-refresh se -si | grep 'tem Pac' | grep -v plication
before deciding on a next step.
Zypper has a --dry-run option you might want to check out.
man zypper
I'm curious about your mention of "various solver.dupAllow* options". I had not noticed them before. :-? To find leftover packages I run this query: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ or this one for importing to a calc sheet: rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \ %{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \ %{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}\n" \ | sort | cut --fields="2-" --delimiter=\; \ | tee rpmlist.csv | less -S It a sorted by install date list of all packages in the system, so at the top you find rpms that belong to the old system. Although in this case some 42.3 packages may have been installed recently, so simply search for them: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE\ Leap\ 15\.0|openSUSE_Leap_15\.0" | less -S which finds everything that doesn't say was built for 15.0 (with some errors). Or search for the string lp150 in the package name. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Felix Miata <mrmazda@earthlink.net> [01-19-19 01:38]:
Marc Chamberlin composed on 2019-01-18 21:45 (UTC-0800): ...
Zypper has a --dry-run option you might want to check out.
man zypper
which you/one may find superfluous as zypper will not commit changes w/o you accepting it's proposal or including "-y" on the command line. man zypper -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 19 januari 2019 07:36:12 CET schreef Felix Miata:
Marc Chamberlin composed on 2019-01-18 21:45 (UTC-0800): ...
I have discovered that the repositories that YaST is using are still pointing at the 42.3 versions, so I suspect I now have a mixed bag of software from both the 42.3 and the 15.0 repos. Doing another zypper dup simply tells me there is nothing to update however...
That's because of the inane choice of release versions, from 13.x to 42.x to 15.x. There is nothing to update according to the package management system when there are bigger version numbers in 42.3 repos than those in 15.0 repos, which is many if not most.
Nonsense. I have no idea where you get this. Next you tell me that upgrading from 13.2 -> 42.1 was not possible due to inane choice of missing numbers in the version sequence.
So I am wondering, could/should I go in to /etc/zypp/repos.d and change all the BaseURL references for the repositories from 42.3 to 15.0 (or perhaps to $releasever )? Seems like I could, but I am guessing.... And then I would think doing a zypper dup (or zypper dup --$releasever 15.0 ) might insure I have a consistent system?...
I've done lots of successful dups from oldLeap to newerLeap, and 13.1 and 13.2 to Leap. The process begins by changing e.g. all instances of 42.3 in /etc/zypp/repos.d/*repo to 15.0.
sed -i 's/42.3/15.0/g' /etc/zypp/repos.d/*repo
That followed by zypper dup might fix you up. For your situation, various solver.dupAllow* options may require adjustment for a full fixup, either in /etc/zypp/zypp.conf or on your zypper cmdline. I'd try first as-is, then check to see what old packages might be left over
zypper --no-refresh se -si | grep 'tem Pac' | grep -v plication
before deciding on a next step.
Zypper has a --dry-run option you might want to check out.
man zypper
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/01/2019 20.02, Knurpht-openSUSE wrote:
Op zaterdag 19 januari 2019 07:36:12 CET schreef Felix Miata:
Marc Chamberlin composed on 2019-01-18 21:45 (UTC-0800): ...
I have discovered that the repositories that YaST is using are still pointing at the 42.3 versions, so I suspect I now have a mixed bag of software from both the 42.3 and the 15.0 repos. Doing another zypper dup simply tells me there is nothing to update however...
That's because of the inane choice of release versions, from 13.x to 42.x to 15.x. There is nothing to update according to the package management system when there are bigger version numbers in 42.3 repos than those in 15.0 repos, which is many if not most.
Nonsense. I have no idea where you get this. Next you tell me that upgrading from 13.2 -> 42.1 was not possible due to inane choice of missing numbers in the version sequence.
On some operation zypper (I do not remember which) was complaining that the target version was lower. I took no notes or photos, but it was obviously due to the release number drop. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Op zaterdag 19 januari 2019 20:21:31 CET schreef Carlos E. R.:
On 19/01/2019 20.02, Knurpht-openSUSE wrote:
Op zaterdag 19 januari 2019 07:36:12 CET schreef Felix Miata:
Marc Chamberlin composed on 2019-01-18 21:45 (UTC-0800): ...
I have discovered that the repositories that YaST is using are still pointing at the 42.3 versions, so I suspect I now have a mixed bag of software from both the 42.3 and the 15.0 repos. Doing another zypper dup simply tells me there is nothing to update however...
That's because of the inane choice of release versions, from 13.x to 42.x to 15.x. There is nothing to update according to the package management system when there are bigger version numbers in 42.3 repos than those in 15.0 repos, which is many if not most.
Nonsense. I have no idea where you get this. Next you tell me that upgrading from 13.2 -> 42.1 was not possible due to inane choice of missing numbers in the version sequence.
On some operation zypper (I do not remember which) was complaining that the target version was lower. I took no notes or photos, but it was obviously due to the release number drop. Something else must have happened, no idea.
See here: https://en.opensuse.org/openSUSE:Packaging_for_Leap , the bit about RPM Distro Version Macros how it works. As you will see the 42.x series have a lower suse_version than 15.x get. That distinguishes 15.0 as a higher version that 42.3 . -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
20.01.2019 3:09, Knurpht-openSUSE пишет:
Op zaterdag 19 januari 2019 20:21:31 CET schreef Carlos E. R.:
On 19/01/2019 20.02, Knurpht-openSUSE wrote:
Op zaterdag 19 januari 2019 07:36:12 CET schreef Felix Miata:
Marc Chamberlin composed on 2019-01-18 21:45 (UTC-0800): ...
I have discovered that the repositories that YaST is using are still pointing at the 42.3 versions, so I suspect I now have a mixed bag of software from both the 42.3 and the 15.0 repos. Doing another zypper dup simply tells me there is nothing to update however...
That's because of the inane choice of release versions, from 13.x to 42.x to 15.x. There is nothing to update according to the package management system when there are bigger version numbers in 42.3 repos than those in 15.0 repos, which is many if not most.
Nonsense. I have no idea where you get this. Next you tell me that upgrading from 13.2 -> 42.1 was not possible due to inane choice of missing numbers in the version sequence.
On some operation zypper (I do not remember which) was complaining that the target version was lower. I took no notes or photos, but it was obviously due to the release number drop. Something else must have happened, no idea.
See here: https://en.opensuse.org/openSUSE:Packaging_for_Leap , the bit about RPM Distro Version Macros
These macros have absolutely nothing to do with version comparison during installation.
how it works. As you will see the 42.x series have a lower suse_version than 15.x get. That distinguishes 15.0 as a higher version that 42.3 .
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/01/2019 07.36, Felix Miata wrote:
Marc Chamberlin composed on 2019-01-18 21:45 (UTC-0800): ...
...
I've done lots of successful dups from oldLeap to newerLeap, and 13.1 and 13.2 to Leap. The process begins by changing e.g. all instances of 42.3 in /etc/zypp/repos.d/*repo to 15.0.
sed -i 's/42.3/15.0/g' /etc/zypp/repos.d/*repo
That followed by zypper dup might fix you up.
Before that, I forgot that it is better to do a "zypper clean", to clean local caches that point to old information from the previous URLs. And before that I also look at each file manually. I took the chance to change some repo names to make them consistent. Then also do a "zypper ref --force", not only because of the refresh itself, but because it downloads from the just edited repo files. Ie: sed edit clean refresh and finally, "zypper dup --download-in-advance". -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Felix Miata -
Knurpht-openSUSE -
Marc Chamberlin -
Patrick Shanahan