Re: How about a roadmap?

[J.P.]

"J.P." <jp@neverwas.me> writes:

> [1] The problem is that package.el (on 28+, at least) does not like
>     packages reporting more than one maintainer. But that's what ELPA
>     describes ERC as having if you build a package from trunk. In
>     `package-menu-mode', clicking an offending package's name triggers
>     an error in `package--print-email-button': it expects a cons of two
>     strings (a name and an email) but gets a list of such conses
>     instead.
>
>     One makeshift solution would be to duct tape over the problem for
>     now with a bubblegum patch for elpa-admin.el, something like:
>
>       https://ttm.sh/tay
>
>     A lasting solution might be to fix the bugged package.el schema and
>     increment its version (and maybe provide a migration script in Emacs
>     28.2, although that's probably unnecessary). Of course, all this is
>     contingent on the assumption I'm using elpaa correctly, which may be
>     far from the truth.

Correction: nothing to see here. It seems ELPA somehow massages these
multi-maintainer specs, and I just failed to notice. Indeed, changing
your `package-archives' to

  (("devel" . "https://elpa.gnu.org/devel/";))

and browsing the latest lineup proves this. Apologies for the noise.