Hi folks,

that's what I just saw when I did a revdev-rebuild on one of my machines:

===================================================

...

broken /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libgij.la (requires 
/usr/lib/libgcj.la)
broken /usr/lib/libpoppler-cairo.la (requires 
/usr/lib/gcc/i686-pc-linux-gnu/4.1.1//libstdc++.la)
done.
(/root/.revdep-rebuild.3_rebuild)

Assigning files to ebuilds... done.
(/root/.revdep-rebuild.4_ebuilds)

Evaluating package order...
Warning: Failed to resolve package order.
Will merge in "random" order!
Possible reasons:
- An ebuild is no longer in the portage tree.
- An ebuild is masked, use /etc/portage/packages.keyword
and/or /etc/portage/package.unmask to unmask it
..... done.
(/root/.revdep-rebuild.5_order)

All prepared. Starting rebuild...
emerge --oneshot emerge.txt ENV.txt ldapdump.1146827010 ldapdump.1146827010.raw 
wlan0.txt =app-text/poppler-bindings-0.5.1-r1 =dev-java/libgnome-java-2.12.1-r1 
=dev-java/libgtk-java-2.8.3-r1 =dev-lang/icc-9.0.030 =dev-libs/opal-2.1.3 
=dev-libs/xmlrpc-c-1.2 =media-plugins/gst-plugins-neon-0.10.1 
=media-sound/bmpx-0.20.1.1 =media-sound/grip-3.3.1 =sys-devel/gcc-4.1.1
..........
Calculating dependencies
emerge: there are no ebuilds to satisfy "emerge.txt".

...

===================================================

It wants to emerge the 'emerge.txt ENV.txt ldapdump.1146827010
ldapdump.1146827010.raw wlan0.txt' ebuils which are, however, just files
within root's home directory. Thus emerge bails out with the above error.
Maybe someone could have a look ... :D

Regards,
        Marc
-- 
[email protected] mailing list

Reply via email to