From: "Wang, Jinfeng (CN)" <Jinfeng.Wang.CN@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap 09/11] glibc: fix CVE-2025-8058
Date: Fri, 26 Sep 2025 01:06:02 -0700 [thread overview]
Message-ID: <21409.1758873962886905830@lists.openembedded.org> (raw)
In-Reply-To: <c2b63f171719e2b1c12ba049cbe776adf9e0244b.1753910853.git.steve@sakoman.com>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
Hi all,
With this patch, after I add INHERIT += "buildhistory" in conf/local.conf, I found the following build errors:
ERROR: glibc-2.39+git-r0.wr2413 do_packagedata: QA Issue: Package version for package ldconfig went backwards which would break package feeds (from 0:2.39+git0+cff1042cce-r0.wr2408.0 to 0:2.39+git0+b027d5b145-r0.wr2413.0) [version-going-backwards]
ERROR: glibc-2.39+git-r0.wr2413 do_packagedata: QA Issue: Package version for package ldd went backwards which would break package feeds (from 0:2.39+git0+cff1042cce-r0.wr2408.0 to 0:2.39+git0+b027d5b145-r0.wr2413.0) [version-going-backwards]
ERROR: glibc-2.39+git-r0.wr2413 do_packagedata: QA Issue: Package version for package ldso went backwards which would break package feeds (from 0:2.39+git0+cff1042cce-r0.wr2408.0 to
I found in the buildhistory.bbclass, bb.utils.vercmp((pkge, pkgv, pkgr), (last_pkge, last_pkgv, last_pkgr)) will compare the version, the hash is part of the version.
The commit(d9b992de0da6be8e9bc26c39c4e5aa7bb9c2049e) in oe-core glibc, upgrade from cff1042cce to b027d5b145. c < b, so it is thought as version-going-backwards. How to deal with this situation?
Regards,
Jinfeng
[-- Attachment #2: Type: text/html, Size: 1326 bytes --]
next prev parent reply other threads:[~2025-09-26 8:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 21:28 [OE-core][scarthgap 00/11] Patch review Steve Sakoman
2025-07-30 21:28 ` [OE-core][scarthgap 01/11] gnutls: patch CVE-2025-32989 Steve Sakoman
2025-07-30 21:28 ` [OE-core][scarthgap 02/11] gnutls: patch read buffer overrun in the "pre_shared_key" extension Steve Sakoman
2025-07-30 21:28 ` [OE-core][scarthgap 03/11] gnutls: patch reject zero-length version in certificate request Steve Sakoman
2025-07-30 21:28 ` [OE-core][scarthgap 04/11] gnutls: patch CVE-2025-32988 Steve Sakoman
2025-07-30 21:28 ` [OE-core][scarthgap 05/11] gnutls: patch CVE-2025-32990 Steve Sakoman
2025-07-30 21:28 ` [OE-core][scarthgap 06/11] gnutls: patch CVE-2025-6395 Steve Sakoman
2025-07-30 21:28 ` [OE-core][scarthgap 07/11] ncurses: patch CVE-2025-6141 Steve Sakoman
2025-07-30 21:28 ` [OE-core][scarthgap 08/11] libxml2: patch CVE-2025-6170 Steve Sakoman
2025-07-30 21:29 ` [OE-core][scarthgap 09/11] glibc: fix CVE-2025-8058 Steve Sakoman
2025-09-26 8:06 ` Wang, Jinfeng (CN) [this message]
2025-09-26 17:19 ` [OE-core] [scarthgap " Gyorgy Sarvari
2025-07-30 21:29 ` [OE-core][scarthgap 10/11] scripts/install-buildtools: Update to 5.0.11 Steve Sakoman
2025-07-30 21:29 ` [OE-core][scarthgap 11/11] linux-libc-headers: Fix invalid conversion in cn_proc.h Steve Sakoman
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=21409.1758873962886905830@lists.openembedded.org \
--to=jinfeng.wang.cn@windriver.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.