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: mail-filter/amavisd-new/
Date: Mon,  6 Dec 2021 08:01:10 +0000 (UTC)	[thread overview]
Message-ID: <1638777660.2066f929d3f3d383cc8a9c18d29ae94c48d54e60.ago@gentoo> (raw)

commit:     2066f929d3f3d383cc8a9c18d29ae94c48d54e60
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Mon Dec  6 08:01:00 2021 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Mon Dec  6 08:01:00 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2066f929

mail-filter/amavisd-new: amd64 stable wrt bug #828359

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

 mail-filter/amavisd-new/amavisd-new-2.12.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mail-filter/amavisd-new/amavisd-new-2.12.1.ebuild b/mail-filter/amavisd-new/amavisd-new-2.12.1.ebuild
index 4245de32669f..9c1451630d7e 100644
--- a/mail-filter/amavisd-new/amavisd-new-2.12.1.ebuild
+++ b/mail-filter/amavisd-new/amavisd-new-2.12.1.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://gitlab.com/amavis/amavis/-/archive/v${PV}/amavis-v${PV}.tar.bz2
 
 LICENSE="GPL-2 BSD-2"
 SLOT="0"
-KEYWORDS="~amd64 ~ppc ~ppc64 ~sparc ~x86"
+KEYWORDS="amd64 ~ppc ~ppc64 ~sparc ~x86"
 IUSE="clamav courier dkim ldap mysql postgres qmail razor rspamd rspamd-https snmp spamassassin"
 
 MY_RSPAMD_DEPEND="dev-perl/HTTP-Message


             reply	other threads:[~2021-12-06  8:01 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06  8:01 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18 20:22 [gentoo-commits] repo/gentoo:master commit in: mail-filter/amavisd-new/ Mike Gilbert
2023-12-14  4:13 Sam James
2023-06-28  7:37 Sam James
2023-06-28  7:37 Sam James
2022-09-06  1:10 Mike Gilbert
2022-03-01 13:57 Ionen Wolkens
2022-02-28 10:14 Agostino Sarubbo
2022-02-28 10:14 Agostino Sarubbo
2022-02-27 13:43 Jakov Smolić
2022-02-27 13:17 Jakov Smolić
2022-02-27  8:57 Agostino Sarubbo
2022-01-31  1:01 Sam James
2021-12-09  6:52 Ionen Wolkens
2021-12-06 11:31 Agostino Sarubbo
2021-12-06  8:06 Agostino Sarubbo
2021-12-06  8:05 Agostino Sarubbo
2021-12-06  8:04 Agostino Sarubbo
2021-02-04 22:33 Thomas Deutschmann
2020-10-15 22:12 Thomas Deutschmann
2020-09-13 20:43 James Le Cuirot
2020-09-13 20:43 James Le Cuirot
2020-09-07 20:05 James Le Cuirot
2020-09-07 20:05 James Le Cuirot
2020-07-18 18:05 Sam James
2020-06-20 15:45 Thomas Deutschmann
2020-05-25  9:36 Sergei Trofimovich
2020-05-22  8:02 Sergei Trofimovich
2020-05-18 16:46 Sergei Trofimovich
2020-03-20 21:53 Matt Turner
2020-02-28  3:52 Joonas Niilola
2020-02-27 13:03 Craig Andrews
2020-02-27 13:03 Craig Andrews
2020-02-21  6:08 Joonas Niilola
2020-02-21  6:08 Joonas Niilola
2020-01-21 15:32 Michael Orlitzky
2019-09-17 17:55 Kent Fredric
2019-08-07 14:27 Michael Orlitzky
2019-02-24  1:41 Andreas K. Hüttel
2019-02-17 17:51 Sergei Trofimovich
2019-02-09 19:29 Sergei Trofimovich
2019-02-07 10:51 Mikle Kolyada
2019-02-03  9:12 Sergei Trofimovich
2019-01-05 16:13 Michael Orlitzky
2019-01-05 16:13 Michael Orlitzky
2018-11-26  0:24 Michael Orlitzky
2018-11-21  3:09 Craig Andrews
2018-11-18 23:56 Michael Orlitzky
2018-11-18 23:56 Michael Orlitzky
2018-06-19 19:13 Sergei Trofimovich
2017-09-24 16:34 Sergei Trofimovich
2017-09-24 16:34 Sergei Trofimovich
2017-08-22 21:31 Michał Górny
2017-02-04  8:53 Jeroen Roovers
2017-01-13 15:41 Agostino Sarubbo
2017-01-11 16:17 Agostino Sarubbo
2016-10-02  7:08 Jeroen Roovers
2016-10-01  8:57 Eray Aslan
2016-04-27 10:17 Eray Aslan
2016-03-09 20:48 Andreas Hüttel
2015-10-15 19:25 Marc Schiffbauer

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=1638777660.2066f929d3f3d383cc8a9c18d29ae94c48d54e60.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