bug#29522: rustc-1.16.0 broken after jemalloc updated to 5.0.1

2017-12-03 Thread Jelle Licht
2017-11-30 23:41 GMT+01:00 Adam Van Ymeren : > I haven't had time to dig in to this further, but in case anyone wants > to fix rustc-1.16.0, it's broken after the upgrade of jemalloc to 5.0.1. > > Reverting commit 475b99fa5cf402430aa93a40e406e854ad2ff6e4 which reverts > jemalloc back to 4.5.0 caus

bug#29537: Core updates broken

2017-12-03 Thread Gábor Boskovits
I'd go the GUIX_GLIBC_VERSION way. That one seems the clearest, at least to me... 2017-12-03 19:43 GMT+01:00 Marius Bakke : > Ricardo Wurmus writes: > > > Marius Bakke writes: > > > >> Gábor Boskovits writes: > >> > >>> It seems, that we have a breakage in current core-updates. m4, > gettext,

bug#29537: Core updates broken

2017-12-03 Thread Marius Bakke
Ricardo Wurmus writes: > Marius Bakke writes: > >> Gábor Boskovits writes: >> >>> It seems, that we have a breakage in current core-updates. m4, gettext, and >>> at least a few other packages fail to build. >> >> Hello! >> >> The problem is that the glibc version string is used a couple of plac

bug#29537: Core updates broken

2017-12-03 Thread Ricardo Wurmus
Marius Bakke writes: > Gábor Boskovits writes: > >> It seems, that we have a breakage in current core-updates. m4, gettext, and >> at least a few other packages fail to build. > > Hello! > > The problem is that the glibc version string is used a couple of places > to determine where locales are

bug#29537: Core updates broken

2017-12-03 Thread Gábor Boskovits
I think it is good to have this one. In my opinion it is ok, but it would be great if someone else could also have a look at that. Once we have a constent that this is a good solution it would be great to it pushed as soon as posssible, so that I can rebase on this. The only case where this might

bug#29537: Core updates broken

2017-12-03 Thread Marius Bakke
Marius Bakke writes: > Marius Bakke writes: > >> Gábor Boskovits writes: >> >>> It seems, that we have a breakage in current core-updates. m4, gettext, and >>> at least a few other packages fail to build. >> >> Hello! >> >> The problem is that the glibc version string is used a couple of places

bug#29516: Maxima fails to build

2017-12-03 Thread Diego Nicola Barbato
Mark H Weaver writes: > Diego Nicola Barbato writes: > >> Leo Famulari writes: >> >>> On Fri, Dec 01, 2017 at 11:53:01AM +0100, Diego Nicola Barbato wrote: `guix build maxima' fails during the `check' phase with the following output: >>> >>> Thanks for your report! > > FYI, the Maxima

bug#29537: Core updates broken

2017-12-03 Thread Marius Bakke
Marius Bakke writes: > Gábor Boskovits writes: > >> It seems, that we have a breakage in current core-updates. m4, gettext, and >> at least a few other packages fail to build. > > Hello! > > The problem is that the glibc version string is used a couple of places > to determine where locales are

bug#28034: elixir build fails

2017-12-03 Thread nee
Hello, thank you for the fast and detailed reply. I made two patches that upgrade erlang and elixir and disable the failing tests in elixir, and got it to build again. I sometimes get this undeterministic compile error (see the attached log). It's always the same error, but it doesn't appear ever

bug#29537: Core updates broken

2017-12-03 Thread Marius Bakke
Gábor Boskovits writes: > It seems, that we have a breakage in current core-updates. m4, gettext, and > at least a few other packages fail to build. Hello! The problem is that the glibc version string is used a couple of places to determine where locales are found. The attached patch fixes it,

bug#29546: Intermittent test failures in 'git'

2017-12-03 Thread Mark H Weaver
On Hydra, the following intermittent test failure in 'git' has occurred twice in the last two days, and twice about a month ago: --8<---cut here---start->8--- not ok 3 - git svn branch tests # # test_must_fail git svn branch a && #

bug#29537: Core updates broken

2017-12-03 Thread Gábor Boskovits
Reverting ee3ebf1a357bd4eb36a2fa1790a7b549cffb305a works. I'm sure it is not optimal, but for now I will go with it. 2017-12-03 9:45 GMT+01:00 Gábor Boskovits : > ee3ebf1a357bd4eb36a2fa1790a7b549cffb305a is the first bad commit. > > 2017-12-03 9:41 GMT+01:00 Gábor Boskovits : > >> 8dd35a0e2 is

bug#29537: Core updates broken

2017-12-03 Thread Gábor Boskovits
ee3ebf1a357bd4eb36a2fa1790a7b549cffb305a is the first bad commit. 2017-12-03 9:41 GMT+01:00 Gábor Boskovits : > 8dd35a0e2 is good > > > 2017-12-02 21:12 GMT+01:00 Gábor Boskovits : > >> It seems, that we have a breakage in current core-updates. m4, gettext, >> and at least a few other packages f

bug#29537: Core updates broken

2017-12-03 Thread Gábor Boskovits
8dd35a0e2 is good 2017-12-02 21:12 GMT+01:00 Gábor Boskovits : > It seems, that we have a breakage in current core-updates. m4, gettext, > and at least a few other packages fail to build. > > We had a discussion about that on irc, here are the important points: > > [09:34:53]