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: dev-python/backports-lzma/
Date: Thu,  3 May 2018 20:54:01 +0000 (UTC)	[thread overview]
Message-ID: <1525380822.2e54f106dad29aa3cfbdad31519646f33c4f26b2.slyfox@gentoo> (raw)

commit:     2e54f106dad29aa3cfbdad31519646f33c4f26b2
Author:     Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Thu May  3 19:51:52 2018 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu May  3 20:53:42 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2e54f106

dev-python/backports-lzma: stable 0.0.10 for sparc

Bug: https://bugs.gentoo.org/654682
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="sparc"

 dev-python/backports-lzma/backports-lzma-0.0.10.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/backports-lzma/backports-lzma-0.0.10.ebuild b/dev-python/backports-lzma/backports-lzma-0.0.10.ebuild
index b13250bc79f..38d07b916dc 100644
--- a/dev-python/backports-lzma/backports-lzma-0.0.10.ebuild
+++ b/dev-python/backports-lzma/backports-lzma-0.0.10.ebuild
@@ -16,7 +16,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${MY_PN}/${MY_P}.tar.gz"
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86 ~x64-cygwin ~amd64-fbsd ~amd64-linux ~x86-linux ~x64-macos"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 sparc ~x86 ~x64-cygwin ~amd64-fbsd ~amd64-linux ~x86-linux ~x64-macos"
 IUSE="test"
 
 RDEPEND="app-arch/xz-utils:0=


             reply	other threads:[~2018-05-03 20:54 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 20:54 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-02  7:52 [gentoo-commits] repo/gentoo:master commit in: dev-python/backports-lzma/ Mikle Kolyada
2020-07-04 15:15 Michał Górny
2020-05-04 10:23 Michał Górny
2020-04-10 22:56 Sergei Trofimovich
2020-04-07 10:21 Mart Raudsepp
2020-03-29 14:45 Sergei Trofimovich
2020-03-25 13:12 Agostino Sarubbo
2020-03-25 12:36 Agostino Sarubbo
2020-03-25 12:23 Agostino Sarubbo
2018-12-27  8:27 Tim Harder
2018-07-01  3:24 Tim Harder
2018-07-01  3:24 Tim Harder
2018-06-03 13:55 Mike Frysinger
2018-06-03  9:49 Mikle Kolyada
2018-05-17  9:09 Mikle Kolyada
2018-05-14 19:21 Tobias Klausmann
2018-05-04 15:36 Thomas Deutschmann
2018-05-04 12:29 Mart Raudsepp
2018-05-03 21:45 Sergei Trofimovich
2018-04-06 11:05 Fabian Groffen
2018-03-11 21:50 Matt Turner
2018-02-27 21:38 Manuel Rüger
2018-02-21 17:20 Michał Górny
2018-02-19 16:28 Michael Haubenwallner
2018-02-06  7:21 Joshua Kinard
2018-01-08 22:34 Michał Górny
2018-01-08 22:34 Michał Górny
2017-12-25 11:42 Markus Meier
2017-12-23 11:17 Markus Meier
2017-12-21 13:07 Sergei Trofimovich
2017-12-04 22:07 Sergei Trofimovich
2017-11-27  8:47 Sergei Trofimovich
2017-11-26 21:02 Sergei Trofimovich
2017-02-14 19:05 Manuel Rüger
2016-08-25 21:50 Tim Harder
2016-08-25 21:50 Tim Harder
2016-07-12 17:48 Tim Harder
2015-08-19  3:12 Mike Gilbert

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=1525380822.2e54f106dad29aa3cfbdad31519646f33c4f26b2.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