On Feb 15 12:18, Christian Franke via Cygwin wrote:
> Corinna Vinschen via Cygwin wrote:
> > On Feb 14 14:14, Corinna Vinschen via Cygwin wrote:
> > > On Feb 14 13:49, Corinna Vinschen via Cygwin wrote:
> > > > On Feb 14 12:24, Christian Franke via Cygwin wrote:
> > > > > Hmm... does "beyond" mean
Corinna Vinschen via Cygwin wrote:
On Feb 14 14:14, Corinna Vinschen via Cygwin wrote:
On Feb 14 13:49, Corinna Vinschen via Cygwin wrote:
On Feb 14 12:24, Christian Franke via Cygwin wrote:
Hmm... does "beyond" mean '>=' or '>' ?
...do you think this fixes it?
diff --git a/winsup/cygwin/fha
On Fri, 14 Feb 2025 at 12:25, Christian Franke via Cygwin
wrote:
>
> Christian Franke via Cygwin wrote:
> > Testcase:
> >
> > $ uname -r
> > 3.5.7-1.x86_64
> >
> > $ cygcheck -f /bin/cp.exe
> > coreutils-9.6-1
> >
> > $ for i in 1 2 3; do cat /bin/cygwin1.dll > file$i; done
> >
> > $ compact /C fi
On Feb 14 14:14, Corinna Vinschen via Cygwin wrote:
> On Feb 14 13:49, Corinna Vinschen via Cygwin wrote:
> > On Feb 14 12:24, Christian Franke via Cygwin wrote:
> > > Hmm... does "beyond" mean '>=' or '>' ?
> >
> > ...do you think this fixes it?
> >
> > diff --git a/winsup/cygwin/fhandler/base.c
On Feb 14 13:49, Corinna Vinschen via Cygwin wrote:
> On Feb 14 12:24, Christian Franke via Cygwin wrote:
> > Hmm... does "beyond" mean '>=' or '>' ?
>
> ...do you think this fixes it?
>
> diff --git a/winsup/cygwin/fhandler/base.cc b/winsup/cygwin/fhandler/base.cc
> index 8f3dbd4ed51a..79dfaaa59
On Feb 14 12:24, Christian Franke via Cygwin wrote:
> Christian Franke via Cygwin wrote:
> > Testcase:
> > [...]
> > Upstream bug?
>
> Possibly not. A closer look shows that the main loop in copy.c:lseek_copy()
> expects that SEEK_DATA fails with ENXIO at EOF.
>
> https://github.com/coreutils/cor
Christian Franke via Cygwin wrote:
Testcase:
$ uname -r
3.5.7-1.x86_64
$ cygcheck -f /bin/cp.exe
coreutils-9.6-1
$ for i in 1 2 3; do cat /bin/cygwin1.dll > file$i; done
$ compact /C file2 # NTFS compression
... (1.7 : 1) ...
$ compact /C /EXE:LZX file3 # Compact OS LZX compression
... (2.8
Testcase:
$ uname -r
3.5.7-1.x86_64
$ cygcheck -f /bin/cp.exe
coreutils-9.6-1
$ for i in 1 2 3; do cat /bin/cygwin1.dll > file$i; done
$ compact /C file2 # NTFS compression
... (1.7 : 1) ...
$ compact /C /EXE:LZX file3 # Compact OS LZX compression
... (2.8 : 1) ...
$ stat -c '%b %s %n' file?
n/cp works without problems.
I think the issues here are:
1. Coreutils 9.5-1 /bin/cp erroneously assumes that a file is sparse
if the number of blocks is smaller than $((filesize / fs_blocksize)) -
but in this case the file is NOT sparse, just compressed.
2. The loop to copy a sparse file is faulty becau
typeset -a FileAttributes=(
> > FILE_ATTRIBUTE_ARCHIVE
> > FILE_ATTRIBUTE_COMPRESSED
> > )
> > )
> > snip
> >
> > If I remove the "FILE_ATTRIBUTE_COMPRESSED" flag /bin/cp works without
> > problems.
> > I thi
ously assumes that a file is sparse
if the number of blocks is smaller than $((filesize / fs_blocksize)) -
but in this case the file is NOT sparse, just compressed.
2. The loop to copy a sparse file is faulty because there are no holes
in that file. That itself is IMHO already a bad idea to hav
Michael Wild writes:
> Thanks, but until I get a running setup.exe I can't get a running
> Cygwin and only then I can get a running apt-cyg, right?
You only need a UPX executable, you can get it from upstream:
https://github.com/upx/upx/releases
And (somewhat uncharacteristically) they actually
On Tue, Jan 22, 2019 at 5:54 PM Brian Inglis wrote:
> > But how do I bootstrap? Can I just use the download from upx.github.io?
> > That'll be
> > what I try next then.
>
> apt-cyg install upx && man upx # ;^>
Thanks, but until I get a running setup.exe I can't get a running
Cygwin and only then
On 2019-01-21 14:12, Michael Wild wrote:
> On Mon, 21 Jan 2019, 20:55 Achim Gratz wrote:
>> Michael Wild writes:
>>> Thanks. I have very little hope of getting it whitelisted... Is UPX
>>> compression really a necessity? Otherwise I'll have to resort to my
>>> custom compiled versions.
>> No, t
On Mon, 21 Jan 2019, 20:55 Achim Gratz wrote:
> Michael Wild writes:
> > Thanks. I have very little hope of getting it whitelisted... Is UPX
> > compression really a necessity? Otherwise I'll have to resort to my
> custom
> > compiled versions.
>
> No, that's just so the download is smaller. Whic
Michael Wild writes:
> Thanks. I have very little hope of getting it whitelisted... Is UPX
> compression really a necessity? Otherwise I'll have to resort to my custom
> compiled versions.
No, that's just so the download is smaller. Which isn't the point if
you've built it yourself anyway… you co
On Mon, 21 Jan 2019, 18:19 Achim Gratz wrote:
> Michael Wild writes:
> > Anybody else experiencing this? I tried trawling through the mailing
> > list, but nothing specific turned up. Maybe this is an interaction
> > with the BLODA imposed on me by our company IT policy. But then I'd
> > expect ot
Michael Wild writes:
> Anybody else experiencing this? I tried trawling through the mailing
> list, but nothing specific turned up. Maybe this is an interaction
> with the BLODA imposed on me by our company IT policy. But then I'd
> expect others to have seen this issue too.
It wouldn't be the fir
new laptop, and surprisingly it worked. I then tried
the stripped version. Again, it worked. However, when I tried to run
the UPX compressed executable, I got the segfault again.
Anybody else experiencing this? I tried trawling through the mailing
list, but nothing specific turned up. Maybe this is
am; but I don't think anyone will want to take on a patch like that.
> It seems gunzip had no problem recognizing the file as double compressed.
No. Your manual gunzip removed one layer of compression, then your tar
command (with or without the 'z') ran a second gunzip to remove
> Date: Mon, 20 Apr 2015 16:38:49 -0700
> From: garyj...@spocom.com
> To: cygwin@cygwin.com
> Subject: Re: tar zxvf won't work with Redhat generated compressed tar file
>
> On 2015-04-20, Murthy Gandikota wrote:
>
>>>>
On 2015-04-20, Murthy Gandikota wrote:
> >> Then it looks like you have a DOUBLE-compressed file. That is, someone
> >> took a .tar.gz file, and ran THAT through gzip again (which seldom does
> >> anything except make a LARGER file - because the first round of
&
Greetings, Murthy Gandikota!
>>> anything except make a LARGER file - because the first round of
>>> compression removed any redundancy). Tar cannot read a
>>> double-compressed stream, but breaking things into two steps lets you
>>> get back to a single compre
> From: murth...@hotmail.com
> To: ebl...@redhat.com; cygwin@cygwin.com
> Subject: RE: tar zxvf won't work with Redhat generated compressed tar file
> Date: Mon, 20 Apr 2015 22:00:10 +
>
>
>
>
> Date: Mon, 20 Apr 2015 15:16:43 -0600
> From: ebl...@redhat.com
> To: cygwin@cygwin.com
> Subject: Re: tar zxvf won't work with Redhat generated compressed tar file
>
> On 04/20/2015 03:08 PM, Murthy Gandikota wrote:
>
&
ink it is actually a tar archive?
>> What
>>
>> gunzip> mytar < mytar.gz; file mytar
>>
>> says?
>>
> Sorry, didn't notice the top-posting here is the output to the command
>
> mytar: gzip compressed data, last modified: Tue Mar 24 03:50
> Date: Mon, 20 Apr 2015 23:50:36 +0300
> From: anrdae...@yandex.ru
> To: murth...@hotmail.com; cygwin@cygwin.com
> Subject: Re: tar zxvf won't work with Redhat generated compressed tar file
>
> Greetings, Murthy Gandikota!
&g
Greetings, Murthy Gandikota!
Please don't top-post. Thank you.
And please no cleartext emails in quoted text.
>>> I am using Cygwin64. I am getting a file from RedHat in tar + zip format.
>>> Currently I am able to unzip it and untar it in 2 steps as follows:
>>
>>> $gunzip mytar.gz
>>> $tar xvf
(My ancient
> CentOS box has it, though.)
GNU tar does NOT use compression libraries; rather, it shells out (via
an equivalent to popen()) to an external program. If you tell tar which
format a file was compressed in, it should try to use that compression
utility without questions; if you om
On 04/20/2015 02:06 PM, Eric Blake wrote:
> But I'd need to be able to reproduce the problem locally before I can
> provide an updated tar build for cygwin that fixes the problem.
As it is, it looks like I'm overdue for a tar build. cygwin tar is
still at 1.27.1, while upstream has released 1.28.
On 04/20/2015 12:40 PM, Murthy Gandikota wrote:
> Hi All
>
> I am using Cygwin64. I am getting a file from RedHat in tar + zip format.
> Currently I am able to unzip it and untar it in 2 steps as follows:
>
> $gunzip mytar.gz
> $tar xvf mytar
According to upstream, some
my provider
for a sample.
Thanks
> From: jlel...@pavlovmedia.com
> To: bertrand.cap...@chunkz.net; cygwin@cygwin.com; murth...@hotmail.com
> Subject: RE: tar zxvf won't work with Redhat generated compressed tar file
> Date: Mon, 20 Apr 2015 19:53:15 +
>
> The
The 'file' command isn't recursive. If you gzip a tar file, it will only say
it's a compressed file, it won't say it's a compressed tar file. See the
example I posted myself earlier in the thread.
I had theorized that the original file is zipped, not gzipped, a
r zxvf won't work with Redhat generated compressed tar file
>
>> Ran this command on Cygwin64
>>
>> $file mytar.gz
>> mytar.gz: gzip compressed data, from Unix
>>
>> Did you want me to run this command on Linux?
>>
>> Thanks
>
> Well as I
> Ran this command on Cygwin64
>
> $file mytar.gz
> mytar.gz: gzip compressed data, from Unix
>
> Did you want me to run this command on Linux?
>
> Thanks
Well as I said it's a gzip archive not a tar + gzip you can't extract it
with tar.
--
CHUNKZ.NET - scr
To: murth...@hotmail.com; cygwin@cygwin.com
> Subject: Re: tar zxvf won't work with Redhat generated compressed tar file
>
> Greetings, Murthy Gandikota!
>
>> Hi All
>
>> I am using Cygwin64. I am getting a file from RedHat in tar + zip format.
>> Currently I am able
Daniel writes:
> Murthy Gandikota wrote:
>> Hi All
>>
>> I am using Cygwin64. I am getting a file from RedHat in tar + zip format.
>> Currently I am able to unzip it and untar it in 2 steps as follows:
>>
>> $gunzip mytar.gz
>> $tar xvf mytar
>>
>> However, I would like to do the following:
>>
>
Greetings, Murthy Gandikota!
> Hi All
> I am using Cygwin64. I am getting a file from RedHat in tar + zip format.
> Currently I am able to unzip it and untar it in 2 steps as follows:
> $gunzip mytar.gz
> $tar xvf mytar
> However, I would like to do the following:
> $tar -zxvf mytar.gz
> The
Ran this command on Cygwin64
$file mytar.gz
mytar.gz: gzip compressed data, from Unix
Did you want me to run this command on Linux?
Thanks
> Date: Mon, 20 Apr 2015 21:18:09 +0200
> From: bertrand.cap...@chunkz.net
> To: cygwin@cygwin.com
>
Murthy Gandikota wrote:
Hi All
I am using Cygwin64. I am getting a file from RedHat in tar + zip format.
Currently I am able to unzip it and untar it in 2 steps as follows:
$gunzip mytar.gz
$tar xvf mytar
However, I would like to do the following:
$tar -zxvf mytar.gz
The error message I see
using, and what command(s) created the
> compressed tarball you're having difficulty with?
>
> If you run the 'file' command on the tarball file, what does 'file' say it
> contains?
>
> rake-0.8.4.tar.gz: gzip compressed data, last modified: Wed Mar
mmand(s) created the
compressed tarball you're having difficulty with?
If you run the 'file' command on the tarball file, what does 'file' say it
contains?
rake-0.8.4.tar.gz: gzip compressed data, last modified: Wed Mar 4 07:31:25
2009, from Unix
Note that some flavors
Got this message from my upstream Linux sender
Please try as well but I previously tried renaming the .tar to .tar.gz (this is
an old Linux issue - not knowing a .tar was compressed unless it had .gz too -
that I haven't seen required in years) - this had no i
> Did you mean tar zcvf ? It still doesn't work on RedHat and Cygwin64.
Yes, I meant this. What does not work ? Do you have a error message ?
--
CHUNKZ.NET - script kiddie and computer technician
Bertrand Caplet, Flers (FR)
Feel free to send encrypted/signed messages
Key ID: 37F70C30
GPG FP: 134
Did you mean tar zcvf ? It still doesn't work on RedHat and Cygwin64.
Thanks
> Date: Mon, 20 Apr 2015 20:44:56 +0200
> From: bertrand.cap...@chunkz.net
> To: cygwin@cygwin.com
> Subject: Re: tar zxvf won't work with Redhat generat
> tar xcvf archive.tar.gz your-files
I said tar xcvf for creating archive but it's tar zcvf my bad.
--
CHUNKZ.NET - script kiddie and computer technician
Bertrand Caplet, Flers (FR)
Feel free to send encrypted/signed messages
Key ID: 37F70C30
GPG FP: 134A 4027 518B 5F4D D409 558D BA9B 7BF0 37F7 0
Hey there,
It's not working because you're trying to decompress a tar + gzip
archive with tar zxvf but it's just a gzip archive.
If you first make a tar + gzip archive with :
tar xcvf archive.tar.gz your-files
and then :
tar zxvf archive.tar.gz
It will be ok :-)
Regards,
--
CHUNKZ.NET - scr
Hi All
I am using Cygwin64. I am getting a file from RedHat in tar + zip format.
Currently I am able to unzip it and untar it in 2 steps as follows:
$gunzip mytar.gz
$tar xvf mytar
However, I would like to do the following:
$tar -zxvf mytar.gz
The error message I see is:
tar: This does not l
Looks like I am hitting zip/gzip incompatibilities. :( thank you all.
-Original Message-
From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of
Vladimir Sakharuk
Sent: Monday, April 20, 2015 9:48 AM
To: cygwin@cygwin.com
Subject: zgrep: "gzip: invalid compr
How could I make zgrep work?
zgrep shows error on archive while
unzip -t
unzip
unzip -p|grep
work without problem
~>unzip -t aa.zip
Archive: aa.zip
testing: aaOK
No errors detected in compressed data of aa.zip.
4376671663 Jan 26 22:42 aa
386634752 Jan 28 16:21 aa.zip
Zgrep wo
On my proper unix/linux systems I do a lot of imaging work with .ppm.gz or
.ppm.bz2
files (binary 'P6' PPM, not the 'P3' ASCII version). The ImageMagick
utilities
(e.g display, convert) understand this format and it works well.
However, with Cygwin, having created an image.ppm.bz2 or image.ppm.gz
Christopher Faylor schrieb:
On Tue, Sep 14, 2004 at 10:33:43AM +0200, Reini Urban wrote:
Larry Hall schrieb:
At 05:01 PM 9/13/2004, you wrote:
If i compress a dir in the home directory using WinXP native compressing,
will it work with cygwin???
Yes. Compression is taken care of by Windows at a v
On Tue, Sep 14, 2004 at 10:33:43AM +0200, Reini Urban wrote:
>Larry Hall schrieb:
>>At 05:01 PM 9/13/2004, you wrote:
>>
>>>If i compress a dir in the home directory using WinXP native compressing,
>>>will it work with cygwin???
>>
>>
>>Yes. Compression is taken care of by Windows at a very low le
Larry Hall schrieb:
At 05:01 PM 9/13/2004, you wrote:
If i compress a dir in the home directory using WinXP native compressing,
will it work with cygwin???
Yes. Compression is taken care of by Windows at a very low level. Cygwin
is a layer over Windows. Cygwin will never know the difference.
B
At 05:01 PM 9/13/2004, you wrote:
>If i compress a dir in the home directory using WinXP native compressing,
>will it work with cygwin???
Yes. Compression is taken care of by Windows at a very low level. Cygwin
is a layer over Windows. Cygwin will never know the difference.
--
Larry Hall
If i compress a dir in the home directory using WinXP native compressing,
will it work with cygwin???
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
On Mon, Feb 10, 2003 at 12:03:48PM +0100, Ronald Landheer-Cieslak wrote:
>Hello all,
>
>During the daily update this morning, I saw a slight anomaly while running
>Setup. I've attached the setup log.
It's a known problem, reported multiple times previously.
cgf
--
Unsubscribe info: http://c
cygwin-apps, I apologize (but I haven't seen it
arrive there either, so I don't think it'll be the case)
setup.log.full.gz
Description: Compressed setup log
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.ht
<>
59 matches
Mail list logo
