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-gfx/qrencode/
Date: Mon, 26 Oct 2020 23:49:29 +0000 (UTC)	[thread overview]
Message-ID: <1603756106.559d7c921c8e1411dacdfb9700155f121e6400e1.slyfox@gentoo> (raw)

commit:     559d7c921c8e1411dacdfb9700155f121e6400e1
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 26 23:48:26 2020 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Mon Oct 26 23:48:26 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=559d7c92

media-gfx/qrencode: stable 4.1.1 for ppc64

stable wrt bug #751142

Package-Manager: Portage-3.0.8, Repoman-3.0.2
RepoMan-Options: --include-arches="ppc64"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

 media-gfx/qrencode/qrencode-4.1.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-gfx/qrencode/qrencode-4.1.1.ebuild b/media-gfx/qrencode/qrencode-4.1.1.ebuild
index 765539417fd..b4649c8e5bd 100644
--- a/media-gfx/qrencode/qrencode-4.1.1.ebuild
+++ b/media-gfx/qrencode/qrencode-4.1.1.ebuild
@@ -9,7 +9,7 @@ SRC_URI="https://fukuchi.org/works/${PN}/${P}.tar.bz2"
 
 LICENSE="LGPL-2"
 SLOT="0/4"
-KEYWORDS="~alpha ~amd64 ~arm arm64 hppa ~ia64 ~mips ppc ~ppc64 ~sparc x86"
+KEYWORDS="~alpha ~amd64 ~arm arm64 hppa ~ia64 ~mips ppc ppc64 ~sparc x86"
 IUSE="test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2020-10-26 23:49 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 23:49 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-24 18:04 [gentoo-commits] repo/gentoo:master commit in: media-gfx/qrencode/ Sam James
2024-07-06  6:35 Michał Górny
2024-07-06  6:10 Sam James
2024-07-06  6:10 Sam James
2024-07-06  6:10 Sam James
2024-07-06  6:10 Sam James
2024-07-06  6:10 Sam James
2024-07-06  6:10 Sam James
2024-07-06  5:57 Sam James
2024-06-20 17:53 Sam James
2022-05-29 20:17 Andreas K. Hüttel
2022-05-20 22:04 Andreas K. Hüttel
2022-05-08  3:10 WANG Xuerui
2022-02-14 12:01 Michał Górny
2021-03-14 21:45 Aaron Bauman
2020-11-03  9:17 Michał Górny
2020-11-03  8:45 Sam James
2020-10-28 16:18 Sam James
2020-10-26 23:51 Sergei Trofimovich
2020-10-26 23:47 Sergei Trofimovich
2020-10-26 23:44 Sergei Trofimovich
2020-10-25 23:19 Sam James
2020-10-25 23:08 Thomas Deutschmann
2020-09-28  9:08 Michał Górny
2020-08-30  3:36 Michał Górny
2019-04-23 22:08 Aaron Bauman
2018-10-19  9:57 Michał Górny
2018-10-09  9:30 Mikle Kolyada
2018-09-14 12:17 Tobias Klausmann
2018-09-09  1:12 Thomas Deutschmann
2018-09-07 23:03 Sergei Trofimovich
2018-09-07 22:57 Sergei Trofimovich
2018-09-07 22:54 Sergei Trofimovich
2018-09-07 22:43 Sergei Trofimovich
2018-09-07 19:04 Sergei Trofimovich
2018-09-07 14:46 Mikle Kolyada
2018-06-07  6:05 Michał Górny
2018-06-07  6:05 Michał Górny
2018-06-05 15:52 Michał Górny
2018-05-14 12:38 Tobias Klausmann
2018-05-03 17:12 Markus Meier
2018-04-19 22:14 Sergei Trofimovich
2018-04-19 19:42 Sergei Trofimovich
2018-04-18 21:39 Sergei Trofimovich
2018-04-18 13:54 Aaron Bauman
2018-03-28 20:55 Matt Turner
2017-09-22 15:53 Michał Górny
2017-09-22 15:53 Michał Górny
2017-09-22 15:53 Michał Górny
2017-06-29 22:22 Michał Górny
2017-06-26  8:37 Alexis Ballier
2016-12-25 22:45 Andrew Savchenko
2016-12-25 10:23 Agostino Sarubbo
2016-12-25 10:14 Agostino Sarubbo
2016-12-25 10:09 Agostino Sarubbo
2016-12-24 10:18 Agostino Sarubbo
2016-10-05 14:53 Jeroen Roovers
2016-09-04 10:21 Tobias Klausmann
2016-08-17  8:21 Jeroen Roovers
2016-08-14 19:12 Markus Meier
2016-06-12 11:39 Michał Górny
2016-06-12 11:04 Andrew Savchenko
2016-06-12 11:04 Andrew Savchenko
2016-06-12  8:00 Andrew Savchenko
2016-06-11 20:39 Pacho Ramos

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=1603756106.559d7c921c8e1411dacdfb9700155f121e6400e1.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