From: Ricardo Wurmus <rekado@elephly.net>
To: Mekeor Melire <mekeor.melire@gmail.com>
Cc: 26914-done@debbugs.gnu.org
Subject: bug#26914: gnu: xmonad: Update to 0.13.
Date: Wed, 21 Jun 2017 09:43:48 +0200 [thread overview]
Message-ID: <87podx3hvv.fsf@elephly.net> (raw)
In-Reply-To: <874lvaql2b.fsf@gmail.com>
Mekeor Melire <mekeor.melire@gmail.com> writes:
> I tested both patches again now: they work. I tested them using both
>
> $ ./pre-inst-env guix build xmonad ghc-xmonad-contrib # and
> $ ./pre-inst-env guix package -i xmonad ghc-xmonad-contrib
>
> and both worked.
>
> Before building the package, I applied the patch for ghc-x11, then I
> applied the patch for xmonad and ghc-xmonad-contrib.
Yes, you’re right. The patch for “ghc-x11” actually hadn’t been
pushed. I was able to build xmonad, but I noticed these warnings:
--8<---------------cut here---------------start------------->8---
Configuring xmonad-0.13...
Warning: This package indirectly depends on multiple versions of the same
package. This is highly likely to cause a compile failure.
package process-1.2.3.0 requires directory-1.2.2.0
package xmonad-0.13 requires directory-1.2.7.0
--8<---------------cut here---------------end--------------->8---
This indicates that we really need to update other packages too.
I’ll push this now and close this bug, but we really need to harmonise
the Haskell packages.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
prev parent reply other threads:[~2017-06-21 7:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 21:47 bug#26914: gnu: xmonad: Update to 0.13 Mekeor Melire
2017-05-13 21:52 ` bug#26914: gnu: ghc-x11: Update to 1.8 Mekeor Melire
2017-05-14 13:38 ` Ludovic Courtès
2017-06-21 7:34 ` [bug#26914] " Ricardo Wurmus
2017-05-13 21:52 ` bug#26914: gnu: xmonad: Update to 0.13 Mekeor Melire
2017-05-14 13:39 ` Ludovic Courtès
2017-05-30 16:01 ` Ludovic Courtès
2017-05-30 21:46 ` Ricardo Wurmus
2017-06-20 23:46 ` [bug#26914] " Mekeor Melire
2017-06-21 7:43 ` Ricardo Wurmus [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=87podx3hvv.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=26914-done@debbugs.gnu.org \
--cc=mekeor.melire@gmail.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).