From: tvon@etria.org
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] QT3?
Date: Mon, 14 Jan 2002 20:57:24 -0500 [thread overview]
Message-ID: <20020114205724.A1733@etria.org> (raw)
In-Reply-To: <000201c19d66$cb248dc0$0300a8c0@tsunami>
On Mon, Jan 14, 2002, Clay Mitchell wrote:
> I get a "No message digest file found. Maintainer: ebuild giest to
> update messages digests."
>
> What is this?
It means that there is no md5 for the files that make up the qt3 source.
After it downloads:
ebuild /usr/portage/x11-libs/qt/qt-3.0.1-r1.ebuild digest
BTW: you can always edit /usr/portage/profiles/package.mask and comment out
the qt3 line so it wont stop you from merging it. Just dont be suprised
if your drive gets corrupted, monitor explodes, or your significant other
dumps you because the software is what the Gentoo developers deem "unstable" or
"problematic". Granted, there has been occasion when something was
unmasked and worked fine after everyone forgot why it was masked in the
first place, but I suspect qt3 falls under a different category.
HTH,
-Tom
next prev parent reply other threads:[~2002-01-15 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 0:52 [gentoo-dev] QT3? Clay Mitchell
2002-01-15 1:10 ` Geert Bevin
2002-01-15 1:48 ` Clay Mitchell
2002-01-15 1:57 ` tvon [this message]
2002-01-15 2:02 ` Geert Bevin
2002-01-15 1:59 ` tvon
2002-01-15 2:13 ` Geert Bevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020114205724.A1733@etria.org \
--to=tvon@etria.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox