Re: [PATCH 2/2] emacs: Add interface for comparing generations.

Ludovic Courtès (2014-11-04 01:22 +0300) wrote: > Alex Kost skribis: [...] >> Perhaps "s/The Emacs Editor/The GNU Emacs Manual/"? As it's the most >> common (but not the one) variant in the Emacs Lisp manual, for example here: >>

Re: [PATCH] gnu: Add freeimage.

Andreas Enge writes: > Unfortunately, it fails to build on mips: >http://hydra.gnu.org/build/136438 > Could you have a look? To me it looks as if there is bad assembly code > in the source: > /tmp/nix-build-freeimage-3.16.0.drv-0/cc1WaZEm.s: Assembler messages: > /tmp/nix-build-freeimage-3.16

Re: [PATCH 2/2] emacs: Add interface for comparing generations.

Alex Kost skribis: > Ludovic Courtès (2014-11-02 20:59 +0300) wrote: > >> Alex Kost skribis: >> >>> In short, now (with this patch) after marking 2 generations (by pressing >>> "m" in a “generation-list” buffer), you can perform diff/ediff on >>> generation packages or manifests. Thanks to Ludo

Re: [PATCH 2/2] gnu: Add gnome-themes-standard.

Federico Beffa skribis: > From 7439f19c1f2966466da88554478b796c3bfca429 Mon Sep 17 00:00:00 2001 > From: Federico Beffa > Date: Sun, 2 Nov 2014 18:09:33 +0100 > Subject: [PATCH 2/2] gnu: Add gnome-themes-standard. > > * gnu/packages/gnome.scm (gnome-themes-standard): New variable. [...] > +;;

Re: [PATCH 1/2] gnu: librsvg: Generate complete loaders.cache including support for SVG.

Federico Beffa skribis: > As mentioned in a previous email, the cache generated by default does > not include support for SVG provided by librsvg itself. With this > patch we generate a full cache file. Nice. > From 36c6d59180bdb2d80e169938097efca39431c122 Mon Sep 17 00:00:00 2001 > From: Fede

Re: Changing python-wrapper to handle lib/ etc.

On Mon, Nov 03, 2014 at 09:49:21PM +0100, Andreas Enge wrote: > In 2.0.12 without python, now the guile tests fail... 3.0.2 without python > compiles well, so I am trying to build the swig dependencies now. Everything worked well, so I pushed this solution to wip-python. Andreas

Re: [PATCH] gnu: Add Cython

On Mon, Nov 3, 2014 at 9:12 PM, Federico Beffa wrote: > No, Andreas is right: this patch suffers from the same problem as Numpy. Maybe I wasn't clear :-) the patch does include python as an input. So, it will build in master, without any change in python-wrapper. After the changes in python-wrap

Re: Changing python-wrapper to handle lib/ etc.

On Mon, Nov 03, 2014 at 09:19:28PM +0100, Andreas Enge wrote: > This was it not. There is also a newer swig-3.0.2, but it also does not > solve the problem. My suspicion is that swig has never worked with python > for us. So my current solution would be to disable it and push this change > if all d

Re: Font package naming convention

Andreas Enge skribis: > On Mon, Nov 03, 2014 at 09:53:21AM +0100, Ludovic Courtès wrote: >> If there’s rough consensus on this, the next step would be to write this >> informal rule in the manual, and to update package names. >> >> Any volunteer? Alex? :-) > > I volunteer, as I feel responsibl

Re: [PATCH] gnu: Add freeimage.

Andreas Enge skribis: > On Mon, Nov 03, 2014 at 10:00:38AM +0100, Ludovic Courtès wrote: >> Same problem as with Valgrind, so I would suggest disabling builds on >> MIPS, as done in commit 67a86d3. > > Speaking of valgrind, how is transitivity of disabled builds handled, > on hydra and by the use

Re: Changing python-wrapper to handle lib/ etc.

