From: William Hubbs <williamh@gentoo.org>
To: gentoo-accessibility@lists.gentoo.org
Subject: Re: [gentoo-accessibility] Espeak 1.26 Digest Verification
Date: Sun, 10 Jun 2007 11:49:06 -0500 [thread overview]
Message-ID: <20070610164905.GA17229@linux1> (raw)
In-Reply-To: <BAY141-DAV259CC59576DA63F382A7A8F1B0@phx.gbl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Zack,
> In upgrading to Espeak 1.26, I've noticed that the upgrade routinely fails with a digest verification error. The expected filesize is 954674, and actual filesize is 955549.
I just re-emerged 1.26 and 1.26-r1 and didn't get this issue here. You
might try again and let me know if it still happens.
> I'm going to assume this is a temporary problem. However, it is quite annoying--should I just wait a day and resync? Also, I notice that the file itself isn't on distfiles.gentoo.org...Is there a reason for that?
The reason the file was not on distfiles.gentoo.org is that when an
ebuild is committed to portage, it takes some time for the source files
to be distributed to the mirrors.
Thanks,
William
- --
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFGbCuBblQW9DDEZTgRAua3AJ46jarHBjFEQBs7U+h7nXRZFG6liQCgia2z
C0yKQ0QHX2xgIL8H1AfUryQ=
=1Fv9
-----END PGP SIGNATURE-----
--
gentoo-accessibility@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-10 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 0:05 [gentoo-accessibility] Espeak 1.26 Digest Verification Zachary Kline
2007-06-10 16:49 ` William Hubbs [this message]
2007-06-10 17:46 ` Zachary Kline
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=20070610164905.GA17229@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-accessibility@lists.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