public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Javier Pena <jpena@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-futurist] noevent: Update to upstream 0.11.0
Date: Sun, 07 Jun 2026 15:59:58 GMT [thread overview]
Message-ID: <178084799829.1.17026856022988483459.rpms-python-futurist-9e0dd93ddc9b@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-futurist
Branch : noevent
Commit : 9e0dd93ddc9b6d147a6b392fb68f3b2a89603665
Author : Javier Pena <jpena@redhat.com>
Date : 2016-02-10T10:21:04+01:00
Stats : +7/-3 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/python-futurist/c/9e0dd93ddc9b6d147a6b392fb68f3b2a89603665?branch=noevent
Log:
Update to upstream 0.11.0
---
diff --git a/.gitignore b/.gitignore
index 4162ec2..72eafa3 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
/futurist-0.4.0.tar.gz
/futurist-0.5.0.tar.gz
/futurist-0.9.0.tar.gz
+/futurist-0.11.0.tar.gz
diff --git a/python-futurist.spec b/python-futurist.spec
index 7e63feb..0654bc8 100644
--- a/python-futurist.spec
+++ b/python-futurist.spec
@@ -7,8 +7,8 @@
%global pypi_name futurist
Name: python-%{pypi_name}
-Version: 0.9.0
-Release: 2%{?dist}
+Version: 0.11.0
+Release: 1%{?dist}
Summary: Useful additions to futures, from the future
License: ASL 2.0
@@ -121,6 +121,9 @@ popd
%endif
%changelog
+* Wed Feb 10 2016 Javier Peña <jpena@redhat.com> - 0.11.0-1
+- Update to upstream 0.11.0
+
* Thu Feb 04 2016 Fedora Release Engineering <releng@fedoraproject.org> - 0.9.0-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
diff --git a/sources b/sources
index fba6878..e471ece 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-626016e1fdda93c0758ddf25eb1a6eec futurist-0.9.0.tar.gz
+6c637bb1d14aaf7c5a351106c7339339 futurist-0.11.0.tar.gz
reply other threads:[~2026-06-07 15: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=178084799829.1.17026856022988483459.rpms-python-futurist-9e0dd93ddc9b@fedoraproject.org \
--to=jpena@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