public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/python3-openid] epel10: Update to 3.1.0, fix FTBFS (#1556287)
Date: Fri, 30 Oct 2026 21:38:25 GMT	[thread overview]
Message-ID: <179339630524.1.6094381077105128076.rpms-python3-openid-6338a6e5c43f@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python3-openid
            Branch : epel10
            Commit : 6338a6e5c43f258bc862ab805493cc7da6872dfa
            Author : Miro Hrončok <miro@hroncok.cz>
            Date   : 2018-06-08T21:21:30+02:00
            Stats  : +11/-6 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/python3-openid/c/6338a6e5c43f258bc862ab805493cc7da6872dfa?branch=epel10

            Log:
            Update to 3.1.0, fix FTBFS (#1556287)

- Use nonenv shebangs

---
diff --git a/.gitignore b/.gitignore
index 6b44282..c3adb4e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@
 /python3-openid-3.0.6.tar.gz
 /python3-openid-3.0.9.tar.gz
 /python3-openid-3.0.10.tar.gz
+/python3-openid-3.1.0.tar.gz

diff --git a/python3-openid.spec b/python3-openid.spec
index b6692d2..e52378a 100644
--- a/python3-openid.spec
+++ b/python3-openid.spec
@@ -1,11 +1,11 @@
 Name:           python3-openid
-Version:        3.0.10
-Release:        4%{?dist}
+Version:        3.1.0
+Release:        1%{?dist}
 Summary:        Python 3 port of the python-openid library
 Group:          Development/Libraries
 License:        ASL 2.0
 URL:            https://github.com/necaris/python3-openid
-Source0:        https://pypi.python.org/packages/f3/fb/4bd7119a01f663d39116dcad1ff65f4044de430bd4688135413152f91809/python3-openid-3.0.10.tar.gz
+Source0:        https://files.pythonhosted.org/packages/source/p/%{name}/%{name}-%{version}.tar.gz
 
 BuildArch:      noarch
 
@@ -29,7 +29,7 @@ including cleanups and updates to the code in general.
 
 # replace env python shebangs with env python3
 grep -Erl '^#!/usr/bin/env python$' | xargs \
-sed -i -r '1 s|^#!/usr/bin/env python$|#!/usr/bin/env python3|g'
+sed -i -r '1 s|^#!/usr/bin/env python$|#!%{__python3}|g'
 
 
 %build
@@ -44,7 +44,7 @@ find %{buildroot} -name "*.po" | xargs rm -f
 
 
 %check
-LC_ALL=en_US.UTF-8 %{__python3} admin/runtests
+%{__python3} -m unittest openid.test.test_suite
 
 
 %files
@@ -81,6 +81,10 @@ LC_ALL=en_US.UTF-8 %{__python3} admin/runtests
 
 
 %changelog
+* Fri Jun 08 2018 Miro Hrončok <mhroncok@redhat.com> - 3.1.0-1
+- Update to 3.1.0, fix FTBFS (#1556287)
+- Use nonenv shebangs
+
 * Fri Feb 09 2018 Fedora Release Engineering <releng@fedoraproject.org> - 3.0.10-4
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
 

diff --git a/sources b/sources
index 589d780..6e48192 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (python3-openid-3.0.10.tar.gz) = 679aa0fba40794e85a806f18ca904e9e4336c8fe1c1c558d4f0b66c14cf1959436c7d9225b6bfbaefd1ddb89d645901308fd30d57841ce7cd3c90c24d41c79b3
+SHA512 (python3-openid-3.1.0.tar.gz) = 9c96efd16191ddb6ddb12c4885a2cce523244d04e70f9418144d0124ef142fd7b6578cd2a01e949995d7dedf0b96cbb3b17d1d3a29db5da8934f7fa875ad8e9c

                 reply	other threads:[~2026-10-30 21:38 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=179339630524.1.6094381077105128076.rpms-python3-openid-6338a6e5c43f@fedoraproject.org \
    --to=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