unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: trentbuck@gmail.com, 52477@debbugs.gnu.org, stefan@marxist.se
Subject: bug#52477: 27.1; .crx and .crx3 are zip files
Date: Thu, 16 Dec 2021 11:22:08 +0200	[thread overview]
Message-ID: <83r1achpkv.fsf@gnu.org> (raw)
In-Reply-To: <87lf0l53mu.fsf@gmx.de> (message from Michael Albinus on Thu, 16 Dec 2021 09:56:57 +0100)

> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Thu, 16 Dec 2021 09:56:57 +0100
> Cc: "Trent W. Buck" <trentbuck@gmail.com>, 52477@debbugs.gnu.org
> 
> > The first couple of bytes of that files is "Cr24", while a normal zip
> > file starts with "PK".
> 
> Yes, and that's why libarchive(3) doesn't handle it. Sadly, I cannot add
> it to tramp-archive.el, therefore.
> 
> But there's no reason to prevent it from adding to arc-mode.el and/or
> dired-aux.el.

If the file doesn't follow the PKZip spec in the initial signature,
who knows what else in that spec doesn't it follow?  The ZIP spec has
a lot of special rules and formatting requirements, so if a file
doesn't follow them, how can we support it without knowing its exact
format specification?





  reply	other threads:[~2021-12-16  9:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14  4:56 bug#52477: 27.1; .crx and .crx3 are zip files Trent W. Buck
2021-12-15 20:51 ` Stefan Kangas
2021-12-16  8:56   ` Michael Albinus
2021-12-16  9:22     ` Eli Zaretskii [this message]
2021-12-16 11:59       ` Michael Albinus
2021-12-16 13:21         ` Eli Zaretskii
2021-12-19 13:09           ` Lars Ingebrigtsen
2021-12-22  3:50           ` Trent W. Buck
2021-12-22 12:20             ` Michael Albinus
2021-12-23  4:01               ` Trent W. Buck
2021-12-24 13:51                 ` Michael Albinus
2021-12-22 12:55             ` Eli Zaretskii

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r1achpkv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52477@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=stefan@marxist.se \
    --cc=trentbuck@gmail.com \
    /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/emacs.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).