public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Carmen Bianca BAKKER <carmen@carmenbianca.eu>
To: git-commits@fedoraproject.org
Subject: [rpms/reuse] epel10: Bump to 1.1.1-2
Date: Wed, 19 Aug 2026 12:50:22 GMT	[thread overview]
Message-ID: <178714382211.1.14628258936904011560.rpms-reuse-0823610f920a@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/reuse
            Branch : epel10
            Commit : 0823610f920aee824193e067f4926d228c4e6d4f
            Author : Carmen Bianca BAKKER <carmen@carmenbianca.eu>
            Date   : 2023-02-06T10:21:35+01:00
            Stats  : +19/-13 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/reuse/c/0823610f920aee824193e067f4926d228c4e6d4f?branch=epel10

            Log:
            Bump to 1.1.1-2

Signed-off-by: Carmen Bianca BAKKER <carmen@carmenbianca.eu>

---
diff --git a/reuse.spec b/reuse.spec
index a5dc49a..bcbf391 100644
--- a/reuse.spec
+++ b/reuse.spec
@@ -1,9 +1,10 @@
 Name:           reuse
 Version:        1.1.1
-Release:        1%{?dist}
+Release:        2
 Summary:        A tool for compliance with the REUSE recommendations
 # The CC0-1.0 licence applies to json data files, not code.
-License:        Apache-2.0 AND CC0-1.0 AND GPL-3.0-or-later
+# CC-BY-SA-4.0 is applied to documentation.
+License:        Apache-2.0 AND CC0-1.0 AND CC-BY-SA-4.0 AND GPL-3.0-or-later
 Url:            https://github.com/fsfe/reuse-tool
 Source0:        %pypi_source
 # Build
@@ -12,8 +13,14 @@ BuildRequires:  gettext
 # Test
 BuildRequires:  git
 BuildRequires:  mercurial
-# This should be installed by Poetry...
-BuildRequires:  python3-pytest
+# These are development dependencies in the Poetry config, not build
+# dependencies.
+BuildRequires:  %{py3_dist pytest}
+BuildRequires:  %{py3_dist Sphinx}
+BuildRequires:  %{py3_dist sphinx_rtd_theme}
+BuildRequires:  %{py3_dist sphinx-autodoc-typehints}
+BuildRequires:  %{py3_dist sphinxcontrib-apidoc}
+BuildRequires:  %{py3_dist recommonmark}
 Recommends:     git
 Recommends:     mercurial
 BuildArch:      noarch
@@ -33,10 +40,10 @@ generates a project's bill of materials.
 
 %build
 %pyproject_wheel
-# pushd docs
-# PBR_VERSION=%{version} sphinx-build-%{python3_version} . html
-# rm -rf html/.{doctrees,buildinfo}
-# popd
+pushd docs
+PBR_VERSION=%{version} sphinx-build-%{python3_version} . html
+rm -rf html/.{doctrees,buildinfo}
+popd
 
 %install
 %pyproject_install
@@ -48,15 +55,14 @@ generates a project's bill of materials.
 
 %files -n reuse -f %{pyproject_files}
 %license LICENSES/*.txt
-%doc README.md CHANGELOG.md
-# docs/html/
+%doc README.md CHANGELOG.md docs/html/
 %{_bindir}/reuse
 
 %changelog
-* Sun Feb 05 2023 Carmen Bianca BAKKER <carmenbianca@fedoraproject.org>
-- new version
+* Mon Feb 06 2023 Carmen Bianca BAKKER <carmenbianca@fedoraproject.org> - 1.1.1-2
+- Also package documentation files again.
 
-* Fri Feb 03 2023 Carmen Bianca BAKKER <carmenbianca@fedoraproject.org> - 1.1.0-1
+* Mon Feb 06 2023 Carmen Bianca BAKKER <carmenbianca@fedoraproject.org> - 1.1.1-1
 - New version.
 - Adapt package to poetry build system.
 

                 reply	other threads:[~2026-08-19 12:50 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=178714382211.1.14628258936904011560.rpms-reuse-0823610f920a@fedoraproject.org \
    --to=carmen@carmenbianca.eu \
    --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