Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: auh@moto-timo.dev
To: openembedded-devel@lists.openembedded.org
Subject: [AUH] python3-sentry-sdk: upgrading to 1.28.0 SUCCEEDED
Date: Wed, 12 Jul 2023 05:31:50 +0000 (UTC)	[thread overview]
Message-ID: <20230712053150.83A6FC001DF@smtp.lore.kernel.org> (raw)

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

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-sentry-sdk* to *1.28.0* has Succeeded.

Next steps:
    - apply the patch: git am 0001-python3-sentry-sdk-upgrade-1.26.0-1.28.0.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 8c337106c6ca4369af7172ceeca9e54c33781ed4 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@moto-timo.dev>
Date: Tue, 11 Jul 2023 22:40:41 -0500
Subject: [PATCH] python3-sentry-sdk: upgrade 1.26.0 -> 1.28.0

---
 ...ython3-sentry-sdk_1.26.0.bb => python3-sentry-sdk_1.28.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-python/recipes-devtools/python/{python3-sentry-sdk_1.26.0.bb => python3-sentry-sdk_1.28.0.bb} (86%)

diff --git a/meta-python/recipes-devtools/python/python3-sentry-sdk_1.26.0.bb b/meta-python/recipes-devtools/python/python3-sentry-sdk_1.28.0.bb
similarity index 86%
rename from meta-python/recipes-devtools/python/python3-sentry-sdk_1.26.0.bb
rename to meta-python/recipes-devtools/python/python3-sentry-sdk_1.28.0.bb
index 697f102a2..6ddfa62b9 100644
--- a/meta-python/recipes-devtools/python/python3-sentry-sdk_1.26.0.bb
+++ b/meta-python/recipes-devtools/python/python3-sentry-sdk_1.28.0.bb
@@ -15,7 +15,7 @@ RDEPENDS:${PN} += "\
 	${PYTHON_PN}-datetime \
 "
 
-SRC_URI[sha256sum] = "760e4fb6d01c994110507133e08ecd4bdf4d75ee4be77f296a3579796cf73134"
+SRC_URI[sha256sum] = "2281ba98011cfa9bc9bb15c1074b6dd9f7fdfce94033cd25b50f18f078ffed4c"
 
 PYPI_PACKAGE = "sentry-sdk"
 
-- 
2.25.1


[-- Attachment #2: 0001-python3-sentry-sdk-upgrade-1.26.0-1.28.0.patch --]
[-- Type: text/x-diff, Size: 1237 bytes --]

From 8c337106c6ca4369af7172ceeca9e54c33781ed4 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@moto-timo.dev>
Date: Tue, 11 Jul 2023 22:40:41 -0500
Subject: [PATCH] python3-sentry-sdk: upgrade 1.26.0 -> 1.28.0

---
 ...ython3-sentry-sdk_1.26.0.bb => python3-sentry-sdk_1.28.0.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-python/recipes-devtools/python/{python3-sentry-sdk_1.26.0.bb => python3-sentry-sdk_1.28.0.bb} (86%)

diff --git a/meta-python/recipes-devtools/python/python3-sentry-sdk_1.26.0.bb b/meta-python/recipes-devtools/python/python3-sentry-sdk_1.28.0.bb
similarity index 86%
rename from meta-python/recipes-devtools/python/python3-sentry-sdk_1.26.0.bb
rename to meta-python/recipes-devtools/python/python3-sentry-sdk_1.28.0.bb
index 697f102a2..6ddfa62b9 100644
--- a/meta-python/recipes-devtools/python/python3-sentry-sdk_1.26.0.bb
+++ b/meta-python/recipes-devtools/python/python3-sentry-sdk_1.28.0.bb
@@ -15,7 +15,7 @@ RDEPENDS:${PN} += "\
 	${PYTHON_PN}-datetime \
 "
 
-SRC_URI[sha256sum] = "760e4fb6d01c994110507133e08ecd4bdf4d75ee4be77f296a3579796cf73134"
+SRC_URI[sha256sum] = "2281ba98011cfa9bc9bb15c1074b6dd9f7fdfce94033cd25b50f18f078ffed4c"
 
 PYPI_PACKAGE = "sentry-sdk"
 
-- 
2.25.1


                 reply	other threads:[~2023-07-12  5:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230712053150.83A6FC001DF@smtp.lore.kernel.org \
    --to=auh@moto-timo.dev \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox