[PATCH 0/3] Package Updates

[PATCH 0/3] Package Updates

[Saul Wold]

Did a build with debian packaging and tested dpkg lightly on the target.

Sau!

The following changes since commit 315367ea9526186d5836c64867ce0cd40d9d8412:

  nativesdk.bbclass: support nativesdk to override with the PACKAGES_DYNAMIC statement (2013-12-09 21:36:30 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib sgw/updates
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/updates

Saul Wold (3):
  util-macros: upgrade to 1.18.0
  dpkg: upgrade to 1.17.4
  cracklib: upgrade to 2.9.1

 meta/recipes-devtools/dpkg/{dpkg_1.17.1.bb => dpkg_1.17.4.bb}         | 4 ++--
 .../cracklib/{cracklib_2.9.0.bb => cracklib_2.9.1.bb}                 | 4 ++--
 .../xorg-util/{util-macros_1.17.1.bb => util-macros_1.18.0.bb}        | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)
 rename meta/recipes-devtools/dpkg/{dpkg_1.17.1.bb => dpkg_1.17.4.bb} (75%)
 rename meta/recipes-extended/cracklib/{cracklib_2.9.0.bb => cracklib_2.9.1.bb} (84%)
 rename meta/recipes-graphics/xorg-util/{util-macros_1.17.1.bb => util-macros_1.18.0.bb} (75%)

-- 
1.8.3.1

[PATCH 1/3] util-macros: upgrade to 1.18.0

[Saul Wold]

Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
 .../xorg-util/{util-macros_1.17.1.bb => util-macros_1.18.0.bb}        | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-graphics/xorg-util/{util-macros_1.17.1.bb => util-macros_1.18.0.bb} (75%)

diff --git a/meta/recipes-graphics/xorg-util/util-macros_1.17.1.bb b/meta/recipes-graphics/xorg-util/util-macros_1.18.0.bb
similarity index 75%
rename from meta/recipes-graphics/xorg-util/util-macros_1.17.1.bb
rename to meta/recipes-graphics/xorg-util/util-macros_1.18.0.bb
index 9274a3a..79759f6 100644
--- a/meta/recipes-graphics/xorg-util/util-macros_1.17.1.bb
+++ b/meta/recipes-graphics/xorg-util/util-macros_1.18.0.bb
@@ -15,5 +15,5 @@ RRECOMMENDS_${PN}-dbg = "${PN}-dev (= ${EXTENDPKGV})"
 
 BBCLASSEXTEND = "native nativesdk"
 
-SRC_URI[md5sum] = "886de1940334e097c5f66233a8393122"
-SRC_URI[sha256sum] = "67bd01d5f4713c9e9d57dc742504d06292dd9c4fb73041ea16fed034c56c622a"
+SRC_URI[md5sum] = "fd0ba21b3179703c071bbb4c3e5fb0f4"
+SRC_URI[sha256sum] = "cf4ab0e17bfee0f7689cdcff8c7d7f164c9a710f851f91c488f5cd81fac9c0aa"
-- 
1.8.3.1

[PATCH 2/3] dpkg: upgrade to 1.17.4

