[gentoo-user] PORTAGE_BUILDDIR does not exist

[gentoo-user] PORTAGE_BUILDDIR does not exist

[Ashley Dixon]

[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]

Hi,

I've been getting this build message for every package that I attempt to emerge.
I'm starting to become  concerned  that  my  Portage  installation  is  corrupt,
although  I  want  to  make  sure  before  I  try  and  embark  on  the  lengthy
Portage-rescue process.

For example, if I try to emerge app-editors/emacs (a package I  have  never  had
installed), I get the following error, both from emerge and a raw Python  crash:

Calculating dependencies  ... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 5) net-libs/liblockfile-1.16::gentoo
 * Fetching files in the background.
 * To view fetch progress, run in another terminal:
 * tail -f /var/log/emerge-fetch.log
[Errno 2] No such file or directory: 'mount': 'mount':
   /bin/bash -c /usr/lib/portage/python3.6/ebuild.sh clean
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/portage/process.py", line 382, in spawn
    unshare_flags, cgroup)
  File "/usr/lib64/python3.6/site-packages/portage/process.py", line 691, in _exec
    '--make-slave', '/proc'])
  File "/usr/lib64/python3.6/subprocess.py", line 729, in __init__
    restore_signals, start_new_session)
  File "/usr/lib64/python3.6/subprocess.py", line 1364, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'mount': 'mount'
 * The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR
 * does not exist: '/var/tmp/portage/net-libs/liblockfile-1.16'

>>> Failed to emerge net-libs/liblockfile-1.16
 * Messages for package net-libs/liblockfile-1.16:

<This is the end of the output; there are no messages from liblockfile.>

Does  anyone  know  if  anything  can  be  done,  short  of  re-installing   and
re-configuring Portage ?

-- 

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] PORTAGE_BUILDDIR does not exist

[Jack]

I'd start by looking at /var/tmp/portage/ (unless you changed the  
default PORTAGE_TMPDIR) to see what evidence the emerge process might  
have left.

On 2020.04.21 16:58, Ashley Dixon wrote:
> Hi,
> 
> I've been getting this build message for every package that I attempt  
> to emerge.
> I'm starting to become  concerned  that  my  Portage  installation   
> is  corrupt,
> although  I  want  to  make  sure  before  I  try  and  embark  on   
> the  lengthy
> Portage-rescue process.
> 
> For example, if I try to emerge app-editors/emacs (a package I  have   
> never  had
> installed), I get the following error, both from emerge and a raw  
> Python  crash:
> 
> Calculating dependencies  ... done!
> 
> >>> Verifying ebuild manifests
> 
> >>> Emerging (1 of 5) net-libs/liblockfile-1.16::gentoo
>  * Fetching files in the background.
>  * To view fetch progress, run in another terminal:
>  * tail -f /var/log/emerge-fetch.log
> [Errno 2] No such file or directory: 'mount': 'mount':
>    /bin/bash -c /usr/lib/portage/python3.6/ebuild.sh clean
> Traceback (most recent call last):
>   File "/usr/lib64/python3.6/site-packages/portage/process.py", line  
> 382, in spawn
>     unshare_flags, cgroup)
>   File "/usr/lib64/python3.6/site-packages/portage/process.py", line  
> 691, in _exec
>     '--make-slave', '/proc'])
>   File "/usr/lib64/python3.6/subprocess.py", line 729, in __init__
>     restore_signals, start_new_session)
>   File "/usr/lib64/python3.6/subprocess.py", line 1364, in  
> _execute_child
>     raise child_exception_type(errno_num, err_msg, err_filename)
> FileNotFoundError: [Errno 2] No such file or directory: 'mount':  
> 'mount'
>  * The ebuild phase 'die_hooks' has been aborted since  
> PORTAGE_BUILDDIR
>  * does not exist: '/var/tmp/portage/net-libs/liblockfile-1.16'
> 
> >>> Failed to emerge net-libs/liblockfile-1.16
>  * Messages for package net-libs/liblockfile-1.16:
> 
> <This is the end of the output; there are no messages from  
> liblockfile.>
> 
> Does  anyone  know  if  anything  can  be  done,  short  of   
> re-installing   and
> re-configuring Portage ?
> 
> --
> 
> Ashley Dixon
> suugaku.co.uk
> 
> 2A9A 4117
> DA96 D18A
> 8A7B B0D2
> A30E BF25
> F290 A8AA
> 
> 

Re: [gentoo-user] PORTAGE_BUILDDIR does not exist

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 2402 bytes --]

On Tue, 21 Apr 2020 21:58:09 +0100, Ashley Dixon wrote:

> I've been getting this build message for every package that I attempt
> to emerge. I'm starting to become  concerned  that  my  Portage
> installation  is  corrupt, although  I  want  to  make  sure  before  I
>  try  and  embark  on  the  lengthy Portage-rescue process.
> 
> For example, if I try to emerge app-editors/emacs (a package I  have
> never  had installed), I get the following error, both from emerge and
> a raw Python  crash:
> 
> Calculating dependencies  ... done!
> 
> >>> Verifying ebuild manifests  
> 
> >>> Emerging (1 of 5) net-libs/liblockfile-1.16::gentoo  
>  * Fetching files in the background.
>  * To view fetch progress, run in another terminal:
>  * tail -f /var/log/emerge-fetch.log
> [Errno 2] No such file or directory: 'mount': 'mount':
>    /bin/bash -c /usr/lib/portage/python3.6/ebuild.sh clean
> Traceback (most recent call last):
>   File "/usr/lib64/python3.6/site-packages/portage/process.py", line
> 382, in spawn unshare_flags, cgroup)
>   File "/usr/lib64/python3.6/site-packages/portage/process.py", line
> 691, in _exec '--make-slave', '/proc'])
>   File "/usr/lib64/python3.6/subprocess.py", line 729, in __init__
>     restore_signals, start_new_session)
>   File "/usr/lib64/python3.6/subprocess.py", line 1364, in
> _execute_child raise child_exception_type(errno_num, err_msg,
> err_filename) FileNotFoundError: [Errno 2] No such file or directory:
> 'mount': 'mount'
>  * The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR
>  * does not exist: '/var/tmp/portage/net-libs/liblockfile-1.16'
> 
> >>> Failed to emerge net-libs/liblockfile-1.16  
>  * Messages for package net-libs/liblockfile-1.16:
> 
> <This is the end of the output; there are no messages from liblockfile.>
> 
> Does  anyone  know  if  anything  can  be  done,  short  of
> re-installing   and re-configuring Portage ?

The reference to PORTAGE_BUILDDIR comes after die_hooks is called, so
the build has already failed at that point. It looks like the clean phase
may be failing, but more output would be helpful. The first thing I would
try is "rm -fr /var/tmp/portage" or wherever PORTAGE_TMPDIR is set.

It may also be worth checking for corruption on that filesystem.


-- 
Neil Bothwick

By the time you can make ends meet, they move the ends.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]