public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jens Petersen <petersen@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/dnf-repo] epel10.2: refresh to cabal-rpm-2.3.2
Date: Wed, 24 Jun 2026 07:09:35 GMT [thread overview]
Message-ID: <178228497568.1.16606657190657131728.rpms-dnf-repo-6ed244613f5f@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/dnf-repo
Branch : epel10.2
Commit : 6ed244613f5fbb69cfaaef1e8ad1e05f4cc913dd
Author : Jens Petersen <petersen@redhat.com>
Date : 2026-01-26T21:16:11+08:00
Stats : +8/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/dnf-repo/c/6ed244613f5fbb69cfaaef1e8ad1e05f4cc913dd?branch=epel10.2
Log:
refresh to cabal-rpm-2.3.2
---
diff --git a/dnf-repo.spec b/dnf-repo.spec
index 2902ac7..b63b0ea 100644
--- a/dnf-repo.spec
+++ b/dnf-repo.spec
@@ -1,4 +1,4 @@
-# generated by cabal-rpm-2.3.0
+# generated by cabal-rpm-2.3.2
# https://docs.fedoraproject.org/en-US/packaging-guidelines/Haskell/
# fails: dnf-repo: /etc/yum.repos.d not found!
@@ -16,8 +16,8 @@ Source0: https://hackage.haskell.org/package/%{name}-%{version}/%{name}-%
# End cabal-rpm sources
# Begin cabal-rpm deps:
-BuildRequires: ghc-Cabal-devel
BuildRequires: ghc-rpm-macros
+BuildRequires: ghc-Cabal-devel
BuildRequires: ghc-Glob-devel
BuildRequires: ghc-base-devel
BuildRequires: ghc-curl-devel
@@ -58,7 +58,11 @@ for a dnf invocation.
set noclobber
mkdir -p %{buildroot}%{bash_completions_dir}
+mkdir -p %{buildroot}%{fish_completions_dir}
+mkdir -p %{buildroot}%{zsh_completions_dir}
%{buildroot}%{_bindir}/%{name} --bash-completion-script %{name} | sed s/filenames/default/ > %{buildroot}%{bash_completions_dir}/%{name}
+%{buildroot}%{_bindir}/%{name} --fish-completion-script %{name} > %{buildroot}%{fish_completions_dir}/%{name}
+%{buildroot}%{_bindir}/%{name} --zsh-completion-script %{name} | sed s/filenames/default/ > %{buildroot}%{zsh_completions_dir}/_%{name}
mkdir -p %{buildroot}%{_mandir}/man1/
help2man --no-info %{buildroot}%{_bindir}/%{name} > %{buildroot}%{_mandir}/man1/%{name}.1
@@ -79,6 +83,8 @@ PATH=%{buildroot}%{_bindir}:$PATH
%{_bindir}/%{name}
%{_datadir}/%{name}-%{version}
%{bash_completions_dir}/%{name}
+%{fish_completions_dir}/%{name}
+%{zsh_completions_dir}/_%{name}
%{_mandir}/man1/%{name}.1*
# End cabal-rpm files
reply other threads:[~2026-06-24 7:09 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=178228497568.1.16606657190657131728.rpms-dnf-repo-6ed244613f5f@fedoraproject.org \
--to=petersen@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