sox-devel@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Jan Stary <hans@stare.cz>
To: "Måns Rullgård" <mans@mansr.com>
Cc: sox-devel@lists.sourceforge.net
Subject: Re: upstream and bugfixes
Date: Tue, 7 Feb 2023 17:27:44 +0100	[thread overview]
Message-ID: <Y+J8APOM3P7MfIeL@www.stare.cz> (raw)
In-Reply-To: <yw1x7cwty2th.fsf@mansr.com>

On Feb 07 14:20:42, mans@mansr.com wrote:
> Jan Stary <hans@stare.cz> writes:
> 
> > Hi Mans,
> >
> > just to clear it up for myself:
> > https://sourceforge.net/p/sox/code/ci/master/tree/
> > is still the ultimate upstream, right?
> 
> Yes, that is the most current code.
> 
> > For reference: there is also
> > https://github.com/cbagwell/sox (last commit 2015, 4 issues, 2 PRs)
> > https://github.com/mansr/sox (forked, last 2017, 1PR, no issue tracker)
> > (and a bunch of nobody's forks of these of course, such as mine).
> >
> > These can be ignored when packaging downstream, right?
> 
> Right, packagers should ignore those.
> 
> > Are the commits in your GH fork included in the SF git?
> 
> Some, not all.  There are some things there of a more experimental
> nature that I'm not comfortable making official.
> 
> > What is currently the right way to report bugs and propose fixes?
> > Are diffs to this devel list the preffered way?
> 
> This list or the SF trackers are both fine by me.

OK, thanks for clearing that up.

> > Last commit to the SF git is May 2021; where should current fixes
> > such as https://marc.info/?l=oss-security&m=167546008232629&w=2 be sent?
> 
> I detest so-called security people and the way they handle their
> so-called vulnerabilities.  If they cared about anything other than
> their own egos, they'd try to engage constructively with the code
> authors/maintainers rather than filing CVE entries without asking or
> understanding, then sending menacing emails in private.

Well, the purpose of my message is precisely to engage constructively
about these patches. The original diffs (by Helmut Grohne)
https://marc.info/?t=167546017100001&r=1&w=2
were prepared against the Debian fork and do not apply to
the SF git master. They are then tweaked by Steffen Nurpmeso
to apply to the last commit of Sun May 9 21:17:32 2021
(which is what the OpenBSD audio/sox port is).

That seems like a good opportunity to get them in.
As a first attempt, here is the simplest of them:
when failing an open_read(), sox does not deallocate the comments.

diff --git a/src/formats.c b/src/formats.c
index 3fcf4382..5eda5e36 100644
--- a/src/formats.c
+++ b/src/formats.c
@@ -627,6 +627,7 @@ error:
   free(ft->priv);
   free(ft->filename);
   free(ft->filetype);
+  sox_delete_comments(&ft->oob.comments);
   free(ft);
   return NULL;
 }


	Jan



_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel

  reply	other threads:[~2023-02-07 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 13:31 upstream and bugfixes Jan Stary
2023-02-07 14:20 ` Måns Rullgård
2023-02-07 16:27   ` Jan Stary [this message]
2023-02-13  9:47     ` Jan Stary
2023-02-13 12:54   ` Jan Stary

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.sourceforge.net/lists/listinfo/sox-devel

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

  git send-email \
    --in-reply-to=Y+J8APOM3P7MfIeL@www.stare.cz \
    --to=sox-devel@lists.sourceforge.net \
    --cc=mans@mansr.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://80x24.org/mirrors/sox.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).