is it possible to tell YaST package manager to work on a different partition?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, To repair a borked system, I would need to use yast running on a rescue partition, but writing packages and such to another partition. I know I can do this with rpm, perhaps with zypper, but I need "yast sw_single" (zypper caused the borking) YaST as used during install can do it. - -- Cheers Carlos E. R. (from openSUSE Leap 15.2 at Legolas) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYRz9Txwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVRZQAoIL5hYIK3oTTkA9wmG/g UXmEq1q5AJ9PvkBMYtyOC2oe6hnzYZ4PDKMzDA== =g3P+ -----END PGP SIGNATURE-----
* Carlos E. R. <robin.listas@telefonica.net> [08-18-21 08:32]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
To repair a borked system, I would need to use yast running on a rescue partition, but writing packages and such to another partition.
I know I can do this with rpm, perhaps with zypper, but I need "yast sw_single"
(zypper caused the borking)
YaST as used during install can do it.
- -- Cheers
Carlos E. R. (from openSUSE Leap 15.2 at Legolas)
-----BEGIN PGP SIGNATURE-----
iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYRz9Txwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVRZQAoIL5hYIK3oTTkA9wmG/g UXmEq1q5AJ9PvkBMYtyOC2oe6hnzYZ4PDKMzDA== =g3P+ -----END PGP SIGNATURE-----
but doesn't "YaST" use zipper? -- (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
On 18/08/2021 15.08, Patrick Shanahan wrote:
* Carlos E. R. <> [08-18-21 08:32]:
Hi,
To repair a borked system, I would need to use yast running on a rescue partition, but writing packages and such to another partition.
I know I can do this with rpm, perhaps with zypper, but I need "yast sw_single"
(zypper caused the borking)
YaST as used during install can do it.
but doesn't "YaST" use zipper?
No. Both use the same libraries, which is different. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.2 (Legolas))
Carlos E. R. wrote:
To repair a borked system, I would need to use yast running on a rescue partition, but writing packages and such to another partition.
Depending on how borked your target system is, maybe you can chroot into it and then run yast ? -- Per Jessen, Zürich (21.9°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland.
On 18/08/2021 17.15, Per Jessen wrote:
Carlos E. R. wrote:
To repair a borked system, I would need to use yast running on a rescue partition, but writing packages and such to another partition.
Depending on how borked your target system is, maybe you can chroot into it and then run yast ?
I was just thinking of doing that this second... yast2 sw_single gives: Main_chrooted_on_Andor:~ # yast2 sw_single & [1] 7918 Main_chrooted_on_Andor:~ # Failure (dbus fatal exception). No protocol specified No protocol specified /sbin/yast2: line 468: 7944 Aborted (core dumped) $ybindir/y2start $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS [1]+ Exit 134 yast2 sw_single Main_chrooted_on_Andor:~ # -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.2 (Legolas))
On 18/08/2021 18.58, Carlos E. R. wrote:
On 18/08/2021 17.15, Per Jessen wrote:
Carlos E. R. wrote:
To repair a borked system, I would need to use yast running on a rescue partition, but writing packages and such to another partition.
Depending on how borked your target system is, maybe you can chroot into it and then run yast ?
I was just thinking of doing that this second...
yast2 sw_single
gives:
Main_chrooted_on_Andor:~ # yast2 sw_single & [1] 7918 Main_chrooted_on_Andor:~ # Failure (dbus fatal exception). No protocol specified No protocol specified /sbin/yast2: line 468: 7944 Aborted (core dumped) $ybindir/y2start $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
[1]+ Exit 134 yast2 sw_single Main_chrooted_on_Andor:~ #
Notice that yast in text mode does run in the real system, but network is borked. Possible way out may be to force upgrade to 15.2 on dvd. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.2 (Legolas))
Carlos E. R. wrote:
On 18/08/2021 17.15, Per Jessen wrote:
Carlos E. R. wrote:
To repair a borked system, I would need to use yast running on a rescue partition, but writing packages and such to another partition.
Depending on how borked your target system is, maybe you can chroot into it and then run yast ?
I was just thinking of doing that this second...
yast2 sw_single
I assume you bind-mounted all the usual? -- Per Jessen, Zürich (20.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
On 18/08/2021 19.27, Per Jessen wrote:
Carlos E. R. wrote:
On 18/08/2021 17.15, Per Jessen wrote:
Carlos E. R. wrote:
To repair a borked system, I would need to use yast running on a rescue partition, but writing packages and such to another partition.
Depending on how borked your target system is, maybe you can chroot into it and then run yast ?
I was just thinking of doing that this second...
yast2 sw_single
I assume you bind-mounted all the usual?
Yep, but there is some environment missing. Not the first rodeo with yast and chroot, but this one I don't know. I feared as much, so the wish/to change the work path of yast. zypper insisted on installing the -preempt kernel instead, then froze on os-prober. I had to kill processes, and finally hard reboot, there was no way out :-/ With YaST I can try to see why it wants the preempt kernel and force it out. Zypper, no way or hell of a way. Now, in chroot, I have attempted another go with zypper, who knows. I'll try to reboot. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.2 (Legolas))
On 18/08/2021 19.42, Carlos E. R. wrote:
On 18/08/2021 19.27, Per Jessen wrote:
Carlos E. R. wrote:
...
Now, in chroot, I have attempted another go with zypper, who knows. I'll try to reboot.
Well, reboot succeeded this time. But kernel running is kernel-preempt, not -default, and I can not remove kernel-preempt. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
participants (3)
-
Carlos E. R. -
Patrick Shanahan -
Per Jessen