Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: md5sum check fails for ffmpeg - how do we deal with situations like this?
Date: Fri, 27 Apr 2007 15:47:43 +0200	[thread overview]
Message-ID: <f0suu0$ij2$1@sea.gmane.org> (raw)

Hi,

I tried to build ffmpeg and got the following:

NOTE: The MD5Sums did not match. Wanted: 
'700b66230a8322493c032c04372b8d74' and Got: 
'ea5587e3c66d50b1503b82ac4179c303'
NOTE: Task failed: Checksum of 
'http://downloads.sourceforge.net/ffmpeg/ffmpeg-0.4.9-pre1.tar.gz' failed

Is the entry in conf/checksums.ini wrong or has the file changed?  
Either way, how do we resolve situations like this in general?

Regards

Rolf




             reply	other threads:[~2007-04-27 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 13:47 Rolf Leggewie [this message]
2007-04-27 14:12 ` md5sum check fails for ffmpeg - how do we deal with situations like this? Holger Freyther
2007-04-28  9:19   ` Rolf Leggewie

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='f0suu0$ij2$1@sea.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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