From: Adam Porter <adam@alphapapa.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: [ELPA] Wrong dependency headers for Ement v0.4
Date: Mon, 24 Oct 2022 10:44:59 -0500 [thread overview]
Message-ID: <75b04605-f880-cfd3-3ee2-48603e741fab@alphapapa.net> (raw)
In-Reply-To: <85sfjfa7v0.fsf@elpa.gnu.org>
Hi Stefan, et al,
I've encountered a strange situation: I recently published v0.4 of
Ement. The describe-package command now shows this:
Package ement is incompatible.
Status: Incompatible because it depends on uninstallable packages.
Archive: gnu
Version: 0.4
Commit: b06c78d1ba700857330520bc796c5a29018b7ec5
Summary: Matrix client
Requires: emacs-27.1, map-2.1, plz-0.2, taxy-0.12.1 (not available),
taxy-magit-section-0.9, svg-lib-0.2.5, transient-0.3.7
Website: https://github.com/alphapapa/ement.el
However, these package headers do not match those in the listed commit,
i.e.
https://github.com/alphapapa/ement.el/blob/b06c78d1ba700857330520bc796c5a29018b7ec5/ement.el
shows:
;; Package-Requires: ((emacs "27.1") (map "2.1") (plz "0.2") (taxy
"0.9") (taxy-magit-section "0.9") (svg-lib "0.2.5") (transient "0.3.7"))
The package headers listed on ELPA correspond to a different commit I
added later, which had that mistake in it
(https://github.com/alphapapa/ement.el/commit/529c6b21e7e2c18d2dbcf35359829c3a907a41bc),
which I've since corrected on git master
(https://github.com/alphapapa/ement.el/commit/81caaae8fd33b67759bbd7403e3e98143acb2915).
I'd like to push a v0.4.1, just hoping that it would trigger ELPA to use
the correct dependency headers, but I've since pushed a v0.5-pre version
to git master, in which I'm preparing the next stable release, so I
can't make a v0.4.1 release for ELPA, since it reads from the same branch.
I could go ahead and release v0.5, but I was planning to work on it
more, to fix some bugs that I didn't want to release yet. So I'm not
sure what to do now.
Aside: This is one way in which MELPA is a bit easier to work with:
although MELPA Stable is generally not recommended for use (due to
various issues), it builds packages from version tags rather than git
master (regular MELPA builds from git master); if ELPA worked the same
way, I could easily tag a v0.4.1 independently of what's on the master
branch.
Given that, would it be possible to have ELPA build from a separate
branch? That's how I organize some of my other packages, with a
"stable" branch and a master branch. If ELPA pulled from a "stable"
branch, I could push a fix to that while the next major version is still
in development.
Thanks for your help.
Adam
next parent reply other threads:[~2022-10-24 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <85sfjfa7v0.fsf@elpa.gnu.org>
2022-10-24 15:44 ` Adam Porter [this message]
2022-10-24 20:51 ` [ELPA] Wrong dependency headers for Ement v0.4 Stefan Monnier
2022-10-27 17:46 ` Adam Porter
2022-10-27 20:18 ` Stefan Monnier
2022-10-27 20:28 ` Adam Porter
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=75b04605-f880-cfd3-3ee2-48603e741fab@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.