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

Bug#955979: does not work with magit in Debian

Hi Antoine,

Вс 05 апр 2020 @ 13:40 Antoine Beaupre <anarcat@debian.org>:

> 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)
>   magit-setup-buffer(magit-todos-list-mode)
>   magit-todos-list-internal("/home/anarcat/src/tor/tsa-misc/")
>   magit-todos-list(nil)
>   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)
>   command-execute(execute-extended-command)
> I reported this in the ITP but it seems that problem was either
> disregarded or overlooked:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951450#10
> It's also been reported upstream:
> https://github.com/alphapapa/magit-todos/issues/87
> 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... :/

I use Emacs and Emacs packages only from the Debian archive. No packages
are installed from MELPA or _any_ other source. And... magit-todos works
for me just fine. I'm not sure why, but I simply cannot reproduce this
bug report.


Reply to: