public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Packit <hello@packit.dev>
To: git-commits@fedoraproject.org
Subject: [rpms/python-ogr] epel10: Update to 0.62.3 upstream release
Date: Fri, 31 Jul 2026 13:28:07 GMT	[thread overview]
Message-ID: <178550448770.1.3190128861399846147.rpms-python-ogr-33ed65d97639@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-ogr
            Branch : epel10
            Commit : 33ed65d97639a7e02d904c2a4204b8d8b85c7472
            Author : Packit <hello@packit.dev>
            Date   : 2026-07-31T11:05:55+00:00
            Stats  : +7/-3 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-ogr/c/33ed65d97639a7e02d904c2a4204b8d8b85c7472?branch=epel10

            Log:
            Update to 0.62.3 upstream release

- Resolves: rhbz#2509741

Upstream tag: 0.62.3
Upstream commit: d35040ff

Commit authored by Packit automation (https://packit.dev/)

---
diff --git a/README.packit b/README.packit
index 173195e..faed60d 100644
--- a/README.packit
+++ b/README.packit
@@ -1,3 +1,3 @@
 This repository is maintained by packit.
 https://packit.dev/
-The file was generated using packit 1.16.1.post1.dev2+gf84fe2d5b.
+The file was generated using packit 1.16.2.post1.dev4+gb52dcef6b.

diff --git a/python-ogr.spec b/python-ogr.spec
index bc48f94..e550e50 100644
--- a/python-ogr.spec
+++ b/python-ogr.spec
@@ -1,5 +1,5 @@
 Name:           python-ogr
-Version:        0.61.2
+Version:        0.62.3
 Release:        1%{?dist}
 Summary:        One API for multiple git forges
 
@@ -47,6 +47,10 @@ One Git library to Rule!
 
 
 %changelog
+* Fri Jul 31 2026 Packit <hello@packit.dev> - 0.62.3-1
+- Emoji reactions on GitLab comments now work reliably
+- Resolves: rhbz#2509741
+
 * Mon Jul 20 2026 Packit <hello@packit.dev> - 0.61.2-1
 - The `ogr` library now correctly handles the Forgejo 'error' commit flag, resolving an issue that previously caused it to fail during internal mapping. (#991)
 - Resolves: rhbz#2502826

diff --git a/sources b/sources
index b5e9d8c..ba16369 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (ogr-0.61.2.tar.gz) = 646aed139f9dbec3c1fa3128a58206f2525388d827f789814f4379d3887b69d81bbd88aef401e791b103969b80361fa79e23ea1ca2f0907d9e8689bf0244525d
+SHA512 (ogr-0.62.3.tar.gz) = 338126c1ff247bc589e45afd1242d1afa333b8d92408d6d77730a9fd96ac9ab601628c1465564ac11f8345252f07264de1c5af913b552c3e8dbf18891d77dfa6

                 reply	other threads:[~2026-07-31 13:28 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=178550448770.1.3190128861399846147.rpms-python-ogr-33ed65d97639@fedoraproject.org \
    --to=hello@packit.dev \
    --cc=git-commits@fedoraproject.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