public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowi@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/graphviz] rawhide: Drop qpdf post-processing
Date: Thu, 13 Aug 2026 20:24:58 GMT	[thread overview]
Message-ID: <178665269820.1.7050070806800402124.rpms-graphviz-3b538615d24c@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/graphviz
            Branch : rawhide
            Commit : 3b538615d24c06fd70de94f53de844c1a4d3d476
            Author : Yaakov Selkowitz <yselkowi@redhat.com>
            Date   : 2026-08-13T15:38:09-04:00
            Stats  : +4/-15 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/graphviz/c/3b538615d24c06fd70de94f53de844c1a4d3d476?branch=rawhide

            Log:
            Drop qpdf post-processing

RHBZ#881173 was dealing with rpmdiff issues.  The -doc subpackages
were supposed to be noarch, meaning they had to be identical regardless
of the build architecture, but build-specific metadata broke that.

commit cf06abaee546e9ff78c522ff6e7c6fcddd412a28 both made the -doc
subpackage archful and (attempted to?) strip the differing metadata.
Only one of those actions should have been necessary.  Making it archful
means any build-time differences are not compared, therefore there is no
need to strip the metadata.

---
diff --git a/graphviz.spec b/graphviz.spec
index 80bb8d6..942e19c 100644
--- a/graphviz.spec
+++ b/graphviz.spec
@@ -108,7 +108,7 @@
 Name:			graphviz
 Summary:		Graph Visualization Tools
 Version:		15.1.1
-Release:		1%{?dist}
+Release:		2%{?dist}
 License:		epl-1.0 AND cpl-1.0 AND bsd-3-clause AND mit AND gpl-3.0-or-later WITH bison-exception-2.2 AND apache-1.1 AND lgpl-2.0-or-later WITH libtool-exception AND smlnj AND hpnd-uc
 URL:			http://www.graphviz.org/
 #Source0:		https://gitlab.com/%%{name}/%%{name}/-/archive/%%{version}/%%{name}-%%{version}.tar.bz2
@@ -165,7 +165,6 @@ BuildRequires:		swig >= 1.3.33
 BuildRequires:		automake
 BuildRequires:		autoconf
 BuildRequires:		libtool
-BuildRequires:		qpdf
 # Temporary workaound for perl(Carp) not pulled
 BuildRequires:		perl-Carp
 %if %{PHP}
@@ -530,19 +529,6 @@ find %{buildroot}%{_docdir}/%{name}/demo -type f -name "*.py" -exec mv {} {}.dem
 # Remove dot_builtins, on demand loading should be sufficient
 rm -f %{buildroot}%{_bindir}/dot_builtins
 
-# Remove metadata from generated PDFs
-pushd %{buildroot}%{_docdir}/%{name}
-for f in prune gvgen.1 gc.1 dot.1 cluster.1
-do
-  if [ -f $f.pdf ]
-  then
-# ugly, but there is probably no better solution
-    qpdf --empty --static-id --pages $f.pdf -- $f.pdf.$$
-    mv -f $f.pdf.$$ $f.pdf
-  fi
-done
-popd
-
 %if %{with python2}
 install -pD tclpkg/gv/.libs/libgv_python2.so %{buildroot}%{python2_sitearch}/_gv.so
 install -p tclpkg/gv/gv.py %{buildroot}%{python2_sitearch}/gv.py
@@ -747,6 +733,9 @@ php --no-php-ini \
 %endif
 
 %changelog
+* Thu Aug 13 2026 Yaakov Selkowitz <yselkowi@redhat.com> - 15.1.1-2
+- Drop qpdf post-processing
+
 * Thu Aug 06 2026 Jaroslav Škarvada <jskarvad@redhat.com> - 15.1.1-1
 - New version
   Resolves: rhbz#2511486

                 reply	other threads:[~2026-08-13 20:24 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=178665269820.1.7050070806800402124.rpms-graphviz-3b538615d24c@fedoraproject.org \
    --to=yselkowi@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