Re: [gentoo-user] Wine-cvs ebuild won't merge

[Brett I. Holcomb]

I filed a bug and got an answer.  CVS builds don't have digests (which I 
knew) or they are empty if you create them.  Previous versions of 
portage didn't say anything about them so we never knew.  This new 
version tells you.  I wasn't used to the verbosity so I assumed it was 
broken.  I never tried running without the -p.



Collins Richey wrote:
On Sat, 07 Feb 2004 19:40:55 -0500
"Brett I. Holcomb" <[EMAIL PROTECTED]> wrote:

I created an ebuild for wine-cvs.  If I run ebuild wine-cvs-0.9.ebuild

install it works - wine is fetched, compiled, made, installed into the

build directory ready to merge.

However, when I do

ACCEPT_KEYWORDS="~x86" emerge app-emulation/wine-cvs -pv

I get an error about empty digest file - see below (I did run ebuild 
wine... digest and it created a digest file - see below).

I've done other ebuilds for cvs and haven't had this trouble. 
However, this is the first ebuild I've done on the new portage - maybe
that's it. 
 As a thought I tried an ebuild that worked on the previous version
 of 
portage - it gives the same error.  What's changed and how do I fix
it?

These are the packages that I would merge, in order:
>>> Computed message digests.



I see this message on a lot of standard packages, so maybe it's just a
current portage quirk?
--
[EMAIL PROTECTED] mailing list