From: Philip Kaludercic <philipk@posteo.net>
To: Eshel Yaron <me@eshelyaron.com>
Cc: 59676@debbugs.gnu.org
Subject: bug#59676: 30.0.50; package-report-bug fails getting maintainer address
Date: Tue, 29 Nov 2022 21:17:47 +0000 [thread overview]
Message-ID: <87ilixbguc.fsf@posteo.net> (raw)
In-Reply-To: <m1fse2th2n.fsf@esmac.lan> (Eshel Yaron's message of "Tue, 29 Nov 2022 08:23:12 +0200")
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
Eshel Yaron <me@eshelyaron.com> writes:
> 1. emacs -Q
> 2. M-x list-packages
> 3. Move point to over some package, e.g. Magit
> 4. M-x package-report-bug
> 5. See error:
>
> package-maintainers: Wrong type argument: char-or-string-p, ("Jonas Bernoulli" . "jonas@bernoul.li")
Does the following fix it?
[-- Attachment #2: Type: text/plain, Size: 582 bytes --]
diff --git a/lisp/emacs-lisp/package.el b/lisp/emacs-lisp/package.el
index 8d44fae30a..8e7c34da38 100644
--- a/lisp/emacs-lisp/package.el
+++ b/lisp/emacs-lisp/package.el
@@ -4549,7 +4549,7 @@ package-maintainers
(user-error "Package `%s' has no explicit maintainer" name))
((and (not (progn
(require 'ietf-drums)
- (ietf-drums-parse-address maint)))
+ (ietf-drums-parse-address (cdr maint))))
(null no-error))
(user-error "Package `%s' has no maintainer address" name))
((not (null maint))
[-- Attachment #3: Type: text/plain, Size: 198 bytes --]
> On another note, seems package-report-bug could also benefit from an
> autoload cookie, no?
I think that would be a good idea, but I don't know if it is too late
now that Emacs 29 has been cut.
next prev parent reply other threads:[~2022-11-29 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 6:23 bug#59676: 30.0.50; package-report-bug fails getting maintainer address Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-29 21:17 ` Philip Kaludercic [this message]
2022-11-29 22:09 ` Eshel Yaron
2022-11-30 19:55 ` Philip Kaludercic
2022-11-30 20:20 ` Eshel Yaron
2022-11-30 20:39 ` Philip Kaludercic
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=87ilixbguc.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=59676@debbugs.gnu.org \
--cc=me@eshelyaron.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).