public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/snakemake] rawhide: Fix wrong man page title
Date: Mon, 01 Jun 2026 10:29:52 GMT	[thread overview]
Message-ID: <178030979258.1.17756819726966439093.rpms-snakemake-1f275001555b@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/snakemake
Branch : rawhide
Commit : 1f275001555b7f33827132b35c150206256965dc
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-06-01T11:14:40+01:00
Stats  : +4/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/snakemake/c/1f275001555b7f33827132b35c150206256965dc?branch=rawhide

Log:
Fix wrong man page title

---
diff --git a/snakemake.spec b/snakemake.spec
index ca92d27..deb64e5 100644
--- a/snakemake.spec
+++ b/snakemake.spec
@@ -49,6 +49,9 @@ Name:           snakemake
 Version:        9.21.0
 Release:        %autorelease
 Summary:        Workflow management system to create reproducible and scalable data analyses
+# The summary macro is overwritten by extras metapackages, but we want to use
+# the base package’s summary text in the man page.
+%global base_summary %{summary}
 
 # The primary license for Snakemake is MIT; web assets contribute a variety of
 # other licenses.
@@ -488,7 +491,7 @@ sed --regexp-extended --in-place \
 install --directory %{buildroot}%{_mandir}/man1
 PATH="${PATH-}:%{buildroot}%{_bindir}" \
     PYTHONPATH='%{buildroot}%{python3_sitelib}' \
-    help2man --no-info --name='%{summary}' snakemake \
+    help2man --no-info --name='%{base_summary}' snakemake \
     > %{buildroot}%{_mandir}/man1/snakemake.1
 
 # Install nano syntax highlighting

                 reply	other threads:[~2026-06-01 10:29 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=178030979258.1.17756819726966439093.rpms-snakemake-1f275001555b@fedoraproject.org \
    --to=code@musicinmybrain.net \
    --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