[Saul Wold]

Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
 meta/recipes-devtools/dpkg/{dpkg_1.17.1.bb => dpkg_1.17.4.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/dpkg/{dpkg_1.17.1.bb => dpkg_1.17.4.bb} (75%)

diff --git a/meta/recipes-devtools/dpkg/dpkg_1.17.1.bb b/meta/recipes-devtools/dpkg/dpkg_1.17.4.bb
similarity index 75%
rename from meta/recipes-devtools/dpkg/dpkg_1.17.1.bb
rename to meta/recipes-devtools/dpkg/dpkg_1.17.4.bb
index 525f759..9e2392c 100644
--- a/meta/recipes-devtools/dpkg/dpkg_1.17.1.bb
+++ b/meta/recipes-devtools/dpkg/dpkg_1.17.4.bb
@@ -11,6 +11,6 @@ SRC_URI += "file://noman.patch \
             file://arch_pm.patch \
            "
 
-SRC_URI[md5sum] = "ece3ae87a099158c17bde95c0036c575"
-SRC_URI[sha256sum] = "8912ea77bc9c14297c0a340f5f461fbd212582ce814e1805d1d0436ca885e3a1"
+SRC_URI[md5sum] = "cc25086e1e3bd9512a95f14cfe9002e1"
+SRC_URI[sha256sum] = "01cdc81c33e77c3d7c40df17e19171794542be7cf12e411381ffcaa8f87b1854"
 
-- 
1.8.3.1

[PATCH 3/3] cracklib: upgrade to 2.9.1

[Saul Wold]

Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
 .../cracklib/{cracklib_2.9.0.bb => cracklib_2.9.1.bb}                 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-extended/cracklib/{cracklib_2.9.0.bb => cracklib_2.9.1.bb} (84%)

diff --git a/meta/recipes-extended/cracklib/cracklib_2.9.0.bb b/meta/recipes-extended/cracklib/cracklib_2.9.1.bb
similarity index 84%
rename from meta/recipes-extended/cracklib/cracklib_2.9.0.bb
rename to meta/recipes-extended/cracklib/cracklib_2.9.1.bb
index bbf88bb..5e6156f 100644
--- a/meta/recipes-extended/cracklib/cracklib_2.9.0.bb
+++ b/meta/recipes-extended/cracklib/cracklib_2.9.1.bb
@@ -13,8 +13,8 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/cracklib/cracklib-${PV}.tar.gz \
            file://0001-packlib.c-support-dictionary-byte-order-dependent.patch \
            file://0002-craklib-fix-testnum-and-teststr-failed.patch"
 
-SRC_URI[md5sum] = "e0f94ac2138fd33c7e77b19c1e9a9390"
-SRC_URI[sha256sum] = "17fecdfa78c0b9b47afa1533ea99b5351c3cef770bbd9c8c34391827efecbdc0"
+SRC_URI[md5sum] = "90536219c520add2ceb3c26f0d7da404"
+SRC_URI[sha256sum] = "408905c2539a97dc8cbbb6d7cd2046cb5647a345b4bda399220d9471be16d156"
 
 inherit autotools gettext
 
-- 
1.8.3.1

[PATCH 0/3] Package Updates

[Saul Wold]

These are some core packages for larger systems that had updates
that should be included in 1.6.

The bind update provides CVE fixes

Sau!

Saul Wold (3):
  util-linux: Update to 2.24.1
  dhcp: Update to 4.3.0
  bind: Update to 9.9.5

 .../bind-9.8.1-CVE-2012-5166.patch                 |   0
 .../{bind-9.8.1 => bind}/bind-CVE-2011-4313.patch  |   0
 .../{bind-9.8.1 => bind}/bind-CVE-2012-1667.patch  |   0
 .../{bind-9.8.1 => bind}/bind-CVE-2012-3817.patch  |   0
 .../{bind-9.8.1 => bind}/bind-CVE-2013-2266.patch  |   0
 .../bind-Fix-CVE-2012-4244.patch                   |   0
 .../bind/{bind-9.8.1 => bind}/conf.patch           |   0
 .../{bind-9.8.1 => bind}/cross-build-fix.patch     |   0
 .../bind/bind/dont-test-on-host.patch              |  13 ++
 .../make-etc-initd-bind-stop-work.patch            |   0
 .../mips1-not-support-opcode.diff                  |   0
 .../bind/{bind_9.8.1.bb => bind_9.9.5.bb}          |  20 +--
 meta/recipes-connectivity/dhcp/dhcp.inc            |   2 +-
 .../dhcp/dhcp/fix-external-bind.patch              | 115 +++++++-------
 .../dhcp/{dhcp_4.2.5-P1.bb => dhcp_4.3.0.bb}       |   6 +-
 meta/recipes-core/util-linux/util-linux.inc        |  12 +-
 .../util-linux/util-linux/fix-configure.patch      |  20 +--
 .../util-linux/util-linux/util-linux-native.patch  | 173 +++------------------
 .../{util-linux_2.23.2.bb => util-linux_2.24.1.bb} |   6 +-
 19 files changed, 123 insertions(+), 244 deletions(-)
 rename meta/recipes-connectivity/bind/{bind-9.8.1 => bind}/bind-9.8.1-CVE-2012-5166.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.8.1 => bind}/bind-CVE-2011-4313.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.8.1 => bind}/bind-CVE-2012-1667.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.8.1 => bind}/bind-CVE-2012-3817.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.8.1 => bind}/bind-CVE-2013-2266.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.8.1 => bind}/bind-Fix-CVE-2012-4244.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.8.1 => bind}/conf.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.8.1 => bind}/cross-build-fix.patch (100%)
 create mode 100644 meta/recipes-connectivity/bind/bind/dont-test-on-host.patch
 rename meta/recipes-connectivity/bind/{bind-9.8.1 => bind}/make-etc-initd-bind-stop-work.patch (100%)
 rename meta/recipes-connectivity/bind/{bind-9.8.1 => bind}/mips1-not-support-opcode.diff (100%)
 rename meta/recipes-connectivity/bind/{bind_9.8.1.bb => bind_9.9.5.bb} (76%)
 rename meta/recipes-connectivity/dhcp/{dhcp_4.2.5-P1.bb => dhcp_4.3.0.bb} (65%)
 rename meta/recipes-core/util-linux/{util-linux_2.23.2.bb => util-linux_2.24.1.bb} (83%)

