From: "J.P." <jp@neverwas.me>
To: Visuwesh <visuweshm@gmail.com>
Cc: 72515@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Suhail Singh <suhailsingh247@gmail.com>
Subject: bug#72515: 29.4; describe-package-1: Wrong type argument: char-or-string-p
Date: Fri, 09 Aug 2024 11:03:42 -0700 [thread overview]
Message-ID: <87ed6xvaip.fsf@neverwas.me> (raw)
In-Reply-To: <87mslnigel.fsf@gmail.com> (Visuwesh's message of "Thu, 08 Aug 2024 13:40:26 +0530")
Visuwesh <visuweshm@gmail.com> writes:
> Eli Zaretskii wrote:
>
>>> From: Suhail Singh <suhailsingh247@gmail.com>
>>> Date: Wed, 07 Aug 2024 15:23:11 -0400
>>>
>>> Viewing the package description for a package that has two maintainers
>>> fails with the following error:
>>>
>>> describe-package-1: Wrong type argument: char-or-string-p
>>>
>>> This can be observed with emacs -Q. Steps to reproduce.
>>> - M-x list-packages
>>> - Navigate to csharp-mode from GNU ELPA
>>> - Press RET to view the package description
>>> - Observe error
>>
>> Thanks. I can reproduce this in Emacs 29, but not on the current
>> emacs-30 release branch, which will eventually become Emacs 30.1. So
>> I guess we fixed this bug already during development of Emacs 30.
>
> This is the same as bug#68288 and bug#72250 if I'm not wrong.
I'm not sure there's much meaningful daylight between these three and
68660 29.2; ELPA: Wrong type argument w. multiple maintainers in package-menu-mode
which addresses ELPA's end of the protocol bargain WRT package-archive
versioning and multiple maintainers. To me, they're really just two
sides of the same coin, so I've gone ahead and merged them (this and
bug#68660).
GNU ELPA should IMO remain backwards compatible with Emacs releases
currently packaged by mainstream GNU/Linux distributions, such as
Debian. Would-be ERC 5.6 users on Emacs versions 29 and below keep
running into this bug in the wild and will continue to do so for a good
while, it seems.
As I've expressed in bug#68660, I think ELPA should either migrate its
current web endpoint to a /v2 for Emacs 30.1's new format, or it should
revert to serving the infamous "concatenated" variant of the
:maintainers data item for everyone. (That's the old format with the
names of all maintainers mashed together along with all but the last
email address, which stands apart [1].)
[1] https://lists.gnu.org/archive/html/emacs-erc/2024-01/msg00051.html
next prev parent reply other threads:[~2024-08-09 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 19:23 bug#72515: 29.4; describe-package-1: Wrong type argument: char-or-string-p Suhail Singh
2024-08-08 5:08 ` Eli Zaretskii
2024-08-08 8:10 ` Visuwesh
2024-08-09 18:03 ` J.P. [this message]
2024-08-15 8:38 ` 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=87ed6xvaip.fsf@neverwas.me \
--to=jp@neverwas.me \
--cc=72515@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=suhailsingh247@gmail.com \
--cc=visuweshm@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).