From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: ELPA ada-mode.release not updating
Date: Mon, 24 Oct 2022 19:38:02 -0700 [thread overview]
Message-ID: <86k04oiq5x.fsf@stephe-leake.org> (raw)
In-Reply-To: <jwvv8o916d8.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 24 Oct 2022 13:33:37 -0400")
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Stefan Monnier [2022-10-24 11:25:25] wrote:
>> Stephen Leake [2022-10-24 02:47:06] wrote:
>>> I pushed a commit to bump the version of ada-mode to 4.3.0 41 hours ago,
>>> but https://elpa.gnu.org/packages/ada-mode.html still shows 4.2.1.
>>> What's wrong?
>>
>> [ Hmm... I must be missing something. In my world,
>> https://elpa.gnu.org/packages/ada-mode.html shows version `7.2.1` and
>> elpa.git has version `7.3.beta1`. I'll assume some gremlin swapped
>> the 4 and 7 keys on your keyboard. ]
>>
>> We don't consider `7.3.beta1` as a "release", so elpa.gnu.org generated
>> a tarball only for GNU-devel.
>
> Oh, I think I understand what's going on. You're using
> a `:release-branch` thingy, but this specifies the release branch of the
> upstream Git repository, whereas `ada-mode` doesn't have an
> upstream repository.
>
> For packages with a nil `:url`, the `:release-branch` happens to act
> only as a boolean and the branch from which the code is fetched is
> always `externals-release/<PKG>` for GNU ELPA and `elpa-release/<PKG>`
> for NonGNU ELPA.
>
> For some reason, the fact that there is no such branch for `ada-mode`
> did not cause any error to be emitted in the cron job's reports :-(
Ok, I've pushed externals-release/ada-mode and externals-release/wisi,
and deleted the other branches.
Attached is a patch for README; ok to commit?
--
-- Stephe
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: readme.diff --]
[-- Type: text/x-patch, Size: 856 bytes --]
diff --git a/README b/README
index b0bb6fc67d..5d1b375e64 100644
--- a/README
+++ b/README
@@ -158,6 +158,14 @@ and only if the version number in the development branch indicates that it
contains development code (i.e. a "snapshot" version, according to
`version-to-list`).
+If there is no upstream (:url is nil), the presence of :release-branch
+just indicates that release and devel branches in elpa.git are desired
+(the name given in :release-branch is ignored). The release branch is
+named `externals-release/<pkg-name>' for GNU ELPA and
+`elpa-release/<pkg-name>` for NonGNU ELPA. The standard package branch
+externals/<pkg-name> is the devel branch in GNU ELPA; the standard
+branch elpa/<pkg-name> is the devel branch in non-GNU ELPA.
+
** =:ignored-files FILES=
Names of files or directories that should not be included in the tarballs.
next prev parent reply other threads:[~2022-10-25 2:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 9:47 ELPA ada-mode.release not updating Stephen Leake
2022-10-24 15:25 ` Stefan Monnier
2022-10-24 17:33 ` Stefan Monnier
2022-10-24 21:00 ` Stephen Leake
2022-10-25 2:38 ` Stephen Leake [this message]
2022-10-25 17:46 ` Stefan Monnier
2022-10-26 13:50 ` Stephen Leake
2022-10-26 15:04 ` Stefan Monnier
2022-10-26 19:00 ` Stephen Leake
2022-10-24 17:38 ` Stephen Leake
2022-10-24 21:12 ` Stefan Monnier
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=86k04oiq5x.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--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.