Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][fido] tzdata: remove 2015d version
Date: Tue, 09 Feb 2016 17:04:11 +0000	[thread overview]
Message-ID: <1455037451.6918.18.camel@linux.intel.com> (raw)
In-Reply-To: <1455029653-4207-1-git-send-email-Martin.Jansa@gmail.com>

On Tue, 2016-02-09 at 15:54 +0100, Martin Jansa wrote:
> * this is left-over from upgrade to 2016a
> 
> * it's safer to remove so that .bbappends in other layers really
> apply to version
>   used in build (currently we have bbappend for 2015d and build will
> use 2016a
>   without any warning
> 
> * the same problem was reported with 2015f upgrade:
>   http://lists.openembedded.org/pipermail/openembedded-core/2015-
> August/109708.html

Thanks, I've pushed this change to my joshuagl/fido-next branch.

http://cgit.openembedded.org/openembedded-core-
contrib/log/?h=joshuagl/fido-next

Regards,

Joshua

> 
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
>  meta/recipes-extended/tzdata/tzdata_2015d.bb | 6 ------
>  1 file changed, 6 deletions(-)
>  delete mode 100644 meta/recipes-extended/tzdata/tzdata_2015d.bb
> 
> diff --git a/meta/recipes-extended/tzdata/tzdata_2015d.bb
> b/meta/recipes-extended/tzdata/tzdata_2015d.bb
> deleted file mode 100644
> index d8e5f24..0000000
> --- a/meta/recipes-extended/tzdata/tzdata_2015d.bb
> +++ /dev/null
> @@ -1,6 +0,0 @@
> -SRC_URI = "ftp://ftp.iana.org/tz/releases/tzdata${PV}.tar.gz;name=tz
> data"
> -
> -SRC_URI[tzdata.md5sum] = "b595bdc4474b8fc1a15cffc67c66025b"
> -SRC_URI[tzdata.sha256sum] =
> "8b9f5008277f09e251e97dba7813f56168d691115bda90ade4638d72f296d531"
> -
> -require tzdata.inc
> -- 
> 2.7.0
> 


      reply	other threads:[~2016-02-09 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 14:54 [PATCH][fido] tzdata: remove 2015d version Martin Jansa
2016-02-09 17:04 ` Joshua G Lock [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=1455037451.6918.18.camel@linux.intel.com \
    --to=joshua.g.lock@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