From: Pjotr Prins <pjotr.public12@thebird.nl>
To: nee <nee@cock.li>
Cc: 28034@debbugs.gnu.org
Subject: bug#28034: elixir build fails
Date: Sun, 3 Dec 2017 06:43:50 +0100 [thread overview]
Message-ID: <20171203054350.GB4188@thebird.nl> (raw)
In-Reply-To: <0bf22cfb-fb98-fff6-12b7-87a14c506192@cock.li>
On Sat, Dec 02, 2017 at 07:04:09PM +0100, nee wrote:
> Hello, what is the current state for the elixir package?
>
> I saw this issue on elixir's github page:
> https://github.com/elixir-lang/elixir/issues/6586
> Has there been any progress since then? From what I understand the build
> fails because of impure test cases. Can we just disable these tests for
> now to make it build again?
I am all for that. Not that many tests fail (in the order of 1%), but it is a
pain to disable them by hand. That is why I have not done an update in a while
- I am running a more recent version on my GUIX_PACKAGE_PATH with tests
disabled.
The simple way is to remove a number of test files. The majority of
tests will work and since Erlang's tests also work - there are a large
number of them (thousands). I would be fully confident the new package is fine.
> I wanted to see if I can install and package the phoenix web-server
> framework and the pleroma federated social network, since both are
> becoming pretty popular recently due to their low resource requirements.
That would be really cool. I would like support for Elixir packages. I
run a REST service and GraphQL is coming. I don't like to depend on Elixir's
packaging system, though it has been reasonably OK so far. It will break at
some point - as they all do. Elixir's packaging is similar to D's dub, so we can
take some cues from that. Elixir packages everything in the local source tree -
similar to Ruby's bundler.
> I also think it's not good to have a broken package on master for so long.
> The hydra web interface shows that version 1.4.2 used to build in the
> past
> https://hydra.gnu.org/job/gnu/master/elixir-1.4.2.x86_64-linux/all?page=2
> and I only see one commit for this version in the past, so what did
> change there?
Must be a dependency that changed. Hmmm. August 2nd.
commit ee217402f7bf4b9fd49250650cf94d882a5e1a23
Author: Peter Mikkelsen <petermikkelsen10@gmail.com>
Date: Mon Jul 31 01:19:15 2017 +0200
gnu: erlang: Update to 20.0.
* gnu/packages/erlang.scm (erlang): Update to 20.0.
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
Must be it ;). It is great people are updating Erlang! These are great
programming languages.
I am happy to work on Elixir with you.
Pj.
--
next prev parent reply other threads:[~2017-12-03 5:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 0:00 bug#28034: elixir build fails nee
2017-08-22 8:09 ` Ludovic Courtès
2017-08-22 15:41 ` Efraim Flashner
2017-12-02 18:04 ` nee
2017-12-03 5:43 ` Pjotr Prins [this message]
2017-12-03 14:48 ` nee
2017-12-04 9:25 ` Ludovic Courtès
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=20171203054350.GB4188@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=28034@debbugs.gnu.org \
--cc=nee@cock.li \
/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).