unofficial mirror
 help / color / mirror / code / Atom feed
From: David Runge <>
Subject: Re: Next release
Date: Thu, 23 May 2019 18:04:18 +0200	[thread overview]
Message-ID: <20190523160418.GH31716@dvzrv.localdomain> (raw)
In-Reply-To: <20181004173911.GC17559@dvzrv.localdomain>

[-- Attachment #1.1: Type: text/plain, Size: 1260 bytes --]

Hi again,

On 2018-10-04 19:39:11 (+0200), David Runge wrote:
> I'm happy to see, that there has been some activity for sox this year.
> I'm even more happy to see, that a lot of CVEs got fixed by patching it!
> Currently, I'm maintaining sox for Arch Linux. I'd love to see a new
> release, so I can drop all the extra patches soon.
> It would of course generally be awesome to have more frequent releases
> again! Is this a possibility for the current developers/maintainers? I
> know, that this is not really an easy task...
> Is there any ticket preventing a new release? If so, how can the process
> be helped?
as sox has now accumulated a total of twelve (!) CVEs for version 14.4.2
[1], I'd like to once more urge the current maintainers to tag a new

Given the maintenance burden of applying all of these patches (and the
numerous other bugfixes that have been added [2]) on top of the last
stable release in a packaging context, I would very much like to see a
new release.

Is there anything preventing it? Is there something that can be helped




[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

SoX-devel mailing list

  reply	other threads:[~2019-05-23 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 17:39 Next release David Runge
2019-05-23 16:04 ` David Runge [this message]
2019-08-31 23:31   ` David Runge
2019-09-02 11:17     ` Claude Warren
2019-09-03 15:41     ` Måns Rullgård

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

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

  git send-email \
    --in-reply-to=20190523160418.GH31716@dvzrv.localdomain \ \

* 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

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).