public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Alfredo Moralejo <amoralej@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-barbicanclient] epel10: Switch to sphinx-build to create doc
Date: Sun, 30 Aug 2026 14:20:47 GMT [thread overview]
Message-ID: <178809964715.1.12428612327875784798.rpms-python-barbicanclient-6bbb46165cde@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-barbicanclient
Branch : epel10
Commit : 6bbb46165cde806d6960876cbcedc49405775346
Author : Alfredo Moralejo <amoralej@redhat.com>
Date : 2023-08-16T10:56:43+02:00
Stats : +5/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-barbicanclient/c/6bbb46165cde806d6960876cbcedc49405775346?branch=epel10
Log:
Switch to sphinx-build to create doc
Sphinx 7 has removed the setuptools integration (see: https://github.com/sphinx-doc/sphinx/pull/11363).
---
diff --git a/python-barbicanclient.spec b/python-barbicanclient.spec
index 92dca43..a4b0e21 100644
--- a/python-barbicanclient.spec
+++ b/python-barbicanclient.spec
@@ -13,7 +13,7 @@ a command-line script (barbican).
Name: python-barbicanclient
Version: 5.5.0
-Release: 3%{?dist}
+Release: 4%{?dist}
Summary: Client Library for OpenStack Barbican Key Management API
License: ASL 2.0
@@ -87,7 +87,7 @@ rm -rf {test-,}requirements.txt
%if 0%{?with_doc}
# doc
-%{__python3} setup.py build_sphinx -b html
+sphinx-build -b html doc/source doc/build/html
# Fix hidden-file-or-dir warnings
rm -fr doc/build/html/.buildinfo
%endif
@@ -111,6 +111,9 @@ ln -s ./barbican %{buildroot}%{_bindir}/barbican-3
%endif
%changelog
+* Wed Aut 16 2023 Alfredo Moralejo <amoralej@gmail.com> - 5.5.0-4
+- Switch to sphinx-build to create the documentation
+
* Fri Jul 21 2023 Fedora Release Engineering <releng@fedoraproject.org> - 5.5.0-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
reply other threads:[~2026-08-30 14:20 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=178809964715.1.12428612327875784798.rpms-python-barbicanclient-6bbb46165cde@fedoraproject.org \
--to=amoralej@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