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

Bug#955979: does not work with magit in Debian

Package: elpa-magit-todos
Version: 1.5.2-1
Severity: grave

magit-todos, as packaged in Debian, does not work. It seems to assume
a magit version that is not present in Debian. When I run "M-x
magit-todos" I get the error:

   magit-todos-list-internal: Symbol’s function definition is void: magit-setup-buffer

The debugger trace is this:

Debugger entered--Lisp error: (void-function magit-setup-buffer)
  funcall-interactively(magit-todos-list nil)
  call-interactively(magit-todos-list record nil)
  command-execute(magit-todos-list record)
  execute-extended-command(nil "magit-todos-list" nil)
  funcall-interactively(execute-extended-command nil "magit-todos-list" nil)
  call-interactively(execute-extended-command nil nil)

I reported this in the ITP but it seems that problem was either
disregarded or overlooked:


It's also been reported upstream:


The response there was:

> Unfortunately, that doesn't matter. Magit is a moving target, and
> it's not feasible for me to produce "stable" versions in sync with
> Magit "stable" versions. Magit does not coordinate its changes with
> me. So when Magit suddenly breaks this package for 99% of users
> without warning, I have to fix it, and that means breaking things
> for older Magit versions.
> If you insist on not upgrading Magit, you could use a version of
> this package from before that change was made.

It's too bad this newer version was packaged instead of a working
version because now it would be difficult to reverse this without
adding an epoch to the version number.

In any case, this is definitely broken right now in Debian, unless we
install magit from *outside* Debian. If that's what is expected of
magit-todos users, the package does not belong in main (because it
requires packages outside of main) but rather contrib.

Alternatively, maybe we can just hope magit will be released upstream
(as it's been promised since november) and that this will fix itself
when it lands in Debian (#952560), but I have kind of stopped hoping
for that at this point... :/

-- System Information:
Debian Release: 10.3
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages elpa-magit-todos depends on:
ii  dh-elpa-helper  2.0.2~bpo10+2
ii  elpa-async      1.9.3-1
ii  elpa-dash       2.14.1+dfsg-1
ii  elpa-f          0.20.0-1
ii  elpa-hl-todo    2.2.0-1
ii  elpa-magit      2.90.1-2
ii  elpa-pcre2el    1.8-1
ii  elpa-s          1.12.0-2
ii  emacsen-common  3.0.4

Versions of packages elpa-magit-todos recommends:
ii  emacs              1:26.1+1-3.2+deb10u1
ii  emacs-gtk [emacs]  1:26.1+1-3.2+deb10u1
ii  git                1:2.20.1-2+deb10u1

elpa-magit-todos suggests no packages.

-- no debconf information

Reply to: