From: "sourcewarebugz-20191105 at billmail dot scconsult.com" <sourceware-bugzilla@sourceware.org>
To: bzip2-devel@sourceware.org
Subject: [Bug bzip2/25164] bzgrep no longer handles multiple archives
Date: Sat, 17 Apr 2021 07:07:39 +0000 [thread overview]
Message-ID: <bug-25164-11876-AwIRY1Hpia@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25164-11876@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25164
Bill Cole <sourcewarebugz-20191105 at billmail dot scconsult.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #3 from Bill Cole <sourcewarebugz-20191105 at billmail dot scconsult.com> ---
I apologize for the noise and the slow response.
The original failure was on a MacOS X 10.6.8 system where /bin/sh was a bespoke
build of bash 5.0.11, based on the MacPorts configuration but with all
libraries other than Apple's libSystem statically linked.
I am no longer able to reproduce this issue, despite retrieving old shell
histories and versions of bzgrep from backups. I am unable to reproduce the
environment and shell options, so I have to conclude that the issue was
grounded in some ephemeral configuration that was in effect at that time but I
have not been able to replicate now. It does not help that I apparently had at
that time at least 4 different scripts named 'bzgrep' which seem to have
descended from at least 2 different original sources.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-04-17 7:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug bzip2/25164] New: " sourcewarebugz-20191105 at billmail dot scconsult.com
2019-01-01 0:00 ` [Bug bzip2/25164] " sourcewarebugz-20191105 at billmail dot scconsult.com
2020-05-17 12:39 ` mark at klomp dot org
2021-04-11 15:10 ` vapier at gentoo dot org
2021-04-17 7:07 ` sourcewarebugz-20191105 at billmail dot scconsult.com [this message]
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-25164-11876-AwIRY1Hpia@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=bzip2-devel@sourceware.org \
/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.
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).