From: "Erik Mackdanz" <stasibear@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/lxcfs/
Date: Sat, 13 Oct 2018 21:29:56 +0000 (UTC) [thread overview]
Message-ID: <1539466171.7be665c89d732286c63ab6cbc411d8164ce020df.stasibear@gentoo> (raw)
commit: 7be665c89d732286c63ab6cbc411d8164ce020df
Author: Erik Mackdanz <stasibear <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 13 21:29:31 2018 +0000
Commit: Erik Mackdanz <stasibear <AT> gentoo <DOT> org>
CommitDate: Sat Oct 13 21:29:31 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7be665c8
sys-fs/lxcfs: Stabilize 3.0.0
Signed-off-by: Erik Mackdanz <stasibear <AT> gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
sys-fs/lxcfs/lxcfs-3.0.0.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sys-fs/lxcfs/lxcfs-3.0.0.ebuild b/sys-fs/lxcfs/lxcfs-3.0.0.ebuild
index 1e619383c4c..a16a47a4d9f 100644
--- a/sys-fs/lxcfs/lxcfs-3.0.0.ebuild
+++ b/sys-fs/lxcfs/lxcfs-3.0.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -19,7 +19,7 @@ else
# e.g. upstream is 2.0.0.beta2, we want 2.0.0_beta2
UPSTREAM_PV=$(replace_version_separator 3 '.' )
SRC_URI="https://github.com/lxc/lxcfs/archive/${PN}-${UPSTREAM_PV}.tar.gz -> ${P}.tar.gz"
- KEYWORDS="~amd64"
+ KEYWORDS="amd64"
fi
# Omit all dbus. Upstream appears to require it because systemd, but
next reply other threads:[~2018-10-13 21:30 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 21:29 Erik Mackdanz [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-25 11:09 [gentoo-commits] repo/gentoo:master commit in: sys-fs/lxcfs/ Joonas Niilola
2024-10-20 6:27 Joonas Niilola
2024-09-17 7:20 Joonas Niilola
2024-08-27 7:00 Joonas Niilola
2024-08-11 7:37 Joonas Niilola
2024-07-08 7:17 Joonas Niilola
2024-06-27 5:32 Joonas Niilola
2024-05-05 6:28 Joonas Niilola
2024-03-28 6:42 Joonas Niilola
2023-10-07 6:20 Joonas Niilola
2023-10-06 7:14 Joonas Niilola
2023-09-10 6:29 Joonas Niilola
2023-09-05 7:31 Joonas Niilola
2023-08-31 7:07 Joonas Niilola
2023-07-26 5:16 Joonas Niilola
2023-02-26 6:41 Joonas Niilola
2023-02-20 8:06 Joonas Niilola
2023-01-19 15:10 Joonas Niilola
2022-11-01 12:19 Joonas Niilola
2022-10-10 12:20 Joonas Niilola
2022-09-10 5:24 Joonas Niilola
2022-08-10 6:03 Joonas Niilola
2022-08-02 5:35 Joonas Niilola
2022-07-27 6:58 Joonas Niilola
2022-07-18 7:01 Joonas Niilola
2022-06-14 14:35 Joonas Niilola
2022-06-12 16:21 Joonas Niilola
2022-06-12 16:03 Joonas Niilola
2022-06-11 9:17 Joonas Niilola
2022-05-22 8:13 Jakov Smolić
2022-04-14 11:51 Joonas Niilola
2022-03-20 6:22 Joonas Niilola
2022-02-02 8:53 Joonas Niilola
2021-12-02 17:39 Joonas Niilola
2021-11-24 6:16 Joonas Niilola
2021-10-24 7:57 Sam James
2021-10-24 7:54 Sam James
2021-10-22 8:39 Joonas Niilola
2021-10-04 5:40 Joonas Niilola
2021-08-25 7:09 Joonas Niilola
2021-08-19 6:23 Joonas Niilola
2021-08-05 2:49 Yixun Lan
2021-07-19 11:15 Joonas Niilola
2021-06-01 8:43 Joonas Niilola
2021-06-01 8:43 Joonas Niilola
2021-04-30 7:01 Joonas Niilola
2021-02-08 6:55 Joonas Niilola
2021-02-08 6:55 Joonas Niilola
2021-01-09 14:28 Joonas Niilola
2020-11-19 10:22 Joonas Niilola
2020-11-19 10:22 Joonas Niilola
2020-10-20 5:43 Joonas Niilola
2020-09-22 6:54 Joonas Niilola
2020-09-03 10:08 Joonas Niilola
2020-09-03 10:08 Joonas Niilola
2020-08-05 7:09 Joonas Niilola
2020-08-04 16:50 Joonas Niilola
2020-06-21 17:02 Joonas Niilola
2020-06-19 6:43 Joonas Niilola
2020-06-01 12:47 Joonas Niilola
2020-05-15 13:55 Joonas Niilola
2020-05-15 13:39 Joonas Niilola
2020-05-15 8:30 Joonas Niilola
2019-04-02 4:05 Erik Mackdanz
2019-04-02 4:03 Erik Mackdanz
2019-02-07 3:16 Erik Mackdanz
2016-03-18 19:11 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=1539466171.7be665c89d732286c63ab6cbc411d8164ce020df.stasibear@gentoo \
--to=stasibear@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