Re: Why is IceCat now only 'supported' on Intel-systems?

l...@gnu.org (Ludovic Courtès) writes: > Efraim Flashner skribis: > >> On Wed, Nov 30, 2016 at 09:39:40PM -0500, Mark H Weaver wrote: >>> According to: >>> >>> https://hydra.gnu.org/eval/109381?filter=icecat#tabs-removed >>> >>> the jobs for icecat on armhf and

Re: [PATCH] gnu: mesa: Update to 13.0.1.

Marius Bakke skribis: > Ludovic Courtès writes: > >> Marius Bakke skribis: >> >>> * gnu/packages/gl.scm (mesa): Update to 13.0.1. >>> [native-inputs]: Move 'mesa-wayland-egl-symbols-check-mips.patch' to ... >>> [source]: ... here. >>>

Re: Why is IceCat now only 'supported' on Intel-systems?

Efraim Flashner skribis: > On Wed, Nov 30, 2016 at 09:39:40PM -0500, Mark H Weaver wrote: >> According to: >> >> https://hydra.gnu.org/eval/109381?filter=icecat#tabs-removed >> >> the jobs for icecat on armhf and mips64el were removed in evaluation >> 109381

Re: i686 badly broken from premature 'python-build-system' merge

Mark H Weaver skribis: > I wrote: > >> I restarted [the yasm build] again. Maybe it will work on the third >> try. > > Indeed, the it worked on the third try, and the 'gdm' build on x86_64 > worked on the second try. I'm restarting all dependency failures now. Weird. Thanks

Re: gtk-doc build failure

Marius Bakke writes: > gtk-doc is not building in current 'master'. It seems to stem from > python-build-system merge. I've committed a workaround in 3cc0342b45406f97d675266cc9ac7877be855122. There is a bug in the 'dblatex' setup.py manifesting when using the new

gtk-doc build failure

Hi, gtk-doc is not building in current 'master'. It seems to stem from python-build-system merge. I ran a bisect but had to skip a bunch of commits due to subversion build failure. To save anyone else the trouble, here is the result: There are only 'skip'ped commits left to test. The first bad

Re: Unable to configure a system with 'cuirass-service'

Hi, Carlo Zancanaro writes: > On Thu, Dec 01 2016, ng0 wrote >> I tried that before (though I did just think it was wrong) and now I >> get the same message as yesterday: >> >> ... >> >> In gnu/services/cuirass.scm: 81: 1 [cuirass-shepherd-service #] In >> unknown

Re: Why is IceCat now only 'supported' on Intel-systems?

On Wed, Nov 30, 2016 at 09:39:40PM -0500, Mark H Weaver wrote: > According to: > > https://hydra.gnu.org/eval/109381?filter=icecat#tabs-removed > > the jobs for icecat on armhf and mips64el were removed in evaluation > 109381 (corresponding to commit 663d5b5), but were present in the >

Re: [PATCH 2/2] system: Add btrfs file system support.

David Craven writes: > * gnu/system/linux-initrd.scm (linux-modules, helper-packages): Add > btrfs modules when a btrfs file-system is used. > * gnu/build/file-systems.scm (check-file-system-irrecoverable-error, > check-file-system-ext): New variables. >

[PATCH] Downgrade psyclpc.

This applies: [PATCH] gnu: psyclpc: Downgrade to The error is not obvious, as I did not submit an psyced package so far, otherwise people would complain about a broken xmpp functionality.

Re: [PATCH] gnu: mesa: Update to 13.0.1.

Marius Bakke writes: > Ludovic Courtès writes: > >> Marius Bakke skribis: >> >>> * gnu/packages/gl.scm (mesa): Update to 13.0.1. >>> [native-inputs]: Move 'mesa-wayland-egl-symbols-check-mips.patch' to ... >>> [source]: ... here. >>>

Re: i686 badly broken from premature 'python-build-system' merge

I wrote: > I restarted [the yasm build] again. Maybe it will work on the third > try. Indeed, the it worked on the third try, and the 'gdm' build on x86_64 worked on the second try. I'm restarting all dependency failures now. Mark

Re: i686 badly broken from premature 'python-build-system' merge

Hi Ludovic, l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver skribis: > >> yasm was apparently broken on i686 on the 'python-build-system' branch, >> which was then subsequently merged into master. As a result, many >> important package are dependency-failures on i686,

Re: [PATCH] gnu: mesa: Update to 13.0.1.

Ludovic Courtès writes: > Marius Bakke skribis: > >> * gnu/packages/gl.scm (mesa): Update to 13.0.1. >> [native-inputs]: Move 'mesa-wayland-egl-symbols-check-mips.patch' to ... >> [source]: ... here. >> [arguments]: Don't apply patch. >> [inputs]: Remove

Re: Why is IceCat now only 'supported' on Intel-systems?

On 01/12/16 15:13, Tobias Geerinckx-Rice wrote: > Most very likely my 7cba764 commit, ‘icecat: Use libjpeg-turbo instead > of bundled libjpeg’[-turbo]. After some more poking around Hydra I might have been too eager to take the blame for this. I'll keep an eye on it, though. Kind regards, T G-R

Re: Unable to configure a system with 'cuirass-service'

On Thu, Dec 01 2016, ng0 wrote I tried that before (though I did just think it was wrong) and now I get the same message as yesterday: ... In gnu/services/cuirass.scm: 81: 1 [cuirass-shepherd-service #] In unknown file: ?: 0 [string=? "" ((# # # # ...))] ERROR: In procedure

Re: i686 badly broken from premature 'python-build-system' merge

Mark H Weaver skribis: > yasm was apparently broken on i686 on the 'python-build-system' branch, > which was then subsequently merged into master. As a result, many > important package are dependency-failures on i686, including all > gstreamer plugins, and thus all media

Re: [PATCH] gnu: texlive-texmf-minimal: Prune in snippet.

Ludovic Courtès writes: > Ricardo Wurmus skribis: > >> Ludovic Courtès writes: >> >>> Ricardo Wurmus skribis: >>> * gnu/packages/tex.scm (texlive-texmf-minimal)[arguments]: Move contents of "prune" build phase...

Re: Why is IceCat now only 'supported' on Intel-systems?

Mark On 01/12/16 03:39, Mark H Weaver wrote: > According to: > > https://hydra.gnu.org/eval/109381?filter=icecat#tabs-removed > > the jobs for icecat on armhf and mips64el were removed in evaluation > 109381 (corresponding to commit 663d5b5), but were present in the > previous evaluation

Hydra replacement and all that

Leo Famulari skribis: > Yes, it's true. And since none of us are motivated to hack on it so far, > we'll probably put up with it until the new Hydra replacement server, > bayfront, is operational. The official ETA is "Real Soon" [0] ;) I confirm the ETA! :-) Mathieu

