From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Phil Sainty Newsgroups: gmane.emacs.bugs Subject: bug#49855: Problem with GNU ELPA build of :core package (Re: [GNU ELPA] So-Long version 1.1) Date: Thu, 05 Aug 2021 00:31:20 +1200 Message-ID: <532c06a4ff892539bc35868acd2fa0d6@webmail.orcon.net.nz> References: <85czqu2qdw.fsf@elpa.gnu.org> <2d94e1d983f91e0322747a86e7a6bcc9@webmail.orcon.net.nz> <87czqteik6.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1540"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Orcon Webmail Cc: 49855@debbugs.gnu.org, monnier@iro.umontreal.ca To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Aug 04 14:32:10 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1mBG4A-0000E0-GP for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 04 Aug 2021 14:32:10 +0200 Original-Received: from localhost ([::1]:57016 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mBG48-000580-AR for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 04 Aug 2021 08:32:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37000) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mBG42-00057q-WC for bug-gnu-emacs@gnu.org; Wed, 04 Aug 2021 08:32:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:59755) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mBG42-0000iz-JG for bug-gnu-emacs@gnu.org; Wed, 04 Aug 2021 08:32:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mBG42-0003IG-Gh for bug-gnu-emacs@gnu.org; Wed, 04 Aug 2021 08:32:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Phil Sainty Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 04 Aug 2021 12:32:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 49855 X-GNU-PR-Package: emacs Original-Received: via spool by 49855-submit@debbugs.gnu.org id=B49855.162808028612612 (code B ref 49855); Wed, 04 Aug 2021 12:32:02 +0000 Original-Received: (at 49855) by debbugs.gnu.org; 4 Aug 2021 12:31:26 +0000 Original-Received: from localhost ([127.0.0.1]:43068 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mBG3S-0003HM-7X for submit@debbugs.gnu.org; Wed, 04 Aug 2021 08:31:26 -0400 Original-Received: from smtp-4.orcon.net.nz ([60.234.4.59]:60005) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mBG3Q-0003HA-CB for 49855@debbugs.gnu.org; Wed, 04 Aug 2021 08:31:25 -0400 Original-Received: from [10.253.37.70] (port=46283 helo=webmail.orcon.net.nz) by smtp-4.orcon.net.nz with esmtpa (Exim 4.90_1) (envelope-from ) id 1mBG3M-0004KZ-7v; Thu, 05 Aug 2021 00:31:21 +1200 Original-Received: from ip-116-251-162-85.kinect.net.nz ([116.251.162.85]) via [10.253.37.253] by webmail.orcon.net.nz with HTTP (HTTP/1.1 POST); Thu, 05 Aug 2021 00:31:20 +1200 In-Reply-To: <87czqteik6.fsf@gnus.org> X-Sender: psainty@orcon.net.nz X-GeoIP: -- X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:211171 Archived-At: On 2021-08-04 20:10, Lars Ingebrigtsen wrote: > I don't really think there's any way to determine the intention here. > The developer may be working in a branch, fix something, bump the > number, fix some more (but doesn't want that to land in ELPA yet), and > then merge, for instance. I guess so. It seems a less-likely workflow to my mind, but that may just be my own habits and biases talking. Still, it would be good if we could at least reduce the chances of people getting tripped up by this. Taking a different tack, perhaps we just need a more detailed (or an additional) notification email. At present I'm sent this: > Subject: [GNU ELPA] So-Long version 1.1.1 > From: ELPA update > To: gnu-emacs-sources@gnu.org > Cc: Phil Sainty > Reply-To: help-gnu-emacs@gnu.org > > Version 1.1.1 of package So-Long has just been released in GNU ELPA. > You can now find it in M-x package-list RET. > > So-Long describes itself as: > Say farewell to performance problems with minified code. > > More at https://elpa.gnu.org/packages/so-long.html If in addition to that information, it also showed the commit hash and message which was used to build the release, I would have immediately seen that I'd messed up. Something like: > Build details: > Commit 359a8e4eda047b7dcb7e64faff7f8eaacf5d937c > ; * lisp/so-long.el: Bump to version 1.1 I'm not sure whether it's appropriate to include such details in that particular notification, or if it would be better to send a separate message to the maintainer; but either way these details would provide direct confirmation as to whether the thing you thought had happened had actually happened. As it was, I thought I'd released "version 1.1", and the notification told me that I'd done exactly that, and so I was completely confident that everything was correct until I found that it wasn't. I suspect that if I hadn't done a sanity-check then I might not realised anything was wrong until someone else told me. -Phil