-- 
1.8.3.1

[PATCH 0/3] Package Updates

[Saul Wold]

The following changes since commit bc6258f88705b0e7989089a8666ac5e5d2355823:

  grep: Add patch for texinfo 5.1 (2013-08-02 08:21:17 -0700)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib sgw/updates
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/updates

Saul Wold (3):
  mc: upgrade to 4.8.10
  util-linux: upgrade to 2.23.2
  man-pages: upgrade to 3.53

 .../util-linux/{util-linux_2.23.1.bb => util-linux_2.23.2.bb}         | 4 ++--
 .../man-pages/{man-pages_3.52.bb => man-pages_3.53.bb}                | 4 ++--
 meta/recipes-extended/mc/{mc_4.8.9.bb => mc_4.8.10.bb}                | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)
 rename meta/recipes-core/util-linux/{util-linux_2.23.1.bb => util-linux_2.23.2.bb} (83%)
 rename meta/recipes-extended/man-pages/{man-pages_3.52.bb => man-pages_3.53.bb} (82%)
 rename meta/recipes-extended/mc/{mc_4.8.9.bb => mc_4.8.10.bb} (93%)

-- 
1.8.1.4

[PATCH 0/3] Package Updates

[Saul Wold]

The following changes since commit 8fc6904fe97438478119db6cd23b7b4eb33b50aa:

  curl: add upstream status to patch (2013-07-18 12:21:13 -0700)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib sgw/updates
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/updates

Saul Wold (3):
  consolekit: Update to 0.4.6
  mklibs-native: Update to 0.1.38
  cups: Update to 1.6.3

 .../mklibs/{mklibs-native_0.1.37.bb => mklibs-native_0.1.38.bb}   | 4 ++--
 meta/recipes-extended/cups/{cups_1.6.2.bb => cups_1.6.3.bb}       | 4 ++--
 .../consolekit/{consolekit_0.4.5.bb => consolekit_0.4.6.bb}       | 8 +++-----
 3 files changed, 7 insertions(+), 9 deletions(-)
 rename meta/recipes-devtools/mklibs/{mklibs-native_0.1.37.bb => mklibs-native_0.1.38.bb} (80%)
 rename meta/recipes-extended/cups/{cups_1.6.2.bb => cups_1.6.3.bb} (80%)
 rename meta/recipes-support/consolekit/{consolekit_0.4.5.bb => consolekit_0.4.6.bb} (90%)

-- 
1.8.1.4

Re: [PATCH 0/3] Package Updates

[Sarbu, Florin-Ionut (Florin)]

[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]

EXTRA_OECONF+="--enable-tests" may be what you are looking for.

-----Original Message-----
From: Radu Moisan [radu.moisan@intel.com<mailto:radu.moisan@intel.com>]
Sent: Monday, May 28, 2012 11:24 PM Pacific Standard Time
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/3] Package Updates



