From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Postfix: update to 3.3.1
Date: Wed, 08 Aug 2018 08:40:55 +0100 [thread overview]
Message-ID: <af4f5a05f92cb9df6fbff53069686745dae92abe.camel@ipfire.org> (raw)
In-Reply-To: <9c220f7f-95fa-f9b7-4efe-0d48e9745025@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
this patch has the same issue as pciutils.
- -Michael
On Tue, 2018-08-07 at 20:56 +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
>
> 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+QCQcFAltqnocACgkQgHnw/2+Q
CQfYsQ//W1cRFvjppG/EH4FRrR84Vf7fxqH5kWT3+zrZ4SB1VcLFrbeeV6mWDRwt
8S13GX+eBySWeJ7K9cgGsENM4Kap08Mx81fheCA80SOaqZx10z8iwIYwCU8rUnSH
N64SQyXV98pIoxLT8bVUEjFjjrwuCEmQHVlcRsqiwaiFvPga8aYPernom4D7+379
MOpmf2dilDYBtTj7s4evGkg0YzKkHd9onHbTK54+DbphO05X7lzeqnxL49sPRb30
aLIMVHIe0CI8rd9DcK+pxi2a3mJqhwHuHyYQneS9E7dyRyJAcXXRVeB1ht5tYSYW
ZQavI34tQqzXt8PzZ0CPnDdQmmXe/lePg8ucBtFBalwZJI0YsLmOR/bQ0uE/u6RJ
wuvH2iKH7zy1Mh4L6ObYeFhJTWxANOLuST7iz/iowK8yZe6Kp5JvqPD+smu0iim5
Sr/8WD/gA7RY3FY7ffK46Bztx9LIwNAeaMqOvJsXBTOosXRqSS2djs4ruGdyOAw/
87AK68GcSz17rHHjXbxQqK7HQ+hqBTRcLY4j8DKkPQP7ZpWYrC3sDD8pmBmdJnZ0
HRAb4SIIrjBY9A2vDpXF+pjeHIOfxX0EcNbuo6yh85dxMqrrtayso7us0kWRywAA
tGjvOkR7ixYCnHw9YmNcoz8WxZHNRWthAO3mM4oKx42eyJd1t/g=
=Euli
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-08-08 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 18:56 Peter Müller
2018-08-08 7:40 ` Michael Tremer [this message]
2018-08-08 16:19 ` Peter Müller
2018-08-11 16:16 ` Broken patches (was: Re: [PATCH] Postfix: update to 3.3.1) Peter Müller
2018-08-14 8:05 ` 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=af4f5a05f92cb9df6fbff53069686745dae92abe.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