From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 74B093857345 for ; Tue, 19 Apr 2022 21:36:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 74B093857345 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (deer0x09.wildebeest.org [172.31.17.139]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 234D130003AA; Tue, 19 Apr 2022 23:36:51 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 112BB2E8192A; Tue, 19 Apr 2022 23:36:51 +0200 (CEST) Date: Tue, 19 Apr 2022 23:36:50 +0200 From: Mark Wielaard To: Helge Kreutzmann Cc: bzip2-devel@sourceware.org Subject: Re: Errors in man pages of bzip2 Message-ID: References: <20220205103540.GA5411@Debian-50-lenny-64-minimal> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220205103540.GA5411@Debian-50-lenny-64-minimal> X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, KAM_NUMSUBJECT, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: bzip2-devel@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bzip2-devel mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2022 21:36:55 -0000 Hi Helge, Sorry for the late reply. On Sat, Feb 05, 2022 at 11:35:40AM +0100, Helge Kreutzmann wrote: > Finally the issues I'm reporting have accumulated over time and are > not always discovered by me, so sometimes my description of the > problem my be a bit limited - do not hesitate to ask so we can clarify > them. > > I'm now reporting the errors for your project. If future reports > should use another channel, please let me know. If you could file future issues in bugzilla: https://sourceware.org/bugzilla/enter_bug.cgi?product=bzip2 Then there is an archive. But sending reports to this list is also fine. > Man page: bzdiff.1 > Issue: missing markup (B< >) > > "cmp(1), diff(1), bzmore(1), bzless(1), bzgrep(1), bzip2(1)" I don't understand what is wrong here. > -- > Man page: bzexe.1 > Issue: markup of the command: B > > "The I utility allows you to compress executables in place and have " > "them automatically uncompress and execute when you run them (at a penalty in " > "performance). For example if you execute ``bzexe /bin/cat'' it will create " > "the following two files:" I believe bzexe is a Debian extension that isn't part of bzip2 as we ship it. > -- > Man page: bzexe.1 > Issue: markup of file names: I<> > > "/bin/cat~ is the original file and /bin/cat is the self-uncompressing " > "executable file. You can remove /bin/cat~ once you are sure that /bin/cat " > "works properly." As above. > -- > Man page: bzexe.1 > Issue: missing markup (B< >) > > msgid "bzip2(1), znew(1), zmore(1), zcmp(1), zforce(1)" As above. > -- > Man page: bzgrep.1 > Issue: missing markup (B< >) > > "grep(1), egrep(1), fgrep(1), bzdiff(1), bzmore(1), bzless(1), bzip2(1)" Again, I don't understand the issue here. > -- > Man page: bzip2.1 > Issue: I → I, > > "Unlike I I will not create a cascade of I<.bz2> suffixes " > "even when using the I<--force> option:" This phrase isn't in our variant of the bzip2.1 man page. > -- > Man page: bzmore.1 > Issue: missing markup (B< >) > > "more(1), less(1), bzip2(1), bzdiff(1), bzgrep(1)" This is like above, I don't really understand what is wrong with the way we use SEE ALSO in the manpages. Thanks, Mark