Hi,
Since then:
- gpac was EOLd in buster
https://salsa.debian.org/debian/debian-security-support/-/commit/a0bfdf01d404aba46893d2971d776f8f7fb5337e
- gpac was removed from bookworm
https://tracker.debian.org/news/1430135/gpac-removed-from-testing/
- gpac was removed from sid
https://tracker.debian.org/news/1548977/removed-221dfsg1-31-from-unstable/
gpac in bullseye still has >100 open CVEs and I don't believe the
situation described by Roberto improved.
Do we want to mark gpac EOL for bullseye as well?
Cheers!
Sylvain Beucler
Debian LTS Team
From: Roberto C. Sánchez <robe...@debian.org>
Date: Fri, 20 May 2022 15:40:06 -0400
LTS and Security Teams,
Based on previous discussion [0], I have marked gpac as end-of-life for
stretch in commit 0a6147d6b8 of debian-security-support [1]. It seems
advisable that the Security Team do the same for gpac in buster and
bullseye.
Regards,
-Roberto
[0] https://lists.debian.org/debian-lts/2022/04/msg00008.html
[1]
https://salsa.debian.org/debian/debian-security-support/-/commit/0a6147d6b88d7c19ee7c072a344bbb63a7b1f32c
--
Roberto C. Sánchez
