public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "orbea" <orbea@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/libressl:master commit in: dev-libs/libressl/
Date: Mon, 11 Mar 2024 17:23:27 +0000 (UTC)	[thread overview]
Message-ID: <1710177770.7192211886561e65148aea720a8cf9cd6c07f3cf.orbea@gentoo> (raw)

commit:     7192211886561e65148aea720a8cf9cd6c07f3cf
Author:     orbea <orbea <AT> riseup <DOT> net>
AuthorDate: Mon Mar 11 17:21:53 2024 +0000
Commit:     orbea <orbea <AT> riseup <DOT> net>
CommitDate: Mon Mar 11 17:22:50 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/libressl.git/commit/?id=71922118

dev-libs/libressl: stabilize 3.7.3-r1 for amd64, arm, arm64, x86

Signed-off-by: orbea <orbea <AT> riseup.net>

 dev-libs/libressl/libressl-3.7.3-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/libressl/libressl-3.7.3-r1.ebuild b/dev-libs/libressl/libressl-3.7.3-r1.ebuild
index a2beb54..f221896 100644
--- a/dev-libs/libressl/libressl-3.7.3-r1.ebuild
+++ b/dev-libs/libressl/libressl-3.7.3-r1.ebuild
@@ -18,7 +18,7 @@ LICENSE="ISC openssl"
 # we'll try to use the max of either. However, if either change between
 # versions, we have to change the subslot to trigger rebuild of consumers.
 SLOT="0/54"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~mips ~ppc ~ppc64 ~s390 ~sparc ~x86 ~amd64-linux ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~loong ~mips ~ppc ~ppc64 ~s390 ~sparc x86 ~amd64-linux ~ppc-macos ~x64-macos ~x64-solaris"
 IUSE="+asm netcat static-libs test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2024-03-11 17:23 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 17:23 orbea [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-13  2:30 [gentoo-commits] repo/proj/libressl:master commit in: dev-libs/libressl/ orbea
2024-11-13  2:30 orbea
2024-10-15 20:09 orbea
2024-09-13  1:40 orbea
2024-08-15  4:35 orbea
2024-07-16 22:04 orbea
2024-05-23 13:22 orbea
2024-05-12 17:49 orbea
2024-04-23 16:39 orbea
2024-04-13 16:14 orbea
2024-04-05  1:28 orbea
2024-03-28 15:24 orbea
2024-03-24 19:42 orbea
2024-03-24 19:42 orbea
2024-03-11  0:42 orbea
2024-03-10 17:21 orbea
2024-02-24 16:07 orbea
2024-01-16 21:14 orbea
2024-01-16  6:56 orbea
2024-01-16  6:46 orbea
2024-01-16  6:34 orbea
2023-12-03 16:21 orbea
2023-11-03 14:13 orbea
2023-11-03 14:13 orbea
2023-11-03 14:13 orbea
2023-09-01  1:08 orbea
2023-06-15 16:18 orbea
2023-06-15 16:18 orbea
2023-05-29 19:49 orbea
2023-05-14 20:15 orbea
2023-04-12 22:45 orbea
2023-04-12 22:45 orbea
2023-03-28 18:51 Quentin Retornaz
2023-03-16 21:53 Quentin Retornaz
2023-03-16 21:53 Quentin Retornaz
2023-02-10  0:59 Quentin Retornaz
2022-12-14 22:47 Quentin Retornaz
2022-12-14 22:47 Quentin Retornaz
2022-12-13 22:18 Quentin Retornaz
2022-12-13 22:18 Quentin Retornaz
2022-11-19 17:27 Quentin Retornaz
2022-10-07 21:11 Quentin Retornaz
2022-07-26 21:42 Quentin Retornaz
     [not found] <1658871652.59ff52355667bc9bf945140dd6abe48336e10f75.quentin@gentoo>
2022-07-26 21:42 ` Quentin Retornaz
2022-07-02 21:59 Quentin Retornaz
2022-06-10 23:36 Quentin Retornaz
2022-05-22 21:09 Quentin Retornaz
2022-05-21 23:51 Quentin Retornaz
2022-05-01  0:19 Quentin Retornaz
2022-04-28 23:40 Quentin Retornaz
2022-03-15 20:47 Quentin Retornaz
2022-03-06 23:41 Quentin Retornaz
2021-12-08 18:32 Quentin Retornaz
2021-11-06 18:21 Quentin Retornaz
2021-09-17 17:45 Quentin Retornaz
2021-08-29  0:20 Quentin Retornaz
2021-05-05 23:54 Quentin Retornaz
2021-04-25 17:03 Quentin Retornaz
2021-04-25 17:03 Quentin Retornaz

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=1710177770.7192211886561e65148aea720a8cf9cd6c07f3cf.orbea@gentoo \
    --to=orbea@riseup.net \
    --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