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: media-sound/lame/
Date: Thu, 26 Oct 2017 21:32:38 +0000 (UTC)	[thread overview]
Message-ID: <1509053554.63f67b77cc9b2f7c142ce035d7eaeb8dde29df80.slyfox@gentoo> (raw)

commit:     63f67b77cc9b2f7c142ce035d7eaeb8dde29df80
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 26 21:31:12 2017 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu Oct 26 21:32:34 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=63f67b77

media-sound/lame: stable 3.100 for ia64, bug #634598

Package-Manager: Portage-2.3.12, Repoman-2.3.4
RepoMan-Options: --include-arches="ia64"

 media-sound/lame/lame-3.100.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-sound/lame/lame-3.100.ebuild b/media-sound/lame/lame-3.100.ebuild
index d74863c491f..93a32b9cba6 100644
--- a/media-sound/lame/lame-3.100.ebuild
+++ b/media-sound/lame/lame-3.100.ebuild
@@ -11,7 +11,7 @@ SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
 
 LICENSE="LGPL-2.1"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 hppa ~ia64 ~mips ~ppc ~ppc64 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~arm-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 hppa ia64 ~mips ~ppc ~ppc64 ~sh ~sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~arm-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x64-solaris ~x86-solaris"
 IUSE="debug cpu_flags_x86_mmx +frontend mp3rtp sndfile static-libs"
 
 # These deps are without MULTILIB_USEDEP and are correct since we only build


             reply	other threads:[~2017-10-26 21:32 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 21:32 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-28 10:03 [gentoo-commits] repo/gentoo:master commit in: media-sound/lame/ James Le Cuirot
2022-05-19  5:08 WANG Xuerui
2021-08-10  8:58 Yixun Lan
2021-01-06 14:31 Fabian Groffen
2020-09-08  7:56 Miroslav Šulc
2020-09-05 15:15 Sam James
2020-09-04 10:31 Sergei Trofimovich
2020-09-02 22:48 Sam James
2020-09-02 22:47 Sam James
2020-08-02 10:54 Miroslav Šulc
2020-07-21 23:15 Kent Fredric
2019-12-24 14:13 Mikle Kolyada
2019-12-10 10:54 Agostino Sarubbo
2019-12-08 10:58 Sergei Trofimovich
2019-12-03 11:58 Agostino Sarubbo
2019-12-03 11:56 Agostino Sarubbo
2019-12-03 10:07 Agostino Sarubbo
2019-12-03 10:06 Agostino Sarubbo
2019-12-03 10:03 Agostino Sarubbo
2019-12-03  0:05 Aaron Bauman
2018-03-23 23:55 Aaron Bauman
2018-03-15 21:15 Sergei Trofimovich
2018-03-15  8:28 Lars Wendler
2018-01-17 13:01 Lars Wendler
2017-11-19 15:14 Markus Meier
2017-11-08 12:51 Tobias Klausmann
2017-10-28 22:21 Sergei Trofimovich
2017-10-26 21:47 Sergei Trofimovich
2017-10-26 19:12 Sergei Trofimovich
2017-10-26 17:38 Thomas Deutschmann
2017-10-25  9:31 Agostino Sarubbo
2017-10-22 20:03 Andreas Hüttel
2016-03-20 23:10 Stephen Klimaszewski
2016-02-17 23:19 Alexis Ballier
2016-02-11  0:29 Manuel Rüger
2015-08-16 14:20 Justin Lecher

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=1509053554.63f67b77cc9b2f7c142ce035d7eaeb8dde29df80.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