public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michal Schorm <mschorm@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/PyGreSQL] rawhide: [bugfix] Add missing description to python3-pygresql subpackage
Date: Wed, 01 Jul 2026 14:38:14 GMT [thread overview]
Message-ID: <178291669454.1.9259124110713333812.rpms-PyGreSQL-a773473bfe45@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/PyGreSQL
Branch : rawhide
Commit : a773473bfe45bc546a8d86d6ba60a536eb5713ea
Author : Michal Schorm <mschorm@redhat.com>
Date : 2026-07-01T12:30:17+02:00
Stats : +1/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/PyGreSQL/c/a773473bfe45bc546a8d86d6ba60a536eb5713ea?branch=rawhide
Log:
[bugfix] Add missing description to python3-pygresql subpackage
The %_description macro was defined (line 26) and used for the SRPM's
%description, but the python3-pygresql subpackage's %description
section was left empty. This caused rpmlint error no-description-tag
on the built RPM, confirmed by inspecting the COPR build output.
The %_description pattern is the standard way to share a single
description across multiple subpackages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_common_descriptions
The bug was introduced in commit b5c8782 (6.1.0 rebase) which
restructured the spec to use pyproject macros but did not carry over
the description reference to the subpackage.
Co-Authored-By: Claude AI <noreply@anthropic.com>
---
diff --git a/PyGreSQL.spec b/PyGreSQL.spec
index 756a5ae..1ebaf26 100644
--- a/PyGreSQL.spec
+++ b/PyGreSQL.spec
@@ -42,7 +42,7 @@ Provides: python3-PyGreSQL = %{uversion}-%{release}
Provides: python3-PyGreSQL%{?_isa} = %{uversion}-%{release}
Obsoletes: python3-PyGreSQL < %{uversion}-%{release}
-%description -n python3-pygresql
+%description -n python3-pygresql %_description
%prep
reply other threads:[~2026-07-01 14:38 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=178291669454.1.9259124110713333812.rpms-PyGreSQL-a773473bfe45@fedoraproject.org \
--to=mschorm@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