emerge --resume should do the trick.

Johnny

Mark Knecht wrote:

> Hi, I apologize if someone has possibly commented on this already,
> but Comcast went down for an hour or so and I haven't seen much
> mail yet. As I did not specifically ask about this earlier I will
> now. Thanks in advance.
>
> I have been trying to do an emerge -U world this morning.
> Unfortunately it has created file system problems 3 times. Now when
> I do it I get a message about an  incomplete emerge:
>
> Wizard root # emerge -Up world
>
>>>> --upgradeonly implies --update... adding --update to options.
>>>>
>
>
> These are the packages that I would merge, in order:
>
> Calculating world dependencies ...done! INCOMPLETE MERGE:
> /var/db/pkg/dev-lang/-MERGING-perl-5.8.0-r12 [ebuild  N    ]
> dev-lang/perl-5.8.0-r12 [ebuild     U ] sys-libs/glibc-2.3.2-r9
> [2.3.2-r8] [ebuild     U ] sys-devel/binutils-2.14.90.0.7-r4
> [2.14.90.0.7]
>
> Wizard root #
>
> I do see these incomplete emerge files:
>
> Wizard root # ls -l  /var/db/pkg/dev-lang/ total 28 drwxr-xr-x    2
> 4096 Jan 18 09:22 -MERGING-perl-5.8.0-r12 -rw-r-----    1    0 Jan
> 18 07:07 -MERGING-perl-5.8.0-r12.portage_lockfile
>
> I'm not clear how to proceed. Is my emerge database now messed up?
> If I attempt to continue at this point the ebuild seems to correput
> my file system. (It's happened 3 times now.)
>
> I've heard about rebuilding the portage database, but I haven't
> found instructions yet.
>
> Looking for instructions.
>
> Thanks, Mark
>
>
> -- [EMAIL PROTECTED] mailing list
>

--
Johnny
Sistumz injunear



--
[EMAIL PROTECTED] mailing list



Reply via email to