Re: [gentoo-user] Strange emerge behavior during new install
On Monday, 6 November 2023 19:04:28 GMT Alan McKinnon wrote: > There is a new item about this: > > https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html > > I did not read or act on any of the unread news articles, leaving it for > later > If only... I make sure I scan all GLEP42 news on a new install before I dive in, to make sure there's no gotchas with Profile changes and associated tarballs. Once bitten ... ;-) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Strange emerge behavior during new install
There is a new item about this: https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html I did not read or act on any of the unread news articles, leaving it for later If only... On Mon, Nov 6, 2023 at 8:46 PM Alan McKinnon wrote: > > > On Mon, Nov 6, 2023 at 7:35 PM Michael wrote: > >> On Monday, 6 November 2023 17:26:45 GMT Alan McKinnon wrote: >> > On Mon, Nov 6, 2023 at 6:56 PM Michael >> wrote: >> > > On Monday, 6 November 2023 16:16:50 GMT Alan McKinnon wrote: >> >> > > > At this point I see the host can't tab complete ls, mount ... export >> > > > more >> > > > stuff in PATH fixes that. >> > > >> > > Upon the baselayout update did you run (for good measure): >> > > >> > > env-update && source /etc/profile >> > > >> > > You shouldn't really need to add directories in your PATH manually. >> > >> > I agree but ls and mount and friends are in /bin and /bin is not in PATH >> > and /etc/profile sets this wrong PATH >> > PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin >> >> Oh! I wonder if this is relevant: >> >> https://wiki.gentoo.org/wiki/Merge-usr >> >> and the baselayout caught you on the hop? > > > Good catch! Yes, that is what the problem was. I could not emerge > merge-usr (grrr) so just fetched the script from git as explained on that > page and now emerge @world is trundling along merrily > > How interesting I used the systemd stage3 from 6 August, I wonder what has > changed with merged-usr in the last 2 months that today's tree no longer > works? > I would not have thought of that actually, before I had often used quite > old stage 3s and emerge @world would always sort it out. > > Thanks for the help! > > > -- > Alan McKinnon > alan dot mckinnon at gmail dot com > -- Alan McKinnon alan dot mckinnon at gmail dot com
Re: [gentoo-user] Strange emerge behavior during new install
On Mon, Nov 6, 2023 at 7:35 PM Michael wrote: > On Monday, 6 November 2023 17:26:45 GMT Alan McKinnon wrote: > > On Mon, Nov 6, 2023 at 6:56 PM Michael wrote: > > > On Monday, 6 November 2023 16:16:50 GMT Alan McKinnon wrote: > > > > > At this point I see the host can't tab complete ls, mount ... export > > > > more > > > > stuff in PATH fixes that. > > > > > > Upon the baselayout update did you run (for good measure): > > > > > > env-update && source /etc/profile > > > > > > You shouldn't really need to add directories in your PATH manually. > > > > I agree but ls and mount and friends are in /bin and /bin is not in PATH > > and /etc/profile sets this wrong PATH > > PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin > > Oh! I wonder if this is relevant: > > https://wiki.gentoo.org/wiki/Merge-usr > > and the baselayout caught you on the hop? Good catch! Yes, that is what the problem was. I could not emerge merge-usr (grrr) so just fetched the script from git as explained on that page and now emerge @world is trundling along merrily How interesting I used the systemd stage3 from 6 August, I wonder what has changed with merged-usr in the last 2 months that today's tree no longer works? I would not have thought of that actually, before I had often used quite old stage 3s and emerge @world would always sort it out. Thanks for the help! -- Alan McKinnon alan dot mckinnon at gmail dot com
Re: [gentoo-user] Strange emerge behavior during new install
On Monday, 6 November 2023 17:26:45 GMT Alan McKinnon wrote: > On Mon, Nov 6, 2023 at 6:56 PM Michael wrote: > > On Monday, 6 November 2023 16:16:50 GMT Alan McKinnon wrote: > > > At this point I see the host can't tab complete ls, mount ... export > > > more > > > stuff in PATH fixes that. > > > > Upon the baselayout update did you run (for good measure): > > > > env-update && source /etc/profile > > > > You shouldn't really need to add directories in your PATH manually. > > I agree but ls and mount and friends are in /bin and /bin is not in PATH > and /etc/profile sets this wrong PATH > PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin Oh! I wonder if this is relevant: https://wiki.gentoo.org/wiki/Merge-usr and the baselayout caught you on the hop? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Strange emerge behavior during new install
On Mon, Nov 6, 2023 at 6:56 PM Michael wrote: > On Monday, 6 November 2023 16:16:50 GMT Alan McKinnon wrote: > > Hi, > > > > New install here, recent .isos: > > install-amd64-minimal-20230806T163139Z.iso > > stage3-amd64-systemd-20230806T163139Z.tar.xz > > > > Following the handbook, keyworded ~amd64, synced, no issues at all until > > the emerge -avuND @world step, making the depgraph goes fine, offers 162 > > ebuilds to build. These first 4 build OK: sys-kernel/linux-headers-6.6 > > sys-devel/gnuconfig-20230731 > > sys-libs/ncurses-6.4_p20230401 > > sys-apps/baselayout-2.14 > > > > app-crypt/libmd-1.1.0 then fails with this: > > > > = > > > > >>> Emerging (5 of 158) app-crypt/libmd-1.1.0::gentoo > > > > /usr/bin/env: ‘bash’: No such file or directory > > * The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR > > * does not exist: '/var/tmp/portage/app-crypt/libmd-1.1.0' > > Does it exist and does it have the right permissions? > Yes, that dir is correct: # ls -ald /var/tmp/portage/ drwxrwxr-x 10 portage portage 138 Nov 6 17:16 /var/tmp/portage/ > e.g.: > > ~ $ stat /var/tmp/portage > File: /var/tmp/portage > Size: 40 Blocks: 0 IO Block: 4096 directory > Device: 0,47Inode: 1 Links: 2 > Access: (0775/drwxrwxr-x) Uid: ( 250/ portage) Gid: ( 250/ portage) > Access: 2023-11-06 08:28:27.627998525 + > Modify: 2023-11-06 08:28:27.627998525 + > Change: 2023-11-06 08:28:27.627998525 + > Birth: 2023-11-06 08:28:27.627998525 + > > > . > > Ok that's weird, never seen baselayout produce that. > > > > At this point I see the host can't tab complete ls, mount ... export more > > stuff in PATH fixes that. > > Upon the baselayout update did you run (for good measure): > > env-update && source /etc/profile > > You shouldn't really need to add directories in your PATH manually. > I agree but ls and mount and friends are in /bin and /bin is not in PATH and /etc/profile sets this wrong PATH PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin lemme go check bgo first Thanks, Alan Alan McKinnon alan dot mckinnon at gmail dot com
Re: [gentoo-user] Strange emerge behavior during new install
On Monday, 6 November 2023 16:16:50 GMT Alan McKinnon wrote: > Hi, > > New install here, recent .isos: > install-amd64-minimal-20230806T163139Z.iso > stage3-amd64-systemd-20230806T163139Z.tar.xz > > Following the handbook, keyworded ~amd64, synced, no issues at all until > the emerge -avuND @world step, making the depgraph goes fine, offers 162 > ebuilds to build. These first 4 build OK: sys-kernel/linux-headers-6.6 > sys-devel/gnuconfig-20230731 > sys-libs/ncurses-6.4_p20230401 > sys-apps/baselayout-2.14 > > app-crypt/libmd-1.1.0 then fails with this: > > = > > >>> Emerging (5 of 158) app-crypt/libmd-1.1.0::gentoo > > /usr/bin/env: ‘bash’: No such file or directory > * The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR > * does not exist: '/var/tmp/portage/app-crypt/libmd-1.1.0' Does it exist and does it have the right permissions? e.g.: ~ $ stat /var/tmp/portage File: /var/tmp/portage Size: 40 Blocks: 0 IO Block: 4096 directory Device: 0,47Inode: 1 Links: 2 Access: (0775/drwxrwxr-x) Uid: ( 250/ portage) Gid: ( 250/ portage) Access: 2023-11-06 08:28:27.627998525 + Modify: 2023-11-06 08:28:27.627998525 + Change: 2023-11-06 08:28:27.627998525 + Birth: 2023-11-06 08:28:27.627998525 + > >>> Failed to emerge app-crypt/libmd-1.1.0 > > .. > [ERROR] Task was destroyed but it is pending! > task: at > /usr/lib/python3.11/site-packages/portage/util/_async/ForkProcess.py:224> > wait_for= > cb=[_EbuildFetcherProcess._proc_join_done( name...code=-SIGTERM>)()]> > [ERROR] Task was destroyed but it is pending! > task: /usr/lib/python3.11/site-packages/portage/util/_async/ForkProcess.py:134> > wait_for= cb=[AsynchronousTask.async_wait..() at > /usr/lib/python3.11/site-packages/_emerge/AsynchronousTask.py:49, > Task.task_wakeup()]> cb=[SpawnProcess._main_exit()]> > [ERROR] Task was destroyed but it is pending! > task: /usr/lib/python3.11/site-packages/portage/util/_async/PipeLogger.py:98> > wait_for= > cb=[PipeLogger._io_loop_done()]> > [ERROR] Task was destroyed but it is pending! > task: /usr/lib/python3.11/site-packages/portage/util/_async/BuildLogger.py:101> > wait_for= cb=[AsynchronousTask.async_wait..() 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: /usr/lib/python3.11/site-packages/portage/util/_async/PipeLogger.py:98> > wait_for= > cb=[PipeLogger._io_loop_done()]> > > > Ok that's weird, never seen baselayout produce that. > > At this point I see the host can't tab complete ls, mount ... export more > stuff in PATH fixes that. Upon the baselayout update did you run (for good measure): env-update && source /etc/profile You shouldn't really need to add directories in your PATH manually. > Now every emerge I attempt does this: > > = > > >>> Running pre-merge checks for dev-libs/gmp-6.3.0 > > /usr/bin/env: ‘bash’: No such file or directory > /usr/bin/env: ‘bash’: No such file or directory > * The ebuild phase 'die_hooks' 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. > /usr/bin/env: ‘bash’: No such file or directory > * 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
