From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#62720: 29.0.60; Not easy at all to upgrade :core packages like Eglot Date: Sat, 8 Apr 2023 10:09:48 +0100 Message-ID: References: <87a5zj2vfo.fsf@gmail.com> <835ya6onmz.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000009e5c7005f8cf812e" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12378"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 62720@debbugs.gnu.org, Stefan Monnier To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 08 11:11:19 2023 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 1pl4bN-00030X-VU for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 08 Apr 2023 11:11:18 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pl4b9-0002LY-FI; Sat, 08 Apr 2023 05:11:03 -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 1pl4b8-0002LN-8B for bug-gnu-emacs@gnu.org; Sat, 08 Apr 2023 05:11:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pl4b7-00015K-Vz for bug-gnu-emacs@gnu.org; Sat, 08 Apr 2023 05:11:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pl4b7-0005ON-Rx for bug-gnu-emacs@gnu.org; Sat, 08 Apr 2023 05:11:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 08 Apr 2023 09:11:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 62720 X-GNU-PR-Package: emacs Original-Received: via spool by 62720-submit@debbugs.gnu.org id=B62720.168094500920660 (code B ref 62720); Sat, 08 Apr 2023 09:11:01 +0000 Original-Received: (at 62720) by debbugs.gnu.org; 8 Apr 2023 09:10:09 +0000 Original-Received: from localhost ([127.0.0.1]:57713 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pl4aG-0005N7-DH for submit@debbugs.gnu.org; Sat, 08 Apr 2023 05:10:08 -0400 Original-Received: from mail-oa1-f41.google.com ([209.85.160.41]:41926) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pl4aD-0005MW-R0 for 62720@debbugs.gnu.org; Sat, 08 Apr 2023 05:10:06 -0400 Original-Received: by mail-oa1-f41.google.com with SMTP id 586e51a60fabf-17fcc07d6c4so33904328fac.8 for <62720@debbugs.gnu.org>; Sat, 08 Apr 2023 02:10:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680945000; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=mNpKzJPAxYC/K3cTyBWWJ+ECz8lwroB630Kr8KP67fA=; b=LmK2EGRAJ98kjhEaDKzZcUDLn3wTLDDPFdNY0k3YT4o03NmrQd3DOnsg4Lc9oUD6Yt XQRJuUzYV40qiYQAvrn+KEScPRFP83/4C6nlwRUzj9DquKpYmkMFdb3xYxjwb3FkGPbZ eEqdxf9fxRJzW5rV08IGEuXCG0Hq11TEFdmXTZh7qQXLVGCaPWMxjmss9r4p7ziWzInb +bGLqB7zQXbdf1H6GXu43/1rwFnXEgW1F4fi4f4cTkhjcesk0j7DZYOIBzPo+YYP/J/F frU/iE3IM3xTItFbH1tECMykmei07KPoAjd6tpd064SsNnC+t2VrPoL0sZbnux9Rrmk0 AxCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680945000; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mNpKzJPAxYC/K3cTyBWWJ+ECz8lwroB630Kr8KP67fA=; b=ckX6Wr4NyGDph/S3nNNX9mV/J2VJb6kzWG3h9mLKCyVL+7nTHUBssNu2MKLlFiULy4 45X4eLlklB+lxKtErtPg1s6dsVxT2+Syft/HZe98q+RHjJgGu596hJWtNaXYAMllOIqs ZF9xEh2y/V0x2AFecMWHpg6puzwAl8c6vJBR4Bg2hBuHsEdNJNF27sPJRTjjcqMemY5c nbngHUK1XTAKSi6j68kp/1dkgsixlIf/OKe2ZzXWzosSkVlsnbbrPiRQ/4WNgXmqlU6A 5fijVrZ6HYEeHFn+VPCOw8mZKVLZVGo5Qk80DXiG8vDFzu3/nYoUdLUT3pwxsteXgl8J oQCQ== X-Gm-Message-State: AAQBX9dSjF978/uv9KI3WXYzyHbwblAip5G8vctgJ9tCCBzU0G3mpCaS N1R8L4RQAcTWy/Kr4njUNz9mfphMyyH2e+9AhGc= X-Google-Smtp-Source: AKy350bEDuHJRQVEbIa1O4HyzHgMsyoNPGFIcnsbnvASxmDAJfy88m6zVAwnm+y2l4ETMsmDNZZrKqpyeRE2rLRvY1g= X-Received: by 2002:a05:6871:81:b0:180:1f9f:923e with SMTP id u1-20020a056871008100b001801f9f923emr2128000oaa.5.1680945000109; Sat, 08 Apr 2023 02:10:00 -0700 (PDT) In-Reply-To: <835ya6onmz.fsf@gnu.org> 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:259460 Archived-At: --0000000000009e5c7005f8cf812e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Apr 8, 2023, 08:09 Eli Zaretskii wrote: > > Cc: monnier@iro.umontreal.ca > > From: Jo=C3=A3o T=C3=A1vora > > Date: Fri, 07 Apr 2023 23:12:43 +0100 > > > > I've been meaning to report this for some time. I really think this > > should be fixed in Emacs 29 before it ships. > > > > src/emacs -Q # Emacs 29 > > > > M-x package-install RET eglot RET > > > > Echoes "No match", even though eglot 1.14 is available from GNU ELPA. > > That's because Eglot is a :core ELPA package and it's already in Emacs > > 29, so package.el thinks there is nothing to install. > > Is :core new in Emacs 29? If not, then this problem is not new: it > existed earlier for every :core package in ELPA, it just didn't exist > for Eglot. > Yes, it existed before. It's a bug but not a regression. But many of these :core packages were primarily used as libraries supporting other packages, not do much as user-facing, command-providing, UI-enhancing packages. >From what I've been seeing in the Eglot bug tracker there is a very significant number of people using third-party package managers to install and upgrade Eglot (straight, elpaca, ...) I always tell them to report problems sweet package-install instead of these managers, as I've seen more than my fair share of problems created by these other managers. My experience and the internal traffic reports tem me Eglot is a popular Emacs package and people are not satisfied with just any old release. If this isn't fixed, it'll be heaps of text to tell people how to upgrade. Not the end of the world, but really awkward. There is certainly code in Emacs 29 that allows upgrading Eglot or other core packages but it's buried deep in that odd workflow. If the code for a M-x package-upgrade, as Stefan suggests, is simple, then i think it should be added to emacs-29. Alternatively, there could be some kind of 'package-bugfixes' non-:core package in elpa.git that adds this new command. Asking people to install that package first is still easier than guiding then through that odd workflow. Jo=C3=A3o > --0000000000009e5c7005f8cf812e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Apr 8, 2023, 08:09 Eli Zaretskii <eliz@gnu.org> wrote:
> Cc: monnier@iro.umontreal.ca
> From: Jo=C3=A3o T=C3=A1vora <joaotavora@gmail.com>
> Date: Fri, 07 Apr 2023 23:12:43 +0100
>
> I've been meaning to report this for some time.=C2=A0 I really thi= nk this
> should be fixed in Emacs 29 before it ships.
>
> src/emacs -Q # Emacs 29
>
> M-x package-install RET eglot RET
>
> Echoes "No match", even though eglot 1.14 is available from = GNU ELPA.
> That's because Eglot is a :core ELPA package and it's already = in Emacs
> 29, so package.el thinks there is nothing to install.

