unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Zhu Zihao <all_but_last@163.com>, 55427@debbugs.gnu.org
Subject: bug#55427: emacs-libgit tests are broken
Date: Wed, 18 May 2022 08:14:36 +0200	[thread overview]
Message-ID: <8913b7de248eb03b468c3ca3fb85f5f749884169.camel@ist.tugraz.at> (raw)
In-Reply-To: <861qwsrxyc.fsf@163.com>

Am Dienstag, dem 17.05.2022 um 23:14 +0800 schrieb Zhu Zihao:
> Due to the inactive status of upstream. I'm planning to remove the
> emacs-libgit input of emacs-magit.
I don't think we need measures quite as drastic as this.  A hotfix for
emacs-libgit was pushed to master, which causes builds to succeed again
(see e.g. [1]).  Since we're talking about free software here, it would
be more constructive to work on a proper patch – if upstream won't take
it, one can always fork it.

> magit will still work with the git executable if there's no
> emacs-libgit.
> 
> Any thoughts?
I don't see any benefits in this approach, do you?

[1] http://ci.guix.gnu.org/build/859957/details




  parent reply	other threads:[~2022-05-18  6:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 11:19 bug#55427: emacs-libgit tests are broken Liliana Marie Prikler
2022-05-16 10:01 ` Zhu Zihao
2022-05-17 15:14   ` Zhu Zihao
2022-05-17 23:10     ` Kyle Meyer
2022-05-18  6:14     ` Liliana Marie Prikler [this message]
2022-05-18 13:17       ` Zhu Zihao
2022-05-18 10:02     ` Maxime Devos
2022-05-18 13:13       ` Zhu Zihao
2022-05-18 13:24         ` Maxime Devos
2022-05-18 13:30           ` Maxime Devos
2022-05-18 15:34             ` Zhu Zihao
2022-05-18 22:44             ` Kyle Meyer
2022-05-16 10:28 ` Taiju HIGASHI
2022-05-16 10:40   ` Taiju HIGASHI

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8913b7de248eb03b468c3ca3fb85f5f749884169.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=55427@debbugs.gnu.org \
    --cc=all_but_last@163.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).