On Thu, 9 Mar 2023 10:01:16 -0600
Dale wrote:
> Peter Humphrey wrote:
> > On Thursday, 9 March 2023 14:31:32 GMT Andreas Stiasny wrote:
> >
> >> You could try gztool
> >>
> >> https://github.com/circulosmeos/gztool/
> >>
> >> "gztool -T" should work like "tail -f".
> > That looks very handy.
On Thursday, 9 March 2023 16:01:16 GMT Dale wrote:
> Peter Humphrey wrote:
> > On Thursday, 9 March 2023 14:31:32 GMT Andreas Stiasny wrote:
> >> You could try gztool
> >>
> >> https://github.com/circulosmeos/gztool/
> >>
> >> "gztool -T" should work like "tail -f".
> >
> > That looks very
Peter Humphrey wrote:
> On Thursday, 9 March 2023 14:31:32 GMT Andreas Stiasny wrote:
>
>> You could try gztool
>>
>> https://github.com/circulosmeos/gztool/
>>
>> "gztool -T" should work like "tail -f".
> That looks very handy. But:
>
> Compiling it from the github source fails because I haven't
On Thu, 2023-03-09 at 15:49 +, Peter Humphrey wrote:
> Fetching a Debian compiled version and running deb2targz on it ends up with a
> .so file, which where to put?
app-arch/deb2targz exists. Would probably satisfy the need.
On Thursday, 9 March 2023 14:31:32 GMT Andreas Stiasny wrote:
>You could try gztool
>
> https://github.com/circulosmeos/gztool/
>
> "gztool -T" should work like "tail -f".
That looks very handy. But:
Compiling it from the github source fails because I haven't found all the
prerequisites.
On 09.03.23 08:46, Bryan Gardiner wrote:
Hi, thanks! --force and --stdout don't seem to help in this case.
Sorry, I was wrong. The problem is not the actual use of gunzip but the
fact that you are trying to decompress a file without reading it from
the beginning. Usually this is not
On Wed, 8 Mar 2023 14:13:35 +0100
Andreas Stiasny wrote:
> On 07.03.23 05:35, Bryan Gardiner wrote:
>
> > but the following hangs with no output:
> >
> > tail -c +1 -f build.log.gz | gunzip
>
> I think you should either use gunzip -f --stdout instead of just
> gunzip or use zcat.
>
>
Hi,
On Tue, 07 Mar 2023 09:01:34 +
Michael wrote:
> On Tuesday, 7 March 2023 07:52:01 GMT Mickaël Bucas wrote:
> > Le mar. 7 mars 2023 à 05:36, Bryan Gardiner a
> > écrit :
> > > Hi folks,
> > >
> > > How can I follow Portage's compressed build logs in real time as
> > > they are
On 07.03.23 05:35, Bryan Gardiner wrote:
but the following hangs with no output:
tail -c +1 -f build.log.gz | gunzip
I think you should either use gunzip -f --stdout instead of just gunzip
or use zcat.
Andreas
On Tuesday, 7 March 2023 07:52:01 GMT Mickaël Bucas wrote:
> Le mar. 7 mars 2023 à 05:36, Bryan Gardiner a écrit :
> > Hi folks,
> >
> > How can I follow Portage's compressed build logs in real time as they
> > are generated?
> >
> > I keep build logs and use FEATURES=compress-build-logs so
Le mar. 7 mars 2023 à 05:36, Bryan Gardiner a écrit :
>
> Hi folks,
>
> How can I follow Portage's compressed build logs in real time as they
> are generated?
>
> I keep build logs and use FEATURES=compress-build-logs so that they
> don't get too large. I can peek at how a build is going with
Hi folks,
How can I follow Portage's compressed build logs in real time as they
are generated?
I keep build logs and use FEATURES=compress-build-logs so that they
don't get too large. I can peek at how a build is going with zless on
build.log.gz, which doesn't update (understandably), but I
12 matches
Mail list logo
