Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *minicom* to *2.9* has Succeeded.
Next steps:
- apply the patch: git am 0001-minicom-upgrade-2.8-2.9.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 78d791cb9b16fd414cdc1ec0f992d9a7328af65e Mon Sep 17 00:00:00 2001
From: Upgrade Helper <[email protected]>
Date: Fri, 1 Mar 2024 15:12:26 +0000
Subject: [PATCH] minicom: upgrade 2.8 -> 2.9
---
...ix-minicom-h-v-return-value-is-not-0.patch | 33 -------------------
.../minicom/allow.to.disable.lockdev.patch | 30 -----------------
.../{minicom_2.8.bb => minicom_2.9.bb} | 7 ++--
3 files changed, 2 insertions(+), 68 deletions(-)
delete mode 100644
meta/recipes-extended/minicom/minicom/0001-fix-minicom-h-v-return-value-is-not-0.patch
delete mode 100644
meta/recipes-extended/minicom/minicom/allow.to.disable.lockdev.patch
rename meta/recipes-extended/minicom/{minicom_2.8.bb => minicom_2.9.bb} (80%)
diff --git
a/meta/recipes-extended/minicom/minicom/0001-fix-minicom-h-v-return-value-is-not-0.patch
b/meta/recipes-extended/minicom/minicom/0001-fix-minicom-h-v-return-value-is-not-0.patch
deleted file mode 100644
index 9e67126f3e..0000000000
---
a/meta/recipes-extended/minicom/minicom/0001-fix-minicom-h-v-return-value-is-not-0.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-Exit normally for help/verison options
-
-If -v or -h is used for the help/version information, it is a normal exit
situation,
-not an error condition. Sometimes these are used as a simple operation test of
the
-resulting binary so the exit code does matter.
-
-Signed-off-by: Richard Purdie <[email protected]>
-Upstream-Status: Submitted
[https://salsa.debian.org/minicom-team/minicom/-/merge_requests/14]
----
- src/minicom.c | 6 ++----
- 1 file changed, 2 insertions(+), 4 deletions(-)
-
-Index: minicom-2.8/src/minicom.c
-===================================================================
---- minicom-2.8.orig/src/minicom.c
-+++ minicom-2.8/src/minicom.c
-@@ -1257,14 +1257,14 @@ int main(int argc, char **argv)
- "modify it under the terms of the GNU General Public
License\n"
- "as published by the Free Software Foundation; either
version\n"
- "2 of the License, or (at your option) any later
version.\n\n"));
-- exit(1);
-+ exit(0);
- break;
- case 's': /* setup mode */
- dosetup = 1;
- break;
- case 'h':
- helpthem();
-- exit(1);
-+ exit(0);
- break;
- case 'p': /* Pseudo terminal to use. */
- if (strncmp(optarg, "/dev/", 5) == 0)
diff --git
a/meta/recipes-extended/minicom/minicom/allow.to.disable.lockdev.patch
b/meta/recipes-extended/minicom/minicom/allow.to.disable.lockdev.patch
deleted file mode 100644
index 39dc5c0492..0000000000
--- a/meta/recipes-extended/minicom/minicom/allow.to.disable.lockdev.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-configure: Allow lockdev to be disabled
-
-When the pkgconfig dependencies may be present, it is useful to be
-able to explictly disable the lockdev dependency. This adds such an
-option.
-
-Signed-off-by: Martin Jansa <[email protected]>
-Signed-off-by: Richard Purdie <[email protected]>
-
-Upstream-Status: Submitted
[https://salsa.debian.org/minicom-team/minicom/-/merge_requests/14]
-
-Index: minicom-2.8/configure.ac
-===================================================================
---- minicom-2.8.orig/configure.ac
-+++ minicom-2.8/configure.ac
-@@ -43,7 +43,13 @@ if test "x$enable_socket" = xyes; then
- fi
-
- PKG_PROG_PKG_CONFIG
--if test -n "$PKG_CONFIG"; then
-+
-+AC_ARG_ENABLE([lockdev],
-+ AS_HELP_STRING([--enable-lockdev],
-+ [Enable lockdev support (def: enabled)]),
-+ [], [enable_lockdev="yes"])
-+
-+if test -n "$PKG_CONFIG" && test "x$enable_lockdev" = xyes; then
- PKG_CHECK_MODULES([LOCKDEV], [lockdev],
AC_DEFINE([HAVE_LOCKDEV],[1],[Define if you have lockdev]),[:])
- fi
-
diff --git a/meta/recipes-extended/minicom/minicom_2.8.bb
b/meta/recipes-extended/minicom/minicom_2.9.bb
similarity index 80%
rename from meta/recipes-extended/minicom/minicom_2.8.bb
rename to meta/recipes-extended/minicom/minicom_2.9.bb
index 2640c6b057..907d5c79c9 100644
--- a/meta/recipes-extended/minicom/minicom_2.8.bb
+++ b/meta/recipes-extended/minicom/minicom_2.9.bb
@@ -7,12 +7,9 @@ LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://COPYING;md5=420477abc567404debca0a2a1cb6b645 \
file://src/minicom.h;beginline=1;endline=12;md5=a58838cb709f0db517f4e42730c49e81"
-SRC_URI = "${DEBIAN_MIRROR}/main/m/${BPN}/${BPN}_${PV}.orig.tar.bz2 \
- file://allow.to.disable.lockdev.patch \
- file://0001-fix-minicom-h-v-return-value-is-not-0.patch \
-"
+SRC_URI = "${DEBIAN_MIRROR}/main/m/${BPN}/${BPN}_${PV}.orig.tar.bz2"
-SRC_URI[sha256sum] =
"38cea30913a20349326ff3f1763ee1512b7b41601c24f065f365e18e9db0beba"
+SRC_URI[sha256sum] =
"9efbb6458140e5a0de445613f0e76bcf12cbf7a9892b2f53e075c2e7beaba86c"
PACKAGECONFIG ??= ""
PACKAGECONFIG[lockdev] = "--enable-lockdev,--disable-lockdev,lockdev"
--
2.42.0
packages/core2-64-poky-linux/minicom: PV changed from "2.8" to "2.9" packages/core2-64-poky-linux/minicom: SRC_URI changed from "http://ftp.debian.org/debian/pool/main/m/minicom/minicom_2.8.orig.tar.bz2 file://allow.to.disable.lockdev.patch file://0001-fix-minicom-h-v-return-value-is-not-0.patch" to "http://ftp.debian.org/debian/pool/main/m/minicom/minicom_2.9.orig.tar.bz2"; packages/core2-64-poky-linux/minicom: PKGV changed from 2.8 [default] to 2.9 [default] packages/core2-64-poky-linux/minicom/minicom-dbg: PKGSIZE changed from 578816 to 584688 (+1%) packages/core2-64-poky-linux/minicom/minicom-dbg: PV changed from "2.8" to "2.9" packages/core2-64-poky-linux/minicom/minicom-dbg: PKGV changed from 2.8 [default] to 2.9 [default] packages/core2-64-poky-linux/minicom/minicom-dev: PV changed from "2.8" to "2.9" packages/core2-64-poky-linux/minicom/minicom-dev: PKGV changed from 2.8 [default] to 2.9 [default] packages/core2-64-poky-linux/minicom/minicom-doc: PKGSIZE changed from 45114 to 45118 (+0%) packages/core2-64-poky-linux/minicom/minicom-doc: PV changed from "2.8" to "2.9" packages/core2-64-poky-linux/minicom/minicom-doc: PKGV changed from 2.8 [default] to 2.9 [default] packages/core2-64-poky-linux/minicom/minicom-locale: PV changed from "2.8" to "2.9" packages/core2-64-poky-linux/minicom/minicom-locale: PKGV changed from 2.8 [default] to 2.9 [default] packages/core2-64-poky-linux/minicom/minicom-src: PKGSIZE changed from 432221 to 438718 (+2%) packages/core2-64-poky-linux/minicom/minicom-src: PV changed from "2.8" to "2.9" packages/core2-64-poky-linux/minicom/minicom-src: PKGV changed from 2.8 [default] to 2.9 [default] packages/core2-64-poky-linux/minicom/minicom-staticdev: PV changed from "2.8" to "2.9" packages/core2-64-poky-linux/minicom/minicom-staticdev: PKGV changed from 2.8 [default] to 2.9 [default] packages/core2-64-poky-linux/minicom/minicom: PKGSIZE changed from 257842 to 271570 (+5%) packages/core2-64-poky-linux/minicom/minicom: PV changed from "2.8" to "2.9" packages/core2-64-poky-linux/minicom/minicom: PKGV changed from 2.8 [default] to 2.9 [default]
0001-minicom-upgrade-2.8-2.9.patch
Description: Binary data
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196518): https://lists.openembedded.org/g/openembedded-core/message/196518 Mute This Topic: https://lists.openembedded.org/mt/104675374/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
