Nondeterministic acl support in coreutils 6.9

Nondeterministic acl support in coreutils 6.9

[Andre McCurdy]

The GPLv2 coreutils recipe has PACKAGECONFIG support for acl, however
the coreutils 6.9 configure script doesn't seem to support
--disable-acl.

Build Configuration:
BB_VERSION        = "1.24.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS        = "i586-rdk-linux"
MACHINE           = "vbox32"
DISTRO            = "rdk"
DISTRO_VERSION    = "2.0"
TUNE_FEATURES     = "m32 core2"
TARGET_FPU        = ""
meta-bsp-vbox     = "(nobranch):0bf672f55d7566541846f32878d87d232ce9e501"
meta-rdk          =
"(detachedfrom74057dd):74057dd18efb19601fdad551b5dc716a1c75bf43"
meta-metrological = "(nobranch):abbd111fee3ae1ade2fc2997ccda0eb9782da761"
meta-multimedia
meta-oe
meta-python
meta-networking
meta-ruby         = "(nobranch):200f6cafc878d4c26871fc56d21ecc8eaa9aa61b"
meta-qt5          =
"(detachedfrom41c5daa):41c5daa84af4466bfc9aa61f6f772c68470a628b"
meta              =
"(detachedfrom93d79fc):93d79fc162bd49387958e9e4d898dc4ba50d20b0"

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: QA Issue: coreutils rdepends on libacl, but it isn't a build
dependency? [build-deps]

Re: Nondeterministic acl support in coreutils 6.9

[Qian Lei]

On Mon, 12 Jan 2015 11:25:19 -0800
Andre McCurdy <armccurdy@gmail.com> wrote:

> The GPLv2 coreutils recipe has PACKAGECONFIG support for acl, however
> the coreutils 6.9 configure script doesn't seem to support
> --disable-acl.

I have the same problem. There's no QA waring aflter droping the PACKAGECONFIG.
I saw the commit message(8030fdc198c1037ae458899eebd14a4fae04c49a) and don'k
know what the  "CQID: 430353" means. Is this a number of bugzilla?
 
> Build Configuration:
> BB_VERSION        = "1.24.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-14.04"
> TARGET_SYS        = "i586-rdk-linux"
> MACHINE           = "vbox32"
> DISTRO            = "rdk"
> DISTRO_VERSION    = "2.0"
> TUNE_FEATURES     = "m32 core2"
> TARGET_FPU        = ""
> meta-bsp-vbox     = "(nobranch):0bf672f55d7566541846f32878d87d232ce9e501"
> meta-rdk          =
> "(detachedfrom74057dd):74057dd18efb19601fdad551b5dc716a1c75bf43"
> meta-metrological = "(nobranch):abbd111fee3ae1ade2fc2997ccda0eb9782da761"
> meta-multimedia
> meta-oe
> meta-python
> meta-networking
> meta-ruby         = "(nobranch):200f6cafc878d4c26871fc56d21ecc8eaa9aa61b"
> meta-qt5          =
> "(detachedfrom41c5daa):41c5daa84af4466bfc9aa61f6f772c68470a628b"
> meta              =
> "(detachedfrom93d79fc):93d79fc162bd49387958e9e4d898dc4ba50d20b0"
> 
> NOTE: Preparing runqueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> WARNING: QA Issue: coreutils rdepends on libacl, but it isn't a build
> dependency? [build-deps]



-- 
Qian Lei

Re: Nondeterministic acl support in coreutils 6.9

[Andre McCurdy]

On Thu, Jan 29, 2015 at 8:24 PM, Qian Lei <qianl.fnst@cn.fujitsu.com> wrote:
> On Mon, 12 Jan 2015 11:25:19 -0800
> Andre McCurdy <armccurdy@gmail.com> wrote:
>
>> The GPLv2 coreutils recipe has PACKAGECONFIG support for acl, however
>> the coreutils 6.9 configure script doesn't seem to support
>> --disable-acl.
>
> I have the same problem. There's no QA waring aflter droping the PACKAGECONFIG.

I think the QA warning will only be seen if acl PACKAGECONFIG is
disabled but coreutils builds with acl support enabled (because it's
configure script finds acl headers in sysroot).

Steps to reproduce the issue are something like:

 - Blacklist GPLv3 packages (ie force coreutils 6.9 to be used)
 - Remove acl from DISTRO_FEATURES
 - Build acl (or build some other recipe which depends on acl)
 - Build coreutils

I think the fix is going to require patching coreutils so that it
respects --disable-acl, but I'm not sure how best to do that.

> I saw the commit message(8030fdc198c1037ae458899eebd14a4fae04c49a) and don'k
> know what the  "CQID: 430353" means. Is this a number of bugzilla?

CQID is a reference to Wind River's bug tracking system. Not publicly
accessible, AFAIK.

>> Build Configuration:
>> BB_VERSION        = "1.24.0"
>> BUILD_SYS         = "x86_64-linux"
>> NATIVELSBSTRING   = "Ubuntu-14.04"
>> TARGET_SYS        = "i586-rdk-linux"
>> MACHINE           = "vbox32"
>> DISTRO            = "rdk"
>> DISTRO_VERSION    = "2.0"
>> TUNE_FEATURES     = "m32 core2"
>> TARGET_FPU        = ""
>> meta-bsp-vbox     = "(nobranch):0bf672f55d7566541846f32878d87d232ce9e501"
>> meta-rdk          =
>> "(detachedfrom74057dd):74057dd18efb19601fdad551b5dc716a1c75bf43"
>> meta-metrological = "(nobranch):abbd111fee3ae1ade2fc2997ccda0eb9782da761"
>> meta-multimedia
>> meta-oe
>> meta-python
>> meta-networking
>> meta-ruby         = "(nobranch):200f6cafc878d4c26871fc56d21ecc8eaa9aa61b"
>> meta-qt5          =
>> "(detachedfrom41c5daa):41c5daa84af4466bfc9aa61f6f772c68470a628b"
>> meta              =
>> "(detachedfrom93d79fc):93d79fc162bd49387958e9e4d898dc4ba50d20b0"
>>
>> NOTE: Preparing runqueue
>> NOTE: Executing SetScene Tasks
>> NOTE: Executing RunQueue Tasks
>> WARNING: QA Issue: coreutils rdepends on libacl, but it isn't a build
>> dependency? [build-deps]
>
>
>
> --
> Qian Lei