On 05/28/2012 04:26 PM, Andrei Gherzan wrote:
On Mon, May 28, 2012 at 4:24 PM, Radu Moisan <radu.moisan@intel.com<mailto:radu.moisan@intel.com>> wrote:
On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
Dbus comes with a test suite. Running those should be a must.
I could not find how to run the test suite. I've tried dbus-daemon, dbus-monitor, and the rest, but non of them have options for some runtime checks. Other than that I imagine the test suite you mention must come in a separate package. Do we have a recipe for that to? Which image should I build to have that package included and be able to test?


There is an internal test suite for dbus. You can enable building those tests in configure:
"--enable-tests"

@g

So, isn't there a way of specifying build options in some file that bitbake will use afterwards to do the build? For instance where from ./configure is executed (from within bitbake I assume). I tried to take a look over configure file of dbus but could not figure out a way of hardcoding the --enable-tests option (not that hardcoding would be a best choice, but for testing purposes I considered it a choice). Any info on this is much appreciated.

Thanks,
Radu

[-- Attachment #2: Type: text/html, Size: 2503 bytes --]

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]

this is what I was looking for. I'll try it soon as my "hard-codded" 
version finshes buiding. thanks.

Radu

On 05/29/2012 10:01 AM, Sarbu, Florin-Ionut (Florin) wrote:
> EXTRA_OECONF+="--enable-tests" may be what you are looking for.
>
> -----Original Message-----
> *From: *Radu Moisan [radu.moisan@intel.com <mailto:radu.moisan@intel.com>]
> *Sent: *Monday, May 28, 2012 11:24 PM Pacific Standard Time
> *To: *openembedded-core@lists.openembedded.org
> *Subject: *Re: [OE-core] [PATCH 0/3] Package Updates
>
>
>
> On 05/28/2012 04:26 PM, Andrei Gherzan wrote:
>> On Mon, May 28, 2012 at 4:24 PM, Radu Moisan <radu.moisan@intel.com 
>> <mailto:radu.moisan@intel.com>> wrote:
>>
>>     On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
>>
>>         Dbus comes with a test suite. Running those should be a must.
>>
>>     I could not find how to run the test suite. I've tried
>>     dbus-daemon, dbus-monitor, and the rest, but non of them have
>>     options for some runtime checks. Other than that I imagine the
>>     test suite you mention must come in a separate package. Do we
>>     have a recipe for that to? Which image should I build to have
>>     that package included and be able to test?
>>
>>
>> There is an internal test suite for dbus. You can enable building 
>> those tests in configure:
>> "--enable-tests"
>>
>> @g
>>
> So, isn't there a way of specifying build options in some file that 
> bitbake will use afterwards to do the build? For instance where from 
> ./configure is executed (from within bitbake I assume). I tried to 
> take a look over configure file of dbus but could not figure out a way 
> of hardcoding the --enable-tests option (not that hardcoding would be 
> a best choice, but for testing purposes I considered it a choice). Any 
> info on this is much appreciated.
>
> Thanks,
> Radu

[-- Attachment #2: Type: text/html, Size: 3609 bytes --]

Re: [PATCH 0/3] Package Updates

[Burton, Ross]

Hi,

First, sorry for the thread breaking, I've just joined this list and I
didn't get this mail.

Koen Kooi wrote:
>>  dbus: Update to version 1.5.12
>
> First: how was this tested?
> Second: From the dbus website:
>
>        The current stable branch is D-Bus 1.4.x. This is the recommended
> version for most purposes.
>        The current development branch is D-Bus 1.5.x, which will lead to a
> 1.6.x stable branch in future.
>
> Why are you deleting the stable branch based recipe and add one from
> the development branch?

The definition of stable and unstable in DBus isn't as hard and fast
as you'd really like -- the 1.5.x cycle is very slow and mostly stable
from a crashy point of view.

I'd say there is a good rationale for having both 1.4.x (.20, so that
also needs an upgrade) and 1.5.x in oe-core.  The default should be
1.4 for obvious reasons (it's the stable release), and 1.5 should be
there for people who need the improvements.  In particular there has
been a lot of work on performance, so anyone heavily using dbus (i.e.
anything using Telepathy, which is where the improvements came from)
should look at 1.5 because it will give a noticeable improvement on
slower hardware.

Ross

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]



