From: "guillaume.audirac at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: bzip2-devel@sourceware.org
Subject: [Bug bzip2/25719] New: uncompress with soft and hard links
Date: Tue, 24 Mar 2020 15:15:32 +0000 [thread overview]
Message-ID: <bug-25719-11876@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25719
Bug ID: 25719
Summary: uncompress with soft and hard links
Product: bzip2
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bzip2
Assignee: nobody at sourceware dot org
Reporter: guillaume.audirac at gmail dot com
CC: bzip2-devel at sourceware dot org
Target Milestone: ---
Hi,
I've got issues with bzip2 when using symbolic and hard links (quite useful for
Yocto generated images).
I'm using Linux Mint 19.3 and bzip2 version 1.0.6 (6-sept-2010). I know the
latest release is 1.0.8 but I could not find any related info in git log
history.
# I have a bz2 file and soft and hard links to it.
$ ln -s my_file.bz2 my_softlink
$ ln my_file.bz2 my_hardlink
# Then I try to uncompress it through the symbolic link
$ bzip2 -d my_softlink
bzip2: Input file my_softlink is not a normal file.
# Now I try to uncompress it using the hard link
$ bzip2 -d my_hardlink
bzip2: Can't guess original name for my_hardlink -- using my_hardlink.out
bzip2: Input file my_hardlink has 1 other link.
For the 2 cases, using the -k option does not help.
For soft links, it would be nice to allow to follow the symlink with another
option, while keeping the input file ('-k').
For hard links, I assume it should work with '-k' when uncompressing.
Regards.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2020-03-24 15:15 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=bug-25719-11876@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=bzip2-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).