unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: Alex Branham <alex.branham@gmail.com>,
	28502@debbugs.gnu.org,
	Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#28502: 25.3; list-packages ends with "error in process filter: End of file during parsing"
Date: Mon, 21 Oct 2019 12:14:32 +0200	[thread overview]
Message-ID: <87y2xeo16f.fsf@web.de> (raw)
In-Reply-To: <CADwFkmno6mKBVZOxN4DDaXghDN8UR0BksdU3ZP3rBbv6OS5x=A@mail.gmail.com> (Stefan Kangas's message of "Mon, 21 Oct 2019 00:05:57 +0200")

Stefan Kangas <stefan@marxist.se> writes:

> The file you saw contained a package entry that was nil.  My guess is
> that this was due to an intermittent error on MELPA, since it was
> well-formed in all other respects.
>
> I don't think it's necessary to signal an error in this case.  We should
> just ignore nil entries.  On the other hand, it might indicate that
> something is wrong with the package archive, so it's nice to warn about
> it.
>
> I've installed the attached patch on master which does that.

If your assumption is correct, this seems like a reasonable fix.  Thank
you!

Michael.





  reply	other threads:[~2019-10-21 10:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 17:48 bug#28502: 25.3; list-packages ends with "error in process filter: End of file during parsing" Alex Branham
2017-09-27  0:45 ` Noam Postavsky
2017-09-27 13:43   ` Michael Heerdegen
2017-09-27 14:06     ` Alex Branham
2017-09-27 14:47       ` Michael Heerdegen
2017-09-27 14:50         ` Alex Branham
2017-09-29 14:34     ` Michael Heerdegen
2019-10-20 22:05 ` Stefan Kangas
2019-10-21 10:14   ` Michael Heerdegen [this message]
2019-10-21 11:50     ` Stefan Kangas
2019-10-21  1:27 ` Stefan Kangas
2019-11-29 13:00   ` 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

  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=87y2xeo16f.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=28502@debbugs.gnu.org \
    --cc=alex.branham@gmail.com \
    --cc=npostavs@users.sourceforge.net \
    --cc=stefan@marxist.se \
    /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).