Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/7] fotowall: update SRC_URI to use github instead of qt-apps.org
Date: Fri, 7 Aug 2015 17:26:39 +0800	[thread overview]
Message-ID: <55C479CF.4000506@windriver.com> (raw)
In-Reply-To: <6a9899fa17063139292c39c162444d1a1356ccce.1438619216.git.alexander.kanavin@linux.intel.com>


Also fotowall:

https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/430/steps/BuildImages/logs/stdio

// Robert

On 08/04/2015 12:29 AM, Alexander Kanavin wrote:
> GitHub is where upstream development is happening, so we are more likely
> to find out about new releases from there
>
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> ---
>   meta/recipes-qt/qt-apps/fotowall_0.9.bb | 6 ++----
>   1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/meta/recipes-qt/qt-apps/fotowall_0.9.bb b/meta/recipes-qt/qt-apps/fotowall_0.9.bb
> index 48dcc02..e92e862 100644
> --- a/meta/recipes-qt/qt-apps/fotowall_0.9.bb
> +++ b/meta/recipes-qt/qt-apps/fotowall_0.9.bb
> @@ -10,13 +10,11 @@ SECTION = "x11/apps"
>
>   PR = "r4"
>
> -SRC_URI = "http://qt-apps.org/CONTENT/content-files/71316-Fotowall-0.9.tar.bz2 \
> +SRCREV = "06d5a4142c599604d9a9fd64727b6945eb8cd3da"
> +SRC_URI = "git://github.com/enricoros/fotowall.git \
>              file://ExportWizard-depends-on-ui_wizard.patch \
>              "
>
> -SRC_URI[md5sum] = "142ef697332e0777c6d22c5bc96cc438"
> -SRC_URI[sha256sum] = "e4d0c005d2cb1d7c09438bfc3098eadebc08946e4fbc0655b7fc8b046de3810d"
> -
>   S = "${WORKDIR}/Fotowall-${PV}"
>
>   inherit qt4x11
>


  reply	other threads:[~2015-08-07  9:26 UTC|newest]

Thread overview: 18+ 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 [this message]
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
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 1/7] fotowall: update SRC_URI to use github instead of qt-apps.org Alexander Kanavin

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=55C479CF.4000506@windriver.com \
    --to=liezhi.yang@windriver.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox