Ricardo Wurmus writes:
> Marius Bakke writes:
>
>> "vim-full" also has a failing test, but is arguably less important.
>> There are "relink" warnings during the test phase, like this:
>>
>> Relink
>> `/gnu/store/vis7x2j2lsmwbl5m5w794c23ysqah8xh-libpng-1.6.28/lib/libpng16.so.16'
>> with
>> `/g
Marius Bakke writes:
> One "greenisland" test is segfaulting. This package is needed for the
> "sddm" display manager, so I don't think we should merge until that is
> sorted. I'm looking into it now, but struggling to produce useful
> debugging information.
Apparently "ctest" will invoke "gdb"
Marius Bakke writes:
> "vim-full" also has a failing test, but is arguably less important.
> There are "relink" warnings during the test phase, like this:
>
> Relink
> `/gnu/store/vis7x2j2lsmwbl5m5w794c23ysqah8xh-libpng-1.6.28/lib/libpng16.so.16'
> with
> `/gnu/store/rmjlycdgiq8pfy5hfi42qhw3k
Ludovic Courtès writes:
> Hi!
>
> It looks like we’re doing okay now? There are still a number of
> armhf-linux builds pending, but if everything goes well, I think we
> should merge tomorrow (Sunday). WDYT?
One "greenisland" test is segfaulting. This package is needed for the
"sddm" display m
Leo Famulari writes:
> On Sun, Apr 02, 2017 at 12:30:28AM +0200, Ludovic Courtès wrote:
>> Hi!
>>
>> It looks like we’re doing okay now? There are still a number of
>> armhf-linux builds pending, but if everything goes well, I think we
>> should merge tomorrow (Sunday). WDYT?
>
> Yes, I like
On Sun, Apr 02, 2017 at 12:30:28AM +0200, Ludovic Courtès wrote:
> Hi!
>
> It looks like we’re doing okay now? There are still a number of
> armhf-linux builds pending, but if everything goes well, I think we
> should merge tomorrow (Sunday). WDYT?
Yes, I like this plan.
signature.asc
Descrip
Hi!
It looks like we’re doing okay now? There are still a number of
armhf-linux builds pending, but if everything goes well, I think we
should merge tomorrow (Sunday). WDYT?
Thanks,
Ludo’.
From: Marius Bakke
Subject: Re: Let’s freeze and build ‘core-updates’!
Date: Wed, 29 Mar 2017 15:41:56 +0200
For the rest.. please share your findings!
Perhaps this is not a “finding”, but just a positive anecdote: I
reconfigured on core-updates and it's working fine (after an
afterno
The following packages are now fixed in core-updates:
* discrover
* hugs
* powertabeditor
* stringtie
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
Marius Bakke writes:
> * discrover
I’ll try to fix this.
> * a handful of guile libraries
Including guile-reader, which has problems with generated code. Not
sure what to do here.
> * hugs (abondoned upstream, no users, remove?)
Hugs may eventually be needed for bootstrapping GHC. I’ll tr
On Wed, Mar 29, 2017 at 03:41:56PM +0200, Marius Bakke wrote:
> With those out of the way, here are most remaining problems on x86_64:
>
> * aegis
> * discrover
> * clang-3.5.2 (can this be removed?)
> * elixir
> * gcc-4.7.4 (likewise)
> * glog
> * a handful of guile libraries
> * hugs (abondoned
On Wed, Mar 29, 2017 at 03:41:56PM +0200, Marius Bakke wrote:
> Here are the results of the latest evaluation:
>
> https://hydra.gnu.org/eval/109570?full=1&compare=master#tabs-now-fail
>
> I cannot reproduce these failures, please try restarting the jobs:
>
> https://hydra.gnu.org/job/gnu/core-u
Marius Bakke writes:
> Here are the results of the latest evaluation:
>
> https://hydra.gnu.org/eval/109570?full=1&compare=master#tabs-now-fail
[...]
> With those out of the way, here are most remaining problems on x86_64:
>
> * aegis
> * discrover
> * clang-3.5.2 (can this be removed?)
> * eli
Leo Famulari writes:
> On Tue, Feb 14, 2017 at 10:05:04AM +0100, Ludovic Courtès wrote:
>> So, here’s a plan:
>>
>> • Once Efraim has pushed some of the aarch64 patches, do another
>> evaluation of the “core” package set for that branch, and check for
>> anything wrong. From there on,
Thomas Danckaert writes:
> From: Leo Famulari
> Subject: Re: Let’s freeze and build ‘core-updates’!
> Date: Mon, 20 Mar 2017 14:41:45 -0400
>
>> Sometimes there is a spurious build failure: The SSH connection
>> used for
>> offloading fails, or the build mach
From: Leo Famulari
Subject: Re: Let’s freeze and build ‘core-updates’!
Date: Mon, 20 Mar 2017 14:41:45 -0400
Sometimes there is a spurious build failure: The SSH connection
used for
offloading fails, or the build machine is out of memory. Reply to
this
thread with a link to the failing build
On Tue, Mar 21, 2017 at 10:19:02PM +0100, Julien Lepiller wrote:
> On Mon, 20 Mar 2017 14:41:45 -0400
> Leo Famulari wrote:
>
> > We are at this stage... please help :)
> >
> > Here is a list of packages that are failing on core-updates but not on
> > the master branch:
> >
> > https://hydra.gn
Julien Lepiller writes:
> zsh (https://hydra.gnu.org/build/1883646) failed but the last line is:
>
> build-succeeded /gnu/store/8q928a90f08qc3nfsdf4h39lx8yyr8pm-zsh-5.2.drv
That was probably a transient failure. It’s currently marked as
“Scheduled to be built”.
--
Ricardo
GPG: BCA6 89B6 3655
On Mon, 20 Mar 2017 14:41:45 -0400
Leo Famulari wrote:
> We are at this stage... please help :)
>
> Here is a list of packages that are failing on core-updates but not on
> the master branch:
>
> https://hydra.gnu.org/eval/109549?compare=master&full=1#tabs-now-fail
>
> It might take a while to
On Tue, Mar 21, 2017 at 12:16:20PM +0100, julien lepiller wrote:
> c-reduce seems to have failed because of a crash in g++. Maybe the server
> lacked memory? It builds fine here.
Thanks for checking on the log!
Indeed, errors like this one...
g++: internal compiler error: Killed (program cc1plus
Le 2017-03-20 19:41, Leo Famulari a écrit :
On Tue, Feb 14, 2017 at 10:05:04AM +0100, Ludovic Courtès wrote:
So, here’s a plan:
• Once Efraim has pushed some of the aarch64 patches, do another
evaluation of the “core” package set for that branch, and check
for
anything wrong. From
On Tue, Feb 14, 2017 at 10:05:04AM +0100, Ludovic Courtès wrote:
> So, here’s a plan:
>
> • Once Efraim has pushed some of the aarch64 patches, do another
> evaluation of the “core” package set for that branch, and check for
> anything wrong. From there on, forbid full-rebuild changes.
On Fri, Mar 10, 2017 at 10:46:34PM +0100, Marius Bakke wrote:
> It looks like Hydra ran out of entropy which caused a bunch of failures.
> Will you restart it? :)
Done!
signature.asc
Description: PGP signature
Leo Famulari writes:
> On Tue, Feb 14, 2017 at 10:05:04AM +0100, Ludovic Courtès wrote:
>> • Build all the packages. (To do that, someone with access to Hydra
>> must change the “subset” argument to “all” in the config of the
>> ‘core-updates’ jobset.)
>
> I've just started an evaluati
On Tue, Feb 14, 2017 at 10:05:04AM +0100, Ludovic Courtès wrote:
> • Build all the packages. (To do that, someone with access to Hydra
> must change the “subset” argument to “all” in the config of the
> ‘core-updates’ jobset.)
I've just started an evaluation of "all" the packages :)
>
On Wed, Mar 08, 2017 at 09:44:26AM +0100, Ludovic Courtès wrote:
> Leo Famulari skribis:
> > Subject: [PATCH 1/2] gnu: xorg-server: Update to 1.19.2 [fixes
> > CVE-2017-2624].
> > Subject: [PATCH 2/2] gnu: gtk+: Build GTK+ with its own xorg-server package.
Pushed!
> After that I think we can st
Leo Famulari skribis:
> On Tue, Mar 07, 2017 at 02:59:39PM +0100, Ludovic Courtès wrote:
>> I guess it could be called ‘xorg-server-1.9.12’ and technically inherit
>> from ‘xorg-server’ but override the version and source.
>
> I've attached patches updating xorg-server and creating a special
> pa
On Tue, Mar 07, 2017 at 02:59:39PM +0100, Ludovic Courtès wrote:
> I guess it could be called ‘xorg-server-1.9.12’ and technically inherit
> from ‘xorg-server’ but override the version and source.
I've attached patches updating xorg-server and creating a special
package to be used for building GTK
Leo Famulari skribis:
> On Mon, Mar 06, 2017 at 04:39:56PM +0100, Ludovic Courtès wrote:
>> It’s been 3 days since their message and it hasn’t happened yet, so
>> perhaps we should simply run autoreconf.
>>
>> Thoughts?
>
> Okay.
>
>> BTW, xorg-server is a build-time dependency of gtk+@3 (for te
On Mon, Mar 06, 2017 at 04:39:56PM +0100, Ludovic Courtès wrote:
> It’s been 3 days since their message and it hasn’t happened yet, so
> perhaps we should simply run autoreconf.
>
> Thoughts?
Okay.
> BTW, xorg-server is a build-time dependency of gtk+@3 (for test
> purposes), which is the main r
On Mon, Mar 06, 2017 at 07:54:06PM +0100, Marius Bakke wrote:
> Another option is to keep version 2.6.2 around, which is better than a
> specialized "flex-for-grub". If the previous version works for both grub
> and wireshark, I prefer this alternative.
The choices are a bit overwhelming; there ar
On Mon, Mar 06, 2017 at 07:49:42PM +0100, Marius Bakke wrote:
> Leo Famulari writes:
> > Let's also decide what to do about GRUB. I updated it originally because
> > something (I forgot what) failed to build without a newer GRUB.
>
> I think you meant "flex" here.
Yup! :p
> According to https:/
Marius Bakke writes:
> Leo Famulari writes:
>
>> On Mon, Mar 06, 2017 at 10:19:34AM +0100, Ludovic Courtès wrote:
>>> Hello Guix!
>>>
>>> Looks like there’s been a disk space issue a few days ago that’s now
>>> solved, so I’ve restarted an evaluation of the “core” subset.
>>>
>>> Is there any
Leo Famulari writes:
> On Mon, Mar 06, 2017 at 10:19:34AM +0100, Ludovic Courtès wrote:
>> Hello Guix!
>>
>> Looks like there’s been a disk space issue a few days ago that’s now
>> solved, so I’ve restarted an evaluation of the “core” subset.
>>
>> Is there any blocker left or should we move fo
On Mon, Mar 06, 2017 at 10:19:34AM +0100, Ludovic Courtès wrote:
> Hello Guix!
>
> Looks like there’s been a disk space issue a few days ago that’s now
> solved, so I’ve restarted an evaluation of the “core” subset.
>
> Is there any blocker left or should we move forward after that?
Let's also d
Marius Bakke skribis:
> Ludovic Courtès writes:
>
>> Hello Guix!
>>
>> Looks like there’s been a disk space issue a few days ago that’s now
>> solved, so I’ve restarted an evaluation of the “core” subset.
>>
>> Is there any blocker left or should we move forward after that?
>
> We were waiting f
Ludovic Courtès writes:
> Hello Guix!
>
> Looks like there’s been a disk space issue a few days ago that’s now
> solved, so I’ve restarted an evaluation of the “core” subset.
>
> Is there any blocker left or should we move forward after that?
We were waiting for the xorg-server 1.19.3 hotfix tha
Hello Guix!
Looks like there’s been a disk space issue a few days ago that’s now
solved, so I’ve restarted an evaluation of the “core” subset.
Is there any blocker left or should we move forward after that?
Thanks,
Ludo’.
Hello,
On Tue, Feb 21, 2017 at 03:03:52PM +0100, Marius Bakke wrote:
> I believe Efraim has pushed the remaining aarch64 patches, and I just
> merged in the updates from staging, as well as an xorg and cmake update.
>
> I think we're ready to build the "core" package set now.
thanks to all who h
On Tue, Feb 21, 2017 at 12:32:01PM -0500, Leo Famulari wrote:
> On Tue, Feb 21, 2017 at 03:03:52PM +0100, Marius Bakke wrote:
> > I believe Efraim has pushed the remaining aarch64 patches, and I just
> > merged in the updates from staging, as well as an xorg and cmake update.
> >
> > I think we're
On Tue, Feb 21, 2017 at 03:03:52PM +0100, Marius Bakke wrote:
> I believe Efraim has pushed the remaining aarch64 patches, and I just
> merged in the updates from staging, as well as an xorg and cmake update.
>
> I think we're ready to build the "core" package set now. Mark, Leo?
I think we shoul
Ludovic Courtès writes:
> Hey Marius,
>
> Marius Bakke skribis:
>
>> Ludovic Courtès writes:
>>
>>> Hello Guix!
>>>
>>> Since I’m about to leave keyboard for a couple of weeks, here’s a to-do
>>> list for those of you who’ll be around. :-)
>>>
>>> The last things I wanted to push for ‘core-upd
Hey Marius,
Marius Bakke skribis:
> Ludovic Courtès writes:
>
>> Hello Guix!
>>
>> Since I’m about to leave keyboard for a couple of weeks, here’s a to-do
>> list for those of you who’ll be around. :-)
>>
>> The last things I wanted to push for ‘core-updates’ were a reproducible
>> Guile (done
Ludovic Courtès writes:
> Hello Guix!
>
> Since I’m about to leave keyboard for a couple of weeks, here’s a to-do
> list for those of you who’ll be around. :-)
>
> The last things I wanted to push for ‘core-updates’ were a reproducible
> Guile (done in b5efd14a9add1bcb4a44fa5b9c1b47706f3df9da),
Hello Guix!
Since I’m about to leave keyboard for a couple of weeks, here’s a to-do
list for those of you who’ll be around. :-)
The last things I wanted to push for ‘core-updates’ were a reproducible
Guile (done in b5efd14a9add1bcb4a44fa5b9c1b47706f3df9da), and a subset
or all of the aarch64 pat
45 matches
Mail list logo
