all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Andreas Enge <andreas@enge.fr>
Cc: Felix Lechner <felix.lechner@lease-up.com>,
	guix-devel@gnu.org, 49817@debbugs.gnu.org
Subject: Re: [core-updates] It would be nice to fix libsndfile CVE-2021-3246 (arbitrary code execution via crafted WAV file)
Date: Wed, 5 Apr 2023 11:54:13 -0400	[thread overview]
Message-ID: <ZC2ZpfVjumeRviQ4@jasmine.lan> (raw)
In-Reply-To: <ZC01TQBgDyWGOCLA@jurong>

On Wed, Apr 05, 2023 at 10:46:05AM +0200, Andreas Enge wrote:
> Well, an update causes a lot of rebuilds anyway. The NEWS of 1.2.0 look
> like it is in fact only a bugfix release, so I took the risk to update to
> this latest version. pulseaudio still compiles, and pavucontrol still works
> on my machine.
> 
> The update is pushed to core-updates, but I would suggest to keep the bug
> open until it is merged to master.

Thank you Andreas!


  reply	other threads:[~2023-04-05 15:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05  2:48 [core-updates] It would be nice to fix libsndfile CVE-2021-3246 (arbitrary code execution via crafted WAV file) Leo Famulari
2023-04-05  3:13 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-05  8:06   ` Josselin Poiret
2023-04-05  8:46   ` Andreas Enge
2023-04-05 15:54     ` Leo Famulari [this message]
2023-04-05 16:19     ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-06 19:11       ` Commits and bug closing (was: something else) Andreas Enge
2023-04-07 10:27         ` Simon Tournier
2023-04-13  2:22           ` Commits and bug closing Maxim Cournoyer
2023-04-25 13:50     ` bug#49817: [core-updates] It would be nice to fix libsndfile CVE-2021-3246 (arbitrary code execution via crafted WAV file) Andreas Enge

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZC2ZpfVjumeRviQ4@jasmine.lan \
    --to=leo@famulari.name \
    --cc=49817@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.