From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: debian.bbclass got broken today Was: [oe-commits] Valentin Popa : xz: updated to version 5.1.1alpha
Date: Wed, 30 May 2012 15:18:33 +0200 [thread overview]
Message-ID: <20120530131833.GP3138@jama.jama.net> (raw)
In-Reply-To: <1338383413.20169.141.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]
On Wed, May 30, 2012 at 02:10:13PM +0100, Richard Purdie wrote:
> On Wed, 2012-05-30 at 14:53 +0200, Martin Jansa wrote:
> > On Wed, May 30, 2012 at 02:20:07PM +0200, Martin Jansa wrote:
> > > On Wed, May 30, 2012 at 02:04:43PM +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
> > > >
> > > > Cheers,
> > >
> > > Looks like whole debian.bbclass got broken by todays merge in oe-core..
> >
> > looking at buildhistory
> > http://git.shr-project.org/git/?p=buildhistory.git;a=commitdiff;h=320a9a8a80f0d412cea31a534a8022bacf6545e6#patch330
> >
> > it looks like run.package_do_shlibs also doesn't work (all RDEPENDS
> > detected from shlibs are gone), can someone confirm this behavior on
> > his system?
>
> Yes, its from:
>
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=5996b2b58e36864edc077326a942795ca12f48da
>
> I'm still trying to figure out the best course of action to fix this...
Ah, thanks for info..
so I have reverted all 3 (to be sure) locally and now trying to find and
rebuild everything which was built today to get sane feed again.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-05-30 13:28 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 [this message]
2012-05-30 13:26 ` Richard Purdie
2012-05-30 12:21 ` Phil Blundell
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=20120530131833.GP3138@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.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