All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH] checksums.ini: correct wrong checksums
Date: Sun, 09 Nov 2008 18:31:46 +0100	[thread overview]
Message-ID: <gf76q2$le2$1@ger.gmane.org> (raw)
In-Reply-To: <1226249673.4235.671.camel@lenovo.internal.reciva.com>

On 09-11-2008 17:54, Phil Blundell wrote:
> On Sun, 2008-11-09 at 16:28 +0300, Dmitry Baryshkov wrote:
>>   [http://gpephone.linuxtogo.org/download/gpephone/libchenabler-0.1/libchenabler-0.1.tar.gz]
>> -md5=f29e1e63fcc55e3ae4e81f5ee9dd7bdd
>> -sha256=448a3ab76109664bb6bd8bcc2c62d957c7d44b52e39c37d91b3b73b5cfe35a3f
>> +md5=866fd13611a8de946428db1df9be8468
>> +sha256=74def55ba6a61e966e0873a4081fd3dd65089b94b837810d3bc056221d7e41c7
>
> How did these wrong checksums get in there?  It seems to defeat the
> point of checksums.ini if the data isn't trustworthy.

The gpephone people are in a habit of replacing the tarballs to get 
bugfixes to people instead of doing a new release. So the problem here 
is that _upstream_ is making a mess of things.
This also highlights why OE is now strictly enforcing checksums.




  reply	other threads:[~2008-11-09 17:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-09 13:28 [PATCH] checksums.ini: add few more checksums Dmitry Baryshkov
2008-11-09 13:28 ` [PATCH] checksums.ini: correct wrong checksums Dmitry Baryshkov
2008-11-09 13:28   ` [PATCH] libmailwrapper: add 1.2.4 version recipe Dmitry Baryshkov
2008-11-09 13:28     ` [PATCH] opie-cardapplet: " Dmitry Baryshkov
2008-11-09 13:28       ` [PATCH] task-sdk-base: switch to newer pixman Dmitry Baryshkov
2008-11-09 13:28         ` [PATCH] task-sdk-opie: correctly select qte or qte-mt Dmitry Baryshkov
2008-11-09 13:28           ` [PATCH] meta-toolchain-opie: add Opie SDK package Dmitry Baryshkov
2008-11-09 13:28             ` [PATCH] src_distribute: update to reflect current bitbake Dmitry Baryshkov
2008-11-09 13:28               ` [PATCH] task-sdk-extra: use randrproto-dev instead of randrext-dev Dmitry Baryshkov
2008-11-09 13:28                 ` [PATCH] x11-sato-image: use correct package names instead of ttf-liberation Dmitry Baryshkov
2008-11-09 13:28                   ` [PATCH] gloox: fix gloox.pc in the staging Dmitry Baryshkov
2008-11-09 13:28                     ` [PATCH] libsvg-cairo: fix building with current libtool/autoconf Dmitry Baryshkov
2008-11-09 13:28                       ` [PATCH] linphone: fix building with current speex Dmitry Baryshkov
2008-11-09 13:28                         ` [PATCH] contacts: fix build error Dmitry Baryshkov
2008-11-09 13:28                           ` [PATCH] tasks: fix building with current libtool Dmitry Baryshkov
2008-11-09 13:28                             ` [PATCH] libgemwidget-1.0: fix build error Dmitry Baryshkov
2008-11-10 23:37           ` [PATCH] task-sdk-opie: correctly select qte or qte-mt Paul Eggleton
2008-11-09 16:54   ` [PATCH] checksums.ini: correct wrong checksums Phil Blundell
2008-11-09 17:31     ` Koen Kooi [this message]
2008-11-10 14:13       ` Philip Balister
2008-11-13 16:43         ` Marcin Juszkiewicz
2008-11-13 17:22           ` Mike (mwester)
2008-11-13 17:59           ` Koen Kooi
2008-11-14  2:16           ` Philip Balister

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='gf76q2$le2$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.