| View previous topic :: View next topic |
| Author |
Message |
ManfredB
Veteran
Joined: 27 Dec 2007
Posts: 1737
|
 Posted: Tue Feb 27, 2024 7:11 am Post subject: unstable Wandlung to merge-user - erfolglos |
 |
|
Hallo zusammen!
Ich habe eben mein unstable-System aktualisiert, danach eselect profile list ausgeführt
und eselect profile set 9 gewählt
Nun Schritt für Schritt nach den News gegangen.
21 (1 update, 20 reinstalls) Packages sollen installiert werden.
Doch der Prozess endet mit folgender Begründung:
| Code: |
Total: 21 packages (1 upgrade, 20 reinstalls), Size of downloads: 13.146 KiB
Would you like to merge these packages? [Yes/No] y
>>> Verifying ebuild manifests
>>> Running pre-merge checks for net-wireless/wireless-regdb-20230503-r2
/usr/bin/env: ‘bash’: No such file or directory
/usr/bin/env: ‘bash’: No such file or directory
>>> Failed to emerge net-wireless/wireless-regdb-20230503-r2, Log file:
>>> '/var/tmp/portage/net-wireless/wireless-regdb-20230503-r2/temp/build.log'
>>> Running pre-merge checks for sys-libs/libxcrypt-4.4.36-r2
/usr/bin/env: ‘bash’: No such file or directory
/usr/bin/env: ‘bash’: No such file or directory
>>> Failed to emerge sys-libs/libxcrypt-4.4.36-r2, Log file:
>>> '/var/tmp/portage/sys-libs/libxcrypt-4.4.36-r2/temp/build.log'
>>> Running pre-merge checks for sys-apps/systemd-255.3-r1
/usr/bin/env: ‘bash’: No such file or directory
/usr/bin/env: ‘bash’: No such file or directory
>>> Failed to emerge sys-apps/systemd-255.3-r1, Log file:
>>> '/var/tmp/portage/sys-apps/systemd-255.3-r1/temp/build.log'
* Messages for package net-wireless/wireless-regdb-20230503-r2:
* The ebuild phase 'pretend' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
* Messages for package sys-libs/libxcrypt-4.4.36-r2:
* The ebuild phase 'pretend' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
* Messages for package sys-apps/systemd-255.3-r1:
* The ebuild phase 'pretend' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
*
* The following 3 packages have failed to build, install, or execute
* postinst:
*
* (net-wireless/wireless-regdb-20230503-r2:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/net-wireless/wireless-regdb-20230503-r2/temp/build.log'
* (sys-libs/libxcrypt-4.4.36-r2:0/1::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/sys-libs/libxcrypt-4.4.36-r2/temp/build.log'
* (sys-apps/systemd-255.3-r1:0/2::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/sys-apps/systemd-255.3-r1/temp/build.log'
*
[ERROR] Task was destroyed but it is pending!
task: <Task pending name='Task-2668' coro=<PipeLogger._io_loop() done, defined at /usr/lib/python3.11/site-packages/portage/util/_async/PipeLogger.py:83> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[PipeLogger._io_loop_done()]>
[ERROR] Task was destroyed but it is pending!
task: <Task pending name='Task-2669' coro=<BuildLogger._main() done, defined at /usr/lib/python3.11/site-packages/portage/util/_async/BuildLogger.py:131> wait_for=<Future pending cb=[AsynchronousTask.async_wait.<locals>.<lambda>() at /usr/lib/python3.11/site-packages/_emerge/AsynchronousTask.py:49, Task.task_wakeup()]> cb=[BuildLogger._main_exit()]>
[ERROR] Task was destroyed but it is pending!
task: <Task pending name='Task-2670' coro=<PipeLogger._io_loop() done, defined at /usr/lib/python3.11/site-packages/portage/util/_async/PipeLogger.py:83> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[PipeLogger._io_loop_done()]>
[ERROR] Task was destroyed but it is pending!
task: <Task pending name='Task-2671' coro=<ForkProcess._main() done, defined at /usr/lib/python3.11/site-packages/portage/util/_async/ForkProcess.py:180> wait_for=<Future pending cb=[AsynchronousTask.async_wait.<locals>.<lambda>() at /usr/lib/python3.11/site-packages/_emerge/AsynchronousTask.py:49, Task.task_wakeup()]> cb=[SpawnProcess._main_exit()]>
|
Wie soll es nun weitergehen. Ich habe alle Schritte, die angezeigt wurden, durchgeführt, doch lzo scheitert.
Gibt es nun eine Lösung oder muss ich auch unstable neu installieren mit stage-merged-usr?
Liebe Grüße
ManfredB |
|
| Back to top |
|
 |
ManfredB
Veteran
Joined: 27 Dec 2007
Posts: 1737
|
| Posted: Tue Feb 27, 2024 7:40 am Post subject: |
|
|
Was hat es mit /usr/bin/env 'bash' zu tun?
Es ist mir vollkommen unklar, was da nicht stimmt - bzw, warum?
ManfredB |
|
| Back to top |
|
|
Josef.95
Advocate
Joined: 03 Sep 2007
Posts: 4669
Location: Germany
|
| Posted: Tue Feb 27, 2024 8:20 am Post subject: |
|
|
Hallo Manfred,
da hast wahrscheinlich den gleichen Fehler wie gestern gemacht -> https://forums.gentoo.org/viewtopic-t-1167555.html
Falsche Reihenfolge - lese dir bitte noch mal die news durch - dort ist genau beschrieben nach welchem Schritt das Profil umgestellt wird.
| Quote: | | und eselect profile set 9 gewählt |
Manfred, nochmal - keiner kann wissen was mit "set 9" gemeint ist (die Nummern können sich ändern) - nenne die Profile bitte beim vollen Namen. |
|
| Back to top |
|
|
ManfredB
Veteran
Joined: 27 Dec 2007
Posts: 1737
|
| Posted: Tue Feb 27, 2024 8:30 am Post subject: |
|
|
Hallo Josef.95!
Ich bin zuerst zum Update gegangen, danach emerge --ask --depclean --exclude nano.
Nun: eselect profile list. eselect profile set 9
[9] default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr (stable) *
emerge --ask merge-usr
merge-usr --dryrun
Dabei sind die ~/ vor den Verzeichnissen nicht vorhanden. |
|
| Back to top |
|
|
Josef.95
Advocate
Joined: 03 Sep 2007
Posts: 4669
Location: Germany
|
|
| Back to top |
|
|
ManfredB
Veteran
Joined: 27 Dec 2007
Posts: 1737
|
| Posted: Tue Feb 27, 2024 9:12 am Post subject: |
|
|
In den news nach dem update stand als erstes: neues Profil einstellen,
erst dann kamen die einzelnen Prozesse.
Das ist ja wirklich ein Durcheinander. Ich muss mich doch an die Anleitungen nach meinem normalen Update halten,
so wurde es mir geschrieben.
Nun ist in der von dir gezeigten Anleitung alles anders, kein Wunder, daß nun nichts funktioniert.
Die Aufforderung zum neuen Profil taucht nach einer roten Schrift auf, in der von dem bisherigen Profile nichts mehr stimmt.
Wenn nun die Anleitung im Netz das Ganze korrigiert, dann könnte das Update danach klappen.
Vielen Dank noch einmal für die Korrektur.
Liebe Grüße
ManfredB |
|
| Back to top |
|
|
Josef.95
Advocate
Joined: 03 Sep 2007
Posts: 4669
Location: Germany
|
| Posted: Tue Feb 27, 2024 9:48 am Post subject: |
|
|
| ManfredB wrote: | | Wenn nun die Anleitung im Netz das Ganze korrigiert, dann könnte das Update danach klappen. |
Manfred, dieser verlinkte news item ist nicht neu - der ist von Dezember 2022,
und, er sollte auch auf deinen System vorhanden sein, schau zb mal via | Code: | | eselect news read 2022-12-01-systemd-usrmerge |
Vermutlich hast du ihn bisher nur übersehen. |
|
| Back to top |
|
|
ManfredB
Veteran
Joined: 27 Dec 2007
Posts: 1737
|
| Posted: Tue Feb 27, 2024 10:33 am Post subject: |
|
|
Ich habe nun in gentoo-stable diese Schritte nacheinander durchgeführt.
Dennoch findet das Update nach dem ersten Paket wieder nicht statt.
/usr/bin/env 'bash' ist der immer wiederkehrende Fehler.
Ich hätte nie gedacht, daß ein bestehendes System derart umgestaltet werden muss und dennoch noicht gelingt.
Was mache ich falsch oder übersehe ich?
Sorry, wenn ich immer wieder stolpere.
Gruß
ManfredB |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Deutsches Forum (German)
