Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 50489 - Unable to emerge various packages (opengl-update, kde-env, kde, etc.) because of zero-sized digests
Summary: Unable to emerge various packages (opengl-update, kde-env, kde, etc.) because...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High blocker (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2004-05-08 14:55 UTC by wiktorw
Modified: 2004-05-09 23:00 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

success! (today,2.88 KB, text/plain)
2004-05-09 22:53 UTC, wiktorw

Note You need to log in before you can comment on or make changes to this bug.
Description wiktorw 2004-05-08 14:55:53 UTC
I downloaded Gentoo 2004.1 and I sucessfully installed it. I went through "Stage1" and "Stage2" (and I am not bragging :-)
However, when I try to emerge additional packages, in some cases it is impossible to do so. In such a case emerge says something like:
"[empty/missing/bad digest]" at the end of description for a package.
[ebuild  N    ] kde-base/kde-env-3-r2   [empty/missing/bad digest]

I have just found these strange digest files in portage tree. They are zero-sized. And there are plenty of them: 176 in "portage-20040430" and 165 in "portage-20040507". So the problem is persistent!

This way I am unable to emerge various packages, especially xfree and kde.
Since ebuild depends on these digest files to know what to build and in what order, I suppose other users can reproduce the same bug. So in my opinion this is somewhat important.

Because of the above I am very unhappy to run text-only version of Gentoo :-(
But I hope this is something that can be relatively easy to fix. :-)

Reproducible: Always
Steps to Reproduce:
There are at least two ways of reproducing the problem.

1. On a clean system, after "stage2" compilation, do:
   emerge sync
   emerge -pv kde     (( <-- warnings! ))
   ls -l /usr/portage/x11-base/opengl-update/files
   (( you can see that all digest-* files are zero-sized ))
   cat /usr/portage/x11-base/opengl-update/Manifest | grep digest | less
   (( you can see again that indeed digest-* files are zero-sized ))

2. Download snapshot "portage-20040507.tar.bz2" and execute:
   tar -tvjf portage-20040507.tar.bz2 | grep "^-.* 0 .*digest" > bad-digests
   You should see in reulting file 165 zero-sized "digest-*" files
   (for "portage-20040430.tar.bz2" there are 176 such files)

Actual Results:  
For 1.

emerge -pv kde

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

Calculating dependencies  ...done!
[ebuild  N    ] media-sound/cdparanoia-3.9.8-r1   113 kB 
[ebuild  N    ] net-print/cups-1.1.20-r1  +pam -slp +ssl  3,653 kB 
[ebuild  N    ] x11-base/opengl-update-1.5   [empty/missing/bad digest] 
[ebuild  N    ] kde-base/kde-env-3-r2   [empty/missing/bad digest] 
[ebuild  N    ] kde-base/kde-3.2.1   [empty/missing/bad digest] 

-rw-r--r--      0 may  8 03:52 digest-opengl-update-1.3
-rw-r--r--      0 may  8 03:52 digest-opengl-update-1.4
-rw-r--r--      0 may  8 03:52 digest-opengl-update-1.5
-rw-r--r--      0 may  8 03:52 digest-opengl-update-1.6

MD5 d41d8cd98f00b204e9800998ecf8427e files/digest-opengl-update-1.3 0
MD5 d41d8cd98f00b204e9800998ecf8427e files/digest-opengl-update-1.4 0
MD5 d41d8cd98f00b204e9800998ecf8427e files/digest-opengl-update-1.5 0
MD5 d41d8cd98f00b204e9800998ecf8427e files/digest-opengl-update-1.6 0

For 2.
Just a sample for opengl-update:

-rw-r--r-- gmirror/gmirror      0 2004-05-08 03:52:43 portage/x11-base/opengl-
-rw-r--r-- gmirror/gmirror      0 2004-05-08 03:52:43 portage/x11-base/opengl-
-rw-r--r-- gmirror/gmirror      0 2004-05-08 03:52:43 portage/x11-base/opengl-
-rw-r--r-- gmirror/gmirror      0 2004-05-08 03:52:43 portage/x11-base/opengl-

Expected Results:  
For 1.
Packages opengl-update, kde-env, kde downloaded, compiled and installed 

For 2.
No zero-length digest files in portage tree.

sorry, I'm posting from different machine, so 'emerge info' is impossible 
right now...
Comment 1 Eric Brown 2004-05-08 15:00:04 UTC
i actually noticed files like that during an install I did this week.  I didn't have any problems emerging though.. yours fails?
Comment 2 Mr. Bones. (RETIRED) gentoo-dev 2004-05-09 19:56:22 UTC
reopen with the output of emerge --info please.
Comment 3 wiktorw 2004-05-09 22:53:10 UTC
Created attachment 31082 [details]

Two days later - and the result is a success...
Comment 4 wiktorw 2004-05-09 23:00:22 UTC
As you requested I included the output of "emerge info".
However, I don't think this will be needed.

As I read more on emerge and ebuild I noticed how to specify an exact
version of package needed. This is what I did:

# emerge sync
# emerge -pv opengl-update

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

Calculating dependencies ...done!
[ebuild  N    ] x11-base/opengl-update-1.5   [empty/missing/bad digest]

Total size of downloads: 0 kB

At this point something hit my mind:

# emerge x11-base/opengl-update-1.5
Calculating dependencies
!!! Problem in x11-base/opengl-update-1.5 dependencies.
!!! "Specific key requires an operator (x11-base/opengl-update-1.5) (try adding an '=')"

# emerge =x11-base/opengl-update-1.5
Calculating dependencies ...done!
>>> emerge (1 of 1) x11-base/opengl-update-1.5 to /
>>> Unpacking source...
>>> Source unpacked.

>>> Install opengl-update-1.5 into /var/tmp/portage/opengl-update-1.5/image/ category x11-base
>>> Completed installing into /var/tmp/portage/opengl-update-1.5/image/

>>> Merging x11-base/opengl-update-1.5 to /
--- /usr/
--- /usr/sbin/
>>> /usr/sbin/opengl-update
 * Caching service dependencies...
>>> x11-base/opengl-update-1.5 merged.

>>> clean: No packages selected for removal.

>>> Auto-cleaning packages ...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.

And the story is over. Simple "emerge =x11-base/opengl-update-1.5"
solved everything.

  don't post a bug until you are COMPLETELY sure it is a bug.

Thanks for your time, guys. For me this bug is closed.