public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Python Maint <python-maint@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-specfile] f44: Rebuilt for Python 3.15
Date: Mon, 20 Jul 2026 19:17:24 GMT	[thread overview]
Message-ID: <178457504491.1.7117371797226674538.rpms-python-specfile-fdd73a4d0dd9@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-specfile
Branch : f44
Commit : fdd73a4d0dd9af90d003896ce9a26b21414bdf4f
Author : Python Maint <python-maint@redhat.com>
Date   : 2026-06-05T00:33:21+02:00
Stats  : +5/-2 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/python-specfile/c/fdd73a4d0dd9af90d003896ce9a26b21414bdf4f?branch=f44

Log:
Rebuilt for Python 3.15

---
diff --git a/python-specfile.spec b/python-specfile.spec
index 7f56f6c..ce26a91 100644
--- a/python-specfile.spec
+++ b/python-specfile.spec
@@ -16,7 +16,7 @@ in a minimal diff.}
 
 Name:           python-specfile
 Version:        %{package_version}
-Release:        1%{?dist}
+Release:        2%{?dist}
 
 Summary:        A library for parsing and manipulating RPM spec files
 License:        MIT
@@ -81,12 +81,15 @@ sed -i 's/setuptools_scm\[toml\]>=7/setuptools_scm[toml]/' pyproject.toml
 
 
 %changelog
+* Thu Jun 04 2026 Python Maint <python-maint@redhat.com> - 0.41.0-2
+- Rebuilt for Python 3.15
+
 * Fri May 29 2026 Packit <hello@packit.dev> - 0.41.0-1
 - Fixed an issue where the value of a tag could have been incorrectly expanded if the spec file contained a macro definition shadowing the tag name, e.g.:
 ```
 %%global release 12
 %%global release_string %%{release}%%{?dist}
-Release: %%{release_string}
+Release: %%{release_string}.1
 ```
 In this case, with `dist` being `.fc44`, `Specfile.expanded_release` returned `12.fc44.fc44` instead of `12.fc44`. (#539)
 

                 reply	other threads:[~2026-07-20 19:17 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=178457504491.1.7117371797226674538.rpms-python-specfile-fdd73a4d0dd9@fedoraproject.org \
    --to=python-maint@redhat.com \
    --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