From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.bugs Subject: bug#70647: 30.0.50; When are :core packages released to GNU ELPA? Date: Mon, 29 Apr 2024 17:55:55 +0000 Message-ID: <87y18wkq8k.fsf@posteo.net> References: <87mspcmj1g.fsf@gmail.com> <86wmogqper.fsf@gnu.org> <87y18wxoll.fsf@gmail.com> <86sez4qndc.fsf@gnu.org> <87cyq8dz4h.fsf@gmail.com> <86r0eoqlrn.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22854"; mail-complaints-to="usenet@ciao.gmane.io" Cc: No Wayman , 70647@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Apr 29 19:56:49 2024 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 1s1VFB-0005jz-CK for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 29 Apr 2024 19:56:49 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s1VF8-0004y2-2U; Mon, 29 Apr 2024 13:56:46 -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 1s1VF6-0004xj-35 for bug-gnu-emacs@gnu.org; Mon, 29 Apr 2024 13:56:44 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1s1VF4-000800-BJ for bug-gnu-emacs@gnu.org; Mon, 29 Apr 2024 13:56:42 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1s1VFO-0000Vx-4E for bug-gnu-emacs@gnu.org; Mon, 29 Apr 2024 13:57:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Philip Kaludercic Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 29 Apr 2024 17:57:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 70647 X-GNU-PR-Package: emacs Original-Received: via spool by 70647-submit@debbugs.gnu.org id=B70647.17144133881960 (code B ref 70647); Mon, 29 Apr 2024 17:57:02 +0000 Original-Received: (at 70647) by debbugs.gnu.org; 29 Apr 2024 17:56:28 +0000 Original-Received: from localhost ([127.0.0.1]:58485 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s1VEp-0000VY-Td for submit@debbugs.gnu.org; Mon, 29 Apr 2024 13:56:28 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:59083) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s1VEl-0000VP-0M for 70647@debbugs.gnu.org; Mon, 29 Apr 2024 13:56:26 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id DA912240103 for <70647@debbugs.gnu.org>; Mon, 29 Apr 2024 19:55:56 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1714413356; bh=Elxin9qpTsLGdrsQwzlc0zFv5PmNtAbTBiHmgnxXmew=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=WHsGQcMFt+XpYbr62QNkry66XaO0KBU4mh9Fp6U4KIn5XcYI03JIHLuz8CNXFeFuq x0Fwb+wkuK/ooYSf/+wgLH+GySkmlMfT9b1pIdiwA8k8tFl8ZUcLI2hSULv3SeuxvX 6mFZ0JKbYp99yC1g8G35ZTtePv1THQOtVzyviFmGMlNJl+v6UUurFSU7otMWcXV62f 4rW8+ytqIkf4CsUUxg4SjztepyOppdtq6r6o9IUS6GZKEq0H4Sxu3yfKfOSXyUDNhZ S7SEGqfnhu0i2VkuYMagGR0sndi/hebfdstzKEkta3qYAm4+m4yjyjZahgsjpc+4uv /zjdMVcefpgGA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4VSrbc2VS6z6tvZ; Mon, 29 Apr 2024 19:55:56 +0200 (CEST) In-Reply-To: <86r0eoqlrn.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 29 Apr 2024 17:35:56 +0300") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:284165 Archived-At: Eli Zaretskii writes: >> From: No Wayman >> Cc: Philip Kaludercic >> Date: Mon, 29 Apr 2024 10:25:50 -0400 >> >> Eli Zaretskii writes: >> >> > [Why private email?] >> >> Apologies. Must've fat-fingered my reply key binding. > > Looks like you did it again. Please use Reply All, to have the bug > tracker CC'ed. > > Resending to the bug tracker. > >> >> From: No Wayman Date: Mon, 29 >> >> Apr 2024 09:52:54 -0400 Eli Zaretskii writes: >> >> >> >> > Are there any differences in the code between version 1.17 on >> >> > ELPA and the Eglot code as of commit b014bca833a. >> >> I would hope not. Otherwise the version information is >> >> incorrect. >> > >> > Then why is this a problem? File time stamps are immaterial >> > with modern VCSes. >> >> The problem is it's confusing. >> When is the "release date" of eglot 1.17? >> The date of the commit which bumped the Version header? >> The date of some other action which triggered an ELPA build? >> If file timestamps are indeed immaterial, than it would make the >> most sense to stick with the commit date which bumped the Version >> header. >> That does not appear to be the case. >> >> >> > What would you like to be documented? >> >> - What triggers a package build/release on GNU ELPA in all >> >> cases >> >> (:core or otherwise)? >> > >> > Philip will tell, but I'm not surprised, given that this is a >> > volunteer project. When a commit modifies the Version header in the main file, then the state of that commit is used to trigger a new release, both for core and otherwise. >> >> - What triggers a package build/release on GNU-devel ELPA. >> > >> > What is "GNU-devel ELPA"? >> >> Forgive me if I misspoke, but: https://elpa.gnu.org/devel/ These are rebuilt on every commit. The intended audience IMO are developers here though, so that they can easily preview the state of packages. >> >

GNU-devel ELPA Packages

>> >> If that's not what it's called, then the website should be updated >> to reflect the preferred name. The name is fine. I am just guessing that it is not something that Eli has to deal with that often. >> > I don't even understand the problem you see here. >> >> I've seen other package maintainers confused about what/when a >> rebuild is triggered. I have reports on Elpaca's issue tracker >> where users are confused by the release dates listed on GNU ELPA's >> websites. I myself am not 100% sure I understand all cases that >> trigger builds. The issue is I could not find a place where this >> is all clearly documented. There were issues related to some recent changes that re-build the package tarballs, but the content should have been the same. But that was a mistake, and not something that should happen on a regular basis. -- Philip Kaludercic on peregrine