| 1 |
On Tue, 21 Apr 2020 21:58:09 +0100, Ashley Dixon wrote: |
| 2 |
|
| 3 |
> I've been getting this build message for every package that I attempt |
| 4 |
> to emerge. I'm starting to become concerned that my Portage |
| 5 |
> installation is corrupt, although I want to make sure before I |
| 6 |
> try and embark on the lengthy Portage-rescue process. |
| 7 |
> |
| 8 |
> For example, if I try to emerge app-editors/emacs (a package I have |
| 9 |
> never had installed), I get the following error, both from emerge and |
| 10 |
> a raw Python crash: |
| 11 |
> |
| 12 |
> Calculating dependencies ... done! |
| 13 |
> |
| 14 |
> >>> Verifying ebuild manifests |
| 15 |
> |
| 16 |
> >>> Emerging (1 of 5) net-libs/liblockfile-1.16::gentoo |
| 17 |
> * Fetching files in the background. |
| 18 |
> * To view fetch progress, run in another terminal: |
| 19 |
> * tail -f /var/log/emerge-fetch.log |
| 20 |
> [Errno 2] No such file or directory: 'mount': 'mount': |
| 21 |
> /bin/bash -c /usr/lib/portage/python3.6/ebuild.sh clean |
| 22 |
> Traceback (most recent call last): |
| 23 |
> File "/usr/lib64/python3.6/site-packages/portage/process.py", line |
| 24 |
> 382, in spawn unshare_flags, cgroup) |
| 25 |
> File "/usr/lib64/python3.6/site-packages/portage/process.py", line |
| 26 |
> 691, in _exec '--make-slave', '/proc']) |
| 27 |
> File "/usr/lib64/python3.6/subprocess.py", line 729, in __init__ |
| 28 |
> restore_signals, start_new_session) |
| 29 |
> File "/usr/lib64/python3.6/subprocess.py", line 1364, in |
| 30 |
> _execute_child raise child_exception_type(errno_num, err_msg, |
| 31 |
> err_filename) FileNotFoundError: [Errno 2] No such file or directory: |
| 32 |
> 'mount': 'mount' |
| 33 |
> * The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR |
| 34 |
> * does not exist: '/var/tmp/portage/net-libs/liblockfile-1.16' |
| 35 |
> |
| 36 |
> >>> Failed to emerge net-libs/liblockfile-1.16 |
| 37 |
> * Messages for package net-libs/liblockfile-1.16: |
| 38 |
> |
| 39 |
> <This is the end of the output; there are no messages from liblockfile.> |
| 40 |
> |
| 41 |
> Does anyone know if anything can be done, short of |
| 42 |
> re-installing and re-configuring Portage ? |
| 43 |
|
| 44 |
The reference to PORTAGE_BUILDDIR comes after die_hooks is called, so |
| 45 |
the build has already failed at that point. It looks like the clean phase |
| 46 |
may be failing, but more output would be helpful. The first thing I would |
| 47 |
try is "rm -fr /var/tmp/portage" or wherever PORTAGE_TMPDIR is set. |
| 48 |
|
| 49 |
It may also be worth checking for corruption on that filesystem. |
| 50 |
|
| 51 |
|
| 52 |
-- |
| 53 |
Neil Bothwick |
| 54 |
|
| 55 |
By the time you can make ends meet, they move the ends. |
Archives