[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1115309: elpa-magit: magit-branch fails with error message



Package: elpa-magit
Version: 4.3.5-1
Severity: normal

Dear Maintainer,

Some parts of Magit as found trixie do not work, at least for me.  The
following recipe should allow to reproduce the problem.  It assumes that
there’s a git repository under /tmp/foo, but it doesn’t have to be an
empty one and, it can be anywhere.

$ git init /tmp/foo
Initialized empty Git repository in /tmp/foo/.git/

Open Emacs ignoring the user startup file
$ emacs -q /tmp/foo

Inside Emacs, activate magit, and launch it
M-: (require 'magit)
M-x magit-status

Pressing “b” (which should launch magit-branch) produces the following
error message:

transient-setup: Invalid function: (## and magit-branch-direct-configure (transient-scope))

This looks to me like an incompatibility between elpa-magit and elpa-transient
as found in trixie.

-- System Information:
Debian Release: 13.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-38-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages elpa-magit depends on:
ii  dh-elpa-helper                 2.1.9
ii  elpa-llama                     0.6.2-1
ii  elpa-magit-section             4.3.5-1
ii  elpa-transient                 0.8.8-1
ii  elpa-with-editor               3.4.3-1
ii  emacs                          1:30.1+1-6
ii  emacs-common [elpa-transient]  1:30.1+1-6
ii  emacs-gtk [emacs]              1:30.1+1-6
ii  emacsen-common                 3.0.8
ii  git                            1:2.47.3-0+deb13u1

elpa-magit recommends no packages.

elpa-magit suggests no packages.

-- no debconf information

Reply to: