Hey Billy,
Well, this caused me to look into it more carefully, so I finally
umounted the portage directory, and then did an emerge sync to get a
new repository on the local machine. Emerge now works. remount
portage, doesn't work.
You were right, this is an NFS problem. Not sure what
On Nov 3, 2005, at 1:42 PM, Billy Holmes wrote:Michael A Rowley, MD wrote: + set +x it's possible there is a problem on that volume, and it's stuck waiting for IO? try fscking that volume?Ok, tried this, and it didn't seem to do anything. The portage directory is on a NFS drive on the network,
Michael A Rowley, MD wrote:
works. But whenever I try to get a package to emerge, I get a failure
at 'set +x' on the debug screen, and it just sits there.
-x The shell shall write to standard error a trace for each command
after it expands the command and before it executes it. It
Michael A Rowley, MD wrote:
+ set +x
it's possible there is a problem on that volume, and it's stuck waiting
for IO? try fscking that volume?
--
gentoo-user@gentoo.org mailing list
Hello all... I am having a perplexing problem, and I have no idea
where to look for an answer.
I ahve a server that has been running well for aver a year. I
decided to upgrade the SVN server on it, so ran emerge -pv subversion
got back:
These are the packages that I would merge, in
On Wednesday 02 November 2005 20:39, Michael A Rowley, MD wrote:
Calculating dependencies ...done!
emerge (1 of 6) net-www/apache-2.0.54-r31 to /
and then nothing... for ever... let this sit over night, and still
nothing... wtf!?!?!? this was working.
I've had similar happen to me on a
On Nov 2, 2005, at 4:33 PM, Mike Williams wrote:
On Wednesday 02 November 2005 20:39, Michael A Rowley, MD wrote:
Calculating dependencies ...done!
emerge (1 of 6) net-www/apache-2.0.54-r31 to /
and then nothing... for ever... let this sit over night, and still
nothing... wtf!?!?!? this
7 matches
Mail list logo
