public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/libmd/
Date: Sun,  5 Dec 2021 19:30:52 +0000 (UTC)	[thread overview]
Message-ID: <1638732643.32c2e1a1a53d03e800976a5268a130e901012eaf.arthurzam@gentoo> (raw)

commit:     32c2e1a1a53d03e800976a5268a130e901012eaf
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sun Dec  5 19:30:21 2021 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sun Dec  5 19:30:43 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=32c2e1a1

app-crypt/libmd: Stabilize 1.0.4 sparc, #828276

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 app-crypt/libmd/libmd-1.0.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-crypt/libmd/libmd-1.0.4.ebuild b/app-crypt/libmd/libmd-1.0.4.ebuild
index 0ded69e5fe5e..33c6b5d1b334 100644
--- a/app-crypt/libmd/libmd-1.0.4.ebuild
+++ b/app-crypt/libmd/libmd-1.0.4.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://archive.hadrons.org/software/libmd/${P}.tar.xz"
 
 LICENSE="|| ( BSD BSD-2 ISC BEER-WARE public-domain )"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ppc ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux"
 
 multilib_src_configure() {
 	ECONF_SOURCE="${S}" econf


             reply	other threads:[~2021-12-05 19:30 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-05 19:30 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-15  3:17 [gentoo-commits] repo/gentoo:master commit in: app-crypt/libmd/ Sam James
2023-08-01 18:27 Arthur Zamarin
2023-07-24 12:07 Jakov Smolić
2023-07-24  8:54 Jakov Smolić
2023-06-14 16:53 Sam James
2023-02-13  4:25 Sam James
2023-01-03  5:58 Sam James
2023-01-03  5:58 Sam James
2022-05-08  2:12 WANG Xuerui
2021-12-07 20:23 Sam James
2021-12-06 15:23 Sam James
2021-12-06 15:20 Sam James
2021-12-05 18:39 Sam James
2021-12-05 18:31 Sam James
2021-12-05  7:49 Jakov Smolić
2021-10-05  4:18 Sam James
2021-10-05  4:09 Sam James
2021-09-21  8:47 James Le Cuirot
2021-08-24 13:39 Andreas Sturmlechner
2021-08-24  0:05 Marek Szuba
2021-08-19 19:57 Sam James
2021-08-19  1:08 Sam James
2021-08-18 12:58 Agostino Sarubbo
2021-08-17 18:56 Sam James
2021-08-16  5:20 Agostino Sarubbo
2021-08-16  5:17 Agostino Sarubbo
2021-08-16  5:16 Agostino Sarubbo
2021-08-16  5:13 Agostino Sarubbo
2021-07-19  7:54 Joshua Kinard
2021-07-16 12:48 Andreas Sturmlechner
2021-06-04 14:25 Sergei Trofimovich
2021-06-02 23:41 Sam James
2021-06-02 10:39 Sam James
2021-03-09 22:49 Sam James
2021-03-09 22:49 Sam James
2021-02-05 12:33 Sam James
2021-02-05 12:29 Sam James
2021-02-03  3:11 Sam James
2021-02-01 13:33 Sam James
2021-01-02 21:08 Sam James
2020-12-20 19:28 Sam James
2020-12-20 19:07 Thomas Deutschmann
2020-12-17 16:41 Agostino Sarubbo
2020-12-17  8:17 Sam James
2020-06-26 21:16 Mart Raudsepp
2019-10-23 12:21 Jeroen Roovers
2019-06-05  7:02 Michael Haubenwallner
2019-06-03 10:51 Michael Haubenwallner
2019-02-17 16:03 Mikle Kolyada
2018-12-29 11:56 Jeroen Roovers
2018-12-28 20:29 Mikle Kolyada
2018-11-17 15:31 Mikle Kolyada
2018-10-24  5:39 Jeroen Roovers
2018-10-23 18:23 Sergei Trofimovich
2018-10-20 12:16 Sergei Trofimovich
2018-10-18  7:52 Tobias Klausmann
2018-10-14 22:35 Sergei Trofimovich
2018-09-29 13:29 Jeroen Roovers
2018-09-29 13:29 Jeroen Roovers
2018-09-29 13:29 Jeroen Roovers
2018-05-26 10:01 Mikle Kolyada
2018-04-20  1:28 Aaron Bauman
2018-02-01  7:01 Lars Wendler
2017-07-23 12:06 Manuel Rüger
2016-12-19 14:14 Tobias Klausmann
2016-09-05  0:21 Manuel Rüger
2016-09-04 22:52 Manuel Rüger

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=1638732643.32c2e1a1a53d03e800976a5268a130e901012eaf.arthurzam@gentoo \
    --to=arthurzam@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