From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/7] distcc: update SRC_URI to not use Google Code
Date: Fri, 07 Aug 2015 06:00:14 -0500 [thread overview]
Message-ID: <1438945214.30467.31.camel@linuxfoundation.org> (raw)
In-Reply-To: <0321088b6ef57a419568c584ef1cc791bb40218b.1438619216.git.alexander.kanavin@linux.intel.com>
On Mon, 2015-08-03 at 19:29 +0300, Alexander Kanavin wrote:
> Google Code is shutting down soon and distcc has moved to github.
>
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> ---
> meta/recipes-devtools/distcc/distcc_3.1.bb | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/meta/recipes-devtools/distcc/distcc_3.1.bb b/meta/recipes-devtools/distcc/distcc_3.1.bb
> index e4b9313..8ea3cac 100644
> --- a/meta/recipes-devtools/distcc/distcc_3.1.bb
> +++ b/meta/recipes-devtools/distcc/distcc_3.1.bb
> @@ -17,16 +17,14 @@ PACKAGECONFIG[popt] = "--without-included-popt,--with-included-popt,popt"
>
> RRECOMMENDS_${PN} = "avahi-daemon"
>
> -SRC_URI = "http://distcc.googlecode.com/files/${BPN}-${PV}.tar.bz2 \
> +SRC_URI = "git://github.com/distcc/distcc.git \
> file://separatebuilddir.patch \
> file://0001-zeroconf-Include-fcntl.h.patch \
> file://default \
> file://distccmon-gnome.desktop \
> file://distcc \
> file://distcc.service"
> -
> -SRC_URI[md5sum] = "a1a9d3853df7133669fffec2a9aab9f3"
> -SRC_URI[sha256sum] = "f55dbafd76bed3ce57e1bbcdab1329227808890d90f4c724fcd2d53f934ddd89"
> +SRCREV = "9a172d3d20042754a30c0cd9a5d63fd1a8120c31"
Patch application fails in:
https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/418/steps/BuildImages_1/logs/stdio
which makes me wonder how identical these versions really are?
Cheers,
Richard
next prev parent reply other threads:[~2015-08-07 11:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 16:29 [PATCH 0/7] More recipe reporting fixes Alexander Kanavin
2015-08-03 16:29 ` [PATCH 1/7] fotowall: update SRC_URI to use github instead of qt-apps.org Alexander Kanavin
2015-08-07 9:26 ` Robert Yang
2015-08-07 11:01 ` Richard Purdie
2015-08-07 12:27 ` Alexander Kanavin
2015-08-03 16:29 ` [PATCH 2/7] distcc: update SRC_URI to not use Google Code Alexander Kanavin
2015-08-07 9:25 ` Robert Yang
2015-08-07 9:40 ` Khem Raj
2015-08-07 11:00 ` Richard Purdie [this message]
2015-08-03 16:29 ` [PATCH 3/7] gptfdisk: update to 1.0.0 Alexander Kanavin
2015-08-03 16:29 ` [PATCH 4/7] oprofile: reorder SRC_URI lines to fix upstream version check Alexander Kanavin
2015-08-03 16:29 ` [PATCH 5/7] xf86-video-omapfb: switch SRC_URI to debian git repo Alexander Kanavin
2015-08-07 11:33 ` Richard Purdie
2015-08-03 16:29 ` [PATCH 6/7] stress: update checksums to match upstream tarball Alexander Kanavin
2015-08-03 16:58 ` Martin Jansa
2015-08-03 17:11 ` Alexander Kanavin
2015-08-03 16:29 ` [PATCH 7/7] recipeutils.py: allow all characters in regexes used to parse version strings Alexander Kanavin
-- strict thread matches above, loose matches on Subject: below --
2015-08-07 14:28 [PATCH 0/7] More recipe reporting fixes Alexander Kanavin
2015-08-07 14:28 ` [PATCH 2/7] distcc: update SRC_URI to not use Google Code Alexander Kanavin
2015-08-08 19:49 ` Khem Raj
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=1438945214.30467.31.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@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.