public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Nicholas Wourms <nwourms@yahoo.com>
To: cygwin@cygwin.com
Subject: Re: 1.3.11(CVS): Tar and bug with utime()?
Date: Tue, 14 May 2002 08:57:00 -0000	[thread overview]
Message-ID: <20020514154029.74800.qmail@web21007.mail.yahoo.com> (raw)
In-Reply-To: <20020514161133.C2671@cygbert.vinschen.de>

Corinna,

They are, as you can see from the output of "tar -ztvf":
-r--r--r-- eggert/src    54232 2002-03-08 19:38:15 gzip-1.3.3/gzip.c
-r--r--r-- eggert/src    31686 1999-10-08 02:46:28 gzip-1.3.3/inflate.c
-r--r--r-- eggert/src      608 1999-10-06 01:01:31 gzip-1.3.3/lzw.c
-r--r--r-- eggert/src    40400 1999-10-06 01:00:00 gzip-1.3.3/trees.c
-r--r--r-- eggert/src     9223 1999-10-06 01:00:00 gzip-1.3.3/unlzh.c
-r--r--r-- eggert/src     8844 1999-11-11 12:57:25 gzip-1.3.3/unlzw.c
-r--r--r-- eggert/src     8170 1999-10-06 01:00:00 gzip-1.3.3/unpack.c
-r--r--r-- eggert/src     6241 1999-10-06 01:00:00 gzip-1.3.3/unzip.c
-r--r--r-- eggert/src    15275 2001-09-26 19:12:28 gzip-1.3.3/util.c
-r--r--r-- eggert/src     1571 2000-08-07 11:44:09 gzip-1.3.3/yesno.c
-r--r--r-- eggert/src     3221 1999-11-11 12:57:25 gzip-1.3.3/zip.c
-r--r--r-- eggert/src    18298 2002-03-08 19:49:50 gzip-1.3.3/gzip.texi
-r--r--r-- eggert/src       16 1999-10-08 02:20:08 gzip-1.3.3/gunzip.1
-r--r--r-- eggert/src     1296 1993-06-16 05:37:18 gzip-1.3.3/gzexe.1
-r--r--r-- eggert/src    15542 2001-11-04 02:52:59 gzip-1.3.3/gzip.1
-r--r--r-- eggert/src       16 1999-10-08 02:20:09 gzip-1.3.3/zcat.1
-r--r--r-- eggert/src       17 1999-10-08 02:20:09 gzip-1.3.3/zcmp.1

Cheers,
Nicholas

--- Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> On Tue, May 14, 2002 at 06:35:06AM -0700, Nicholas Wourms wrote:
> > After executing "tar -zxvf gzip-1.3.3.tar.gz", I get
> > 
> > gzip-1.3.3/lzw.h
> > tar: gzip-1.3.3/lzw.h: Cannot utime: Permission denied
> 
> Are the files given with R/O permissions in the tar archive?
> 
> Corinna
> 
> -- 
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Developer                                mailto:cygwin@cygwin.com
> Red Hat, Inc.
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 


__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2002-05-14 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14  7:11 Nicholas Wourms
2002-05-14  7:56 ` Corinna Vinschen
2002-05-14  8:57   ` Nicholas Wourms [this message]
2002-05-14  9:27     ` Corinna Vinschen
2002-05-14 10:11       ` Nicholas Wourms
2002-05-14 11:35         ` Corinna Vinschen
2002-05-14 18:03           ` Nicholas Wourms
2002-05-15  5:36             ` Corinna Vinschen
2002-05-15  6:04               ` Nicholas Wourms
2002-05-17  4:44                 ` Corinna Vinschen
2002-05-17  5:35                   ` Nicholas Wourms
2002-05-17  5:47                     ` Nicholas Wourms

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=20020514154029.74800.qmail@web21007.mail.yahoo.com \
    --to=nwourms@yahoo.com \
    --cc=cygwin@cygwin.com \
    /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).