On Mon, Nov 03, 2014 at 11:13:45AM +0100, Andreas Enge wrote: > Thanks, I will try to update and keep you updated. This was it not. There is also a newer swig-3.0.2, but it also does not solve the problem. My suspicion is that swig has never worked with python for us. So my current solution would

Re: [PATCH] gnu: Add Cython

On Mon, Nov 3, 2014 at 8:50 PM, Andreas Enge wrote: > On Mon, Nov 03, 2014 at 08:42:25PM +0100, Ludovic Courtès wrote: >> But are you sure you aren’t confusing it with NumPy, which requires the >> new python-wrapper? > > Probably I am confusing things, even less problems then! > No, Andreas is ri

Re: [PATCH] gnu: Add Cython

On Mon, Nov 03, 2014 at 08:42:25PM +0100, Ludovic Courtès wrote: > But are you sure you aren’t confusing it with NumPy, which requires the > new python-wrapper? Probably I am confusing things, even less problems then! Andreas

Re: [PATCH] gnu: Add Cython

Andreas Enge skribis: > On Mon, Nov 03, 2014 at 05:57:58PM +0100, Ludovic Courtès wrote: >> Federico Beffa skribis: >> > Subject: [PATCH] gnu: Add Cython >> > * gnu/packages/python.scm(cython,cython2): New variables. >> Pushed, with missing spaces in the commit log added. > > I think that should

Re: Volunteering

Felipe López skribis: > Should I send patches to the mailing list or do I join Guix in Savannah > for commit access? Patches would be inadequate. What about posting a link to the SVGs to the mailing list so we can see, and then commit those that are selected to the artwork.git repo? For the la

Re: [PATCH] gnu: Add Cython

On Mon, Nov 03, 2014 at 05:57:58PM +0100, Ludovic Courtès wrote: > Federico Beffa skribis: > > Subject: [PATCH] gnu: Add Cython > > * gnu/packages/python.scm(cython,cython2): New variables. > Pushed, with missing spaces in the commit log added. I think that should have gone on the wip-python bran

Re: [PATCH] gnu: Add docbook-xml-4.2

Andreas Enge skribis: > On Sun, Nov 02, 2014 at 06:26:59PM +0100, Federico Beffa wrote: >> Add version 4.2. It is needed by dconf. > > This looks very safe Yes, please push. > (although we will end up with four versions of it!). Right, but it seems inherent to DocBook and document systems in

Re: [PATCH] gnu: Add Cython

Federico Beffa skribis: > From 3155aa1ec614afb01b7bff0bbf3eabb4ee5bb0de Mon Sep 17 00:00:00 2001 > From: Federico Beffa > Date: Mon, 20 Oct 2014 19:52:45 +0200 > Subject: [PATCH] gnu: Add Cython > > * gnu/packages/python.scm(cython,cython2): New variables. Pushed, with missing spaces in the com

Re: [PATCH] gnu: add atlas

Federico Beffa skribis: > Thanks for the offer! I've created an account. My knowledge of git > is very limited and I've never pushed any change with it. I will > therefore need some guidance. I'm reading Git Pro > http://git-scm.com/book/en/v2 No problem. If in doubt just ask by email or st

Re: Volunteering

On 03/11/14 04:27, Ludovic Courtès wrote: > Hello, > > Felipe López skribis: > >> I read somewhere that you may be needing some graphics soon. In >> gNewSense I used to do visual-theme proposals for each mayor version of >> the system [1][2] and I would like to do the same for Guix if you think

Re: Font package naming convention

Andreas Enge (2014-11-03 12:30 +0300) wrote: > On Mon, Nov 03, 2014 at 09:53:21AM +0100, Ludovic Courtès wrote: >> If there’s rough consensus on this, the next step would be to write this >> informal rule in the manual, and to update package names. >> >> Any volunteer? Alex? :-) > > I volunteer

Re: Changing python-wrapper to handle lib/ etc.

