Hi Lev,

Lev Lamberov <dogs...@debian.org> writes:

> Hi Nicholas and David,
>
> Пн 24 фев 2020 @ 12:27 Nicholas D Steeves <nstee...@gmail.com>:
>
>> Lev Lamberov <dogs...@debian.org> writes:
>>
>>> Hmmm, looks like the bug is caused by undo-tree, since when
>>> elpa-undo-tree 0.6.4-3 is installed tests are passed correctly.
>>> Moreover, when new upstream version of undo-tree is used (0.7.4, not
>>> currently in Debian) tests also are passed correctly.
>>
>> Lev, thank you for working to find, and finding the cause!  Sorry, I
>> share the blame for this regression because I sponsored the upload of
>> 0.7.1.  How urgently would you like a fix?  I'd like to give David some
>> time to prepare the new undo-tree release, but can prepare it myself if
>> too much time passes.  BTW, are undo-trees tests flaky or could you
>> enable autopkgtests for it at this time?
>
> In fact, this was not that urgent. Anyway, thank you both for your work
> and kindness! There's no one to blame simply because it is up to
> impossible to check a package against all possible regressions
> (especially given that dependency chain becomes way too long pretty
> quickly).
>

Thank you Lev, that's kind :-)  On the upside, autopkgtests give us an
edge over MELPA Stable!  Sorry for not noticing emacs-bind-map already
had them enabled.  IIRC the dep chain for this package is now covered,
so our early-warning system should be functional.  'wish we had
untruncated backtraces...

> Thanks again! I'm closing this bug (it also motivated me to update
> packaging of emacs-bind-map, which should have been done at some point).
>

Wonderful!  By the way, whenever I see a lot of packaging updates on our
mailing list it also motivates me to work on my packages :-D


Take care,
Nicholas

Attachment: signature.asc
Description: PGP signature

Reply via email to