On 05/28/2012 01:55 PM, Burton, Ross wrote:
> Hi,
>
> First, sorry for the thread breaking, I've just joined this list and I
> didn't get this mail.
>
> Koen Kooi wrote:
>>>   dbus: Update to version 1.5.12
>> First: how was this tested?
the only testing I've done so far is to ensure it build and then check 
the version with dbus-daemon --version
>> Second: From the dbus website:
>>
>>         The current stable branch is D-Bus 1.4.x. This is the recommended
>> version for most purposes.
>>         The current development branch is D-Bus 1.5.x, which will lead to a
>> 1.6.x stable branch in future.
>>
>> Why are you deleting the stable branch based recipe and add one from
>> the development branch?
> The definition of stable and unstable in DBus isn't as hard and fast
> as you'd really like -- the 1.5.x cycle is very slow and mostly stable
> from a crashy point of view.
>
> I'd say there is a good rationale for having both 1.4.x (.20, so that
> also needs an upgrade) and 1.5.x in oe-core.  The default should be
> 1.4 for obvious reasons (it's the stable release), and 1.5 should be
> there for people who need the improvements.  In particular there has
> been a lot of work on performance, so anyone heavily using dbus (i.e.
> anything using Telepathy, which is where the improvements came from)
> should look at 1.5 because it will give a noticeable improvement on
> slower hardware.
>
> Ross
I suppose, then, I should add another recipe and support both. However, 
can someone point out how can I make one of them default.
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

[-- Attachment #2: Type: text/html, Size: 2916 bytes --]

Re: [PATCH 0/3] Package Updates

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]

On 05/28/2012 02:21 PM, Radu Moisan wrote:
>
>
> On 05/28/2012 01:55 PM, Burton, Ross wrote:
>> Hi,
>>
>> First, sorry for the thread breaking, I've just joined this list and I
>> didn't get this mail.
>>
>> Koen Kooi wrote:
>>>>   dbus: Update to version 1.5.12
>>> First: how was this tested?
> the only testing I've done so far is to ensure it build and then check 
> the version with dbus-daemon --version

Dbus comes with a test suite. Running those should be a must.
>>> Second: From the dbus website:
>>>
>>>         The current stable branch is D-Bus 1.4.x. This is the recommended
>>> version for most purposes.
>>>         The current development branch is D-Bus 1.5.x, which will lead to a
>>> 1.6.x stable branch in future.
>>>
>>> Why are you deleting the stable branch based recipe and add one from
>>> the development branch?
>> The definition of stable and unstable in DBus isn't as hard and fast
>> as you'd really like -- the 1.5.x cycle is very slow and mostly stable
>> from a crashy point of view.
>>
>> I'd say there is a good rationale for having both 1.4.x (.20, so that
>> also needs an upgrade) and 1.5.x in oe-core.  The default should be
>> 1.4 for obvious reasons (it's the stable release), and 1.5 should be
>> there for people who need the improvements.  In particular there has
>> been a lot of work on performance, so anyone heavily using dbus (i.e.
>> anything using Telepathy, which is where the improvements came from)
>> should look at 1.5 because it will give a noticeable improvement on
>> slower hardware.
>>
>> Ross
> I suppose, then, I should add another recipe and support both. 
> However, can someone point out how can I make one of them default.

DEFAULT_PREFERENCE

@g

[-- Attachment #2: Type: text/html, Size: 2889 bytes --]

Re: [PATCH 0/3] Package Updates

[Paul Eggleton]

On Monday 28 May 2012 14:21:30 Andrei Gherzan wrote:
> On 05/28/2012 02:21 PM, Radu Moisan wrote:
> > I suppose, then, I should add another recipe and support both.
> > However, can someone point out how can I make one of them default.
> 
> DEFAULT_PREFERENCE

i.e. set DEFAULT_PREFERENCE = "-1" in the newer recipe.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
> Dbus comes with a test suite. Running those should be a must.
I could not find how to run the test suite. I've tried dbus-daemon, 
dbus-monitor, and the rest, but non of them have options for some 
runtime checks. Other than that I imagine the test suite you mention 
must come in a separate package. Do we have a recipe for that to? Which 
image should I build to have that package included and be able to test?

Radu

Re: [PATCH 0/3] Package Updates

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 687 bytes --]

On Mon, May 28, 2012 at 4:24 PM, Radu Moisan <radu.moisan@intel.com> wrote:

> On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
>
>> Dbus comes with a test suite. Running those should be a must.
>>
> I could not find how to run the test suite. I've tried dbus-daemon,
> dbus-monitor, and the rest, but non of them have options for some runtime
> checks. Other than that I imagine the test suite you mention must come in a
> separate package. Do we have a recipe for that to? Which image should I
> build to have that package included and be able to test?
>
>
There is an internal test suite for dbus. You can enable building those
tests in configure:
"--enable-tests"

@g

[-- Attachment #2: Type: text/html, Size: 1181 bytes --]

Re: [PATCH 0/3] Package Updates

[Burton, Ross]

On 28 May 2012 14:26, Andrei Gherzan <andrei@gherzan.ro> wrote:
> There is an internal test suite for dbus. You can enable building those
> tests in configure:
> "--enable-tests"

Is there a good reason why these shouldn't be always ran when building dbus?

Ross

Re: [PATCH 0/3] Package Updates

[Richard Purdie]

On Mon, 2012-05-28 at 14:30 +0100, Burton, Ross wrote:
> On 28 May 2012 14:26, Andrei Gherzan <andrei@gherzan.ro> wrote:
> > There is an internal test suite for dbus. You can enable building those
> > tests in configure:
> > "--enable-tests"
> 
> Is there a good reason why these shouldn't be always ran when building dbus?

Well, we're cross compiling so it depends how they're written and
whether they can run in a cross environment. We've also taken steps to
reduce our build time so if these need something like perl or python,
adding those into the dependency chain is problematic.

I'm open to ideas here but so far they've not been useful so are likely
disabled.

Cheers,

Richard

Re: [PATCH 0/3] Package Updates

[Burton, Ross]

On 28 May 2012 14:44, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
>> Is there a good reason why these shouldn't be always ran when building dbus?
>
> Well, we're cross compiling so it depends how they're written and
> whether they can run in a cross environment. We've also taken steps to
> reduce our build time so if these need something like perl or python,
> adding those into the dependency chain is problematic.
>
> I'm open to ideas here but so far they've not been useful so are likely
> disabled.

I guess the overhead of setting up a qemu just to run the tests is a
bit excessive. :)

Ross

Re: [PATCH 0/3] Package Updates

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 917 bytes --]