On Mon, Nov 03, 2014 at 11:11:22AM +0100, Federico Beffa wrote: > - Compilation fixes on some systems for the generated Lua, PHP, Python > and R wrappers. > Maybe, it was an upstream bug? Thanks, I will try to update and keep you updated. Andreas

Re: Changing python-wrapper to handle lib/ etc.

On Sun, Nov 2, 2014 at 10:32 PM, Andreas Enge wrote: > With the new python wrapper, something is found: > checking for python3-config... python3-config > checking for Python 3.x prefix... > /gnu/store/r6614z0w2inxn78wzaa7ic5sai8s7l9f-python-3.3.5 > checking for Python 3.x exec-prefix... > /gnu/s

[andr...@enge.fr: ATLAS fails to build on mips]

As I am not sure if Fede is subscribed to the bug mailing list, I am forwarding my report here. It is http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18933 Andreas - Forwarded message from Andreas Enge - ATLAS fails to build on mipsel64: http://hydra.gnu.org/build/133025 with mkdir A

Re: Font package naming convention

On Mon, Nov 03, 2014 at 09:53:21AM +0100, Ludovic Courtès wrote: > If there’s rough consensus on this, the next step would be to write this > informal rule in the manual, and to update package names. > > Any volunteer? Alex? :-) I volunteer, as I feel responsible for the package guidelines. An

Re: [PATCH] gnu: Add freeimage.

On Mon, Nov 03, 2014 at 10:00:38AM +0100, Ludovic Courtès wrote: > Same problem as with Valgrind, so I would suggest disabling builds on > MIPS, as done in commit 67a86d3. Speaking of valgrind, how is transitivity of disabled builds handled, on hydra and by the users? I noticed that some packages

Re: Volunteering

Hello, Felipe López skribis: > I read somewhere that you may be needing some graphics soon. In > gNewSense I used to do visual-theme proposals for each mayor version of > the system [1][2] and I would like to do the same for Guix if you think > it's OK. Is anyone working on the visual part of th

Re: Changing python-wrapper to handle lib/ etc.

Andreas Enge skribis: > On Thu, Oct 30, 2014 at 02:12:58PM +0100, Ludovic Courtès wrote: >> We’ll also need the patch from >> in >> this branch. > > Maybe not Indeed. (I replied in the other thread.) > I created the branch, s

Re: [PATCH] gnu: Add freeimage.

Andreas Enge skribis: > Could you have a look? To me it looks as if there is bad assembly code > in the source: > /tmp/nix-build-freeimage-3.16.0.drv-0/cc1WaZEm.s: Assembler messages: > /tmp/nix-build-freeimage-3.16.0.drv-0/cc1WaZEm.s:360: Error: opcode not > supported on this processor: mips3 (

Re: Different versions of a package in the same profile?

Federico Beffa skribis: > Andreas Enge writes: > >> On Sun, Nov 02, 2014 at 06:22:28PM +0100, Ludovic Courtès wrote: >> There is also the question of conflicts with identical file names. They are >> already there now, but their probability should be higher with identical >> package names. Maybe

Re: Font package naming convention

Andreas Enge skribis: > On Sun, Nov 02, 2014 at 06:18:19PM +0100, Ludovic Courtès wrote: >> Some of the fonts created by foundries are often referred to it using >> the foundry’s name, such as “Bitstream Vera”; there are also >> counter-examples, like Gentium, Charis, etc. (by SIL.) >> >> So, ag

Re: [PATCH 0/2] gnu: Add sdl-union and guile-sdl

David Thompson skribis: > Regarding sdl-union: > > * This package isn't useful for users, only developers. Should I keep it > private so that it doesn't show up in package searches? Probably, yes. But could you remind me why it’s needed? ISTR from earlier discussions that some tools (‘sdl-con

Volunteering

Hi, I've been helping in libre software projects for some years. The last project in which I participated was gNewSense. I helped there since version 2.4 doing some graphics, documentation, and translations. I've done some scripting in Python, and I'm learning to program, but I'm a naive programme