[Bug bzip2/25164] New: bzgrep no longer handles multiple archives

[Bug bzip2/25164] New: bzgrep no longer handles multiple archives

[sourcewarebugz-20191105 at billmail dot scconsult.com]

https://sourceware.org/bugzilla/show_bug.cgi?id=25164

            Bug ID: 25164
           Summary: bzgrep no longer handles multiple archives
           Product: bzip2
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: bzip2
          Assignee: nobody at sourceware dot org
          Reporter: sourcewarebugz-20191105 at billmail dot scconsult.com
                CC: bzip2-devel at sourceware dot org
  Target Milestone: ---

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug bzip2/25164] bzgrep no longer handles multiple archives

[sourcewarebugz-20191105 at billmail dot scconsult.com]

https://sourceware.org/bugzilla/show_bug.cgi?id=25164

--- Comment #1 from Bill Cole <sourcewarebugz-20191105 at billmail dot scconsult.com> ---
Since the change at
https://sourceware.org/git/?p=bzip2.git;a=commit;f=bzgrep;h=d0b47bde0e2f5bae7502ca55b80ab006523db820
released with 1.0.8, running bzgrep with a list of files only searched the
first file. e.g.:

$ bzgrep foo /tmp/{3,2,1,0}.bz2
/tmp/3.bz2:foo
$ for x in {3..0} ; do printf "/tmp/$x.bz2: " ;bzgrep foo /tmp/$x.bz2; done
/tmp/3.bz2: foo
/tmp/2.bz2: foo
/tmp/1.bz2: foo
/tmp/0.bz2: foo

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug bzip2/25164] bzgrep no longer handles multiple archives

[mark at klomp dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=25164

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
Hi Bill,

Could you give some more information about your setup?
Which system are you running this on? What does /bin/sh point to?

It does seem to work for me as intended:
$ ~/src/bzip2/bzgrep foo /tmp/bar{0,1,2,3}.bz2
/tmp/bar0.bz2:foo
/tmp/bar1.bz2:foo
/tmp/bar2.bz2:foo
/tmp/bar3.bz2:foo

That is on both a system that has /bin/sh point to bash and on one that has
/bin/sh point to dash.

Thanks,

Mark

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug bzip2/25164] bzgrep no longer handles multiple archives

[vapier at gentoo dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=25164

Mike Frysinger <vapier at gentoo dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2021-04-11
     Ever confirmed|0                           |1

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug bzip2/25164] bzgrep no longer handles multiple archives

[sourcewarebugz-20191105 at billmail dot scconsult.com]

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.