public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Kevin Fenzi <kevin@scrye.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-translationstring] epel10: Upgrade to 1.4
Date: Wed, 08 Jul 2026 22:59:58 GMT	[thread overview]
Message-ID: <178355159868.1.13584613230416332440.rpms-python-translationstring-c2d503238fd3@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-translationstring
            Branch : epel10
            Commit : c2d503238fd3e01e4799e944ab1c8502132d0620
            Author : Kevin Fenzi <kevin@scrye.com>
            Date   : 2024-11-24T15:40:58-08:00
            Stats  : +18/-13 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-translationstring/c/c2d503238fd3e01e4799e944ab1c8502132d0620?branch=epel10

            Log:
            Upgrade to 1.4

Fix FTBFS. Fixes rhbz#2319730
Upgrade to 1.4
Fix FTBFS. Fixes rhbz#2319730

---
diff --git a/.gitignore b/.gitignore
index cb58be9..02db583 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
 /translationstring-0.3.tar.gz
 /translationstring-1.1.tar.gz
 /translationstring-1.3.tar.gz
+/translationstring-1.4.tar.gz

diff --git a/python-translationstring.spec b/python-translationstring.spec
index f04525c..124750c 100644
--- a/python-translationstring.spec
+++ b/python-translationstring.spec
@@ -1,8 +1,8 @@
 %global modname translationstring
 
 Name:           python-%{modname}
-Version:        1.3
-Release:        30%{?dist}
+Version:        1.4
+Release:        1%{?dist}
 Summary:        Library used for internationalization (i18n) duties related to translation
 
 # Automatically converted from old format: BSD - review is highly recommended.
@@ -28,31 +28,35 @@ work best when provided with an instance of the babel.support.Translations class
 Summary:        %{summary}
 %{?python_provide:%python_provide python3-%{modname}}
 BuildRequires:  python3-devel
-BuildRequires:  python3-setuptools
 
 %description -n python3-%{modname} %{_description}
 
-Python 3 version.
-
 %prep
-%setup -q -n %{modname}-%{version}
+%autosetup -p1 -n %{modname}-%{version}
+
+%generate_buildrequires
+%pyproject_buildrequires -t
 
 %build
-%py3_build
+%pyproject_wheel
 
 %install
-%py3_install
+%pyproject_install
+
+%pyproject_save_files -l translationstring
 
 %check
-%{__python3} setup.py test
+%{py3_test_envvars} %{python3} -m unittest
 
-%files -n python3-%{modname}
+%files -n python3-%{modname} -f %{pyproject_files}
 %license LICENSE.txt
 %doc README.rst changes.rst
-%{python3_sitelib}/%{modname}/
-%{python3_sitelib}/%{modname}-*.egg-info/
 
 %changelog
+* Sun Nov 24 2024 Kevin Fenzi <kevin@scrye.com> - 1.4-1
+- Upgrade to 1.4
+- Fix FTBFS. Fixes rhbz#2319730
+
 * Wed Sep 04 2024 Miroslav Suchý <msuchy@redhat.com> - 1.3-30
 - convert license to SPDX
 

diff --git a/sources b/sources
index 58c0f0c..6e0f4e8 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-086ee66d378b0f5893fadac776f2d9fe  translationstring-1.3.tar.gz
+SHA512 (translationstring-1.4.tar.gz) = f470967e04701f7d5c27acefcd3c058d0b9c600115e2e33212d6855ef0eb932d025b8af0d2017202cf6e1893ef8023edd60453de1c45e495c88846627af200db

                 reply	other threads:[~2026-07-08 22:59 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=178355159868.1.13584613230416332440.rpms-python-translationstring-c2d503238fd3@fedoraproject.org \
    --to=kevin@scrye.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