Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] Valentin Popa : xz: updated to version 5.1.1alpha
Date: Wed, 30 May 2012 13:21:33 +0100	[thread overview]
Message-ID: <1338380494.1964.369.camel@phil-desktop> (raw)
In-Reply-To: <20120530120443.GL3138@jama.jama.net>

On Wed, 2012-05-30 at 14:04 +0200, Martin Jansa wrote:
> On Wed, May 30, 2012 at 11:05:49AM +0000, git@git.openembedded.org wrote:
> > Module: openembedded-core.git
> > Branch: master
> > Commit: da98266f3a228cf65f279db9810a5326c8bd5422
> > URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=da98266f3a228cf65f279db9810a5326c8bd5422
> > 
> > Author: Valentin Popa <valentin.popa@intel.com>
> > Date:   Wed May 23 14:08:58 2012 +0300
> > 
> > xz: updated to version 5.1.1alpha
> 
> this upgrade is causing liblzma package name change
> -liblzma5_5.0.3-r1_armv4te.ipk
> +liblzma_5.1.1alpha-r0_armv4t.ipk
> 
> so all packages which rdepends on liblzma should get PR bump, e.g.:
>  *libsystemd-journal0
>  *libpoppler18
>  *libsdl-image-1.2-0
>  *libpoppler-glib8
>  *systemd
>  *ethumb
>  *libtiff5
>  *epdf

Or, better, someone should identify why the package has stopped getting
renamed and correct that.  Most likely some binary has leaked in to the
package which ought to contain only libraries.

p.





  parent reply	other threads:[~2012-05-30 12:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120530110550.04FA710217@opal>
2012-05-30 12:04 ` [oe-commits] Valentin Popa : xz: updated to version 5.1.1alpha Martin Jansa
2012-05-30 12:20   ` debian.bbclass got broken today Was: " Martin Jansa
2012-05-30 12:53     ` Martin Jansa
2012-05-30 13:10       ` Richard Purdie
2012-05-30 13:18         ` Martin Jansa
2012-05-30 13:26           ` Richard Purdie
2012-05-30 12:21   ` Phil Blundell [this message]
2012-05-30 12:21   ` Koen Kooi
2012-05-30 12:32     ` 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=1338380494.1964.369.camel@phil-desktop \
    --to=philb@gnu.org \
    --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