-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Alan Hourihane on 10/27/2005 3:30 AM: > Now, having upgraded everything to the latest releases things started to > go wrong with the packaging scripts. > > tar started to bleat with "Cannot stat: No such file or directory" for > lots of different things.
Can you reproduce this down into a smaller test case? Tar is only printing the error message it gets from calling stat(), so now we need to figure out if tar is passing bad information to stat() or if cygwin is having problems doing the stat(). If you can reproduce a smaller testcase, it might also help to run strace between the two versions to see what might have changed in the sequence of syscalls. > > I've reverted to tar 1.13.25 and everything is fine. > > One other thing to note is that I'm building on a samba connected drive > if that matters to tar. I don't have access to a samba drive myself, so if it IS drive related (although I am inclined to doubt that), it will be up to you to do a lot of the debugging effort. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] volunteer cygwin tar maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDYMfC84KuGfSFAYARAgnhAJ9Z4pN1D4KGfq2mmzCsmg9h7DTYLACfZhBU wuTQwH0/TgzbXl4GXoNKgU0= =1Nom -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
