From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-physics/espresso/
Date: Mon, 15 Feb 2021 00:32:21 +0000 (UTC) [thread overview]
Message-ID: <1613349118.efc046af4b3479a93b8c237dce7a78c9115fbfbc.sam@gentoo> (raw)
commit: efc046af4b3479a93b8c237dce7a78c9115fbfbc
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 14 23:22:11 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Feb 15 00:31:58 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=efc046af
sci-physics/espresso: 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>
sci-physics/espresso/espresso-4.1.3.ebuild | 1 -
sci-physics/espresso/espresso-9999.ebuild | 1 -
2 files changed, 2 deletions(-)
diff --git a/sci-physics/espresso/espresso-4.1.3.ebuild b/sci-physics/espresso/espresso-4.1.3.ebuild
index 66c2b9a4c69..1ef336f2ab4 100644
--- a/sci-physics/espresso/espresso-4.1.3.ebuild
+++ b/sci-physics/espresso/espresso-4.1.3.ebuild
@@ -15,7 +15,6 @@ if [[ ${PV} = 9999 ]]; then
EGIT_REPO_URI="https://github.com/${PN}md/${PN}.git"
EGIT_BRANCH="python"
inherit git-r3
- KEYWORDS=""
else
SRC_URI="https://github.com/${PN}md/${PN}/releases/download/${PV}/${P}.tar.gz"
KEYWORDS="~amd64 ~x86 ~amd64-linux"
diff --git a/sci-physics/espresso/espresso-9999.ebuild b/sci-physics/espresso/espresso-9999.ebuild
index 66c2b9a4c69..1ef336f2ab4 100644
--- a/sci-physics/espresso/espresso-9999.ebuild
+++ b/sci-physics/espresso/espresso-9999.ebuild
@@ -15,7 +15,6 @@ if [[ ${PV} = 9999 ]]; then
EGIT_REPO_URI="https://github.com/${PN}md/${PN}.git"
EGIT_BRANCH="python"
inherit git-r3
- KEYWORDS=""
else
SRC_URI="https://github.com/${PN}md/${PN}/releases/download/${PV}/${P}.tar.gz"
KEYWORDS="~amd64 ~x86 ~amd64-linux"
next reply other threads:[~2021-02-15 0:32 UTC|newest]
Thread overview: 18+ 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 --
2021-07-17 18:18 [gentoo-commits] repo/gentoo:master commit in: sci-physics/espresso/ David Seifert
2021-01-06 15:19 Fabian Groffen
2020-08-16 15:22 Christoph Junghans
2020-02-09 16:36 Michał Górny
2020-01-16 7:03 Michał Górny
2018-09-07 15:27 Christoph Junghans
2017-07-30 10:04 Michał Górny
2017-07-17 14:58 Christoph Junghans
2017-06-15 17:37 Pacho Ramos
2017-03-06 13:48 Tobias Klausmann
2016-11-16 20:53 Christoph Junghans
2016-11-14 2:01 Christoph Junghans
2016-09-06 21:25 Christoph Junghans
2016-08-03 18:00 Christoph Junghans
2016-07-22 20:31 Christoph Junghans
2016-07-19 16:58 Christoph Junghans
2016-07-18 19:40 Christoph Junghans
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=1613349118.efc046af4b3479a93b8c237dce7a78c9115fbfbc.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