public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-cluster/crmsh/
Date: Mon, 15 Feb 2021 00:32:21 +0000 (UTC)	[thread overview]
Message-ID: <1613349121.bf18b3bae4e9d483da45023bb596d3b425a51670.sam@gentoo> (raw)

commit:     bf18b3bae4e9d483da45023bb596d3b425a51670
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 14 23:25:05 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Feb 15 00:32:01 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bf18b3ba

sys-cluster/crmsh: fix double KEYWORDS

Double KEYWORDS lines break tools like ekeyword and Nattka.
As per PMS, blank/empty KEYWORDS is implied by not defining
the variable.

See: https://projects.gentoo.org/qa/policy-guide/ebuild-format.html#pg0105
Package-Manager: Portage-3.0.14, Repoman-3.0.2
Signed-off-by: Sam James <sam <AT> gentoo.org>

 sys-cluster/crmsh/crmsh-4.2.1.ebuild | 1 -
 1 file changed, 1 deletion(-)

diff --git a/sys-cluster/crmsh/crmsh-4.2.1.ebuild b/sys-cluster/crmsh/crmsh-4.2.1.ebuild
index 312f01a1ed1..9397c762c64 100644
--- a/sys-cluster/crmsh/crmsh-4.2.1.ebuild
+++ b/sys-cluster/crmsh/crmsh-4.2.1.ebuild
@@ -6,7 +6,6 @@ EAPI=6
 PYTHON_COMPAT=( python3_{7,8,9} )
 
 AUTOTOOLS_AUTORECONF=true
-KEYWORDS=""
 SRC_URI=""
 
 if [[ ${PV} == *9999 ]]; then


             reply	other threads:[~2021-02-15  0:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15  0:32 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-17  8:14 [gentoo-commits] repo/gentoo:master commit in: sys-cluster/crmsh/ Michał Górny
2023-11-08 10:58 Sergey Popov
2022-11-25  8:56 Sergey Popov
2022-11-25  8:56 Sergey Popov
2022-08-10  3:31 Sam James
2022-03-13  5:54 Sam James
2021-05-08 12:43 Sergey Popov
2021-02-08  9:25 Alexys Jacob
2020-09-19 12:29 Michał Górny
2019-12-12 22:24 Alexys Jacob
2018-08-14 22:02 Alexys Jacob
2017-07-30  9:23 Michał Górny

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=1613349121.bf18b3bae4e9d483da45023bb596d3b425a51670.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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