From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Rodion Goritskov <rodion.goritskov@gmail.com>
Cc: 72799-done@debbugs.gnu.org, ashish.is@lostca.se
Subject: bug#72799: [PATCH 0/3] ffmpeg updates [fixes CVE-2024-7055, CVE-2024-7272]
Date: Tue, 12 Nov 2024 21:09:34 +0900 [thread overview]
Message-ID: <871pzg4ps1.fsf@gmail.com> (raw)
In-Reply-To: <87r0a5aeci.fsf@gmail.com> (Rodion Goritskov's message of "Sat, 31 Aug 2024 01:30:05 +0400")
Hello,
Rodion Goritskov <rodion.goritskov@gmail.com> writes:
> Hi!
>
> Patches apply and build fine.
>
> However, it looks like ffmpeg-4 and ffmpeg-6 triggers lots (~1000 for
> ffmpeg-4 and ~700 for ffmpeg-6) package rebuilds.
> ffmpeg-5 is fine, only 12 packages to be rebuild.
>
> Maybe ffmpeg-4 and ffmpeg-6 should be grafted (these CVEs looks scary) and patches for them send
> in the separate branch?
>
> Need some experienced maintainers to understand how it should be resolved.
It would have been better to build on a topic branch, but I've opted to
take a shortcut here and push directly to master for this time.
Closing!
--
Thanks,
Maxim
prev parent reply other threads:[~2024-11-12 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 0:34 [bug#72799] [PATCH 0/3] ffmpeg updates [fixes CVE-2024-7055, CVE-2024-7272] ashish.is--- via Guix-patches via
2024-08-25 0:39 ` [bug#72799] [PATCH 1/3] gnu: ffmpeg: Update to 6.1.2 [fixes CVE-2024-7055] ashish.is--- via Guix-patches via
2024-08-25 0:39 ` [bug#72799] [PATCH 2/3] gnu: ffmpeg-5: Update to 5.1.6 [fixes CVE-2024-7055, CVE-2024-7272] ashish.is--- via Guix-patches via
2024-08-25 0:39 ` [bug#72799] [PATCH 3/3] gnu: ffmpeg-4: Update to 4.4.5 [fixes CVE-2024-7055] ashish.is--- via Guix-patches via
2024-08-30 21:30 ` [bug#72799] [PATCH 0/3] ffmpeg updates [fixes CVE-2024-7055, CVE-2024-7272] Rodion Goritskov
2024-11-12 12:09 ` Maxim Cournoyer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871pzg4ps1.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=72799-done@debbugs.gnu.org \
--cc=ashish.is@lostca.se \
--cc=rodion.goritskov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).