From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 40582 invoked by alias); 24 Jun 2019 09:34:24 -0000 Mailing-List: contact bzip2-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Sender: bzip2-devel-owner@sourceware.org Received: (qmail 40572 invoked by uid 89); 24 Jun 2019 09:34:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=picked, HX-Languages-Length:1594, Which, efforts X-Spam-Status: No, score=-6.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Message-ID: Subject: Re: [PATCH] bzip2: Fix return value when combining --test,-t and -q. From: Mark Wielaard To: Santiago Ruano =?ISO-8859-1?Q?Rinc=F3n?= Cc: bzip2-devel@sourceware.org, Anibal Monsalve Salazar , Anthony Fok , Federico Mena Quintero Date: Tue, 01 Jan 2019 00:00:00 -0000 In-Reply-To: <20190624083116.GN6125@bartik> References: <1561362056-4393-1-git-send-email-mark@klomp.org> <20190624083116.GN6125@bartik> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-2.el7) Mime-Version: 1.0 X-Spam-Flag: NO X-SW-Source: 2019-q2/txt/msg00006.txt.bz2 On Mon, 2019-06-24 at 10:31 +0200, Santiago Ruano Rinc=C3=B3n wrote: > For information, Federico Mena (in CC) is taking over the development > of > bzip2: https://people.gnome.org/~federico/blog/maintaining-bzip2.html >=20 > You should consider coordinating your efforts! Thanks. I assumed Federico was already on the bzip2-devel mailinglist. We did email earlier to discuss bzip2 maintenance and that all the infrastructure was already setup on the new sourceware.org bzip2 project. But it seems we did some duplicate work. Sorry for the miscommunication. It looks like we picked at least similar patches for the C sources, so those look mostly identical. I'll go over the remaining differences and try to cherry-pick or merge them into the bzip2 git repo. Some other files have been moved around, so it is harder to see whether we did the same for the manual and other docs. And I explicitly didn't touch the build system. I was looking at the autotools setup opensuse uses, but that also uses libtool which would mean changing the bzip.so verion/name. Which would be OK for Fedora and OpenSuse, since they already changed it long ago, but it would not be good for Debian, which uses the upstream libbz2.so.1.0 name. Also the buildbot, release scripts and the automatic updating of the homepage/manual is somewhat tied to the current setup. So I was thinking, first do a new 1.0.7 release with just the distro fixes and the updated project home, and then look at updating the rest of the build infrastructure. Cheers, Mark