Tumbleweed rescue upgrade: Product problem during update initialisation
Dear openSUSE experts, I would like to rescue damaged tumbleweed instalation via upgrade from bootobale usb due to damaged are shim, glibc and rpm database at least. Chroot form SystemRecuseCD/SystemRecue is not possible to use After settings with only one popup window due to not popssible grub2 config read (error in script), there is everything ok. When upgrade is initialising it crashhed with no method path available in to remove product Tumblewwed 202105..in /mounts/imp001/usr/share/YaST2/lib/y2packager/resolvable.rb script on line 132. Maybe it is due to I was to used packager repository from openSuse build service repository in the past. Is there any solution to remove product from selection if trying to edit product list is not allowed in the installer,please? Something like moveing files from /etc/zypp/repos.d for packages will be helpfull to me, too. Or is there any other recomended solution,please? I look forward hearing from you Yours faithfully Peter Fodrek,j.r.
Op dinsdag 15 maart 2022 16:58:53 CET schreef Peter Fodrek,ml.-súkromne:
Dear openSUSE experts,
I would like to rescue damaged tumbleweed instalation via upgrade from bootobale usb due to damaged are shim, glibc and rpm database at least. Chroot form SystemRecuseCD/SystemRecue is not possible to use
After settings with only one popup window due to not popssible grub2 config read (error in script), there is everything ok. When upgrade is initialising it crashhed with no method path available in to remove product Tumblewwed 202105..in /mounts/imp001/usr/share/YaST2/lib/y2packager/resolvable.rb script on line 132.
Maybe it is due to I was to used packager repository from openSuse build service repository in the past.
Is there any solution to remove product from selection if trying to edit product list is not allowed in the installer,please?
Something like moveing files from /etc/zypp/repos.d for packages will be helpfull to me, too.
Or is there any other recomended solution,please?
I look forward hearing from you
Yours faithfully
Peter Fodrek,j.r.
In short: You use TW in a way you should never use it. It is a rolling distro, and now you want to update a 10 month old install ???? Please read the docs on updating TW. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
Am Dienstag, 15. März 2022, 17:03:43 CET schrieb Knurpht-openSUSE:
Op dinsdag 15 maart 2022 16:58:53 CET schreef Peter Fodrek,ml.-súkromne:
Dear openSUSE experts,
I would like to rescue damaged tumbleweed instalation via upgrade from bootobale usb due to damaged are shim, glibc and rpm database at least. Chroot form SystemRecuseCD/SystemRecue is not possible to use
After settings with only one popup window due to not popssible grub2 config read (error in script), there is everything ok. When upgrade is initialising it crashhed with no method path available in to remove product Tumblewwed 202105..in /mounts/imp001/usr/share/YaST2/lib/y2packager/resolvable.rb script on line 132.
Maybe it is due to I was to used packager repository from openSuse build service repository in the past.
Is there any solution to remove product from selection if trying to edit product list is not allowed in the installer,please?
Something like moveing files from /etc/zypp/repos.d for packages will be helpfull to me, too.
In short: You use TW in a way you should never use it. It is a rolling distro, and now you want to update a 10 month old install ????
And? It should work, and it worked for me already. I have not understood completely what the issue is: When you select upgrade from the USB it has issues with the old repository? During installation you can open a terminal window (CRTL-ALT-F2 for example) or from an X terminal window by pressing Ctrl-Alt-Shift-X. That should allow you to remove the problematic repository Cheers Axel
ut 15. 3. 2022 o 18:42 Axel Braun <docb@opensuse.org> napísal(a):
Am Dienstag, 15. März 2022, 17:03:43 CET schrieb Knurpht-openSUSE:
Op dinsdag 15 maart 2022 16:58:53 CET schreef Peter Fodrek,ml.-súkromne:
In short: You use TW in a way you should never use it. It is a rolling distro, and now you want to update a 10 month old install ????
And? It should work, and it worked for me already.
I have not understood completely what the issue is: When you select upgrade from the USB it has issues with the old repository?
During installation you can open a terminal window (CRTL-ALT-F2 for example) or from an X terminal window by pressing Ctrl-Alt-Shift-X. That should allow you to remove the problematic repository
Thank you for your answer. There seems not to be problem with repository but with removing product Tumblewwed 20210523 I was to mention if there are corresponding files for products as they exists for repositories I look forward hearing from you Yours faithfully Peter Fodrek
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2022-03-15 a las 18:41 +0100, Axel Braun escribió:
Am Dienstag, 15. März 2022, 17:03:43 CET schrieb Knurpht-openSUSE:
Op dinsdag 15 maart 2022 16:58:53 CET schreef Peter Fodrek,ml.-súkromne:
...
In short: You use TW in a way you should never use it. It is a rolling distro, and now you want to update a 10 month old install ????
And? It should work, and it worked for me already.
IMO, it is not supposed to work. The intended usage of Tumbleweed is frequent updating. Weekly. Monthly at worst. - -- Cheers Carlos E. R. (from openSUSE 15.3 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYjDZQhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVeisAn0+jRnIl3CkT+GXMPOrE FVeae+3PAJ0aTB94Z5sSqBL0ESQ0Z/IjGy84Uw== =jusD -----END PGP SIGNATURE-----
* Carlos E. R. <robin.listas@telefonica.net> [03-15-22 14:23]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El 2022-03-15 a las 18:41 +0100, Axel Braun escribió:
Am Dienstag, 15. März 2022, 17:03:43 CET schrieb Knurpht-openSUSE:
Op dinsdag 15 maart 2022 16:58:53 CET schreef Peter Fodrek,ml.-súkromne:
...
In short: You use TW in a way you should never use it. It is a rolling distro, and now you want to update a 10 month old install ????
And? It should work, and it worked for me already.
IMO, it is not supposed to work.
well, it is *supposed* to work and does.
The intended usage of Tumbleweed is frequent updating. Weekly. Monthly at worst.
I have not yet seen any set limit on when an update *must* be performed. and I hazard, nor have you. -- (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 oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...
Am 15.03.22 um 19:32 schrieb Patrick Shanahan:
* Carlos E. R. <robin.listas@telefonica.net> [03-15-22 14:23]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El 2022-03-15 a las 18:41 +0100, Axel Braun escribió:
Am Dienstag, 15. März 2022, 17:03:43 CET schrieb Knurpht-openSUSE:
Op dinsdag 15 maart 2022 16:58:53 CET schreef Peter Fodrek,ml.-súkromne:
...
In short: You use TW in a way you should never use it. It is a rolling distro, and now you want to update a 10 month old install ????
And? It should work, and it worked for me already.
IMO, it is not supposed to work.
well, it is *supposed* to work and does.
The intended usage of Tumbleweed is frequent updating. Weekly. Monthly at worst.
I have not yet seen any set limit on when an update *must* be performed. and I hazard, nor have you.
I sometimes update after long time >6 month on some systems. working fine. ... and when i have started, with tumbleweed, sombody here (or on another opensuse-mailinglist) told me there is "official" no limit for updating older systems. back to your problem: for tumbleweed you should have a internet connection to do the upgrades ("zypper dup") normaly you do not have to change any repos. if you use "tumbleweed cli" then your installation get stuck some weeks on a fixed version. after some weeks the repo ofthis version is gone and you do not find the repo any more. then you have to use the cli to change automatically the repo-path. updateing with usb stick i have no idear how this should work. as i understood the idear behind tumbleweed is to use internet. simoN -- www.becherer.de
Think I got it: the old entry for the install USB is still present. Look at the setup with zypper lr -d and you will see the repo index number. Do sudo zypper rr $repo index number -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
Dear Mr./Ms. Knurpht, Dňa 15. 3. 2022 o 19:52 Knurpht-openSUSE napísal(a):
Think I got it: the old entry for the install USB is still present. Look at the setup with zypper lr -d and you will see the repo index number. Do sudo zypper rr $repo index number
Doining this in chroot environment is impossible and does not work due to problem with glibc on orginal unbootable system. Only bussybox taken via System Rescue CD runs on original system. Every dynamically linked binary fails to load on original system even if full path is supplied. It seems to be glibc or even runtime linker problem. Is there available staticaly linked zypper, please? Therefor I am asking for file to manually edit/delete to do same as zypper rr. I am not able to find such file, yet. Thank for any help.
Dear Mr. Brzenkov, Dňa 16. 3. 2022 o 17:42 Andrei Borzenkov napísal(a):
On 16.03.2022 17:28, Peter Fodrek,ml.-súkromne wrote:
Therefor I am asking for file to manually edit/delete to do same as zypper rr. I am not able to find such file, yet.
/etc/zypp/repos.d
I have same error as before even after mount /dev/sdb3 ./suse cd suse/etc/zypp/repos.d mv *.repo .. sync cd umount ./suse in installer tty2 Before this I have benn done only selected repository file movement. Maybe zypper rr is not correct solution of my problem. I still cannot change selection of the products Tumbleweed and Tumbleweed-nonOSS in the installer I have separate partitions for / /home /var/log /boot /tmp two swap partitions and logically boot/efi Thanks Kind regards Peter
Dear SUSE, Dňa 15. 3. 2022 o 17:03 Knurpht-openSUSE napísal(a):
In short: You use TW in a way you should never use it. It is a rolling distro, and now you want to update a 10 month old install ???? Please read the docs on updating TW.
It just crashed when we needed to finish first version of software quickly . Due to this we used dual boot an Leap in WSL. And after finishing final version I was to try recover Tumbleeed. I know it is misuse. Then there is pending unwanted aleternative for me: To make fresh install of Tumbleweed with use of partitions from current system on same mountpoint as used now. Thanks Petere
Am Mittwoch, 16. März 2022, 09:24:38 CET schrieb Peter Fodrek,ml.-súkromne:
Dear SUSE,
Dňa 15. 3. 2022 o 17:03 Knurpht-openSUSE napísal(a):
In short: You use TW in a way you should never use it. It is a rolling distro, and now you want to update a 10 month old install ???? Please read the docs on updating TW.
It just crashed when we needed to finish first version of software quickly . Due to this we used dual boot an Leap in WSL. And after finishing final version I was to try recover Tumbleeed.
So ist not a bare-metal or VM Installation, but on WSL? Sorry, I'm out here. Base system is broken by design
I know it is misuse.
Then there is pending unwanted aleternative for me: To make fresh install of Tumbleweed with use of partitions from current system on same mountpoint as used now.
Do it. In a proper virtual machine or on real hardware. ANd try to avoid manual 'optimizations' Axel
Dňa 16. 3. 2022 o 21:01 Axel Braun napísal(a):
Am Mittwoch, 16. März 2022, 09:24:38 CET schrieb Peter Fodrek,ml.-súkromne:
Dear SUSE,
Dňa 15. 3. 2022 o 17:03 Knurpht-openSUSE napísal(a):
In short: You use TW in a way you should never use it. It is a rolling distro, and now you want to update a 10 month old install ???? Please read the docs on updating TW. It just crashed when we needed to finish first version of software quickly . Due to this we used dual boot an Leap in WSL. And after finishing final version I was to try recover Tumbleeed. So ist not a bare-metal or VM Installation, but on WSL?
WSL system worsks OK but bare metal is damaged. So I have been finished original bare matel project using WSL on the same dual boot machine. But finishing procets was too long to recover system as I heve been told here
Sorry, I'm out here. Base system is broken by design
OK
I know it is misuse.
Then there is pending unwanted aleternative for me: To make fresh install of Tumbleweed with use of partitions from current system on same mountpoint as used now. Do it. In a proper virtual machine or on real hardware. ANd try to avoid manual 'optimizations'
Problem is on bare metal Kind regards Peter
Dear SUSE, Dňa 15. 3. 2022 o 17:03 Knurpht-openSUSE napísal(a): In short: You use TW in a way you should never use it. It is a rolling distro, and now you want to update a 10 month old install ???? Please read the docs on updating TW. It just crashed when we needed to finish first version of software quickly . Due to this we used dual boot an Leap in WSL. And after finishing final version I was to try recover Tumbleeed. I know it is misuse. Then there is pending unwanted aleternative for me: To make fresh install of Tumbleweed with use of partitions from current system on same mountpoint as used now. Thanks Peter
participants (9)
-
Andrei Borzenkov -
Axel Braun -
Axel Braun -
Carlos E. R. -
Knurpht-openSUSE -
Patrick Shanahan -
Peter Fodrek -
Peter Fodrek,ml.-súkromne
-
Simon Becherer