All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: "koen@dominion.thruhere.net" <koen@dominion.thruhere.net>
Subject: Re: php: museum.php.net is broken - change recipe SRC_URI?
Date: Wed, 5 Nov 2014 15:25:41 +0100	[thread overview]
Message-ID: <20141105142541.GB2457@jama> (raw)
In-Reply-To: <7571365.1nZ3Uh4ESC@peggleto-mobl5.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]

On Wed, Nov 05, 2014 at 01:32:08PM +0000, Paul Eggleton wrote:
> On Wednesday 05 November 2014 13:20:48 Bryan Evenson wrote:
> > There hasn't been any follow-up on this thread for a couple days.  I'd like
> > to know if there would be an acceptable solution for this issue.  I'd
> > propose changing the SRC_URI for php-5.4.14 to
> > http://git.php.net/?p=web/php-distributions.git;a=blob;f=php-5.4.14.tar.bz2
> > ;h=0d950f179d586bb1d0e879e0d4aa3a5140e8d5f5;hb=3dd2f12609fc8a730d7cf341a932f
> > 6c7b241f03c, which will directly pull only the tarball we need directly from
> > the PHP Git repository.  I believe it's the only path that would be
> > guaranteed to work long term.
> 
> Presumably if we did that we will need to keep updating the hash as well 
> though?
> 
> Looking at the bug there are at least two mirrors mentioned, although those 
> may not be reliable on a permanent basis there should be others (e.g. distros 
> often provide copies of the upstream sources they use). We could leave the 
> museum.php.net URL in place since it does appear it will eventually return, 
> and add MIRRORS values to cover the situation while it's unavailable.
> 
> Does this sound like a workable plan?

We can also send the archive to Tom King to put in in
http://sources.openembedded.org/
(like
http://lists.openembedded.org/pipermail/openembedded-devel/2014-June/096444.html)

We're not changing php version so often, so keeping the tarball there
won't cause so big maintenance burden.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2014-11-05 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 14:03 php: museum.php.net is broken - change recipe SRC_URI? Bryan Evenson
2014-11-03 15:46 ` Paul Eggleton
2014-11-03 16:08   ` Bryan Evenson
2014-11-03 18:03     ` Boszormenyi Zoltan
2014-11-03 18:40       ` Bryan Evenson
2014-11-05 13:20         ` Bryan Evenson
2014-11-05 13:32           ` Paul Eggleton
2014-11-05 14:25             ` Martin Jansa [this message]

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=20141105142541.GB2457@jama \
    --to=martin.jansa@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --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.