all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	65023@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#65023: 29.1.50; Tramp 2.6.1.1 cannot be installed as ELPA package
Date: Tue, 08 Aug 2023 09:03:59 +0200	[thread overview]
Message-ID: <87o7jixbfk.fsf@gmx.de> (raw)
In-Reply-To: <08b6d706-5741-1c7c-687c-21cd45dc1e21@gmail.com> (Jim Porter's message of "Mon, 7 Aug 2023 19:44:06 -0700")

Jim Porter <jporterbugs@gmail.com> writes:

Hi Jim,

> Maybe this is something that the "compat" patch should handle, or
> maybe there should even be a separate GNU ELPA package for Emacs
> hotfixes? I'm not sure if this would be too much extra maintenance
> burden though...

Perhaps. But AFAIU, compat is based on major Emacs versions like "29". I
don't know whether they can provide also compat code for versions like "29.1".

A hotfix package could work. However, we aren't in that need yet. For
Tramp we have the instructions now, and there seems to be only org as
another ELPA package, which uses <pkg>-loaddefs.el. Don't know whether
they have problems installing the org package with Emacs 29.1.

Best regards, Michael.





  reply	other threads:[~2023-08-08  7:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 14:16 bug#65023: 29.1.50; Tramp 2.6.1.1 cannot be installed as ELPA package Michael Albinus
2023-08-04 16:40 ` Jim Porter
2023-08-04 17:52   ` Eli Zaretskii
2023-08-04 18:20     ` Jim Porter
2023-08-05  9:19       ` Michael Albinus
2023-08-05 20:34         ` Jim Porter
2023-08-06  8:57           ` Michael Albinus
2023-08-07 15:28             ` Michael Albinus
2023-08-08  2:44               ` Jim Porter
2023-08-08  7:03                 ` Michael Albinus [this message]
2023-08-15  3:09             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7jixbfk.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=65023@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.