On Mon, May 28, 2012 at 4:44 PM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Mon, 2012-05-28 at 14:30 +0100, Burton, Ross wrote:
> > On 28 May 2012 14:26, Andrei Gherzan <andrei@gherzan.ro> wrote:
> > > There is an internal test suite for dbus. You can enable building those
> > > tests in configure:
> > > "--enable-tests"
> >
> > Is there a good reason why these shouldn't be always ran when building
> dbus?
>
> Well, we're cross compiling so it depends how they're written and
> whether they can run in a cross environment. We've also taken steps to
> reduce our build time so if these need something like perl or python,
> adding those into the dependency chain is problematic.
>
>
The fact that these tests are not compiled by default it's good. As a
normal user of dbus i don't need those. But while doing an update a compile
with tests i think it's necessary.

@g

[-- Attachment #2: Type: text/html, Size: 1366 bytes --]

Re: [PATCH 0/3] Package Updates

[Philip Balister]

On 05/28/2012 09:58 AM, Andrei Gherzan wrote:
> On Mon, May 28, 2012 at 4:44 PM, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> 
>> On Mon, 2012-05-28 at 14:30 +0100, Burton, Ross wrote:
>>> On 28 May 2012 14:26, Andrei Gherzan <andrei@gherzan.ro> wrote:
>>>> There is an internal test suite for dbus. You can enable building those
>>>> tests in configure:
>>>> "--enable-tests"
>>>
>>> Is there a good reason why these shouldn't be always ran when building
>> dbus?
>>
>> Well, we're cross compiling so it depends how they're written and
>> whether they can run in a cross environment. We've also taken steps to
>> reduce our build time so if these need something like perl or python,
>> adding those into the dependency chain is problematic.
>>
>>
> The fact that these tests are not compiled by default it's good. As a
> normal user of dbus i don't need those. But while doing an update a compile
> with tests i think it's necessary.

Can you build the tests and package them separately? Then they could be
installed as part of a test image.

Philip

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]



