From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS6130 216.105.38.0/24 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 12FFA1F5A0 for ; Tue, 7 Feb 2023 14:39:41 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=sourceforge.net header.i=@sourceforge.net header.a=rsa-sha256 header.s=x header.b=aqBKVro7; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=sf.net header.i=@sf.net header.a=rsa-sha256 header.s=x header.b=LeTMjZz4; dkim-atps=neutral Received: from [127.0.0.1] (helo=sfs-ml-1.v29.lw.sourceforge.com) by sfs-ml-1.v29.lw.sourceforge.com with esmtp (Exim 4.95) (envelope-from ) id 1pPP8D-0001Tr-8W; Tue, 07 Feb 2023 14:39:36 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-1.v29.lw.sourceforge.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1pPP8C-0001Tf-2m for sox-devel@lists.sourceforge.net; Tue, 07 Feb 2023 14:39:35 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version :Message-ID:In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=rR7vmeHMcpGdElvMgU9vJz0UFhrzNhczbtQbU0ninhU=; b=aqBKVro7IHT5yhAeltteK6HExF 1Up4oikdtw/3J/eoMn4Lxz2eMRM7N3ItTAie45fKrLJFramUMMXKUKFhUdTBRiHMSnavYZ1aisVDN T2ElDrmS8ex9nOKzxGTbVF0dAjJoi+MfRLc/GEE96y8Z16/EycLMwYuv4td2wfLE9s84=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=rR7vmeHMcpGdElvMgU9vJz0UFhrzNhczbtQbU0ninhU=; b=LeTMjZz4rhnYjgLltUZqYneVGt ySkHjksXkpSlO8iINVvRWyyzzDoKQkPwfEcB1Wq08JGydaQWyA4FtaKANk/neiQBYZEucdmCflLmD fWsHs8bkPDF72MWovaM9vQ0vu92RtBiHJBB1/7bNiBzcvF8TCnPJva8zXfT5lBeTSi1g=; Received: from unicorn.mansr.com ([81.2.72.234]) by sfi-mx-2.v28.lw.sourceforge.com with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.95) id 1pPP89-00047r-Mx for sox-devel@lists.sourceforge.net; Tue, 07 Feb 2023 14:39:35 +0000 Received: from raven.mansr.com (raven.mansr.com [81.2.72.235]) by unicorn.mansr.com (Postfix) with ESMTPS id 59D9D15360; Tue, 7 Feb 2023 14:20:42 +0000 (GMT) Received: by raven.mansr.com (Postfix, from userid 51770) id 35A8D221BB8; Tue, 7 Feb 2023 14:20:42 +0000 (GMT) From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= To: Jan Stary References: Date: Tue, 07 Feb 2023 14:20:42 +0000 In-Reply-To: (Jan Stary's message of "Tue, 7 Feb 2023 14:31:56 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Headers-End: 1pPP89-00047r-Mx Subject: Re: upstream and bugfixes X-BeenThere: sox-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: sox-devel@lists.sourceforge.net Cc: sox-devel@lists.sourceforge.net Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: sox-devel-bounces@lists.sourceforge.net Jan Stary 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. > The SF issues seem to be untouched for years. Send more time. > Last commit to the SF git is May 2021; where should current fixes > such as https://marc.info/?l=3Doss-security&m=3D167546008232629&w=3D2 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. > Also, last release was 8 years ago. Piling the patches > is starting to get cubersome when packaging downstream > - are there any plans for a release? I can slap a tag on the git repo and call it a day if that makes people happy. The process for creating the files comprising earlier releases is convoluted and probably broken in a million ways by now. -- = M=E5ns Rullg=E5rd _______________________________________________ SoX-devel mailing list SoX-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-devel