/usr/portage itself is NFS mounted from a server and is fine.
However, emerge --metadata and emerge -av1 glibc both report problems
with some bdb stuff and doesn't work.
This all happened after a failed glibc emerge. It detected that it
was nptlonly, said it was removing /lib/tls, does with a preinst
problem (on the rm as far as I can tell), and emerge has been hosed
ever since.
(After I rm -rf /var/cache/edb):
% emerge --metadata
>>> /var/cache/edb doesn't exist, creating it...
>>> /var/cache/edb/dep doesn't exist, creating it...
Performing Global Updates: /usr/portage/profiles/updates/3Q-2002
.................... clipped ..........................
** Skipping packages. Run 'fixpackages' or set it in FEATURES to fix the
tbz2's in the packages directory. Note: This can take a very long time.
skipping sync
>>> Updating Portage cache:
Failed cache update: app-accessibility/SphinxTrain-0.9.1-r1 (38, 'Function not
implemented -- process-private: unable to initialize environment lock: Function
not implemented')
Failed cache update: app-accessibility/at-poke-0.2.2 (38, 'Function not
implemented -- process-private: unable to initialize environment lock: Function
not implemented')
and so on and on and on
Here is emerge -av1 glibc:
These are the packages that I would merge, in order:
Calculating dependencies
!!! Problem in sys-libs/glibc dependencies.
!!! (38, 'Function not implemented -- process-private: unable to initialize
environment lock: Function not implemented') bsddb._db
--
[email protected] mailing list
