public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/nano] rawhide: remove redundant build requires
Date: Wed, 03 Jun 2026 12:40:32 GMT	[thread overview]
Message-ID: <178049043240.1.15101159920051611327.rpms-nano-9d27f33090b7@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/nano
            Branch : rawhide
            Commit : 9d27f33090b73ad7d0a4a2b38b96cb29fb45c74a
            Author : Lukáš Zaoral <lzaoral@redhat.com>
            Date   : 2026-06-03T14:40:04+02:00
            Stats  : +4/-3 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/nano/c/9d27f33090b73ad7d0a4a2b38b96cb29fb45c74a?branch=rawhide

            Log:
            remove redundant build requires

Related: https://mkoncek.fedorapeople.org/unbreq.html

---
diff --git a/nano.spec b/nano.spec
index 0ed1a9f..a3cb0cd 100644
--- a/nano.spec
+++ b/nano.spec
@@ -8,7 +8,7 @@
 Summary:         A small text editor
 Name:            nano
 Version:         9.0
-Release:         1%{?dist}
+Release:         2%{?dist}
 License:         GPL-3.0-or-later
 URL:             https://www.nano-editor.org
 
@@ -31,11 +31,9 @@ BuildRequires:   gettext-devel
 BuildRequires:   gcc
 BuildRequires:   git-core
 BuildRequires:   gnupg2
-BuildRequires:   groff
 BuildRequires:   make
 BuildRequires:   ncurses-devel
 BuildRequires:   sed
-BuildRequires:   texinfo
 Conflicts:       filesystem < 3
 
 %description
@@ -133,6 +131,9 @@ install -Dpm 0644 %{SOURCE13} %{buildroot}%{_datadir}/fish/vendor_conf.d/%{basen
 
 
 %changelog
+* Wed Jun 03 2026 Lukáš Zaoral <lzaoral@redhat.com> - 9.0-2
+- remove redundant build requires
+
 * Thu Apr 09 2026 Lukáš Zaoral <lzaoral@redhat.com> - 9.0-1
 - rebase to the latest upstream release (rhbz#2456541)
 

                 reply	other threads:[~2026-06-03 12:40 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=178049043240.1.15101159920051611327.rpms-nano-9d27f33090b7@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