All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Javier Viguera <javier.viguera@digi.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-webserver] cherokee: fix SRC_URI
Date: Thu, 5 Sep 2013 14:45:40 +0200	[thread overview]
Message-ID: <20130905144540.6c14eeb8@e6520eb> (raw)
In-Reply-To: <52287758.6050506@digi.com>

Hi Javier,

Le Thu, 5 Sep 2013 14:21:44 +0200,
Javier Viguera <javier.viguera@digi.com> a écrit :
> On 05/09/13 14:09, Eric Bénard wrote:
> > in fact the correct URL is now :
> > https://github.com/cherokee/webserver/archive/v1.2.98.tar.gz
> > so I think you can switch to :
> > +SRC_URI = "https://github.com/cherokee/webserver/archive/v${PV}.tar.gz
> 
> The problem with the "official" one in github is that it is not the 
> same. The checksums are different and a basic *diff* verification 
> between the unpacked packages shows a bunch of differences.
> 
interesting :-(

> The one in the OSUOSL is exactly the same (same checksums).
> 
> Regarding the mirror policies i just don't know. I was bitten by this 
> problem trying to build cherokee in Dylan branch and tried to find a 
> mirror. I selected OSUOSL because of its track supporting open source 
> projects.
> 
while you keep the same checksum there is no risk to get a wrong source
base so I don't see a problem here.

Eric


  reply	other threads:[~2013-09-05 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 11:54 [meta-webserver] cherokee: fix SRC_URI Javier Viguera
2013-09-05 12:04 ` Emil R. Petersen
2013-09-05 12:15   ` Paul Eggleton
2013-09-05 12:09 ` Eric Bénard
2013-09-05 12:09   ` Emil R. Petersen
2013-09-05 12:21   ` Javier Viguera
2013-09-05 12:45     ` Eric Bénard [this message]
2013-09-05 12:46     ` Martin Jansa

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=20130905144540.6c14eeb8@e6520eb \
    --to=eric@eukrea.com \
    --cc=javier.viguera@digi.com \
    --cc=openembedded-devel@lists.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.