From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Broken patches (was: Re: [PATCH] Postfix: update to 3.3.1)
Date: Tue, 14 Aug 2018 09:05:52 +0100 [thread overview]
Message-ID: <4689504b297f765d50f13f751f83ad444cb7cc9d.camel@ipfire.org> (raw)
In-Reply-To: <4281151b-c8a3-289d-a80c-b3c6bc939c84@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 2635 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please see my email in the ET thread about this...
On Sat, 2018-08-11 at 18:16 +0200, Peter Müller wrote:
> Hello Michael,
>
> > Hello,
> > > Hi,
> > >
> > > this patch has the same issue as pciutils.
> >
> > same thing here. No idea what is going wrong.
>
> should I send in more patches (SSH hardening, etc. etc.)?
> Or do you want to investigate further what went wrong here?
>
> Thanks, and best regards,
> Peter Müller
> >
> > Best regards,
> > Peter Müller
> > >
> > > -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+QCQcFAltyjWAACgkQgHnw/2+Q
CQe2Bw/7BfdQLVx3f+6q0pmXfHBn450OMWJhbi0UJ/Vs9cuRSpF+QooiSQ6/2lub
M8qXloDY3+1qP0Rv8V6NnKs/eutzlsw0ESeIQzJuP9ESTgSGRbPEpVv3eQDn/Udl
zYnx2EArGJmVnWo8eV+5Z2XMapNQREP3aoNvOtHKkzAiQkCHQc14a0Bchp4GA7+9
FTHufxwHtsN1FxOdmU2w+k9erF1wEjX/Y74Jdnb8yQeyXPlN5kvdkZ8S2PFetQpN
UdJ0FgrL3zJgGgrR67thpLK6vrgEWrK6EovAnPoRiVnsTeijeLMGGeiXU/Ui3gf/
SUWGkR89y3P0f1wPnTbSj3E4fJimcilsy3foFt0aYnZIcx+TfWnjx0j/3NEkHBjp
jjzapaaQykxER74MtBYeKAA7Sc9cYTXB5KCE4lSt0MVf0MagUhYtYpfiKA9okzYw
pAkZAaWRx0FQMYVGlI8XTq7Wf11ZCBlNf3NCSuISKSWtOj8Rk0ZT4alVoBUGPIgj
cx7qtrqFgE8iY4WJGpXAsofrelvSkgPR/NnXGnRgvW9L3rCcWLkPk/jNnje4ts5G
3xsM213MBRpyoQcskZ/wEtOct0KNQkd+upGhKlll3Pzo4fk+frVWABl3ZvfcFSKi
ChXYO9Q+9g6QBEldqr0PaW3Ipja/Ynn5CkRCCzntFdRCvmUF3mw=
=E2iw
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2018-08-14 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 18:56 [PATCH] Postfix: update to 3.3.1 Peter Müller
2018-08-08 7:40 ` Michael Tremer
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 [this message]
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=4689504b297f765d50f13f751f83ad444cb7cc9d.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