public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/ckermit] epel8: Add BR: perl (Fix F26FTBS).
Date: Fri, 18 Sep 2026 13:57:35 GMT	[thread overview]
Message-ID: <178973985590.1.6861308773125178252.rpms-ckermit-b3150ac38f4b@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/ckermit
Branch : epel8
Commit : b3150ac38f4ba2f7ffa6b98c880bdda8715bf29c
Author : Ralf Corsépius <corsepiu@fedoraproject.org>
Date   : 2017-02-16T11:16:26+01:00
Stats  : +6/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/ckermit/c/b3150ac38f4ba2f7ffa6b98c880bdda8715bf29c?branch=epel8

Log:
Add BR: perl (Fix F26FTBS).

---
diff --git a/ckermit.spec b/ckermit.spec
index 18eed51..c7b6204 100644
--- a/ckermit.spec
+++ b/ckermit.spec
@@ -3,7 +3,7 @@
 Summary:       The quintessential all-purpose communications program
 Name:          ckermit
 Version:       9.0.%{patchlevel}
-Release:       10%{?dist}
+Release:       11%{?dist}
 License:       BSD with advertising and MIT
 # Most of the package is under a three-clause BSD license, but the file
 # ckaut2.h appears to be covered by three licenses:
@@ -26,6 +26,8 @@ BuildRequires: gmp-devel >= 3.1.1
 BuildRequires: libtermcap-devel
 BuildRequires: ncurses-devel
 BuildRequires: lockdev-devel >= 1.0.1-8
+BuildRequires: perl
+
 Requires:      lockdev >= 1.0.1-8
 BuildRoot:     %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
 # NB There used to be a spurious "Obsoletes: gkermit" line here, but ckermit
@@ -90,6 +92,9 @@ rm -rf %{buildroot}
 %doc README.fedora
 
 %changelog
+* Thu Feb 16 2017 Ralf Corsépius <corsepiu@fedoraproject.org> - 9.0.302-11
+- Add BR: perl (Fix F26FTBS).
+
 * Fri Feb 10 2017 Fedora Release Engineering <releng@fedoraproject.org> - 9.0.302-10
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
 

                 reply	other threads:[~2026-09-18 13:57 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=178973985590.1.6861308773125178252.rpms-ckermit-b3150ac38f4b@fedoraproject.org \
    --to=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