Created attachment 565800 [details] build.log Fails to emerge with this error: >>> Configuring source in /var/tmp/portage/mail-mta/postfix-3.3.2-r1/work/postfix-3.3.2 ... sed: -e expression #1, char 20: unknown option to `s' sed: -e expression #1, char 12: unknown option to `s' make -j5 makefiles shared=yes dynamicmaps=no pie=yes shlib_directory=/usr/lib64/postfix/MAIL_VERSION DEBUG= CC=x86_64-pc-linux-gnu-gcc 'OPT=-O2 -march=native -pipe -fuse-linker-plugin -flto -ftree-vectorize -ft$ make -f Makefile.in MAKELEVEL= Makefiles (echo "# Do not edit -- this file documents how Postfix was built for your machine."; /bin/sh makedefs) >makedefs.tmp ATTENTION: ATTENTION: Unknown system type: Linux 5.0.0-rc5 ATTENTION: make: *** [Makefile.in:31: Makefiles] Error 1 make: *** [Makefile:22: makefiles] Error 2
Reported upstream at http://postfix.1071664.n5.nabble.com/Support-for-quot-Linux-5-quot-td99786.html
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2e1f94e9569a9715073765e994e8db45ad63dc50 commit 2e1f94e9569a9715073765e994e8db45ad63dc50 Author: Eray Aslan <eras@gentoo.org> AuthorDate: 2019-02-21 15:30:14 +0000 Commit: Eray Aslan <eras@gentoo.org> CommitDate: 2019-02-21 15:30:14 +0000 mail-mta/postfix: bump to 3.4.0-RC2 Closes: https://bugs.gentoo.org/678362 Closes: https://bugs.gentoo.org/678326 Closes: https://github.com/gentoo/gentoo/pull/11099 Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Eray Aslan <eras@gentoo.org> mail-mta/postfix/Manifest | 2 +- mail-mta/postfix/files/postfix-linux-5.patch | 29 ++++++++++++++++++++++ ...pre20190129.ebuild => postfix-3.4.0_rc2.ebuild} | 16 ++++++++++-- 3 files changed, 44 insertions(+), 3 deletions(-)
Reopening as the commit closing this issue doesn't fix the issue. According to package.mask: # Eray Aslan <eras@gentoo.org> (08 Feb 2018) # Mask experimental software =mail-mta/postfix-3.4* Therefore, users (myself includes) won't get postfix-3.4.0_rc2 that you just added. Linux 5.0 will be out soon, the RCs are already available; therefore, this change should be made for postfix-3.3 as well.
I'll add it to postfix-3.3 if Linux-5 gets released before postfix-3.4
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7d2c60c0152907cbcaf9ab1f905d37713d026539 commit 7d2c60c0152907cbcaf9ab1f905d37713d026539 Author: Eray Aslan <eras@gentoo.org> AuthorDate: 2019-02-27 05:28:17 +0000 Commit: Eray Aslan <eras@gentoo.org> CommitDate: 2019-02-27 05:28:17 +0000 mail-mta/postfix: bump to 3.3.3 and fix compiling with Linux-5 Closes: https://bugs.gentoo.org/678326 Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Eray Aslan <eras@gentoo.org> mail-mta/postfix/Manifest | 1 + mail-mta/postfix/postfix-3.3.3.ebuild | 309 ++++++++++++++++++++++++++++++++++ 2 files changed, 310 insertions(+)
*** Bug 683854 has been marked as a duplicate of this bug. ***
*** Bug 684190 has been marked as a duplicate of this bug. ***
*** Bug 683064 has been marked as a duplicate of this bug. ***
*** Bug 685248 has been marked as a duplicate of this bug. ***
*** Bug 686524 has been marked as a duplicate of this bug. ***
*** Bug 686552 has been marked as a duplicate of this bug. ***
I observe only that 3.3.1-r1 is the last release marked stable. Perhaps 3.3.3 should be stabilized...?
Ya, current stable still exhibits this bug, either please add a depends-on for a stable req or backport the patch (and fast stable-req).
(In reply to Phil Stracchino (Unix Ronin) from comment #12) > I observe only that 3.3.1-r1 is the last release marked stable. Perhaps > 3.3.3 should be stabilized...? This is not a bug. You are mixing stable and unstable packages. Anyway, see bug #686586
(In reply to Eray Aslan from comment #14) > (In reply to Phil Stracchino (Unix Ronin) from comment #12) > > I observe only that 3.3.1-r1 is the last release marked stable. Perhaps > > 3.3.3 should be stabilized...? > > This is not a bug. You are mixing stable and unstable packages. > > Anyway, see bug #686586 uhm, wrong quote. was meant to reply comment #13. Sorry.
*** Bug 686674 has been marked as a duplicate of this bug. ***
*** Bug 686734 has been marked as a duplicate of this bug. ***
