Hi Enrico,
regarding the content of d/changelog only. I think it is good
and can be uploaded.
I am not sure, whether the mention "CVE-2021-3566" in
d/changelog will be parsed and this CVE will unintentionally
be closed again in the security database. Please double-check
when you generate DLA.
Be
On Wed, May 04, 2022 at 01:27:29PM +0200, Enrico Zini wrote:
> On Wed, May 04, 2022 at 12:24:22PM +0200, Thijs Kinkhorst wrote:
> > Maybe we should just remove it from the instructions? One less hoop for
> > people to jump through and it does not add any real value.
> Thank you and Moritz! I filed
On Wed, May 04, 2022 at 12:24:22PM +0200, Thijs Kinkhorst wrote:
> Maybe we should just remove it from the instructions? One less hoop for
> people to jump through and it does not add any real value.
Thank you and Moritz! I filed a bug to developers-reference with
attached patch to remove that li
On Wed, May 4, 2022 12:03, Moritz Muehlenhoff wrote:
> Hi Enrico,
>
>> in the Developers's reference[1] it says, in boldface, that security
>> updates should be built with "urgency=high".
>
> This is incorrect advice and I have idea where it came from. The urgency
> is completely irrelevant for any
Hi Enrico,
> in the Developers's reference[1] it says, in boldface, that security
> updates should be built with "urgency=high".
This is incorrect advice and I have idea where it came from. The urgency
is completely irrelevant for any security upload to LTS/oldstable/stable,
only for testing-secu
Hello,
in the Developers's reference[1] it says, in boldface, that security
updates should be built with "urgency=high".
In ffmpeg's changelog[2] however, everything is urgency=medium.
The LTS/Development wiki page does not mention urgency values.
Should I:
* assume previous ffmpeg uploads use
