unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jack Hill <jackhill@jackhill.us>
Cc: 31726@debbugs.gnu.org
Subject: bug#31726: Attempt to use git reference for haskell-mode
Date: Mon, 23 Jul 2018 10:20:30 +0200	[thread overview]
Message-ID: <87y3e2uzw1.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1807201526550.11087@marsh.hcoop.net> (Jack Hill's message of "Fri, 20 Jul 2018 15:58:55 -0400 (EDT)")

Hello Jack,

Jack Hill <jackhill@jackhill.us> skribis:

> I've returned to working on the haskell-mode fixes for Emacs
> 26.1. However, I'm afraid that I'll need a bit more guidance about the
> best path forward to prepare a patch that is suitable for inclusion in
> Guix.
>
> When I left off, in addition to your comments, I was concerned with
> test failures, so I tried to instead to define the package using a git
> reference (patch below (I have not yet worked on the commit
> message). Unfortunately, more of the tests fail than before. I was
> able to get more of the tests to pass by adding ghc as an input. With
> test disabled, I am able to install the package and load it in Emacs.
>
> A breakdown of the number of failing test is as follows:
> 16.1 version with patch  -- 4
> git version without ghc -- 11
> git version with ghc -- 7
>
> I'm not sure which version to prefer, or how to proceed making that
> decision. Version 16.1 was released in September 2016. By moving to
> the git version, we would no longer need to run a substitution in
> haskell-code-conventions.el as that file has been removed upstream.

From what you’re saying and from the previous discussion, it seems clear
to me that we’d rather use a recent Git snapshot.

> Would it be acceptable to disable the tests?

If there are 7 failing tests, perhaps that indicates a real issue.
Could you take a look at the test log to see if this is something
benign?  Sometimes it’s just hard-coded /usr/bin file names or similar
that cause tests to fail, and that is easy to fix.

Now, if haskell-mode has been failing to build for 2+ months, an update
without tests is still preferable over the status quo.  So if you don’t
see an immediate solution to the test failures, I suppose we could go
ahead and apply the patch.

Thank you,
Ludo’.

      reply	other threads:[~2018-07-23  8:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 16:27 bug#31726: haskell-mode fails to build with (at least) Emacs 26.1 Jack Hill
     [not found] ` <handler.31726.B.1528217025308.ack@debbugs.gnu.org>
2018-06-05 21:02   ` bug#31726: Acknowledgement (haskell-mode fails to build with (at least) Emacs 26.1) Jack Hill
2018-06-07 16:14     ` Ludovic Courtès
2018-06-07 21:43 ` bug#31726: confirming proposed change Jack Hill
2018-06-08 14:30   ` Ludovic Courtès
2018-06-08 19:46     ` Jack Hill
2018-06-09 20:34       ` Ludovic Courtès
2018-07-20 19:58 ` bug#31726: Attempt to use git reference for haskell-mode Jack Hill
2018-07-23  8:20   ` Ludovic Courtès [this message]

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=87y3e2uzw1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=31726@debbugs.gnu.org \
    --cc=jackhill@jackhill.us \
    /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).