public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/ipv6calc/
Date: Tue, 27 Mar 2018 22:24:11 +0000 (UTC)	[thread overview]
Message-ID: <1522189447.cd69be00ad57858cd9bc916ff87de123a2c84a3c.slyfox@gentoo> (raw)

commit:     cd69be00ad57858cd9bc916ff87de123a2c84a3c
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 27 22:24:00 2018 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Tue Mar 27 22:24:07 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cd69be00

net-misc/ipv6calc: stable 0.99.2 for hppa, bug #622734

Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="hppa"

 net-misc/ipv6calc/ipv6calc-0.99.2.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net-misc/ipv6calc/ipv6calc-0.99.2.ebuild b/net-misc/ipv6calc/ipv6calc-0.99.2.ebuild
index 47d2fa7d338..2070cec352d 100644
--- a/net-misc/ipv6calc/ipv6calc-0.99.2.ebuild
+++ b/net-misc/ipv6calc/ipv6calc-0.99.2.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI="6"
@@ -9,7 +9,7 @@ SRC_URI="ftp://ftp.bieringer.de/pub/linux/IPv6/ipv6calc/${P}.tar.gz"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~hppa ppc sparc x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 hppa ppc sparc x86 ~amd64-linux ~x86-linux"
 IUSE="geoip libressl test"
 
 RDEPEND="


             reply	other threads:[~2018-03-27 22:24 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 22:24 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-17 19:29 [gentoo-commits] repo/gentoo:master commit in: net-misc/ipv6calc/ Arthur Zamarin
2023-03-17 17:00 Sam James
2023-03-17 17:00 Sam James
2023-03-17 16:28 Arthur Zamarin
2022-06-11  5:48 Sam James
2022-05-15  0:29 Anthony G. Basile
2022-05-15  0:29 Anthony G. Basile
2022-05-14 11:51 Anthony G. Basile
2021-10-29 19:00 Anthony G. Basile
2021-10-29 16:56 Anthony G. Basile
2021-10-29 16:50 Anthony G. Basile
2021-10-28 10:03 Anthony G. Basile
2021-09-25 23:46 Sam James
2021-09-25  5:18 Agostino Sarubbo
2021-09-24 22:47 Sam James
2021-09-24 22:47 Sam James
2021-09-24 16:14 Anthony G. Basile
2021-09-24 16:13 Anthony G. Basile
2021-05-09 22:01 Sam James
2021-05-02 12:09 Mikle Kolyada
2021-02-17  1:01 Sam James
2021-02-03 23:55 Thomas Deutschmann
2021-02-01 18:04 Sergei Trofimovich
2020-06-15 20:41 Sergei Trofimovich
2019-12-24  8:09 Agostino Sarubbo
2019-12-20 12:13 Agostino Sarubbo
2019-12-19 10:49 Anthony G. Basile
2019-12-18 14:57 Agostino Sarubbo
2019-12-17 17:48 Anthony G. Basile
2019-10-15 16:09 Anthony G. Basile
2019-06-01 13:35 Anthony G. Basile
2019-06-01 13:35 Anthony G. Basile
2019-04-28  1:21 Anthony G. Basile
2019-02-08 23:46 Anthony G. Basile
2018-10-15 18:43 Sergei Trofimovich
2018-10-14  8:59 Sergei Trofimovich
2018-10-13 16:14 Sergei Trofimovich
2018-10-12 14:02 Mikle Kolyada
2018-10-10  3:13 Thomas Deutschmann
2018-10-10  0:31 Anthony G. Basile
2017-06-26 14:14 Anthony G. Basile
2017-06-26 14:14 Anthony G. Basile
2017-03-09 10:01 Michael Palimaka
2017-02-19  1:22 Anthony G. Basile
2017-02-19  1:22 Anthony G. Basile
2016-08-06  9:39 Pacho Ramos
2015-10-26 14:11 Aaron Bauman
2015-09-21 11:27 Agostino Sarubbo
2015-09-06 13:25 Agostino Sarubbo
2015-09-05 17:03 Anthony G. Basile
2015-08-18  5:35 Jeroen Roovers
2015-08-14  6:27 Anthony G. Basile
2015-08-14  6:27 Anthony G. Basile
2015-08-09 22:54 Mikle Kolyada
2015-08-09 11:18 Agostino Sarubbo

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=1522189447.cd69be00ad57858cd9bc916ff87de123a2c84a3c.slyfox@gentoo \
    --to=slyfox@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