Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'guix' has been submitted
by the Tamil team of translators. The file is available at:
https://translationproject.org/latest/guix/ta.po
(We can arrange things so that in the
On Tue, Nov 10, 2020 at 04:11:55PM +0100, Simon Josefsson wrote:
> Thanks for the review! How about this updated patch?
Thank you!
> From 7c57d7b93f1315ff02e55d11d41b8c9442bb7633 Mon Sep 17 00:00:00 2001
> From: Simon Josefsson
> Date: Tue, 10 Nov 2020 16:10:17 +0100
> Subject: [PATCH] gnu:
On Tue, Nov 10, 2020 at 08:56:21PM +0100, Tobias Platen wrote:
> Hello,
>
> I've got the wip-ppc branch of Guix compiling unmodified on my Talos II.
> Since the POWER9 is backwards compatible with the PowerPC G4, it can run
> the existing bootstrap binaries for powerpc-linux. The binaries from
>
Pierre Neidhardt writes:
>> I had not realized sbcl-static-dispatch failed to build even on 'master'
>> initially, did you commit it by mistake? If I'd known I would not have
>> let it hold up the merge.
>
> Weird, it works for me on be0ebf33aa19dcfd36c7a8d22a53344dc3b4a533
It did not work for
Marius Bakke writes:
> I can confirm the above commit works.
Cool, thanks!
> I had not realized sbcl-static-dispatch failed to build even on 'master'
> initially, did you commit it by mistake? If I'd known I would not have
> let it hold up the merge.
Weird, it works for me on
Hello,
I've got the wip-ppc branch of Guix compiling unmodified on my Talos II.
Since the POWER9 is backwards compatible with the PowerPC G4, it can run
the existing bootstrap binaries for powerpc-linux. The binaries from
http://flashner.co.il/guix/bootstrap/powerpc-linux/ have been verified
Pierre Neidhardt writes:
> Marius Bakke writes:
>
>> Speaking of the Common Lisp build system on 'staging', the newly-added
>> 'sbcl-static-dispatch' fails to build when merged or cherry-picked.
>>
>> Can you look into it?
>
> I haven't tested but this could be fixed by the commit I've just
Bonface M. K. writes:
> Christopher Lemmer Webber
> writes:
>
>> Dimos Dimakakos writes:
>>
>>> Bonface M. K. writes:
>>>
To simply put it, AFAIU updating a package would
require racket to update it's references(either
links, and other references that I won't go into),
hence
Leo Famulari writes:
> I notice that the commit message says "Drop patch", but that this change
> actually removes two patches from the oath-toolkit.
>
> It removes the application of both "oath-toolkit-glibc-compat.patch" and
> also the "oath-toolkit-update-gnulib.patch". Is that intended?
>
>
Dear,
On Fri, 6 Nov 2020 at 13:52, zimoun wrote:
> > Thoughts? Patches? Ideas? :-)
>
> A lot of substitutes are still missing (for example R). Is it possible
> to trigger the builds?
I think Ludo tried to trigger a rebuild of all the r-* packages, see
[1]. However, "guix weather -c 15"
Hi racket-dev and racket-users!
I'm trying to create a build system for Racket in
Guix(a long-standing feature for some of us in the
Guix community). It appears that Racket, vis-a-vis
raco, maintains some "global" state whereby
package-installs leads to the update of some
files, links,
Christopher Lemmer Webber
writes:
> Dimos Dimakakos writes:
>
>> Bonface M. K. writes:
>>
>>> To simply put it, AFAIU updating a package would
>>> require racket to update it's references(either
>>> links, and other references that I won't go into),
>>> hence creating some form of "global
Hi folks! I use Emacs to write and maintain Guix packages, and I've
created some tools and snippets to automate repetitive tasks and remove
guesswork. If you also use Emacs, you might be interested to try them or
contribute your own.
My repository is here:
Looks like static-dispatch works on staging, but there is an issue with
the new build system for the next package I want to add, generic-cl.
I need to ping Guillaume on that and preferably before merging staging.
I'll open an issue just now.
--
Pierre Neidhardt
https://ambrevar.xyz/
Hi Tanguy,
Am 10.11.20 um 09:47 schrieb Tanguy Le Carrour:
Actually, I'm not even yet sure that Poetry needs a dedicated build system,
as it also relies on a build-backend (defined in `pyproject.toml`) which
just happened to be `poetry.core.masonry`, but could be another one… I
guess, I'm not
Hi Hartmut,
Le 11/09, Hartmut Goebel a écrit :
> seems like another messages of mine, regarding the first thread about a
> poetry build system, did not make it to the list.
>
> Am 08.11.20 um 15:27 schrieb Tanguy Le Carrour:
> > I've just learned, by accident (working on `python-keyring` [1]),
Hi Leo,
Le 11/08, Leo Famulari a écrit :
> On Sun, Nov 08, 2020 at 03:27:17PM +0100, Tanguy Le Carrour wrote:
> > `pep517` keeps on trying to download dependencies, which won't work.
>
> That usually means that the software is missing some dependencies. If
> you think they should be available in
Hi Michael,
Le 11/08, Michael Rohleder a écrit :
> Tanguy Le Carrour writes:
> > I've just learned, by accident (working on `python-keyring` [1]), that
> > `python setup.py install` was somehow deprecated in favor of tools like
> > `pep517` or `build`.
> >
> > So, I've tried packaging
18 matches
Mail list logo
