From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-chemistry/votca-xtp/
Date: Mon, 20 May 2019 11:03:28 +0000 (UTC) [thread overview]
Message-ID: <1558350176.6fa28cb05a3e64b8c7d8a7705b7443ae1481d430.zlogene@gentoo> (raw)
commit: 6fa28cb05a3e64b8c7d8a7705b7443ae1481d430
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Mon May 20 11:02:56 2019 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Mon May 20 11:02:56 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6fa28cb0
sci-chemistry/votca-xtp: amd64 stable wrt bug #685046
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11
RepoMan-Options: --include-arches="amd64"
sci-chemistry/votca-xtp/votca-xtp-1.5.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sci-chemistry/votca-xtp/votca-xtp-1.5.ebuild b/sci-chemistry/votca-xtp/votca-xtp-1.5.ebuild
index 15a8759ad21..ce2077c641d 100644
--- a/sci-chemistry/votca-xtp/votca-xtp-1.5.ebuild
+++ b/sci-chemistry/votca-xtp/votca-xtp-1.5.ebuild
@@ -11,12 +11,12 @@ IUSE="doc"
if [ "${PV}" != "9999" ]; then
SRC_URI="https://github.com/${PN/-//}/archive/v${PV}.tar.gz -> ${P}.tar.gz
doc? ( https://github.com/${PN/-//}/releases/download/v${PV}/${PN}-manual-${PV}.pdf )"
- KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-macos"
+ KEYWORDS="amd64 ~x86 ~amd64-linux ~x86-macos"
S="${WORKDIR}/${P#votca-}"
else
inherit git-r3
EGIT_REPO_URI="https://github.com/${PN/-//}.git"
- KEYWORDS=""
+ KEYWORDS="amd64"
fi
DESCRIPTION="Votca excitation and charge properties module"
next reply other threads:[~2019-05-20 11:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 11:03 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-20 14:58 [gentoo-commits] repo/gentoo:master commit in: sci-chemistry/votca-xtp/ Christoph Junghans
2022-02-20 14:58 Christoph Junghans
2021-09-19 15:20 Christoph Junghans
2021-07-18 23:24 Christoph Junghans
2021-04-05 16:53 Andreas Sturmlechner
2021-03-28 10:02 Agostino Sarubbo
2021-03-27 16:07 Sam James
2021-03-19 19:46 Christoph Junghans
2021-03-14 19:15 Christoph Junghans
2021-02-28 18:08 Andreas Sturmlechner
2021-01-18 10:14 David Seifert
2021-01-13 1:20 Christoph Junghans
2021-01-06 15:10 Fabian Groffen
2020-12-10 19:26 Christoph Junghans
2020-08-22 23:36 Christoph Junghans
2020-06-21 15:41 Christoph Junghans
2020-04-18 5:01 Christoph Junghans
2020-04-02 22:05 Christoph Junghans
2020-01-12 21:51 Christoph Junghans
2019-11-22 2:26 Christoph Junghans
2019-01-31 20:16 Christoph Junghans
2018-10-02 12:58 Christoph Junghans
2018-09-28 12:37 Christoph Junghans
2018-09-27 17:31 Christoph Junghans
2018-09-27 17:31 Christoph Junghans
2017-09-04 18:06 Christoph Junghans
2017-09-03 14:55 Christoph Junghans
2017-09-03 13:41 Christoph Junghans
2017-07-30 10:04 Michał Górny
2016-12-20 14:30 Tobias Klausmann
2016-12-09 17:25 Christoph Junghans
2016-11-14 2:01 Christoph Junghans
2016-10-29 21:41 Christoph Junghans
2016-09-27 18:13 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=1558350176.6fa28cb05a3e64b8c7d8a7705b7443ae1481d430.zlogene@gentoo \
--to=zlogene@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