linux-yocto and linux-libc-headers are again going backwards

linux-yocto and linux-libc-headers are again going backwards

[Martin Jansa]

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

Either use 4.7.99+4.8-rc4 like most other recipes do or at least "4.8~rc4"
which might sort lower than "4.8" (but needs to be verified for all
packaging backends first).

Ignoring all this completely results with what we can see in oe-core
now:

ERROR: linux-libc-headers-4.8-r0 do_packagedata: QA Issue: Package
version for package linux-libc-headers-dbg went backwards which would
break package feeds from (0:4.8-rc4-r0.0 to 0:4.8-r0.0)
[version-going-backwards]

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 169 bytes --]

Re: linux-yocto and linux-libc-headers are again going backwards

[Richard Purdie]

On Thu, 2016-10-06 at 10:54 +0200, Martin Jansa wrote:
> Either use 4.7.99+4.8-rc4 like most other recipes do or at least
> "4.8~rc4"
> which might sort lower than "4.8" (but needs to be verified for all
> packaging backends first).
> 
> Ignoring all this completely results with what we can see in oe-core
> now:
> 
> ERROR: linux-libc-headers-4.8-r0 do_packagedata: QA Issue: Package
> version for package linux-libc-headers-dbg went backwards which would
> break package feeds from (0:4.8-rc4-r0.0 to 0:4.8-r0.0)
> [version-going-backwards]