On 05/29/2012 03:10 PM, Philip Balister wrote:
> On 05/28/2012 09:58 AM, Andrei Gherzan wrote:
>> On Mon, May 28, 2012 at 4:44 PM, Richard Purdie<
>> richard.purdie@linuxfoundation.org>  wrote:
>>
>>> On Mon, 2012-05-28 at 14:30 +0100, Burton, Ross wrote:
>>>> On 28 May 2012 14:26, Andrei Gherzan<andrei@gherzan.ro>  wrote:
>>>>> There is an internal test suite for dbus. You can enable building those
>>>>> tests in configure:
>>>>> "--enable-tests"
>>>> Is there a good reason why these shouldn't be always ran when building
>>> dbus?
>>>
>>> Well, we're cross compiling so it depends how they're written and
>>> whether they can run in a cross environment. We've also taken steps to
>>> reduce our build time so if these need something like perl or python,
>>> adding those into the dependency chain is problematic.
>>>
>>>
>> The fact that these tests are not compiled by default it's good. As a
>> normal user of dbus i don't need those. But while doing an update a compile
>> with tests i think it's necessary.
> Can you build the tests and package them separately? Then they could be
> installed as part of a test image.
>
> Philip
>
That would certainly be an option, but I really don't know where to 
start from :)
Meanwhile, I tried to further debug my scenario with 
--enable-modular-tests and I tried to manually resolve the missing *.h 
files (by copying them from dbus-glib to dbus include folder) just to 
see where is goes. I found out, somehow expected, that further undefined 
reference errors were thrown (to functions from dbus-glib). Thus now I'm 
looking to point somehow dbus tests to link against dbus-glib. Does 
anyone have a clue where should I look?

Radu

[-- Attachment #2: Type: text/html, Size: 2721 bytes --]

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]



On 05/28/2012 04:26 PM, Andrei Gherzan wrote:
> On Mon, May 28, 2012 at 4:24 PM, Radu Moisan <radu.moisan@intel.com 
> <mailto:radu.moisan@intel.com>> wrote:
>
>     On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
>
>         Dbus comes with a test suite. Running those should be a must.
>
>     I could not find how to run the test suite. I've tried
>     dbus-daemon, dbus-monitor, and the rest, but non of them have
>     options for some runtime checks. Other than that I imagine the
>     test suite you mention must come in a separate package. Do we have
>     a recipe for that to? Which image should I build to have that
>     package included and be able to test?
>
>
> There is an internal test suite for dbus. You can enable building 
> those tests in configure:
> "--enable-tests"
>
> @g
>
So, isn't there a way of specifying build options in some file that 
bitbake will use afterwards to do the build? For instance where from 
./configure is executed (from within bitbake I assume). I tried to take 
a look over configure file of dbus but could not figure out a way of 
hardcoding the --enable-tests option (not that hardcoding would be a 
best choice, but for testing purposes I considered it a choice). Any 
info on this is much appreciated.

Thanks,
Radu

[-- Attachment #2: Type: text/html, Size: 2543 bytes --]

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]



