Hi Thorsten,
Thorsten Wilms writes:
> Hi Guix!
>
> I already had a "rename" binary via util-linux. Then I installed the
> package "rename", resulting in another "rename" binary, as I prefer
> the Perl version. This was a success in that I got what I wanted.
>
> However, should this name clash
>
> Laura, I saw you already have an account for libreplanet. Feel free to
> go on editing this page. I really just copy/pasted Ricardos email here.
>
> Great! Yes, I created it to edit the file about attending to FOSDEM, was
that wrong?
And thanks!
Regards :)
Laura
On Fri, 23 Nov 2018 10:04:02 +0100
Ricardo Wurmus wrote:
> Björn Höfling writes:
>
> > On Wed, 21 Nov 2018 17:18:54 -0300
> > Laura Lazzati wrote:
> >
> >> Hi again!
> >>
> >> I went through past emails and this new ones.
> >>
> >> In a previous mail, Bjorn suggested using the wiki -
> >>
Hi Ludovic,
l...@gnu.org (Ludovic Courtès) writes:
> guix-comm...@gnu.org skribis:
>
>> commit e1d97c4efc42a661bd2772041371303e4070aa4f
>> Author: Mark H Weaver
>> Date: Mon Nov 5 04:04:45 2018 -0500
>>
>> gnu: rhythmbox: Update hash of patch.
>>
>> * gnu/packages/gnome.scm
l...@gnu.org (Ludovic Courtès) writes:
> Heya,
>
> Marius Bakke skribis:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>>
>>> Hello Guix,
>>>
>>> As briefly discussed with Marius on IRC, we both tried to fix
>>> LibreOffice on ‘core-updates’. The initial problem is that some of the
>>> libraries
Le Sun, 25 Nov 2018 15:26:37 +0100,
l...@gnu.org (Ludovic Courtès) a écrit :
> Heya,
>
> Marius Bakke skribis:
>
> > l...@gnu.org (Ludovic Courtès) writes:
> >
> >> Hello Guix,
> >>
> >> As briefly discussed with Marius on IRC, we both tried to fix
> >> LibreOffice on ‘core-updates’. The
Hello Mark,
guix-comm...@gnu.org skribis:
> commit e1d97c4efc42a661bd2772041371303e4070aa4f
> Author: Mark H Weaver
> Date: Mon Nov 5 04:04:45 2018 -0500
>
> gnu: rhythmbox: Update hash of patch.
>
> * gnu/packages/gnome.scm (rhythmbox)[source]: Update hash of the applied
>
Hello,
n...@n0.is skribis:
> names for packages are (mostly) random, although in some
> cases following classiifcations (see python-*, r-*, ...).
That randomness is very limited in practice, if I may. :-)
https://gnu.org/software/guix/manual/en/html_node/Package-Naming.html
“qtoctave” was
Hello Danny,
Danny Milosavljevic skribis:
> On Fri, 23 Nov 2018 14:52:42 +0100
> l...@gnu.org (Ludovic Courtès) wrote:
>
>> --
>>
Alex Vong writes:
> n...@n0.is writes:
>
>> names for packages are (mostly) random, although in some
>> cases following classiifcations (see python-*, r-*, ...).
>>
> I am thinking that should we rename qtoctave to octave and octave to
> octave-cli (or octave-minimal)?
>
> Firstly, a new user
Hello,
I had a look at that. You should not need the if there, just 'return'
the test of the if.
If has a form (if test conseqent alternate), alternate is optional and
returns the value of the
evaluated branch (consequent or alternate). This gives you a syntax
error, as the mandatory
consequent
Heya,
Marius Bakke skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Hello Guix,
>>
>> As briefly discussed with Marius on IRC, we both tried to fix
>> LibreOffice on ‘core-updates’. The initial problem is that some of the
>> libraries it depends on fail to build with the new Boost.
>>
>>
n...@n0.is writes:
> names for packages are (mostly) random, although in some
> cases following classiifcations (see python-*, r-*, ...).
>
I am thinking that should we rename qtoctave to octave and octave to
octave-cli (or octave-minimal)?
Firstly, a new user wanting to install octave will
Hi
I am still a novice in guile so I humbly ask for help with this error
trying to get the blacklisting to work:
sdb@komputilo ~$ ~/guix-tree/pre-inst-env guix import npm leaflet
ice-9/boot-9.scm:222:17: In procedure map1:
Syntax error:
/home/sdb/guix-tree/guix/import/npm.scm:304:2: source
On 2018-11-24 16:41, Jelle Licht wrote:
Hey swedebugia,
I will still send a more elaborate reply to the general npm-importer
thread later this week, but we can assume that generally these
recursive dependencies can be untangled by looking at the different
versions of the dependencies.
So in
>> I'm trying to build the core-updates-next branch. I'm getting the
>> following hash mismatch error. Is someone else facing the same problem
>> too, or is this something wrong on my side?
>
> Oops, I accidentally uploaded a newer (intermediate) tarball yesterday.
> Should be fixed now. Can
Arun Isaac writes:
Hi!
> I'm trying to build the core-updates-next branch. I'm getting the
> following hash mismatch error. Is someone else facing the same problem
> too, or is this something wrong on my side?
Oops, I accidentally uploaded a newer (intermediate) tarball yesterday.
Should be
On Sat, Nov 24, 2018 at 11:29:08PM +, Jelle Licht wrote:
> >So in your example, I imagine an input chain like:
> >node-glob 0.1 -> node-rimraf 0.1 -> node-glob 0.2 ->
> node-rimraf 0.2
> >-> -> node-glob 1.0 -> node-rimraf 1.0
> >While *extremely*
I'm trying to build the core-updates-next branch. I'm getting the
following hash mismatch error. Is someone else facing the same problem
too, or is this something wrong on my side?
Starting download of
19 matches
Mail list logo
