updating from an old 2006 pkg based install to latest 2008 and have
gotten pretty far along... right now emerging udev in an
emerge -vuDN system
command.

The emerge is hung at:

Calculating dependencies... done!
[ebuild U ] sys-fs/udev-120 [087-r1] USE="(-selinux)" 0 kB

Total: 1 package (1 upgrade), Size of downloads: 0 kB

>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) sys-fs/udev-120 to /
waiting for lock on /var/tmp/portage/sys-fs/.udev-120.portage_lockfile

And has been there a good while.

Looking at the bugs I see it mentioned but says it was fixed quite
sometime ago.

Any suggestions of how to get past this item and on with updating world?

--
gentoo-user@lists.gentoo.org mailing list

On Thursday 01 May 2008, reader@newsguy.com wrote:

> waiting for lock on
> /var/tmp/portage/sys-fs/.udev-120.portage_lockfile
>
> And has been there a good while.
>
> Looking at the bugs I see it mentioned but says it was fixed quite
> sometime ago.
>
> Any suggestions of how to get past this item and on with updating
> world?

Ctrl-C to kill the emerge and
rm /var/tmp/portage/sys-fs/.udev-120.portage_lockfile

then try again

--
Alan McKinnon
alan dot mckinnon at gmail dot com

--
gentoo-user@lists.gentoo.org mailing list

Alan McKinnon <alan.mckinnon@gmail.com> writes:

> Ctrl-C to kill the emerge and
> rm /var/tmp/portage/sys-fs/.udev-120.portage_lockfile

Egad and how many times have done that in other situations...

I tried emerge -vC udev followed by emerge -v udev

No help

Its just udev-120 that does this.

Before seeing your post I backed up to udev-119 and went right thru.
So must still be something a little off there.

However I emerged udev again and deleted the lock file as recommended
and 120 went right thru.

120 must be the first version that concerns itself with lock files.

--
gentoo-user@lists.gentoo.org mailing list

On Thursday 01 May 2008, reader@newsguy.com wrote:
> Alan McKinnon <alan.mckinnon@gmail.com> writes:
> > Ctrl-C to kill the emerge and
> > rm /var/tmp/portage/sys-fs/.udev-120.portage_lockfile
>
> Egad and how many times have done that in other situations...
>
> I tried emerge -vC udev followed by emerge -v udev
>
> No help
>
> Its just udev-120 that does this.
>
> Before seeing your post I backed up to udev-119 and went right thru.
> So must still be something a little off there.
>
> However I emerged udev again and deleted the lock file as recommended
> and 120 went right thru.
>
> 120 must be the first version that concerns itself with lock files.

I've seen similar messages a few times on my boxes recently, but each
time the emerge got going again after a short while. So I never really
bothered finding out exactly what is going on.

You mentioned a reported bug earlier, do you have a link that describes
it more?

--
Alan McKinnon
alan dot mckinnon at gmail dot com

--
gentoo-user@lists.gentoo.org mailing list

On Thu, 2008-05-01 at 23:21 +0200, Alan McKinnon wrote:
> I've seen similar messages a few times on my boxes recently, but each
> time the emerge got going again after a short while. So I never really
> bothered finding out exactly what is going on.

I believe portage recently switched to using parallel-fetch by default,
which causes a similar message to appear if the build thread catches up
with the fetch thread. In this situation, it is, essentially, harmless,
and is just a message to say "I haven't died".

Rob.