https://github.com/libical/libical/issues/603 Nothing for maintainer to do here, just tracking these. Can close when cleaned up.
> Nothing for maintainer to do here, just tracking these. Can close when > cleaned up. Oh, I lied, it could be backported, but I wouldn't say you have to.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9f829fb9b30d3bd85375fe57279d835abd21869d commit 9f829fb9b30d3bd85375fe57279d835abd21869d Author: Sam James <sam@gentoo.org> AuthorDate: 2022-10-10 21:36:05 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-10-10 21:36:28 +0000 dev-libs/libical: backport parsing regression fix; backport F_S=3 fix Closes: https://bugs.gentoo.org/876625 Closes: https://bugs.gentoo.org/876622 Signed-off-by: Sam James <sam@gentoo.org> .../files/libical-3.0.15-fortify-source-3.patch | 43 ++++++++ .../files/libical-3.0.15-revert-bad-fuzz-fix.patch | 36 +++++++ dev-libs/libical/libical-3.0.15-r1.ebuild | 119 +++++++++++++++++++++ 3 files changed, 198 insertions(+)
