[yocto] rocko: QA issue with glibc-locale

[Belisko Marek]

Hi,

On Fri, Oct 20, 2017 at 6:26 PM, Martin Jansa <martin.jansa at gmail.com> wrote:
> Similar QA issue is shown when you use:
> LOCALE_GENERATION_WITH_CROSS-LOCALEDEF_forcevariable = "0"
>
> which is needed to build glibc-locale with pyro on hosts with glibc-2.26
> (with ENABLE_BINARY_LOCALE_GENERATION = "1").
>
> On Fri, Oct 20, 2017 at 11:44 AM, Alexander Kanavin
> <alexander.kanavin at linux.intel.com> wrote:
>>
>> On 10/19/2017 10:15 PM, Burton, Ross wrote:
>>>
>>> On 19 October 2017 at 12:10, Belisko Marek <marek.belisko at gmail.com
>>> <mailto:marek.belisko at gmail.com>> wrote:
>>>
>>>     I'm using latest origin/rocko
>>>     (65d23bd7986615fdfb0f1717b615534a2a14ab80) with no change to build
>>>     beaglebone core-image-minimal. While build I got this QA error:
>>>
>>>     ERROR: glibc-locale-2.26-r0 do_package: QA Issue: glibc-locale:
>>>     Files/directories were installed but not shipped in any package:
>>>        /usr/share/i18n
>>>
>>>
>>> I've seen this (and some other weird ones) in glibc-locales, and they've
>>> always been resolved by just rebuilding the recipe. bitbake glibc-locale
>>> -cclean && bitbake glibc-locale might well make it go away.
>>
>>
>> I'm beginning to wonder if the best way to resolve these elusive
>> glibc-locale issues (also the notorious host contamination one) is to throw
>> away the existing, extremely convoluted recipe, and do a clean rewrite.
Probably. Should I fill some bugzilla somewhere? Rocko should be
released in few days (if not yet already) and this issue can be really
annoying ;)
>>
>> Alex
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>

BR,

marek



-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com