unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Philip Kaludercic <philipk@posteo.net>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] Build process stuck?
Date: Mon, 25 Mar 2024 12:58:23 -0500	[thread overview]
Message-ID: <7e1bb411-7f47-4c84-a710-537e594700a2@alphapapa.net> (raw)
In-Reply-To: <jwvr0fyfdg3.fsf-monnier+emacs@gnu.org>


Hi Stefan,

On 3/25/24 12:08, Stefan Monnier wrote:
>> A few days ago I pushed v0.8.1 of listen.el, and I see that ELPA has pulled
>>    those changes, yet the version available on ELPA remains v0.8. Is the
>>   build process stuck?
> 
> I don't see any version 0.8.1 in the history.  `C-x v h` tells me:
> 
>      commit 6bca5d6c764ef69b4a66ee9dc74bed678fe8cb87
>      Author: Adam Porter <adam@alphapapa.net>
>      Date:   Wed Mar 20 21:29:56 2024 -0500
>      
>          Meta: v0.9-pre

Thanks for checking on this.  I don't know what the problem is, then. 
At 
<https://lists.gnu.org/archive/html/emacs-elpa-diffs/2024-03/msg01417.html> 
it shows that the commit which updated the version header was pulled in.

And the latest commit on the configured release branch for ELPA is 
b76e5cc1b3f1d1b7e67e72eb1a5d52058f45cf84, which is the one that updates 
the version header to 0.8.1.

> So I'm not surprised `elpa.gnu.org` didn't see any 0.8.1 release
> either.
As far as I can tell, I've done what I'm supposed to do; it's always 
worked before.

--Adam



  reply	other threads:[~2024-03-25 17:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 14:18 [ELPA] Build process stuck? Adam Porter
2024-03-25 17:08 ` Stefan Monnier
2024-03-25 17:58   ` Adam Porter [this message]
2024-03-25 18:29     ` Stefan Monnier
2024-03-25 19:43       ` Adam Porter
2024-03-25 21:39         ` Stefan Monnier
2024-03-25 22:06           ` Adam Porter
2024-03-25 22:13             ` 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

  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=7e1bb411-7f47-4c84-a710-537e594700a2@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=emacs-devel@gnu.org \
    --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 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).