public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Laurentiu Palcu : libdrm: upgrade to 2.4.44
Date: Thu, 23 May 2013 11:26:58 +0300	[thread overview]
Message-ID: <519DD2D2.3010009@intel.com> (raw)
In-Reply-To: <20130522160725.GM32431@jama>



On 05/22/2013 07:07 PM, Martin Jansa wrote:
> On Sun, May 12, 2013 at 04:33:07PM +0000, git@git.openembedded.org wrote:
>> > Module: openembedded-core.git
>> > Branch: master
>> > Commit: 563edb321594b007cae2294e807235ad22fd27da
>> > URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=563edb321594b007cae2294e807235ad22fd27da
>> > 
>> > Author: Laurentiu Palcu <laurentiu.palcu@intel.com>
>> > Date:   Fri May 10 16:23:33 2013 +0300
>> > 
>> > libdrm: upgrade to 2.4.44
>> > 
>> > Removed part of the installtests.patch since tests can now be installed
>> > giving an option to configure script.
>> > 
>> > Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
>> > Signed-off-by: Saul Wold <sgw@linux.intel.com>
> Are you using buildhistory to test such upgrades?
> 
> This was caused by added --enable-install-test-programs.
> 
> Buildhistory shows that kmstest and vbltest were added to PN causing PKG to 
> change from libdrm2 to libdrm and breaking upgrade path
> 
> ${PN}-tests looks like better place for tests.
> 
>  * check_data_file_clashes: Package libdrm wants to install file /usr/lib/libdrm.so.2
>         But that file is already provided by package  * libdrm2
>  * check_data_file_clashes: Package libdrm wants to install file /usr/lib/libdrm.so.2.4.0
>         But that file is already provided by package  * libdrm2
> 
> -PV = 2.4.42
> -PR = r4.0
> -PKGR = r4.0.2
> -PKG = libdrm2
> +PV = 2.4.44
> +PR = r0
> +PKGR = r0.0
>  RPROVIDES = 
> -RDEPENDS = eglibc (>= 2.17)
> +RDEPENDS = eglibc (>= 2.17) libdrm-kms (>= 2.4.44)
>  RRECOMMENDS = 
> -PKGSIZE = 34635
> +PKGSIZE = 46491
>  FILES = /usr/bin/* /usr/sbin/* /usr/lib/libdrm/* /usr/lib/lib*.so.* /etc /com /var /bin/* /sbin/* /lib/*.so.* /lib/udev/rules.d /usr/lib/udev/rules.d /usr/share/libdrm /usr/lib/libdrm/* /usr/share/pixmaps /usr/share/applications /usr/share/idl /usr/share/omf /usr/share/sounds /usr/lib/bonobo/servers
> -FILELIST = /usr/lib/libdrm.so.2 /usr/lib/libdrm.so.2.4.0
> +FILELIST = /usr/bin/kmstest /usr/bin/vbltest /usr/lib/libdrm.so.2 /usr/lib/libdrm.so.2.4.0
> 
No, I didn't use buildhistory on this... :( My bad. I just wasn't
expecting the PKG to change. It looks like I was wrong.

Thanks for reminding me. Hopefully, I'll remember it next time.

I agree that the tests should be in a separate package. I'll make the
change as soon as I find some time.

Thanks,
Laurentiu


  reply	other threads:[~2013-05-23  8:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130512163307.035FC504FC@opal>
2013-05-22 16:07 ` [oe-commits] Laurentiu Palcu : libdrm: upgrade to 2.4.44 Martin Jansa
2013-05-23  8:26   ` Laurentiu Palcu [this message]
2013-05-23  8:55     ` [PATCH] libdrm: fix packaging after last upgrade Martin Jansa
2013-05-23  9:08       ` Burton, Ross
2013-05-24 20:48         ` 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=519DD2D2.3010009@intel.com \
    --to=laurentiu.palcu@intel.com \
    --cc=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