Is :core new in Emacs 29?=C2=A0 If not, then this problem is not new: it existed earlier for every :core package in ELPA, it just didn't exist for Eglot.

Yes, it existed before. It's a bug but not a regression. But = many of these :core packages were primarily used as libraries supporting ot= her packages, not do much as user-facing, command-providing, UI-enhancing p= ackages.=C2=A0

From what= I've been seeing in the Eglot bug tracker there is a very significant = number of people using third-party package managers to install and upgrade = Eglot (straight, elpaca, ...)

I always tell them to report problems sweet package-install instead o= f these managers, as I've seen more than my fair share of problems crea= ted by these other managers.

My experience and the internal traffic reports tem me Eglot is a popul= ar Emacs package and people are not satisfied with just any old release. If= this isn't fixed, it'll be heaps of text to tell people how to upg= rade. Not the end of the world, but really awkward.
=
There is certainly code in Emacs 29 that allows= upgrading Eglot or other core packages but it's buried deep in that od= d workflow. If the code for a M-x package-upgrade, as Stefan suggests, is s= imple, then i think it should be added to emacs-29.
=
Alternatively, there could be some kind of '= ;package-bugfixes' non-:core package in elpa.git that adds this new com= mand. Asking people to install that package first is still easier than guid= ing then through that odd workflow.

Jo=C3=A3o
--0000000000009e5c7005f8cf812e--