On 05/29/2012 09:28 AM, Radu Moisan wrote:
>
>
> On 05/28/2012 04:26 PM, Andrei Gherzan wrote:
>> On Mon, May 28, 2012 at 4:24 PM, Radu Moisan <radu.moisan@intel.com 
>> <mailto:radu.moisan@intel.com>> wrote:
>>
>>     On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
>>
>>         Dbus comes with a test suite. Running those should be a must.
>>
>>     I could not find how to run the test suite. I've tried
>>     dbus-daemon, dbus-monitor, and the rest, but non of them have
>>     options for some runtime checks. Other than that I imagine the
>>     test suite you mention must come in a separate package. Do we
>>     have a recipe for that to? Which image should I build to have
>>     that package included and be able to test?
>>
>>
>> There is an internal test suite for dbus. You can enable building 
>> those tests in configure:
>> "--enable-tests"
>>
>> @g
>>
> So, isn't there a way of specifying build options in some file that 
> bitbake will use afterwards to do the build? For instance where from 
> ./configure is executed (from within bitbake I assume). I tried to 
> take a look over configure file of dbus but could not figure out a way 
> of hardcoding the --enable-tests option (not that hardcoding would be 
> a best choice, but for testing purposes I considered it a choice). Any 
> info on this is much appreciated.
>
> Thanks,
> Radu
Found it in oe_runconf(). Will try to build them, see what comes out of 
it :)
Any comments still apreciated.

Radu

[-- Attachment #2: Type: text/html, Size: 2946 bytes --]

[PATCH 0/3] Package Updates

[Radu Moisan]

This patchset updates dbus, mtd-utils and foomatic-filters.

The following changes since commit 0f795f81fe5ad3ef78c21a177eca90fbc8810f81:

  qemu: disable vnc-jpeg compression (2012-05-24 08:53:40 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib rmoisan/updates
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rmoisan/updates

Radu Moisan (3):
  foomatic-filters: update to version 4.0.15
  mtd-utils: Update to version 1.5.0
  dbus: Update to version 1.5.12

 .../dbus/{dbus-1.4.16 => dbus-1.5.12}/dbus-1.init  |    0
 .../dbus/{dbus-1.4.16 => dbus-1.5.12}/tmpdir.patch |    0
 meta/recipes-core/dbus/dbus_1.4.16.bb              |    7 -------
 meta/recipes-core/dbus/dbus_1.5.12.bb              |    7 +++++++
 .../add-exclusion-to-mkfs-jffs2-git-2.patch        |    0
 .../mtd/{mtd-utils_1.4.9.bb => mtd-utils_1.5.0.bb} |    2 +-
 ...filters_4.0.7.bb => foomatic-filters_4.0.15.bb} |    6 +++---
 7 files changed, 11 insertions(+), 11 deletions(-)
 rename meta/recipes-core/dbus/{dbus-1.4.16 => dbus-1.5.12}/dbus-1.init (100%)
 rename meta/recipes-core/dbus/{dbus-1.4.16 => dbus-1.5.12}/tmpdir.patch (100%)
 delete mode 100644 meta/recipes-core/dbus/dbus_1.4.16.bb
 create mode 100644 meta/recipes-core/dbus/dbus_1.5.12.bb
 rename meta/recipes-devtools/mtd/{mtd-utils-1.4.9 => mtd-utils-1.5.0}/add-exclusion-to-mkfs-jffs2-git-2.patch (100%)
 rename meta/recipes-devtools/mtd/{mtd-utils_1.4.9.bb => mtd-utils_1.5.0.bb} (98%)
 rename meta/recipes-extended/foomatic/{foomatic-filters_4.0.7.bb => foomatic-filters_4.0.15.bb} (90%)

-- 
1.7.9.5

Re: [PATCH 0/3] Package Updates

[Koen Kooi]

Op 25 mei 2012, om 10:50 heeft Radu Moisan het volgende geschreven:

> This patchset updates dbus, mtd-utils and foomatic-filters.
> 
> The following changes since commit 0f795f81fe5ad3ef78c21a177eca90fbc8810f81:
> 
>  qemu: disable vnc-jpeg compression (2012-05-24 08:53:40 +0100)
> 
> are available in the git repository at:
> 
>  git://git.yoctoproject.org/poky-contrib rmoisan/updates
>  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rmoisan/updates
> 
> Radu Moisan (3):
>  foomatic-filters: update to version 4.0.15
>  mtd-utils: Update to version 1.5.0
>  dbus: Update to version 1.5.12

First: how was this tested?
Second: From the dbus website:

	The current stable branch is D-Bus 1.4.x. This is the recommended version for most purposes.
	The current development branch is D-Bus 1.5.x, which will lead to a 1.6.x stable branch in future.

Why are you deleting the stable branch based recipe and add one from the development branch?