From: Mikhail Ramendik <mr@ramendik.ru>
To: Bart Oldeman <bartoldeman@users.sourceforge.net>
Cc: linux-msdos@vger.kernel.org
Subject: Problem with untarring dosemu-freedos-bin.tgz
Date: Fri, 26 Mar 2004 19:23:44 +0300 [thread overview]
Message-ID: <1080318223.5949.75.camel@localhost.localdomain> (raw)
Bart and list,
I have started to catch the problem that leads to a failing SRPM build.
Apparently, under some conditions,
tar --no-same-owner -xzpf dosemu-freedos-bin.tgz
or even:
tar -xzf dosemu-freedos-bin.tgz
produces a zero-length zero-permission file instead of every symlink.
And it also produces a number of lines line this:
tar: dosemu/freedos/bin/command.com: Cannot unlink: Permission denied
I found that this happens in some directories and not in others, while I
have full (rwx) access to any of them; running as normal user in both
cases.
I am now trying to pinpoint the exact situations in which this happens.
In fact, this may even be a bug in tar. (I am using GNU tar 1.13.25 from
ASP Linux, probably same as RH9; I could not find a later version, and
gnu.org just has 1.13).
Yours, Mikhail Ramendik
reply other threads:[~2004-03-26 16:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1080318223.5949.75.camel@localhost.localdomain \
--to=mr@ramendik.ru \
--cc=bartoldeman@users.sourceforge.net \
--cc=linux-msdos@vger.kernel.org \
/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