unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: "(" <paren@disroot.org>
Cc: 59131@debbugs.gnu.org
Subject: bug#59131: gnu: emacs-magit: Tests fail.
Date: Tue, 08 Nov 2022 23:04:18 -0500	[thread overview]
Message-ID: <877d043ha5.fsf@kyleam.com> (raw)
In-Reply-To: <CO76AMURS689.12UOEPAP8T4KW@guix-framework>

paren--- via Bug reports for GNU Guix writes:

>   $ guix describe
>   Generation 240	Nov 08 2022 18:38:30	(current)
>   guix c52cdd1
>     repository URL: https://git.savannah.gnu.org/git/guix.git
>     branch: master
>     commit: c52cdd18d6f8dddd69dfb1f8b5214a0db6ebb562
> [...]
>
>   2 unexpected results:
>      FAILED  magit-get
>      FAILED  magit-toplevel:submodule
>
>   1 skipped results:
>     SKIPPED  magit-toplevel:tramp
>
>   make: *** [Makefile:111: test] Error 1
>
> This appears to have been caused by commit 83ede5a ("gnu: git: Update to 2.38.1.").

Thanks for posting this.  This recently started failing on Magit's CI,
but nobody had looked into it too deeply yet.  Your message suggested
that bisecting Git v2.38.0..v2.38.1 would be a good place to start.

That pointed to this being fallout from Git's a1d4f67c12 (transport:
make `protocol.file.allow` be "user" by default, 2022-10-01), and the
two failures above are now resolved by Magit's 36059e0b (test: Set
protocol.file.allow=always to restore old Git behavior, 2022-11-08).

(In terms of fixing Guix's emacs-magit build, 36059e0b applies cleanly
to v3.3.0's tree.)




  reply	other threads:[~2022-11-09  4:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 19:48 bug#59131: gnu: emacs-magit: Tests fail paren--- via Bug reports for GNU Guix
2022-11-09  4:04 ` Kyle Meyer [this message]
2022-11-09  7:44   ` paren--- via Bug reports for GNU Guix
2022-11-09  8:06   ` paren--- via Bug reports for GNU Guix
2022-11-09 19:50 ` bug#59131: paren--- via Bug reports for GNU Guix
2023-03-30 12:43   ` bug#59131: gnu: emacs-magit: Tests fail Maxim Cournoyer

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=877d043ha5.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=59131@debbugs.gnu.org \
    --cc=paren@disroot.org \
    /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).