Hi Guix!
Few days ago, I submitted a patch to update `python-tomlkit`. It was pushed
to master and, after I upgraded my packages today, I realised that `poetry`
(and possibly other python packages) was broken!
The "problem" is that Poetry depends on `tomlkit = "^0.5.11"`. This
translates to
Hello,
On Mon, Jul 27, 2020 at 12:58:52PM +0200, Ludovic Courtès wrote:
> It’s gonna take a while, but I think we’d rather be safe than sorry
> given that these two libraries underpin the toolchain chain (sic).
oh well, never ask a question when you fear the answer might not be
what you hope for
Hello Jonathan,
Thanks a lot for this nice report. Let me summarize a bit the situation
first, before commenting on your findings.
On our main "berlin" build farm, we have currently a few aarch64
machines:
* overdrive.guixsd.org
* dover.guix.info
* dmitri.tobias.gr
* sergei.tobias.gr
We are
Hi fellow hackers,
after recent discussions about our Softiron OverDrive in IRC, I thought
it might be a good idea to have look what options for powerful ARM
machines are around. That was some weeks ago.
Today there where another discussions on IRC about building packages on
ARM, so I sent in my
Partially done:
42...@debbugs.gnu.org
It's not working at the moment because header files are still referenced
in the dependents .so. Any idea how to work around this?
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Dear Bengt,
On Tue, 28 Jul 2020 at 11:37, Bengt Richter wrote:
> It would seem easy to forget that all readers may not know what MPFR and MPC
> (and other acronyms) mean, yet be curious enough to want to look them up ;-)
Interestingly, “guix show mpfr” says MPFR stands for Multiple Precision
Hi,
On +2020-07-23 15:36:21 +0200, Andreas Enge wrote:
> Hello,
>
> mpfr just had a new release 4.1.0:
>https://ftp.gnu.org/pub/gnu/mpfr/
> and I am planning to make one for mpc as well.
>
> Should I follow some procedure for an update in Guix, or could I just push
> two commits to
Hey Ludo,
> I think we’ve pretty much reached all these milestones. So we need to
> do some testing again of the installer, but at least we no longer have
> the excuse of adding one last feature. So I guess we could seriously
> work on it. Thoughts?
That's true, really nice we could achieve
