From: ecordonnier@snap.com
To: openembedded-core@lists.openembedded.org
Cc: Etienne Cordonnier <ecordonnier@snap.com>
Subject: [OE-core][PATCH v4 1/2] opkg: upgrade 0.7.0 -> 0.8.0
Date: Thu, 23 Oct 2025 15:46:55 +0200 [thread overview]
Message-ID: <20251023134656.2059483-1-ecordonnier@snap.com> (raw)
From: Etienne Cordonnier <ecordonnier@snap.com>
See release notes at
- http://downloads.yoctoproject.org/releases/opkg/opkg-0.8.0.release-notes
[0.8.0] - 2025-01-10
The minor version bump in this release is due to the changes to cURL error output line format.
- [Changed](https://git.yoctoproject.org/opkg/commit/?id=ab03377868256427279b36c4b2a298edae4260b8) the error output for the curl download backend, to now report the HTTP error code for failed requests.
- e.g. `error: log_curl_download_error: Failed to download headers of https://foo.bar/all/Packages.gz: The requested URL returned error: 401`
- Enabling debug-verbosity, while using the cURL backend, [will now](https://git.yoctoproject.org/opkg/commit/?id=ce6fede3db931bb0da70d1334cdc4101d0aec702) print cURL's verbose error log to stderr when there is a download failure.
- The verbose output may contain confidential information about your cURL transactions. So this is your reminder that debug-verbosity should not be enabled in production systems or sensitive security environments.
- The commandline configuration file option (`-f`) [can now](https://git.yoctoproject.org/opkg/commit/?id=36d08b93d2859992b624a4ba2f412cfa5c766050) be specified multiple times, and each configuration file will be loaded and their settings merged.
- [Fixed](https://git.yoctoproject.org/opkg/commit/?id=c87188d7535684fddb8cf80993c147b215602b63) a bug in control field parsing where custom fields whose keys are similar to other fields could be confused by the parser.
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
---
meta/recipes-devtools/opkg/{opkg_0.7.0.bb => opkg_0.8.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/opkg/{opkg_0.7.0.bb => opkg_0.8.0.bb} (97%)
diff --git a/meta/recipes-devtools/opkg/opkg_0.7.0.bb b/meta/recipes-devtools/opkg/opkg_0.8.0.bb
similarity index 97%
rename from meta/recipes-devtools/opkg/opkg_0.7.0.bb
rename to meta/recipes-devtools/opkg/opkg_0.8.0.bb
index 95480b47164..12e2edf7e3f 100644
--- a/meta/recipes-devtools/opkg/opkg_0.7.0.bb
+++ b/meta/recipes-devtools/opkg/opkg_0.8.0.bb
@@ -18,7 +18,7 @@ SRC_URI = "http://downloads.yoctoproject.org/releases/${BPN}/${BPN}-${PV}.tar.gz
file://run-ptest \
"
-SRC_URI[sha256sum] = "d973fd0f1568f58f87d6aecd9aa95e3e1f60214a45cee26704bf8fe757c54567"
+SRC_URI[sha256sum] = "582a4c9e220cce0b7d08a0915c95db9f24ae43ad372ed5d42d5ec5f6cd413f0c"
# This needs to be before ptest inherit, otherwise all ptest files end packaged
# in libopkg package if OPKGLIBDIR == libdir, because default
--
2.43.0
next reply other threads:[~2025-10-23 13:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 13:46 ecordonnier [this message]
2025-10-23 13:46 ` [OE-core][PATCH v4 2/2] opkg: upgrade 0.8.0 -> 0.9.0 ecordonnier
2025-11-27 17:08 ` Gyorgy Sarvari
2025-11-27 18:10 ` Etienne Cordonnier
2025-12-03 21:04 ` Khem Raj
2025-12-03 21:34 ` Khem Raj
2025-12-04 18:56 ` Etienne Cordonnier
2025-12-05 22:15 ` Etienne Cordonnier
2025-12-05 22:34 ` Khem Raj
2025-12-05 22:36 ` Etienne Cordonnier
2025-12-05 22:55 ` Khem Raj
2025-12-08 23:44 ` Etienne Cordonnier
2025-12-09 0:20 ` Khem Raj
2026-01-09 23:43 ` Ricardo de Araujo (Salveti)
[not found] ` <187122D70EFBB6A8.8642@lists.openembedded.org>
2025-11-17 9:26 ` Etienne Cordonnier
2025-11-17 9:43 ` Mathieu Dubois-Briand
[not found] <187122D53E394F49.25104@lists.openembedded.org>
2025-10-23 13:50 ` [OE-core][PATCH v4 1/2] opkg: upgrade 0.7.0 -> 0.8.0 Etienne Cordonnier
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=20251023134656.2059483-1-ecordonnier@snap.com \
--to=ecordonnier@snap.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.