emerge -u broken

wizy · Tux's lil' helper Joined: 26 May 2002 Posts: 133

*[root@localhost:root] qpkg -I -v portage
sys-apps/portage-2.0.14 *
*[root@localhost:root] qpkg -I -v baselayout
sys-apps/baselayout-1.7.9-r2 *
*[root@localhost:root] emerge -up system

These are the packages that I would merge, in order.

Calculating system dependencies ...done!
[ebuild U ] sys-apps/baselayout-1.7.9-r1 to /
[ebuild U ] sys-apps/portage-2.0.13 to /

*[root@localhost:root]

I didnt actually notice it last night and let it do an emerge world (i am obviously an idiot for letting it go unattented without checking first)

*[root@localhost:root] qpkg -I -v glibc
sys-libs/glibc-2.2.5-r4 *
sys-libs/glibc-2.2.5-r5 *

I had r5 on their, and it installed r4 overnight during the emerge world.

*[root@localhost:root] qpkg -I -v libpng
media-libs/libpng-1.2.3-r1 *
media-libs/libpng-1.2.4 *
*[root@localhost:root] qpkg -I -v dhcpcd
net-misc/dhcpcd-1.3.20_p0 *
net-misc/dhcpcd-1.3.20_p0-r1 *
*[root@localhost:root] qpkg -I -v util-linux
sys-apps/util-linux-2.11r *
sys-apps/util-linux-2.11r-r1 *

All 3 of them did the same thing. So whats goin on? Did I break something? How can I fix this problem, and what do I do about the glibc, will removing the -r4 even though it was the latest installed hurt anything?

Gregg

Naan Yaar · Bodhisattva Joined: 27 Jun 2002 Posts: 1549

You probably got an old mirror when doing "emerge rsync". You can try "emerge --clean rsync" or "emerge rsync" again to, hopefully, sync with an updated mirror.

One way to check how old the mirror was is to check the timestamp on, say, your package.mask file.

wizy · Tux's lil' helper Joined: 26 May 2002 Posts: 133

What do I do about glibc?

delta407 · Posted: Tue Jul 16, 2002 3:10 pm Post subject:

What's wrong with it?
_________________
I don't believe in witty sigs.

Naan Yaar · Bodhisattva Joined: 27 Jun 2002 Posts: 1549

Once you are synced with a new mirror, you can can "emerge glibc" to reemerge the new version. Similar things with other packages. In the end, do "emerge clean" to clean up the debris

wizy · Tux's lil' helper Joined: 26 May 2002 Posts: 133

Did it and look:

*[root@sc.am:etc] emerge -up world

These are the packages that I would merge, in order.

Calculating world dependencies ...done!
[ebuild U ] sys-apps/portage-2.0.13 to /
[ebuild U ] dev-php/mod_php-4.2.1-r5 to /
[ebuild U ] sys-apps/baselayout-1.7.9-r1 to /

*[root@sc.am:etc] qpkg -I -v portage
sys-apps/portage-2.0.14 *
*[root@sc.am:etc] qpkg -I -v mod_php
dev-php/mod_php-4.2.1-r4 *
*[root@sc.am:etc] qpkg -I -v baselayout
sys-apps/baselayout-1.7.9-r2 *

Still broken, I did it 3 times, and all 3 times got didferent rsync servers. And all 3 times, it still had this problem. Any other ideas?

wizy · Tux's lil' helper Joined: 26 May 2002 Posts: 133

the problems in the first message are still there as well. Since I dont seem to be getting the right information from an rsync I dont want to emerge glibc and clean to clear up the debris until I get this resolved.

Naan Yaar · Bodhisattva Joined: 27 Jun 2002 Posts: 1549

I notice that it does list a new package for php. Can you do two things:

- check the date stamp on the package.mask file. How recent is this?
- look at the package.mask file itself. May be the newer versions were masked because some issues. Usually there is a comment in the file that describes this.

wizy · Tux's lil' helper Joined: 26 May 2002 Posts: 133

date stamped last night, and none of the packages giving me problems are masked out.