public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] odd ebuild problem
Date: 24 Mar 2003 21:54:38 -0500	[thread overview]
Message-ID: <m3znnk40lt.fsf@lugabout.jhcloos.org> (raw)

I just got this output from an emerge update:

21:24:57 (4.65 KB/s) - `/usr/portage/distfiles/color-theme-6.5.0.tar.bz2' saved [56278/56278]

!!! A file is corrupt or incomplete. (Digests do not match)
>>> our recorded digest: 5186ed7eef48a09d5cd219c81defce88
>>>  your file's digest: 78f340b5ee6e97426c0fe71bd69d3b1f

>>> Please delete /usr/portage/distfiles/color-theme-6.5.0.tar.bz2 and refetch.

The problem is that .../color-theme/files/digest-digest-color-theme-6.5.0
says  MD5 78f340b5ee6e97426c0fe71bd69d3b1f color-theme-6.5.0.tar.bz2 56278
not MD5 5186ed7eef48a09d5cd219c81defce88.

I can find no file in portage that has 5186ed7eef48a09d5cd219c81defce88 in it.
Nor any under /var.

Any ideas about the root of this problem?

Portage is 2.0.47-r11.

-JimC


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-03-25  2:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25  2:54 James H. Cloos Jr. [this message]
2003-03-25 14:56 ` [gentoo-dev] odd ebuild problem Abhishek Amit

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=m3znnk40lt.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --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