Sorry, we did screw up there :(. Lots of moving pieces and its hard to
catch/remember everything.

I wish we knew for certain whether ~ works properly everywhere. A good
case for some unittests I guess...

Cheers,

Richard

Re: linux-yocto and linux-libc-headers are again going backwards

[Burton, Ross]

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

On 6 October 2016 at 10:27, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> I wish we knew for certain whether ~ works properly everywhere. A good
> case for some unittests I guess...
>

I own the bug for that and there's actually a start at this in
poky-contrib.  The problem is that it's practically impossible to ask RPM
to do a version check from a shell, and opkg at the time had three
different comparison algorithms depending on what you were doing.

I'll have another look for 2.3.

Ross

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

Re: linux-yocto and linux-libc-headers are again going backwards

[Khem Raj]

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


> On Oct 6, 2016, at 2:27 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> 
> On Thu, 2016-10-06 at 10:54 +0200, Martin Jansa wrote:
>> Either use 4.7.99+4.8-rc4 like most other recipes do or at least
>> "4.8~rc4"
>> which might sort lower than "4.8" (but needs to be verified for all
>> packaging backends first).
>> 
>> Ignoring all this completely results with what we can see in oe-core
>> now:
>> 
>> ERROR: linux-libc-headers-4.8-r0 do_packagedata: QA Issue: Package
>> version for package linux-libc-headers-dbg went backwards which would
>> break package feeds from (0:4.8-rc4-r0.0 to 0:4.8-r0.0)
>> [version-going-backwards]
> 
> Sorry, we did screw up there :(. Lots of moving pieces and its hard to
> catch/remember everything.
> 
> I wish we knew for certain whether ~ works properly everywhere. A good
> case for some unittests I guess…

I always wished there was a magic wand ( a sanity test) sort of which
was able to catch the package feed upgradability

> 
> Cheers,
> 
> Richard
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

Re: linux-yocto and linux-libc-headers are again going backwards

[Richard Purdie]

On Thu, 2016-10-06 at 10:07 -0700, Khem Raj wrote:
> > 
> > On Oct 6, 2016, at 2:27 AM, Richard Purdie <richard.purdie@linuxfou
> > ndation.org> wrote:
> > 
> > On Thu, 2016-10-06 at 10:54 +0200, Martin Jansa wrote:
> > > 
> > > Either use 4.7.99+4.8-rc4 like most other recipes do or at least
> > > "4.8~rc4"
> > > which might sort lower than "4.8" (but needs to be verified for
> > > all
> > > packaging backends first).
> > > 
> > > Ignoring all this completely results with what we can see in oe-
> > > core
> > > now:
> > > 
> > > ERROR: linux-libc-headers-4.8-r0 do_packagedata: QA Issue:
> > > Package
> > > version for package linux-libc-headers-dbg went backwards which
> > > would
> > > break package feeds from (0:4.8-rc4-r0.0 to 0:4.8-r0.0)
> > > [version-going-backwards]
> > Sorry, we did screw up there :(. Lots of moving pieces and its hard
> > to
> > catch/remember everything.
> > 
> > I wish we knew for certain whether ~ works properly everywhere. A
> > good
> > case for some unittests I guess…
> I always wished there was a magic wand ( a sanity test) sort of which
> was able to catch the package feed upgradability

There is buildhistory but sadly it catches it too late (after 4.8-rcX
merges and is changed to 4.8, not when 4.7 -> 4.8-rcX).

Cheers,

Richard

Re: linux-yocto and linux-libc-headers are again going backwards

[Martin Jansa]

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

On Thu, Oct 06, 2016 at 10:54:22AM +0200, Martin Jansa wrote:
> Either use 4.7.99+4.8-rc4 like most other recipes do or at least "4.8~rc4"
> which might sort lower than "4.8" (but needs to be verified for all
> packaging backends first).
> 
> Ignoring all this completely results with what we can see in oe-core
> now:
> 
> ERROR: linux-libc-headers-4.8-r0 do_packagedata: QA Issue: Package
> version for package linux-libc-headers-dbg went backwards which would
> break package feeds from (0:4.8-rc4-r0.0 to 0:4.8-r0.0)
> [version-going-backwards]

I've noticed one more thing related to linux-yocto. Is it expected that
only qemuarm is using 4.8 by default and (qemu)x86* is still using 4.4?

meta/conf/machine/include/x86-base.inc:PREFERRED_VERSION_linux-yocto ??= "4.4%"
meta/conf/machine/qemuarm.conf:PREFERRED_VERSION_linux-yocto ??= "4.8%"

I've checked poky repository and it is using 4.8 at least for qemu* and various
other MACHINEs, so it might make sense to use the same for nodistro for consistency?

OE @ ~/extras/poky $ git grep PREFERRED_VERSION.*linux-yocto
bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml:     PREFERRED_VERSION_linux-yocto = "3.10%"
documentation/bsp-guide/bsp.xml:     PREFERRED_VERSION_linux-yocto ?= "4.4%"
documentation/ref-manual/ref-variables.xml:     PREFERRED_VERSION_linux-yocto = "3.19%"
documentation/ref-manual/ref-variables.xml:     PREFERRED_VERSION_linux-yocto_qemux86 = "3.4%"
documentation/ref-manual/ref-variables.xml:     PREFERRED_VERSION_linux-yocto_forcevariable = "3.4%"
meta-poky/conf/distro/poky-lsb.conf:PREFERRED_VERSION_linux-yocto_linuxstdbase ?= "4.1%"
meta-poky/conf/distro/poky-tiny.conf:PREFERRED_VERSION_linux-yocto-tiny ?= "4.4%"
meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemux86 ?= "4.8%"
meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemux86-64 ?= "4.8%"
meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemuarm ?= "4.8%"
meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemumips ?= "4.8%"
meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemumips64 ?= "4.8%"
meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemuppc ?= "4.8%"
meta-yocto-bsp/conf/machine/beaglebone.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
meta-yocto-bsp/conf/machine/edgerouter.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
meta-yocto-bsp/conf/machine/genericx86-64.conf:PREFERRED_VERSION_linux-yocto_genericx86-64 ?= "4.8%"
meta-yocto-bsp/conf/machine/genericx86.conf:PREFERRED_VERSION_linux-yocto_genericx86 ?= "4.8%"
meta-yocto-bsp/conf/machine/include/genericx86-common.inc:PREFERRED_VERSION_linux-yocto ?= "4.4%"
meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
meta/conf/machine/include/x86-base.inc:PREFERRED_VERSION_linux-yocto ??= "4.4%"
meta/conf/machine/qemuarm.conf:PREFERRED_VERSION_linux-yocto ??= "4.8%"
meta/conf/machine/qemuarm.conf:QB_DTB = "${@base_version_less_or_equal('PREFERRED_VERSION_linux-yocto', '4.7', '', 'zImage-versatile-pb.dtb', d)}"

Regards,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 169 bytes --]

Re: linux-yocto and linux-libc-headers are again going backwards

[Jonathan Liu]

On 12 October 2016 at 23:18, Martin Jansa <martin.jansa@gmail.com> wrote:
> On Thu, Oct 06, 2016 at 10:54:22AM +0200, Martin Jansa wrote:
>> Either use 4.7.99+4.8-rc4 like most other recipes do or at least "4.8~rc4"
>> which might sort lower than "4.8" (but needs to be verified for all
>> packaging backends first).
>>
>> Ignoring all this completely results with what we can see in oe-core
>> now:
>>
>> ERROR: linux-libc-headers-4.8-r0 do_packagedata: QA Issue: Package
>> version for package linux-libc-headers-dbg went backwards which would
>> break package feeds from (0:4.8-rc4-r0.0 to 0:4.8-r0.0)
>> [version-going-backwards]
>
> I've noticed one more thing related to linux-yocto. Is it expected that
> only qemuarm is using 4.8 by default and (qemu)x86* is still using 4.4?
>
> meta/conf/machine/include/x86-base.inc:PREFERRED_VERSION_linux-yocto ??= "4.4%"
> meta/conf/machine/qemuarm.conf:PREFERRED_VERSION_linux-yocto ??= "4.8%"
>
> I've checked poky repository and it is using 4.8 at least for qemu* and various
> other MACHINEs, so it might make sense to use the same for nodistro for consistency?

Using bitbake and OE-core actually selects linux-yocto 4.8 for me.
Probably because x86-base.inc isn't actually used by the machine
definitions in OE-core.

I am also running into a kernel bug with linux-yocto 4.8 on x86:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10402

>
> OE @ ~/extras/poky $ git grep PREFERRED_VERSION.*linux-yocto
> bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml:     PREFERRED_VERSION_linux-yocto = "3.10%"
> documentation/bsp-guide/bsp.xml:     PREFERRED_VERSION_linux-yocto ?= "4.4%"
> documentation/ref-manual/ref-variables.xml:     PREFERRED_VERSION_linux-yocto = "3.19%"
> documentation/ref-manual/ref-variables.xml:     PREFERRED_VERSION_linux-yocto_qemux86 = "3.4%"
> documentation/ref-manual/ref-variables.xml:     PREFERRED_VERSION_linux-yocto_forcevariable = "3.4%"
> meta-poky/conf/distro/poky-lsb.conf:PREFERRED_VERSION_linux-yocto_linuxstdbase ?= "4.1%"
> meta-poky/conf/distro/poky-tiny.conf:PREFERRED_VERSION_linux-yocto-tiny ?= "4.4%"
> meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
> meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemux86 ?= "4.8%"
> meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemux86-64 ?= "4.8%"
> meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemuarm ?= "4.8%"
> meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemumips ?= "4.8%"
> meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemumips64 ?= "4.8%"
> meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemuppc ?= "4.8%"
> meta-yocto-bsp/conf/machine/beaglebone.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
> meta-yocto-bsp/conf/machine/edgerouter.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
> meta-yocto-bsp/conf/machine/genericx86-64.conf:PREFERRED_VERSION_linux-yocto_genericx86-64 ?= "4.8%"
> meta-yocto-bsp/conf/machine/genericx86.conf:PREFERRED_VERSION_linux-yocto_genericx86 ?= "4.8%"
> meta-yocto-bsp/conf/machine/include/genericx86-common.inc:PREFERRED_VERSION_linux-yocto ?= "4.4%"
> meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
> meta/conf/machine/include/x86-base.inc:PREFERRED_VERSION_linux-yocto ??= "4.4%"
> meta/conf/machine/qemuarm.conf:PREFERRED_VERSION_linux-yocto ??= "4.8%"
> meta/conf/machine/qemuarm.conf:QB_DTB = "${@base_version_less_or_equal('PREFERRED_VERSION_linux-yocto', '4.7', '', 'zImage-versatile-pb.dtb', d)}"
>
> Regards,
> --
> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

Re: linux-yocto and linux-libc-headers are again going backwards

[Martin Jansa]

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

On Wed, Oct 12, 2016 at 11:55:00PM +1100, Jonathan Liu wrote:
> On 12 October 2016 at 23:18, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Thu, Oct 06, 2016 at 10:54:22AM +0200, Martin Jansa wrote:
> >> Either use 4.7.99+4.8-rc4 like most other recipes do or at least "4.8~rc4"
> >> which might sort lower than "4.8" (but needs to be verified for all
> >> packaging backends first).
> >>
> >> Ignoring all this completely results with what we can see in oe-core
> >> now:
> >>
> >> ERROR: linux-libc-headers-4.8-r0 do_packagedata: QA Issue: Package
> >> version for package linux-libc-headers-dbg went backwards which would
> >> break package feeds from (0:4.8-rc4-r0.0 to 0:4.8-r0.0)
> >> [version-going-backwards]
> >
> > I've noticed one more thing related to linux-yocto. Is it expected that
> > only qemuarm is using 4.8 by default and (qemu)x86* is still using 4.4?
> >
> > meta/conf/machine/include/x86-base.inc:PREFERRED_VERSION_linux-yocto ??= "4.4%"
> > meta/conf/machine/qemuarm.conf:PREFERRED_VERSION_linux-yocto ??= "4.8%"
> >
> > I've checked poky repository and it is using 4.8 at least for qemu* and various
> > other MACHINEs, so it might make sense to use the same for nodistro for consistency?
> 
> Using bitbake and OE-core actually selects linux-yocto 4.8 for me.
> Probably because x86-base.inc isn't actually used by the machine
> definitions in OE-core.

You're right, the issue was caused by bbappend in one of my layers,
which bumps PE, so the 4.4 which had this bbappend sorted higher than
other versions, from bitbake-layers:

linux-yocto:
  meta                 1:4.4.22+gitAUTOINC+d9f20333c4_f4e52341c3
  meta                 4.1.33+gitAUTOINC+322fa5b279_a38cb20273
  meta                 4.8+gitAUTOINC+03bf3dd731_67813e7efa

You're also right that x86-base.inc isn't used anywhere in oe-core's
MACHINEs so it just confused me, that qemuarm explicitly selects 4.8
version even when there is no negative D_P and 4.8 is now default.

> I am also running into a kernel bug with linux-yocto 4.8 on x86:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10402

I didn't get that far to actually boot it yet, in my environment I need
http://lists.openembedded.org/pipermail/openembedded-core/2016-October/127512.html
for sysconfig to find the kernel.

When I've created /vmlinuz manually then almost everything was failing
to start for whatever reason (that's why I started checking the kernel
version as well).

Thanks

> > OE @ ~/extras/poky $ git grep PREFERRED_VERSION.*linux-yocto
> > bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml:     PREFERRED_VERSION_linux-yocto = "3.10%"
> > documentation/bsp-guide/bsp.xml:     PREFERRED_VERSION_linux-yocto ?= "4.4%"
> > documentation/ref-manual/ref-variables.xml:     PREFERRED_VERSION_linux-yocto = "3.19%"
> > documentation/ref-manual/ref-variables.xml:     PREFERRED_VERSION_linux-yocto_qemux86 = "3.4%"
> > documentation/ref-manual/ref-variables.xml:     PREFERRED_VERSION_linux-yocto_forcevariable = "3.4%"
> > meta-poky/conf/distro/poky-lsb.conf:PREFERRED_VERSION_linux-yocto_linuxstdbase ?= "4.1%"
> > meta-poky/conf/distro/poky-tiny.conf:PREFERRED_VERSION_linux-yocto-tiny ?= "4.4%"
> > meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
> > meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemux86 ?= "4.8%"
> > meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemux86-64 ?= "4.8%"
> > meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemuarm ?= "4.8%"
> > meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemumips ?= "4.8%"
> > meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemumips64 ?= "4.8%"
> > meta-poky/conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto_qemuppc ?= "4.8%"
> > meta-yocto-bsp/conf/machine/beaglebone.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
> > meta-yocto-bsp/conf/machine/edgerouter.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
> > meta-yocto-bsp/conf/machine/genericx86-64.conf:PREFERRED_VERSION_linux-yocto_genericx86-64 ?= "4.8%"
> > meta-yocto-bsp/conf/machine/genericx86.conf:PREFERRED_VERSION_linux-yocto_genericx86 ?= "4.8%"
> > meta-yocto-bsp/conf/machine/include/genericx86-common.inc:PREFERRED_VERSION_linux-yocto ?= "4.4%"
> > meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf:PREFERRED_VERSION_linux-yocto ?= "4.8%"
> > meta/conf/machine/include/x86-base.inc:PREFERRED_VERSION_linux-yocto ??= "4.4%"
> > meta/conf/machine/qemuarm.conf:PREFERRED_VERSION_linux-yocto ??= "4.8%"
> > meta/conf/machine/qemuarm.conf:QB_DTB = "${@base_version_less_or_equal('PREFERRED_VERSION_linux-yocto', '4.7', '', 'zImage-versatile-pb.dtb', d)}"
> >
> > Regards,
> > --
> > Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 169 bytes --]