I have been trying for the past couple of days to do an emerge --emptytree world. However, it fails with "No message digest entry found" for at least two packages. In my case I have seen it with media-libs/freetype-2.1.2-r1 and media-video/mplayer-0.90_pre8. In the first case there is no digest entry for ftdocs-2.1.2.tar.bz2 and in the latter for default-skin-0.1.tar.bz2. I have verified that these entries are indeed missing in the digest files in my portage tree, but they are present in the CVS versions as seen through the CVS web interface. I wouldn't mind generating the digests myself, but the next rsync would take me back to the old, broken digest files. I also want to make a suggestion - it would be nice if the --fetchonly emerge option checked these digest entries, because otherwise the only way to detect a failure is during the actual emerge. If the failure occurs during an emerge --emptytree world, this is especially bad, because it may occur an hour or two into the process and there is no way to restart from the failed package after fixing it. Everything that did build successfully must be built again.
digest files are checked before the emerge happens, so you wouldnt have to restart the package ...
Yes, but that doesn't help if I want to force a rebuild of all the packages on my system. Digests for a particular package are checked before that package is merged; they aren't all checked at the beginning.
*** Bug 8619 has been marked as a duplicate of this bug. ***
*** Bug 8697 has been marked as a duplicate of this bug. ***
*** Bug 8878 has been marked as a duplicate of this bug. ***
*** Bug 8908 has been marked as a duplicate of this bug. ***
*** Bug 8911 has been marked as a duplicate of this bug. ***
*** Bug 8801 has been marked as a duplicate of this bug. ***
*** Bug 8314 has been marked as a duplicate of this bug. ***
*** Bug 8480 has been marked as a duplicate of this bug. ***
The mplayer bug is perhaps not a showstopper, (most newbies can live without mplayer) however the freetype bug is CRITICAL. If doc is in your USE flags you will not be able to emerge kde. I assume most new users have the doc USE flag. That means a new user will probably not be able to emerge kde. This will give the new user a bad impression of gentoo. (gnome probably depends on freetype too, but I'm not sure.) This bug was opened about 12 days ago. It is probably stopping a lot of new users trying out gentoo. This should be fixed as soon as possible. ... Looking through the other bug reports marked as duplicates of this bug it seems like the rsync servers are not getting updated from cvs correctly. What is happening here?
Today i saw my rsync downloaded new mplayer-digest. Seems to be fixed now. Can you others confirm this?
emerge mplayer works here now
allright here, too.
I can confirm that all appears normal here this morning. Good job!
The digests are all right now, so this bug seems to be fixed. Next bug will get filed against sudo.
I was trying this evening to look at the sys-kernel/crypto-sources revs >-r7... (CVS lists -r8 thru -r10) but ehy are not on 4-5 of the rsync mirrors I found. Perhaps this problem is more pervasive?
My bad -- I got gentoo-sources confused with crypto-sources. Sorry.
drobbins made a fix on this one a while ago. It should/seems-to be resolved.
# date Sun Feb 15 22:36:05 EST 2004 # emerge -u freetype Calculating dependencies ...done! >>> emerge (1 of 1) media-libs/freetype-2.1.5 to / >>> Downloading http://gentoo.oregonstate.edu/distfiles/ftdocs-2.1.5.tar.bz2 --22:36:20-- http://gentoo.oregonstate.edu/distfiles/ftdocs-2.1.5.tar.bz2 => `/usr/portage/distfiles/ftdocs-2.1.5.tar.bz2' Resolving gentoo.oregonstate.edu... 128.193.0.3 Connecting to gentoo.oregonstate.edu[128.193.0.3]:80... connected. HTTP request sent, awaiting response... 404 Not Found 22:36:20 ERROR 404: Not Found. {this repeats about 15 times and then we get:} !!! Couldn't download ftdocs-2.1.5.tar.bz2. Aborting.
