all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
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: Mon, 7 Aug 2023 19:44:06 -0700	[thread overview]
Message-ID: <08b6d706-5741-1c7c-687c-21cd45dc1e21@gmail.com> (raw)
In-Reply-To: <871qge6fdn.fsf@gmx.de>

On 8/7/2023 8:28 AM, Michael Albinus wrote:
> Michael Albinus <michael.albinus@gmx.de> writes:
> 
> Hi Jim,
> 
>>> This makes the 'package-data' argument never be nil, which avoids
>>> running the broken code. I'd be a little worried about publishing this
>>> without further testing, but hopefully it (or something like it) could
>>> be a solution until 29.2 is released...
>>
>> I've tried to apply this change, but it doesn't work as expected yet.
> 
> Finally, I've decided to add the following to the Tramp README on ELPA:

Hmm, yeah, if my attempt didn't work reliably, this is probably the best 
solution for now (unless we want to spend a lot more time on this).

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...






  reply	other threads:[~2023-08-08  2:44 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 [this message]
2023-08-08  7:03                 ` Michael Albinus
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=08b6d706-5741-1c7c-687c-21cd45dc1e21@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=65023@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.de \
    --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.