Re: magit_4.1.2-1_source.changes ACCEPTED into unstable
Thanks, Matteo!
Yes, magit 4.1.1 works okay, as far as I can tell.
The issue is when it runs its test suite at build time.
Under some circumstances, it tries to pop up a subservient emacs
process to edit the commit message.
I was starting to track that down...
And re 4.1.1 → 4.1.2 dependency delta ... oops, mea culpa.
On Sun, 3 Nov 2024 at 09:06, Matteo F. Vescovi <mfvescovi@gmail.com> wrote:
>
> I uploaded 4.1.1 as ut was working fine (tested with piuparts).
> 4.1.2 is now forcing 0.7.8 for transient. Thus, I've uploaded 0.7.8 and forge 0.4.4 to fix the issue.
>
> Cheers.
>
> mfv
>
>
> Il dom 3 nov 2024, 09:04 Barak A. Pearlmutter <bap@debian.org> ha scritto:
>>
>> True: transient needs to be uploaded too.
>>
>> I tested locally with my own updated transient. But I actually hadn't finished testing; there's an issue where the test suite runs okay in the CI systems (minimal install) but gets a failure running an emacsclient and blocking on wait for the recursive edit to finish. For this reason, I didn't actually mean to upload magit. I pushed magit 4.1.1-1 to salsa; someone else dput it. I dput 4.1.2-1 because there's no practical difference between the two.
Reply to: