public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apache/modsecurity-crs/
Date: Fri,  9 Oct 2020 08:41:00 +0000 (UTC)	[thread overview]
Message-ID: <1602232816.b12fe653107c27b72a7de5c2d1b3741030245b52.ago@gentoo> (raw)

commit:     b12fe653107c27b72a7de5c2d1b3741030245b52
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Fri Oct  9 08:40:16 2020 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Fri Oct  9 08:40:16 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b12fe653

www-apache/modsecurity-crs: x86 stable wrt bug #719250

Package-Manager: Portage-2.3.103, Repoman-2.3.23
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 www-apache/modsecurity-crs/modsecurity-crs-3.3.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www-apache/modsecurity-crs/modsecurity-crs-3.3.0.ebuild b/www-apache/modsecurity-crs/modsecurity-crs-3.3.0.ebuild
index 985caa85072..ab22a721d84 100644
--- a/www-apache/modsecurity-crs/modsecurity-crs-3.3.0.ebuild
+++ b/www-apache/modsecurity-crs/modsecurity-crs-3.3.0.ebuild
@@ -9,7 +9,7 @@ SRC_URI="https://github.com/coreruleset/coreruleset/archive/v${PV}.tar.gz -> ${P
 
 LICENSE="Apache-2.0"
 SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="~amd64 x86"
 
 RDEPEND=">=www-apache/mod_security-2.9.1"
 


             reply	other threads:[~2020-10-09  8:41 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09  8:41 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-26  1:25 [gentoo-commits] repo/gentoo:master commit in: www-apache/modsecurity-crs/ Sam James
2025-04-26  1:17 Sam James
2025-03-12 12:38 Petr Vaněk
2025-03-01  9:00 Petr Vaněk
2025-03-01  9:00 Petr Vaněk
2025-02-11  9:49 Sam James
2025-02-11  9:49 Sam James
2025-02-11  9:21 Sam James
2025-02-11  9:21 Sam James
2024-12-04 18:10 Joonas Niilola
2024-12-04 18:10 Joonas Niilola
2024-12-04 18:10 Joonas Niilola
2024-10-26  6:02 Joonas Niilola
2024-10-26  6:02 Joonas Niilola
2024-10-26  3:49 Sam James
2024-10-26  3:49 Sam James
2024-10-25 11:36 Joonas Niilola
2024-10-25 11:36 Joonas Niilola
2024-07-20  6:42 Joonas Niilola
2024-07-20  6:42 Joonas Niilola
2024-04-27 13:21 Petr Vaněk
2024-04-27 13:21 Petr Vaněk
2024-04-26 17:16 Sam James
2024-04-26 17:16 Sam James
2024-03-16  9:26 Joonas Niilola
2024-01-11 14:06 Joonas Niilola
2024-01-11 14:06 Joonas Niilola
2023-10-31  0:06 Sam James
2023-10-30 23:13 Sam James
2023-10-28  7:07 Hans de Graaff
2022-12-02  6:15 John Helmert III
2022-12-02  3:38 Sam James
2022-12-02  3:34 Sam James
2022-11-21  9:22 Joonas Niilola
2022-11-21  9:22 Joonas Niilola
2021-12-24  8:02 Sam James
2021-12-22  0:45 Sam James
2021-12-22  0:44 Sam James
2021-12-21  2:05 Sam James
2020-12-29  2:00 Sam James
2020-10-09 15:23 Agostino Sarubbo
2020-10-07 18:58 Sam James
2019-03-04  1:35 Thomas Deutschmann
2018-10-26  0:52 Thomas Deutschmann
2018-10-20 18:01 Mikle Kolyada
2018-05-20 23:26 Aaron Bauman
2018-03-29 19:23 Michał Górny
2016-11-03 21:46 Diego Elio Pettenò
2016-08-07  9:30 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=1602232816.b12fe653107c27b72a7de5c2d1b3741030245b52.ago@gentoo \
    --to=ago@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