all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "J.P." <jp@neverwas.me>
Cc: Philip Kaludercic <philipk@posteo.net>,
	emacs-erc@gnu.org, Amin Bandali <bandali@gnu.org>,
	68660@debbugs.gnu.org
Subject: bug#68660: 29.2; ELPA: Wrong type argument w. multiple maintainers in package-menu-mode
Date: Wed, 14 Feb 2024 15:08:44 -0500	[thread overview]
Message-ID: <jwvmss2lsgn.fsf-monnier+emacs__15826.7192471371$1707941477$gmane$org@gnu.org> (raw)
In-Reply-To: <877cj6eu2t.fsf@neverwas.me> (J. P.'s message of "Wed, 14 Feb 2024 11:15:06 -0800")

OK, OK, I'll see if I can find some time&motivation to work on this.
It shouldn't be very hard,


        Stefan


J.P. [2024-02-14 11:15:06] wrote:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> "J.P." <jp@neverwas.me> writes:
>>
>>> Stefan has suggested renaming the `:maintainer' item in the `extras'
>>> slot of `package-desc' objects to `:maintainers' (plural). IIUC, this
>>> would have the effect of solving the issue by omitting the "Maintainer:"
>>> line item in *Help* buffers produced by `package-menu-describe-package'
>>> and friends for all packages on all Emacs versions below 30.1. 
>>
>> That also seems to be the best idea to me as well.
>
> Nice. And to be clear, by 'omitting the "Maintainer:" line', I meant
> only WRT the `describe-package' results in Emacs and (hopefully) not the
> web pages at http://elpa.gnu.org/packages/foo.html, etc.
>
>>
>>>                                                                Full
>>> remediation would, I think, also require that foo-pkg.el files and
>>> /archive-contents data hosted on elpa.gnu.org reflect the newer format.
>>
>> I am not familiar with ERC's infrastructure, shouldn't this happen
>> automatically?
>
> Yes, automatically. But I think elpa-admin would still need a shim, at
> least until such time as the Emacs running on the production instance is
> upgraded to 30.1 (or 29.3, if such a thing ever materializes). Not sure
> if it's Stefan or the GNU infra people who control this.
>
>>
>>> To help move this process along, Stefan has called for patches, but I
>>> unfortunately am unable to reciprocate because I lack the wherewithal.
>>> Hoping you're able to assist in this regard either directly, with code,
>>> or by pointing out specific areas in the Emacs code base (and possibly
>>> elpa-admin's as well) that would need addressing.
>>
>> I could help, but I don't understand what is going on well enough to
>> produce any concrete patches.
>
> Thanks. I myself don't understand the whole picture either, only what's
> readily apparent from observed behavior. I mean, I guess I can give it a
> shot, but I'll mostly be flying blind.
>
>>
>>> TIA,
>>> J.P.
>>>
>>> [1]
>>> https://lists.gnu.org/archive/html/bug-gnu-emacs/2024-01/msg01575.html






  parent reply	other threads:[~2024-02-14 20:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 14:56 bug#68660: 29.2; ELPA: Wrong type argument w. multiple maintainers in package-menu-mode J.P.
2024-01-22 15:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found] ` <jwvjzo11jh2.fsf-monnier+emacs@gnu.org>
2024-01-23 14:57   ` J.P.
     [not found]   ` <87o7dcm718.fsf@neverwas.me>
2024-01-23 19:48     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]     ` <jwvplxrx2be.fsf-monnier+emacs@gnu.org>
2024-01-23 22:34       ` J.P.
     [not found]       ` <87le8fisqg.fsf@neverwas.me>
2024-01-24  0:55         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]         ` <jwvv87jsgfz.fsf-monnier+emacs@gnu.org>
2024-01-24  1:22           ` J.P.
     [not found]           ` <87ede7frtz.fsf@neverwas.me>
2024-01-24 14:31             ` J.P.
     [not found]             ` <87y1ceby5w.fsf@neverwas.me>
2024-01-24 15:41               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]               ` <jwv5xziyc60.fsf-monnier+emacs@gnu.org>
2024-01-24 17:57                 ` J.P.
     [not found]                 ` <877cjyaa31.fsf@neverwas.me>
2024-01-27 20:30                   ` Amin Bandali
2024-01-31 19:24                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                   ` <jwvr0hxtinl.fsf-monnier+emacs@gnu.org>
2024-02-01  2:52                     ` J.P.
     [not found]                     ` <87ttmssxok.fsf@neverwas.me>
2024-02-14  1:58                       ` J.P.
     [not found]                       ` <87eddfg61t.fsf@neverwas.me>
2024-02-14 16:59                         ` Philip Kaludercic
     [not found]                         ` <87a5o3gexk.fsf@posteo.net>
2024-02-14 19:15                           ` J.P.
     [not found]                           ` <877cj6eu2t.fsf@neverwas.me>
2024-02-14 20:08                             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
     [not found]                             ` <jwvmss2lsgn.fsf-monnier+emacs@gnu.org>
2024-02-14 20:54                               ` J.P.

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='jwvmss2lsgn.fsf-monnier+emacs__15826.7192471371$1707941477$gmane$org@gnu.org' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=68660@debbugs.gnu.org \
    --cc=bandali@gnu.org \
    --cc=emacs-erc@gnu.org \
    --cc=jp@neverwas.me \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    /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.