From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 63236@debbugs.gnu.org
Subject: bug#63236: 29.0.90; loaddefs-generate not 100% backwards compatible
Date: Wed, 03 May 2023 14:21:05 +0300 [thread overview]
Message-ID: <83bkj1mzj2.fsf@gnu.org> (raw)
In-Reply-To: <871qjxlseb.fsf@gmail.com> (message from Robert Pluim on Wed, 03 May 2023 10:40:28 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Date: Wed, 03 May 2023 10:40:28 +0200
>
> >>>>> On Tue, 02 May 2023 19:06:14 +0200, Robert Pluim <rpluim@gmail.com> said:
>
> Robert> I attempted to upgrade my packages today using `list-packages', which
> Robert> errored out when regenerating the autoloads for vlf-write.el:
>
> Robert> Debugger entered--Lisp error: (search-failed "\n\f\n;;;")
> Robert> search-forward("\n\f\n;;;")
> Robert> loaddefs-generate("/home/rpluim/.emacs.d/elpa/vlf-20191126.2250" "/home/rpluim/.emacs.d/elpa/vlf-20191126.2250/vlf-a..." nil "(add-to-list 'load-path (or (and load-file-name (f...")
> Robert> package-generate-autoloads(vlf "/home/rpluim/.emacs.d/elpa/vlf-20191126.2250")
>
> The minimal patch I can come up with is this, which seems safe enough
> but Iʼd appreciate it if someone who knows the code could comment
Can you describe what was special in your use case, and explain why
the original code didn't work in that case?
Thanks.
next prev parent reply other threads:[~2023-05-03 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 17:06 bug#63236: 29.0.90; loaddefs-generate not 100% backwards compatible Robert Pluim
2023-05-03 8:40 ` Robert Pluim
2023-05-03 8:48 ` Andreas Schwab
2023-05-03 11:21 ` Eli Zaretskii [this message]
2023-05-03 13:47 ` Robert Pluim
2023-05-03 15:02 ` Robert Pluim
2023-05-03 15:50 ` Eli Zaretskii
2023-05-04 8:45 ` Robert Pluim
2023-05-04 10:42 ` Eli Zaretskii
2023-05-04 14:04 ` Robert Pluim
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=83bkj1mzj2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63236@debbugs.gnu.org \
--cc=rpluim@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).