[opensuse] Tumbleweed advice
I have an old Tumbleweed install that has been sitting on a shelf. OOC, I thought I would try to update it. I know it has been perhaps too long, but it is just a test. The problem is related to zypper-migration-plugin, which I am pretty sure I want to get updated correctly! The other problems are not an issue, as I see it. systems:~ # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20170929" ID=opensuse ID_LIKE="suse" VERSION_ID="20170929" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20170929" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" systems:~ # 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... 6 Problems: Problem: problem with installed package python-cx_Freeze-4.3.2-1.2.i586 Problem: problem with installed package windowswmproto-devel-1.0.4-3.1.i586 Problem: problem with installed package wine-mono-4.5.2-10.7.noarch Problem: nothing provides rubygem(ruby:2.6.0:suse-connect) >= 0.3.10 needed by zypper-migration-plugin-0.12.1536145027.be6a3dd-1.5.noarch Problem: libopenssl-1_0_0-devel-1.0.2r-1.4.i586 conflicts with libopenssl-devel > 1.0.2r provided by libopenssl-devel-1.1.1c-1.1.noarch Problem: transfig-3.2.7a-2.6.i586 requires texlive-epstopdf, but this requirement cannot be provided [SNIP] Problem: nothing provides rubygem(ruby:2.6.0:suse-connect) >= 0.3.10 needed by zypper-migration-plugin-0.12.1536145027.be6a3dd-1.5.noarch Solution 1: keep obsolete zypper-migration-plugin-0.10.1488806253.1c712c3-1.2.noarch Solution 2: break zypper-migration-plugin-0.12.1536145027.be6a3dd-1.5.noarch by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): Neither solution seems hopeful. Any better options? Even if the system is not being used right now, I would like to keep it set up. I would prefer not to lose it. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne čtvrtek 8. srpna 2019 10:26:47 CEST, Roger Oberholtzer napsal(a):
I have an old Tumbleweed install that has been sitting on a shelf. OOC, I thought I would try to update it. I know it has been perhaps too long, but it is just a test. The problem is related to zypper-migration-plugin, which I am pretty sure I want to get updated correctly! The other problems are not an issue, as I see it.
[...]
Any better options? Even if the system is not being used right now, I would like to keep it set up. I would prefer not to lose it.
As first step I'd ensure there are correct repositories. E.g. I have https://paste.opensuse.org/view/raw/7711291 You need at least http://download.opensuse.org/tumbleweed/repo/non-oss/ http://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/update/tumbleweed/ -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/
On Thu, Aug 8, 2019 at 10:34 AM Vojtěch Zeisek <vojtech.zeisek@opensuse.org> wrote:
Dne čtvrtek 8. srpna 2019 10:26:47 CEST, Roger Oberholtzer napsal(a):
I have an old Tumbleweed install that has been sitting on a shelf. OOC, I thought I would try to update it. I know it has been perhaps too long, but it is just a test. The problem is related to zypper-migration-plugin, which I am pretty sure I want to get updated correctly! The other problems are not an issue, as I see it.
[...]
Any better options? Even if the system is not being used right now, I would like to keep it set up. I would prefer not to lose it.
As first step I'd ensure there are correct repositories. E.g. I have https://paste.opensuse.org/view/raw/7711291 You need at least http://download.opensuse.org/tumbleweed/repo/non-oss/ http://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/update/tumbleweed/
Yes: # | Alias | Name | Enabled | GPG Check | Refresh | Type | URI --+--------------+--------------+---------+-----------+---------+----------+----------------------------------------------------- 1 | Local_RPMs | Local RPMs | No | ---- | ---- | plaindir | dir:///root/localRepo 2 | repo-debug | repo-debug | Yes | (r ) Yes | Yes | rpm-md | http://download.opensuse.org/tumbleweed/repo/debug 3 | repo-non-oss | repo-non-oss | Yes | (r ) Yes | Yes | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss 4 | repo-oss | repo-oss | Yes | (r ) Yes | Yes | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss 5 | repo-update | repo-update | Yes | (r ) Yes | Yes | rpm-md | http://download.opensuse.org/update/tumbleweed/ -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.08.19 um 10:33 schrieb Vojtěch Zeisek:
Dne čtvrtek 8. srpna 2019 10:26:47 CEST, Roger Oberholtzer napsal(a):
I have an old Tumbleweed install that has been sitting on a shelf. OOC, I thought I would try to update it. I know it has been perhaps too long, but it is just a test. The problem is related to zypper-migration-plugin, which I am pretty sure I want to get updated correctly! The other problems are not an issue, as I see it.
[...]
Any better options? Even if the system is not being used right now, I would like to keep it set up. I would prefer not to lose it.
As first step I'd ensure there are correct repositories. E.g. I have https://paste.opensuse.org/view/raw/7711291 You need at least http://download.opensuse.org/tumbleweed/repo/non-oss/ http://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/update/tumbleweed/
and make sure you do not have a installation CD still enabled in the list. sometimes if i had problems with zypper, i stay on the old version of the problematic dependency and use yast later on the problematic pieces to update it. i have had situations where it then would update in yast (after a zypper dup with problems) without problems (all resolved automatically). simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Aug 8, 2019 at 8:44 PM Simon Becherer <simon@becherer.de> wrote:
and make sure you do not have a installation CD still enabled in the list. sometimes if i had problems with zypper, i stay on the old version of the problematic dependency and use yast later on the problematic pieces to update it. i have had situations where it then would update in yast (after a zypper dup with problems) without problems (all resolved automatically).
The ISO/CD is disabled and not in the computer. What worries me is that if zypper gets messed up, things surely will go bad. zypper-migration-plugin seems like something one does not want to take chances with. An up-to-date (within a week) Tumbleweed has these zypper-named packages: zypper-aptitude-1.14.28-1.2.noarch zypper-log-1.14.28-1.2.noarch zypper-needs-restarting-1.14.28-1.2.noarch zypper-lifecycle-plugin-0.6.1490613702.a925823-2.9.noarch zypper-1.14.28-1.2.x86_64 Maybe zypper-migration-plugin is no longer needed? Or perhaps it needs to do some migration stuff first? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Roger Oberholtzer <roger.oberholtzer@gmail.com> [08-08-19 15:00]:
On Thu, Aug 8, 2019 at 8:44 PM Simon Becherer <simon@becherer.de> wrote:
and make sure you do not have a installation CD still enabled in the list. sometimes if i had problems with zypper, i stay on the old version of the problematic dependency and use yast later on the problematic pieces to update it. i have had situations where it then would update in yast (after a zypper dup with problems) without problems (all resolved automatically).
The ISO/CD is disabled and not in the computer.
What worries me is that if zypper gets messed up, things surely will go bad. zypper-migration-plugin seems like something one does not want to take chances with.
make it a habit to: zypper ref zypper up/dup -d zypper up/dup downloading in advance will make sure you have the necessary zipper components to install but make sure you perform the above in sequence and immediately after each other. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri 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
Am 08.08.19 um 20:57 schrieb Roger Oberholtzer:
On Thu, Aug 8, 2019 at 8:44 PM Simon Becherer <simon@becherer.de> wrote:
and make sure you do not have a installation CD still enabled in the list. sometimes if i had problems with zypper, i stay on the old version of the problematic dependency and use yast later on the problematic pieces to update it. i have had situations where it then would update in yast (after a zypper dup with problems) without problems (all resolved automatically).
The ISO/CD is disabled and not in the computer.
What worries me is that if zypper gets messed up, things surely will go bad. zypper-migration-plugin seems like something one does not want to take chances with.
An up-to-date (within a week) Tumbleweed has these zypper-named packages:
zypper-aptitude-1.14.28-1.2.noarch zypper-log-1.14.28-1.2.noarch zypper-needs-restarting-1.14.28-1.2.noarch zypper-lifecycle-plugin-0.6.1490613702.a925823-2.9.noarch zypper-1.14.28-1.2.x86_64
Maybe zypper-migration-plugin is no longer needed? Or perhaps it needs to do some migration stuff first?
sorry no good idea, but maybe (if you use the tumbleweed cli) try to set to another target and check if it updates there. tumbleweed list 20190806 20190805 20190730 20190726 20190724 20190723 20190721 20190718 20190717 20190716 20190713 20190708 20190704 20190703 20190702 20190701 20190630 20190628 20190627 20190626 on my systems 20190607 zypper-migration-plugin is installed. i will update maybe next week so if its a problem, i will run (maybe) into it also.... if you find a solution, .... :-)) simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Aug 8, 2019 at 9:20 PM Simon Becherer <simon@becherer.de> wrote:
Maybe zypper-migration-plugin is no longer needed? Or perhaps it needs to do some migration stuff first?
sorry no good idea, but maybe (if you use the tumbleweed cli) try to set to another target and check if it updates there.
I have not been using tumbleweed cli...
on my systems 20190607 zypper-migration-plugin is installed. i will update maybe next week so if its a problem, i will run (maybe) into it also.... if you find a solution, .... :-))
Odd. On a different Tumbleweed (not the one with the problem) from 20190730, it is not installed. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 8 augustus 2019 22:50:29 CEST schreef Roger Oberholtzer:
On Thu, Aug 8, 2019 at 9:20 PM Simon Becherer <simon@becherer.de> wrote:
Maybe zypper-migration-plugin is no longer needed? Or perhaps it needs to do some migration stuff first?
sorry no good idea, but maybe (if you use the tumbleweed cli) try to set to another target and check if it updates there.
I have not been using tumbleweed cli...
on my systems 20190607 zypper-migration-plugin is installed. i will update maybe next week so if its a problem, i will run (maybe) into it also.... if you find a solution, .... :-))
Odd. On a different Tumbleweed (not the one with the problem) from 20190730, it is not installed. It is not on my ~3 year old TW install.... Remove it, and dup :-)
-- 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 8/8/19 3:20 PM, Simon Becherer wrote:
Am 08.08.19 um 20:57 schrieb Roger Oberholtzer:
On Thu, Aug 8, 2019 at 8:44 PM Simon Becherer <simon@becherer.de> wrote:
and make sure you do not have a installation CD still enabled in the list. sometimes if i had problems with zypper, i stay on the old version of the problematic dependency and use yast later on the problematic pieces to update it. i have had situations where it then would update in yast (after a zypper dup with problems) without problems (all resolved automatically).
The ISO/CD is disabled and not in the computer.
What worries me is that if zypper gets messed up, things surely will go bad. zypper-migration-plugin seems like something one does not want to take chances with.
An up-to-date (within a week) Tumbleweed has these zypper-named packages:
zypper-aptitude-1.14.28-1.2.noarch zypper-log-1.14.28-1.2.noarch zypper-needs-restarting-1.14.28-1.2.noarch zypper-lifecycle-plugin-0.6.1490613702.a925823-2.9.noarch zypper-1.14.28-1.2.x86_64
Maybe zypper-migration-plugin is no longer needed? Or perhaps it needs to do some migration stuff first?
I highly, highly recommend updating zypper and it's dependencies first. Then run... zypper -v dup --dry-run (to test if the dup will actually first then run...) zypper -v dup -d run a second or third time until all packages have been downloaded. Once all package updates are downloaded then proceed with the actual DUP. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Ken Schneider - openSUSE <suse-list3@bout-tyme.net> [08-09-19 18:04]:
On 8/8/19 3:20 PM, Simon Becherer wrote:
Am 08.08.19 um 20:57 schrieb Roger Oberholtzer:
On Thu, Aug 8, 2019 at 8:44 PM Simon Becherer <simon@becherer.de> wrote:
and make sure you do not have a installation CD still enabled in the list. sometimes if i had problems with zypper, i stay on the old version of the problematic dependency and use yast later on the problematic pieces to update it. i have had situations where it then would update in yast (after a zypper dup with problems) without problems (all resolved automatically).
The ISO/CD is disabled and not in the computer.
What worries me is that if zypper gets messed up, things surely will go bad. zypper-migration-plugin seems like something one does not want to take chances with.
An up-to-date (within a week) Tumbleweed has these zypper-named packages:
zypper-aptitude-1.14.28-1.2.noarch zypper-log-1.14.28-1.2.noarch zypper-needs-restarting-1.14.28-1.2.noarch zypper-lifecycle-plugin-0.6.1490613702.a925823-2.9.noarch zypper-1.14.28-1.2.x86_64
Maybe zypper-migration-plugin is no longer needed? Or perhaps it needs to do some migration stuff first?
I highly, highly recommend updating zypper and it's dependencies first. Then run... zypper -v dup --dry-run (to test if the dup will actually first then run...) zypper -v dup -d
run a second or third time until all packages have been downloaded. Once all package updates are downloaded then proceed with the actual DUP.
zypper -v ref ; zypper -v dup --no-r --no-allow-v -d && zypper -v dup --no-r --no-allow-v -y -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri 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
Roger Oberholtzer composed on 2019-08-08 10:26 (UTC+0200):
VERSION_ID="20170929" .. Problem: nothing provides rubygem(ruby:2.6.0:suse-connect) >= 0.3.10 needed by zypper-migration-plugin-0.12.1536145027.be6a3dd-1.5.noarch ... Any better options? Even if the system is not being used right now, I would like to keep it set up. I would prefer not to lose it.
I have a vague recollection this might have had something to do with a base filesystem move, something from /usr/ somewhere to /run/ somewhere, which may have originally been created as a symlink rather than a real directory, or vice versa, and needing special handling for the reconfiguration to succeed. If you still have zypper-migration-plugin installed, what do its changelog and rpm -qi have to say about it? If last log entry is before 20170929, I'd just remove it and proceed to dup. If you're still worried about system management getting corrupted, do as I do, upgrade package management first. Run the following between zypper ref and zypper dup: zypper in --download-in-advance zypper libzypp libsolv-tools rpm libproxy1 libmodman1 libyui10 libyui-qt10 libyui-qt-pkg10 libyui-ncurses10 libyui-ncurses-pkg10 libyui-qt-graph10 I just finished a successful 32bit zypper dup from TW20190604 to TW20190808 without zypper-migration-plugin installed either before or after. -- 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
participants (7)
-
Felix Miata -
Ken Schneider - openSUSE -
Knurpht-openSUSE -
Patrick Shanahan -
Roger Oberholtzer -
Simon Becherer -
Vojtěch Zeisek