public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Karolina Surma <ksurma@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-py] pr7: Remove documentation from the package
Date: Sat, 01 Aug 2026 11:43:46 GMT	[thread overview]
Message-ID: <178558462648.1.11102334249143215202.rpms-python-py-1bd2cd131773@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-py
            Branch : pr7
            Commit : 1bd2cd1317734bc24f72b11ad40bbfe7aecd8ce5
            Author : Karolina Surma <ksurma@redhat.com>
            Date   : 2022-02-15T17:06:26+01:00
            Stats  : +5/-14 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-py/c/1bd2cd1317734bc24f72b11ad40bbfe7aecd8ce5?branch=pr7

            Log:
            Remove documentation from the package

Docs have started to emit a lot of warnings with Sphinx 4.x,
but with Sphinx 4.4.x they're unable to build at all.
Upstream was notified of this issue in https://github.com/pytest-dev/py/issues/272
and stated that library is in maintenance mode only, receving only security fixes.
Regarding this context it seems better to just stop shipping docs rather
than patching the library downstream.

---
diff --git a/python-py.spec b/python-py.spec
index 4cb7852..08fc3d0 100644
--- a/python-py.spec
+++ b/python-py.spec
@@ -1,6 +1,5 @@
 # we have a circular (build) dependency with the (new) pytest package
-# when generating the docs or running the testsuite
-%bcond_without docs
+# when running the testsuite
 # the testsuite is currently not compatible with pytest 3, see
 # https://github.com/pytest-dev/py/issues/104
 %if 0%{?fedora} || 0%{?rhel} > 7
@@ -16,7 +15,7 @@
 
 Name:           python-%{srcname}
 Version:        1.11.0
-Release:        2%{?dist}
+Release:        3%{?dist}
 Summary:        Library with cross-python path, ini-parsing, io, code, log facilities
 License:        MIT and Public Domain
 #               main package: MIT, except: doc/style.css: Public Domain
@@ -45,10 +44,6 @@ Summary:        Library with cross-python path, ini-parsing, io, code, log facil
 BuildRequires:  python3-devel
 BuildRequires:  python3-setuptools
 BuildRequires:  python3-setuptools_scm
-%if %{with docs}
-BuildRequires: make
-BuildRequires:  %{_bindir}/sphinx-build
-%endif # with_docs
 %if %{with tests}
 BuildRequires:  python3-pytest >= %{pytest_version_lb}, python3-pytest < %{pytest_version_ub}
 %endif # with tests
@@ -81,10 +76,6 @@ find . \
 
 %build
 %py3_build
-%if %{with docs}
-make -C doc html PYTHONPATH=$(pwd)
-rm -rf doc/_build/html/.buildinfo
-%endif # with docs
 
 
 %install
@@ -108,14 +99,14 @@ py.test-%{python3_version} -r s -k"-TestWCSvnCommandPath" testing
 %doc CHANGELOG.rst
 %doc README.rst
 %license LICENSE
-%if %{with docs}
-%doc doc/_build/html
-%endif # with_docs
 %{python3_sitelib}/py-*.egg-info/
 %{python3_sitelib}/py/
 
 
 %changelog
+* Tue Feb 15 2022 Karolina Surma <ksurma@redhat.com> - 1.11.0-3
+- Remove documentation from the package
+
 * Fri Jan 21 2022 Fedora Release Engineering <releng@fedoraproject.org> - 1.11.0-2
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
 

                 reply	other threads:[~2026-08-01 11:43 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=178558462648.1.11102334249143215202.rpms-python-py-1bd2cd131773@fedoraproject.org \
    --to=ksurma@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