public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matthew Thode" <prometheanfire@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyroute2/
Date: Sat, 30 May 2020 17:52:18 +0000 (UTC)	[thread overview]
Message-ID: <1590860429.d3396c354853c4af72ef9c3245b535ff306a98e1.prometheanfire@gentoo> (raw)

commit:     d3396c354853c4af72ef9c3245b535ff306a98e1
Author:     Matthew Thode <prometheanfire <AT> gentoo <DOT> org>
AuthorDate: Sat May 30 17:40:29 2020 +0000
Commit:     Matthew Thode <prometheanfire <AT> gentoo <DOT> org>
CommitDate: Sat May 30 17:40:29 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d3396c35

dev-python/pyroute2: 0.5.12 allarches stablized

Stablized for Openstack USSURI

Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Matthew Thode <prometheanfire <AT> gentoo.org>

 dev-python/pyroute2/pyroute2-0.5.12.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/pyroute2/pyroute2-0.5.12.ebuild b/dev-python/pyroute2/pyroute2-0.5.12.ebuild
index 09505762e11..101c5a98dd3 100644
--- a/dev-python/pyroute2/pyroute2-0.5.12.ebuild
+++ b/dev-python/pyroute2/pyroute2-0.5.12.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://github.com/svinota/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
 
 LICENSE="Apache-2.0"
 SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~x86"
+KEYWORDS="amd64 ~arm64 x86"
 IUSE="test"
 
 BDEPEND="


             reply	other threads:[~2020-05-30 17:52 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-30 17:52 Matthew Thode [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-02  9:59 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyroute2/ Arthur Zamarin
2024-02-20  9:09 Michał Górny
2024-02-20  8:09 Sam James
2024-02-13 16:45 Michał Górny
2024-02-13 16:45 Michał Górny
2024-02-13  4:33 Michał Górny
2024-02-09 14:10 Joonas Niilola
2024-02-04 20:11 Sam James
2024-01-21  6:21 Michał Górny
2024-01-21  2:44 Sam James
2024-01-06 14:18 Michał Górny
2023-07-10  1:25 Michał Górny
2023-07-09 17:08 Arthur Zamarin
2023-06-11 16:15 Michał Górny
2023-06-11 13:35 Sam James
2023-06-05 16:43 Amy Liffey
2023-05-08 19:25 Michał Górny
2023-05-04  5:04 Michał Górny
2023-05-04  4:38 Arthur Zamarin
2023-03-31 17:15 Michał Górny
2023-03-14  6:11 Michał Górny
2023-03-13 22:36 Sam James
2023-02-05  9:13 Joonas Niilola
2023-02-05  9:12 Joonas Niilola
2022-11-27 21:14 Andrew Ammerlaan
2022-10-10 20:18 Michał Górny
2022-10-10 18:34 Sam James
2022-09-10  5:38 Arthur Zamarin
2022-09-06 21:12 Sam James
2022-08-04  7:12 Joonas Niilola
2022-06-16 16:33 Sam James
2022-06-16 16:32 Sam James
2022-05-20  2:01 Matthew Thode
2021-02-22 22:40 Matthew Thode
2020-11-16  0:02 Michał Górny
2020-11-15 23:50 Sam James
2020-11-14 22:06 Michał Górny
2020-10-15 23:24 Matthew Thode
2020-07-20 20:04 Matthew Thode
2020-07-06 21:43 Matthew Thode
2020-03-28 18:26 Michał Górny
2020-03-28 18:26 Michał Górny
2019-06-16 18:54 Matthew Thode
2019-04-12 19:44 Matthew Thode
2017-09-13 17:39 Matt Thode
2017-09-01 19:42 Matt Thode
2017-08-30 19:47 Matt Thode
2017-07-13  3:48 Matt Thode
2017-03-26  4:16 Matt Thode
2017-02-27  5:45 Matt Thode

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=1590860429.d3396c354853c4af72ef9c3245b535ff306a98e1.prometheanfire@gentoo \
    --to=prometheanfire@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