Your message dated Fri, 28 Apr 2023 21:03:40 +0200
with message-id <[email protected]>
and subject line Re: Bug#1034798: RM: gpac/2.0.0+dfsg1-4
has caused the Debian Bug report #1034798,
regarding RM: gpac/2.0.0+dfsg1-4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1034798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034798
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: rm
X-Debbugs-Cc: [email protected], [email protected],
[email protected]
Control: affects -1 + src:gpac
In priot discussion between Reinhard, Sebastian and the Security team we've
come to the
conclusion that gpac isn't suitable to be included in a stable release. The
massive
influx of security issues makes that untenable (and there's no suitable LTS
branch
we could use, which e.g. makes ffmpeg manageable).
This removal hint needs to wait until x264 is unblocked (#1034653).
The only other rdep in ccextractor, which is already out of testing due to a
lack of
support for ffmpeg 5.
Cheers,
Moritz
--- End Message ---
--- Begin Message ---
On 2023-04-24 19:23:10 +0200, Moritz Muehlenhoff wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: rm
> X-Debbugs-Cc: [email protected], [email protected],
> [email protected]
> Control: affects -1 + src:gpac
>
> In priot discussion between Reinhard, Sebastian and the Security team we've
> come to the
> conclusion that gpac isn't suitable to be included in a stable release. The
> massive
> influx of security issues makes that untenable (and there's no suitable LTS
> branch
> we could use, which e.g. makes ffmpeg manageable).
>
> This removal hint needs to wait until x264 is unblocked (#1034653).
>
> The only other rdep in ccextractor, which is already out of testing due to a
> lack of
> support for ffmpeg 5.
Hint added. Thanks
Cheers
--
Sebastian Ramacher
--- End Message ---
