[arch-general] [anikom15@gmail.com: odd compress command]
I don't think my previous email went through. I apologize and disregard if it did. Here is the original message: ----- Forwarded message from Westley Martínez <anikom15@gmail.com> ----- Date: Sun, 4 Sep 2011 00:44:46 -0700 From: Westley Martínez <anikom15@gmail.com> To: arch-general@archlinux.org Subject: odd compress command User-Agent: Mutt/1.5.21 (2010-09-15) Hello, on my [Arch] system the compress program is actually a wrapper to gzip. This has caused a test to fail for Python <http://bugs.python.org/issue11340>. The bug is quite old but it is still relevant and I've been working on fixing it. I'd like to ask if anyone knows exactly why Arch's compress program outputs .gz files and not .Z files. I honestly could not find any information concerning its history or its rationale, and I come to this mailing-list as a last resort. Likewise, I think it would be appropriate to adopt the true compress program or not include a compress command at all, because, as you can see, problems have been created. ----- End forwarded message -----
On Tue, Sep 6, 2011 at 1:44 PM, Westley Martínez <anikom15@gmail.com> wrote:
I don't think my previous email went through. I apologize and disregard if it did. Here is the original message:
----- Forwarded message from Westley Martínez <anikom15@gmail.com> -----
Date: Sun, 4 Sep 2011 00:44:46 -0700 From: Westley Martínez <anikom15@gmail.com> To: arch-general@archlinux.org Subject: odd compress command User-Agent: Mutt/1.5.21 (2010-09-15)
Hello, on my [Arch] system the compress program is actually a wrapper to gzip. This has caused a test to fail for Python <http://bugs.python.org/issue11340>. The bug is quite old but it is still relevant and I've been working on fixing it. I'd like to ask if anyone knows exactly why Arch's compress program outputs .gz files and not .Z files.
It's a symlink /bin/compress -> gzip. I assume the gzip binary is intended to behave as `compress` when it's called as `compress`. Yet it fails to do so, i.e. it's a bug in gzip, IMO.
I honestly could not find any information concerning its history or its rationale, and I come to this mailing-list as a last resort. Likewise, I think it would be appropriate to adopt the true compress program or not include a compress command at all, because, as you can see, problems have been created.
----- End forwarded message -----
On Tue, Sep 6, 2011 at 3:51 PM, lolilolicon <lolilolicon@gmail.com> wrote:
It's a symlink /bin/compress -> gzip. I assume the gzip binary is intended to behave as `compress` when it's called as `compress`. Yet it fails to do so, i.e. it's a bug in gzip, IMO.
Hmm, according to the PKGBUILD, the symlink is created by the Arch package, not by upstream: ln -sf ${pkgname} compress Weird, and why?
Am 06.09.2011 07:44, schrieb Westley Martínez:
I don't think my previous email went through. I apologize and disregard if it did. Here is the original message:
This symlink has been created in PKGBUILD for as long as our history dates back. It seems wrong anyway. Open a bug report, please.
On Tue, Sep 6, 2011 at 4:54 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Am 06.09.2011 07:44, schrieb Westley Martínez:
I don't think my previous email went through. I apologize and disregard if it did. Here is the original message:
This symlink has been created in PKGBUILD for as long as our history dates back. It seems wrong anyway. Open a bug report, please.
I did it, https://bugs.archlinux.org/task/25908
participants (3)
-
lolilolicon
-
Thomas Bächler
-
Westley Martínez