From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@infotropique.org>
Cc: 28972@debbugs.gnu.org
Subject: [bug#28972] [PATCH] gnu: Remove unrar.
Date: Tue, 24 Oct 2017 17:14:52 -0400 [thread overview]
Message-ID: <20171024211452.GB8739@jasmine.lan> (raw)
In-Reply-To: <20171024204032.ouumwcg6dyr2lvgo@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
On Tue, Oct 24, 2017 at 08:40:32PM +0000, ng0 wrote:
> > On Tue, Oct 24, 2017 at 10:09:00PM +0200, nee wrote:
> > > The closest replacement that I know is libarchive, it's not a
> > > commandline utility like unrar, but it is used in file-roller which can
> > > open some rars.
>
> The problem is "some".
Does anyone know what the problem is that prevents "some" from becoming
"all"?
File-roller is a graphical application, so it's not really a replacement
for unrar anyways, even if it could handle all the same files. Is there
really no command-line alternative to our buggy unrar?
> As I pointed out in the previous email, mc uses it.
> I personally use unrar for some files which are older than 15 years,
> but I'm okay with just taking our unrar and maintain it in my repository.
>
> The reason why I'm asking to reconsider until we have a replament is
> software such as mc. We can not[*] search every line of sourcecode
> of packages we have to see where unrar is implicitly used without
> a store reference.
Okay, thanks for this information. It's true that we can't effectively
search for this kind of command-line use.
We had mc packaged for a few years before unrar was added, so the fact
that mc can use unrar does not mean that we must keep unrar.
My opinion is that keeping unrar packaged even though it can be
exploited by attackers who can provide a crafted RAR file does not help
Guix users.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-24 21:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 18:52 [bug#28972] [PATCH] gnu: Remove unrar Leo Famulari
2017-10-24 19:07 ` ng0
2017-10-24 19:22 ` Adonay Felipe Nogueira
2017-10-24 19:29 ` ng0
2017-10-25 14:30 ` Ricardo Wurmus
2017-11-12 21:20 ` bug#28972: " Leo Famulari
2017-10-24 20:09 ` [bug#28972] " nee
2017-10-24 20:25 ` Leo Famulari
2017-10-24 20:40 ` ng0
2017-10-24 21:14 ` Leo Famulari [this message]
2017-10-24 20:36 ` ng0
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171024211452.GB8739@jasmine.lan \
--to=leo@famulari.name \
--cc=28972@debbugs.gnu.org \
--cc=ng0@infotropique.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).