From: Stefan Kangas <stefan@marxist.se>
To: comproprasad@gmail.com
Cc: 41000@debbugs.gnu.org
Subject: bug#41000: 28.0.50; Package file(.el) is 0 bytes after downloading
Date: Sun, 03 May 2020 22:15:13 +0200 [thread overview]
Message-ID: <87mu6o22su.fsf@stefankangas.se> (raw)
In-Reply-To: <f379b2a2ca30c78651796da9e25d8eff1336b53a.camel@gmail.com> (comproprasad@gmail.com's message of "Fri, 01 May 2020 20:09:44 +0530")
Hi,
comproprasad@gmail.com writes:
> After downloading a package using `package-install` or automatically at
> startup through `leaf` or `use-package`, I sometimes get an Emacs Lisp
> file of size 0 bytes only. When I try to use `M-x load-library
> zero-bytes-package` it loads fine but the related definitions(variables
> and functions) are not loaded into the interpreter i.e. `M-x` or `C-h
> v`
> or `C-h f`. The package manager is very dumb and only reports a void
> definition error when a related configuration is loaded at startup.
Thanks for the bug report.
Do you have a recipe for reproducing this issue? Or does it happen
only sporadically? Can you reproduce it under "emacs -Q"?
FWIW, I can't remember having seen anything like that myself.
> Suggestions:
>
> 1. There should be hash checking mechanism after package download so
> that a corrupted file can be detected earlier and can be
> re-downloaded.
Agreed, and for other reasons as well. See Bug#19565:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=19565
I have a patch there which no one has commented on. As soon as its
reviewed and any outstanding issues are addressed, it should only be a
matter of writing the documentation before it could go in, I think.
> 2. Another option would be to re-download a 0 bytes emacs lisp package.
> The issue would be that a partially downloaded package might go
> unnoticed which will be a rare case anyway. I haven't found such a
> case personally.
Yes, it would probably be a good idea to add a check for that. It
should be easier to do than the above, in any case.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-05-03 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 14:39 bug#41000: 28.0.50; Package file(.el) is 0 bytes after downloading comproprasad
2020-05-03 20:15 ` Stefan Kangas [this message]
2020-05-03 20:56 ` Noam Postavsky
2020-05-03 20:59 ` Stefan Kangas
2021-08-10 15:57 ` Lars Ingebrigtsen
2021-08-10 17:06 ` Compro Prasad
2021-08-11 11:07 ` Lars Ingebrigtsen
2021-08-11 11:38 ` Compro Prasad
[not found] ` <CAF5vbPmCoDV0TbytBL1xz4wz_BLiBmiA3MCTLEJHZa0kkKqj1w@mail.gmail.com>
[not found] ` <CADwFkm=pXfZzM_9Z71trmt3OfTNeTaY-YXC_g=4iFHYpSrw+fg@mail.gmail.com>
[not found] ` <CAF5vbPmvMt9C21L-gBbH1fuci32RYX35ZQZM5xY5WjEDDSZ57A@mail.gmail.com>
2021-08-24 14:29 ` bug#41000: Fwd: " Stefan Kangas
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=87mu6o22su.fsf@stefankangas.se \
--to=stefan@marxist.se \
--cc=41000@debbugs.gnu.org \
--cc=comproprasad@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.