Re: New python build system merged

Leo Famulari skribis: > On Wed, Nov 30, 2016 at 12:26:00PM -0500, Leo Famulari wrote: >> On Wed, Nov 30, 2016 at 11:59:43AM -0500, Leo Famulari wrote: >> > This is the currently running evaluation (post-merge) compared with >> > before the merge: >> > >> >

Re: [PATCH] gnu: mesa: Update to 13.0.1.

Marius Bakke skribis: > * gnu/packages/gl.scm (mesa): Update to 13.0.1. > [native-inputs]: Move 'mesa-wayland-egl-symbols-check-mips.patch' to ... > [source]: ... here. > [arguments]: Don't apply patch. > [inputs]: Remove eudev. eudev was added in this commit: commit

Re: [PATCH] gnu: texlive-texmf-minimal: Prune in snippet.

Ricardo Wurmus skribis: > Ludovic Courtès writes: > >> Ricardo Wurmus skribis: >> >>> * gnu/packages/tex.scm (texlive-texmf-minimal)[arguments]: Move contents >>> of "prune" build phase... >>> [source]: ...to a snippet here. >> >> It looks

Re: [PATCH] gnu: Add uget.

Tomáš Čech skribis: > * gnu/packages/bittorrent.scm (uget): New variable. You can add a copyright line for yourself in that file. > +(license l:lgpl2.1))) Version 2.1 only? Otherwise LGTM, thanks! Ludo’.

Re: Unable to configure a system with 'cuirass-service'

Carlo Zancanaro writes: > On Thu, Dec 01 2016, ng0 wrote >> https://ptpb.pw/gQOZ.scm with this change it fails differently: > > This is wrong again, but for a different reason. The > `%desktop-services` must be the last argument to the `cons*` call. I tried that before

Re: Unable to configure a system with 'cuirass-service'

On Thu, Dec 01 2016, ng0 wrote https://ptpb.pw/gQOZ.scm with this change it fails differently: This is wrong again, but for a different reason. The `%desktop-services` must be the last argument to the `cons*` call. You want it to look like this (assuming my formatting comes out at least a

Re: Unable to configure a system with 'cuirass-service'

Sorry, I should really set up my client to add CC or even To with lists... Carlo Zancanaro writes: > On Wed, Nov 30 2016, ng0 wrote >> Is there anything obvious I have to change? [ 6 more citation lines. Click/Enter to show. ] > > Your

Re: i686 badly broken from premature 'python-build-system' merge

Am 01.12.2016 um 11:06 schrieb Mark H Weaver: > yasm was apparently broken on i686 on the 'python-build-system' branch, This error is not related to the python build system - until you proof me wrong. I've spend some time now for seeking the error (see below), until i discovered that yasm is nor

[PATCH] gnu: Add grantlee.

>From 2a6447853b240887810459e06e6336b1d925756f Mon Sep 17 00:00:00 2001 From: Thomas Danckaert Date: Thu, 1 Dec 2016 12:25:38 +0100 Subject: [PATCH] gnu: Add grantlee. * gnu/packages/qt.scm (grantlee): New variable. --- gnu/packages/qt.scm | 33

[PATCH] gnu: Add libksysguard.

Hi Guix, this patch adds libksysguard. I put it in kde.scm, but it's actually a part of the plasma framework. Should there be a separate module 'gnu/packages/plasma.scm' for if/when more plasma packages get packaged? Thomas >From 2e9a25b4f99ee354ce226759396fcf806502faa1 Mon Sep 17

Re: i686 badly broken from premature 'python-build-system' merge

Am 01.12.2016 um 11:06 schrieb Mark H Weaver: > yasm was apparently broken on i686 on the 'python-build-system' branch, Can you please send me the ./test-suite.log. Given only the information in the build log it is very hard to find the reason. -- Regards Hartmut Goebel | Hartmut Goebel

i686 badly broken from premature 'python-build-system' merge

Hi, yasm was apparently broken on i686 on the 'python-build-system' branch, which was then subsequently merged into master. As a result, many important package are dependency-failures on i686, including all gstreamer plugins, and thus all media players and web browsers. This branch should not

Re: [PATCH] gnu: Add varnish.

Marius Bakke writes: > Ricardo Wurmus writes: > >>> + (add-after 'install 'wrap-binary >>> + (lambda* (#:key inputs outputs #:allow-other-keys) >>> + (let* ((out (assoc-ref outputs "out")) >>> +(varnishd