From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2] Postfix: update to 3.3.1
Date: Wed, 15 Aug 2018 23:34:55 +0100 [thread overview]
Message-ID: <ccec10ae800fb92763aa2609d930533da9354333.camel@ipfire.org> (raw)
In-Reply-To: <8372c6ab-7668-42a2-ee22-b8867d4fbbb5@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hmm, why hasn't patchwork seen this patch?
On Wed, 2018-08-15 at 16:54 +0200, Peter Müller wrote:
> This updates Postfix to recent 3.3.x series, which contains
> some new features. Release announcement available at
> http://www.postfix.org/announcements/postfix-3.3.1.html
>
> The second version of this patch supersedes the first one,
> which contained crappy line wraps due to a bug in PGP/MIME
> implementation in MUA.
>
> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> ---
> lfs/postfix | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lfs/postfix b/lfs/postfix
> index 0fe4dfe08..07a869594 100644
> --- a/lfs/postfix
> +++ b/lfs/postfix
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 3.2.6
> +VER = 3.3.1
>
> THISAPP = postfix-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = postfix
> -PAK_VER = 15
> +PAK_VER = 16
>
> DEPS = ""
>
> @@ -66,7 +66,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = d10f1fb551be86f6e48c2908dd8a12ff
> +$(DL_FILE)_MD5 = 4381c6492f415e4a69cf5099d4acea76
>
> install : $(TARGET)
>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAlt0qo8ACgkQgHnw/2+Q
CQckmQ/9G91Q+4I45d4nEw/mQbTpKJObcCVEC5TNEWNLt+N4tkGFA/8+X8462rs5
9jAsIBKJdcagIioyT+z9GEVvNUFiz4U+o0AmA6laDdSuULrZhFC1Tjo2ygSIvp0c
ly0uaxtxjE14sV5kzYWzBPAIxFQix2UFTXiZ0JHyhS0Iq3truKu/6PHWWuWc+8uS
nlzVEL8+bLts4ag94FoPZdB5x4OFDH3IaJ0dPTpRJt6XlwAxqW+3Cl+RyJTrl1mz
ZwjPyJjw7OS7jltsEuKVcFGVWRVeqWPtXDt1J2CiYkfp8DLel3ugJQ2030F5WI6Z
0no3PO8ak0/ouThK466Z+MA+hKeqHw3WsLZOwjaVR6STTBAH4kvWtspYqmEhNZXa
Esi3m5UizvgBFTgMpUyZ86YOR+zI4lthkC0PiUKfHk0SWf/m4jyOWrIcJRnTl1iQ
j48hHb2CwURYvMDUTiy3ZoGhlC/5UQP+FBHo0UiytDT2lU265SFdRwp52p5uNfqm
FU9hUGpR3CO4t7DO+saYRO6/UKj6JTV9Cqv703ytGrp0iCQgFmqpT8p9hG1kCFju
UISza1w1xtpNJNtGECD8qsOHZ0Ut8Xb2JaMqDxQ6ZKWCLGDfH9P48LeXsO8TLpTb
TCzvAaQPBEx/EHKJYMrFt0NbWqk3+uJ5d89dcMQg9ltIWDgk47I=
=BbQB
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-08-15 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 14:54 Peter Müller
2018-08-15 22:34 ` Michael Tremer [this message]
2018-08-16 9:57 ` Michael Tremer
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=ccec10ae800fb92763aa2609d930533da9354333.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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