From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#62720: 29.0.60; Not easy at all to upgrade :core packages like Eglot Date: Thu, 27 Apr 2023 08:41:15 +0300 Message-ID: <837ctxubk4.fsf@gnu.org> References: <87a5zj2vfo.fsf@gmail.com> <838rem636a.fsf@gnu.org> <83leil4u63.fsf@gnu.org> <8a9d0e2b-6ae2-bcdc-efd0-52a44ac862bb@gutov.dev> <83h6t94hru.fsf@gnu.org> <7676c8d2-1324-31e7-38b3-de167ecf683a@gutov.dev> <8e9bd99a-3093-3b69-8429-aa1ae6b7240d@gutov.dev> <834jp82u5c.fsf@gnu.org> <83ildo189j.fsf@gnu.org> <6e91a10e-e8bb-c7db-f6ce-917790e7e391@gutov.dev> <83edoc1602.fsf@gnu.org> <8e4ec101-adc3-0d1b-af3d-cce92f17b874@gutov.dev> <83r0sbyuew.fsf@gnu.org> <83edoazr8k.fsf@gnu.org> <3fb17c71-2a37-b306-472b-d8bc845e5777@gutov.dev> <83a5yyznfe.fsf@gnu.org> <41a79777-2cc6-9562-8915-9f28070b7bc9@gutov.dev> <83cz3txzi5.fsf@gnu.org> <5ae14089-f76f-84a1-d39a-3ec9e473a0aa@gutov.dev> <83jzy0wggy.fsf@gnu.org> <60a19aa0-e87c-1702-4ef4-df4450ed8fc7@gutov.dev> <831qk8w2rx.fsf@gnu.org> <0295d425-7c42-9a09-bda0-d3e4c92b4ff4@gutov.dev> <56893beb-90a2-7936-1c67-62ce3bae3f5d@gutov.dev> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5671"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jporterbugs@gmail.com, philipk@posteo.net, 62720@debbugs.gnu.org, joaotavora@gmail.com, larsi@gnus.org, monnier@iro.umontreal.ca To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Apr 27 07:41:18 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 1pruNZ-0001J4-Kq for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 27 Apr 2023 07:41:17 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pruNU-000105-0c; Thu, 27 Apr 2023 01:41:12 -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 1pruNL-0000zg-D8 for bug-gnu-emacs@gnu.org; Thu, 27 Apr 2023 01:41:06 -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 1pruNK-0007Cs-TN for bug-gnu-emacs@gnu.org; Thu, 27 Apr 2023 01:41:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pruNK-0007Ph-DP for bug-gnu-emacs@gnu.org; Thu, 27 Apr 2023 01:41:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 27 Apr 2023 05:41:02 +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.168257405728478 (code B ref 62720); Thu, 27 Apr 2023 05:41:02 +0000 Original-Received: (at 62720) by debbugs.gnu.org; 27 Apr 2023 05:40:57 +0000 Original-Received: from localhost ([127.0.0.1]:57387 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pruNE-0007PF-T1 for submit@debbugs.gnu.org; Thu, 27 Apr 2023 01:40:57 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:44358) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pruNC-0007P0-ME for 62720@debbugs.gnu.org; Thu, 27 Apr 2023 01:40:55 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pruN4-00079y-Gj; Thu, 27 Apr 2023 01:40:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=yy/PwCZmlQPl64unYTMijLjHgl+N0L0np3ggisNjSZk=; b=PUKddca7zvG6aSzM73QF pVpw5Q5kQ+GdhzntbiZ2donylT+tfkR0K0C27c+5brKbAi/yg+HAhPMsuqDzzRI6LTi+Lu+wdORvo Xz3U95PIz5GFeVK8wDDxpFzPu2pxrZu1wtyB4W2yEEIaWPI24dw6ZZPcDoxgMarsOVlZdaB33u0yy WDCAq+zvcthfv/W9/scapdAqnCntAMTneeKaq2jje/yE1AXclvd/tS29sdH8xygJf51yiLWhStGU5 rUAtPgQ6NyBFe0Qivqwo/uM+/aX1l+Ytb76Q3edsvPnSGNE7IDNHj5BlBFtJ4ceNH7exVCfCUMjwK zqzHMW8Dl3yeww==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pruN1-00040i-Lc; Thu, 27 Apr 2023 01:40:44 -0400 In-Reply-To: <56893beb-90a2-7936-1c67-62ce3bae3f5d@gutov.dev> (message from Dmitry Gutov on Thu, 27 Apr 2023 02:05:21 +0300) 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:260702 Archived-At: > Date: Thu, 27 Apr 2023 02:05:21 +0300 > From: Dmitry Gutov > Cc: jporterbugs@gmail.com, philipk@posteo.net, 62720@debbugs.gnu.org, > monnier@iro.umontreal.ca, larsi@gnus.org, joaotavora@gmail.com > > On 25/04/2023 21:35, Dmitry Gutov wrote: > >> So I think we need to rephrase that.  Something like > >> > >>    Packages which are part of the Emacs distribution cannot be updated > >>    that way. > > > > This is probably better. As long as we understand it to read "packages > > which are part ... and were never upgraded to a version from ELPA". > > Anyway, if we agree to keep this unfixed, we should probably add this > text somewhere: either into the docstring anyway, or to etc/PROBLEMS. Do we agree to leave package-update unchanged? And what about the renaming you suggested in another bug report? I'd like to make a new pretest soon, with all these issues finalized as best as we can. As for PROBLEMS, I'm not sure. We usually put there only something that people actually complain about, not proactively. How about mentioning this in the doc string instead?