files/dunst-1.6.1-no-Os.patch fails to apply to recent code due to change in DEFAULT_CFLAGS - it got appended ${EXTRA_CFLAGS} IMHO - there's little sence in overriding default flags if CFLAGS from env override them. Reproducible: Always
Created attachment 709911 [details] build.log + emerge --info.txt Even if it's obvious, please still attach build.log + emerge --info for build failures next time.
If the "PATCHES" line from the ebuild is removed , it builds fine and it works fine
Created attachment 719433 [details] build.log
Created attachment 719436 [details] emerge --info
Created attachment 723997 [details, diff] Patch fixing the bug
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=67223872158b0a243523fb9aacefed3233dbd4fa commit 67223872158b0a243523fb9aacefed3233dbd4fa Author: Thomas Schneider <qsx@chaotikum.eu> AuthorDate: 2021-07-15 11:56:48 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2021-07-16 09:51:44 +0000 x11-misc/dunst: Use sed instead of patch file in -9999 This way it won’t fail when config.mk changes upstream. Closes: https://bugs.gentoo.org/790854 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Thomas Schneider <qsx@chaotikum.eu> Signed-off-by: Joonas Niilola <juippis@gentoo.org> x11-misc/dunst/dunst-9999.ebuild | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
