Regression in eshell-tramp since Emacs 29.1

  • Open
  • quality assurance status badge
Details
2 participants
  • Baptiste Strazzulla
  • Baptiste Strazzulla
Owner
unassigned
Submitted by
Baptiste Strazzulla
Severity
normal
B
B
Baptiste Strazzulla wrote on 7 Mar 19:08 +0100
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
AS8P189MB2024CB83B0F4901E3B302B40B9202@AS8P189MB2024.EURP189.PROD.OUTLOOK.COM
Hello!

Since the Emacs upgrade to 29.1 last october, I've been struggling with `sudo` in Emacs shell with the `eshell-tramp` module loaded (`(add-to-list 'eshell-modules-list 'eshell-tramp)`).

It fails if given any command in ~/.guix-profile/bin:

```
~ $ sudo git
git: command not found
```

and also fails (and downright kills the buffer) if given any command in /run/current-system/profile/bin

```
~ $ sudo guix
sudo: /run/current-system/profile/bin/sudo must be owned by uid 0 and have the setuid bit set
```

I tried with Emacs 28.1 on an old generation of packages I had and both commands worked fine on it.

I could also just not load this module anymore but as it turns out, `guix` is having problem finding modules defined in external channels then:

```
~ $ sudo guix system reconfigure ~/.config/guix/config.scm
guix system: error: failed to load '/home/baptiste/.config/guix/config.scm':
/home/baptiste/.config/guix/config.scm:127:2: Module named (nongnu packages linux) has no public interface
```

Does anyone have any ideas?

Kind regards and thank you for your dedication,
Baptiste Strazzulla
Attachment: file
B
B
Baptiste Strazzulla wrote on 1 Aug 18:13 +0200
(name . 69616@debbugs.gnu.org)(address . 69616@debbugs.gnu.org)
8gyz_YreaFGE1y0PuRbM7r-jWBuAfhRjAGpGEn9pSGxfNgb_UsfgcNDa0t6pukjenEw-VMN988mKaLIHv88QIXpKrFIkkgtOmJ6Y5vE5u2w=@protonmail.com
Hello again,

It seems it has been fixed!
Attachment: file
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 69616@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 69616
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch