From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: linux-yocto and linux-libc-headers are again going backwards
Date: Thu, 6 Oct 2016 10:54:22 +0200 [thread overview]
Message-ID: <20161006085422.GA2921@jama> (raw)
[-- 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 --]
next reply other threads:[~2016-10-06 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 8:54 Martin Jansa [this message]
2016-10-06 9:27 ` linux-yocto and linux-libc-headers are again going backwards Richard Purdie
2016-10-06 10:20 ` Burton, Ross
2016-10-06 17:07 ` Khem Raj
2016-10-06 18:58 ` Richard Purdie
2016-10-12 12:18 ` Martin Jansa
2016-10-12 12:55 ` Jonathan Liu
2016-10-12 13:14 ` 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=20161006085422.GA2921@jama \
--to=martin.jansa@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.