From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] Build process stuck? Date: Mon, 25 Mar 2024 14:29:26 -0400 Message-ID: References: <7e1bb411-7f47-4c84-a710-537e594700a2@alphapapa.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40614"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Philip Kaludercic , emacs-devel To: Adam Porter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Mar 25 19:33:10 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rop89-000AEi-2E for ged-emacs-devel@m.gmane-mx.org; Mon, 25 Mar 2024 19:33:09 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rop6z-0007yd-8A; Mon, 25 Mar 2024 14:31:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rop6w-0007xl-5l for emacs-devel@gnu.org; Mon, 25 Mar 2024 14:31:54 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rop6s-0007Xq-JX for emacs-devel@gnu.org; Mon, 25 Mar 2024 14:31:53 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 8E90C441BB4; Mon, 25 Mar 2024 14:31:47 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1711391506; bh=ycE0SlancPmeOf6jCLkLlKWarf0rLGQr+bl3L8Gxvos=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=VtuqyQwjC9TklvlGerzlhDBundis4WN2FxMIoJR7QJOWUd/ssTELLTJBR73JN6gqe jYc9ZLPGRtfHh7pFSh0+dC/Ls+TShIaBS0T1r3kwZt9HTvfypPcVFrYeby0owL2KLU ghazBq5rm8sQTttAqtnyOsr/nqNABz5lmxOLU0imu/HtA+qMBZVikctPCsRfkXiqt+ f0/sKEdyIUz6YZz6t7tubixLrvqQz7hcrqcZQzl/Ffd71hK/f949FMKRA8VCp9aRdo SeKUXYeui6EKxcVpVi+nUK388U7aeb/0Iv8WwYQsuPkR0XWEgMaRkqian5P+3a1JFH r8Ge4dYoeng5w== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 4C9994417AF; Mon, 25 Mar 2024 14:31:46 -0400 (EDT) Original-Received: from lechazo (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 3FA7212025D; Mon, 25 Mar 2024 14:31:46 -0400 (EDT) In-Reply-To: <7e1bb411-7f47-4c84-a710-537e594700a2@alphapapa.net> (Adam Porter's message of "Mon, 25 Mar 2024 12:58:23 -0500") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:317286 Archived-At: > 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. The `listen` recipe is: (listen :url "https://github.com/alphapapa/listen.el" :doc "README.org") so there is no configured "release branch". >> 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. AFAICT the commit b76e5cc1b3f1d1b7e67e72eb1a5d52058f45cf84 was made on a branch, which is why `git log -L` isn't seeing it. Stefan