Hi Ludo,
Ludovic Courtès writes:
> Look at this weird phenomenon.
>
> First, with ‘guix build’, everything works as expected:
> [...]
> But now ‘guix shell’ (same revision) wants to build ungoogled-chromium:
> [...]
> Why does ‘guix shell’ want to build a different derivation for the same
> pack
Am Mittwoch, dem 01.03.2023 um 02:58 + schrieb Csepp:
> emacs-org-roam is installed in my default profile and all the other
> emacs packages work with the emacs-next-pgtk package in the same
> profile.
> guix shell emacs-org-roam emacs-next-pgtk does not work, guix shell
> emacs-org-roam emacs
Hi,
winter--- via Bug reports for GNU Guix writes:
> Hi,
>
> As of commit ec8c7370dfd66136f7cb517d31fa6fda31e2cb74, the following `guix
> import` invocation fails:
>
> $ guix import go --recursive github.com/tdewolff/minify/v2
> [...]
> In gnu/packages/check.scm:
> 1037:13 1 (_)
> In ice-9/bo
Becaus (gnu packages golang) and (gnu packages check) use each other, this
avoids an undefined symbol.
* gnu/packages/check.scm (go-github-com-robfig-cron-1.2): Move to...
* gnu/packages/golang.scm (go-github-com-robfig-cron-1.2): ...here.
---
gnu/packages/check.scm | 18 --
gnu/
Hi Vagrant,
Vagrant Cascadian writes:
> Tried the guix installer 1.4.0, and it seemed to be going smoothly,
> downloading substitutes... but eventually timed out waiting for
> substitutes...
>
> The "Resume" option for the install dropped me back to selecting locale,
> keyboard, substitutes, roo
Hi,
On mer., 01 mars 2023 at 10:48, Josselin Poiret via Bug reports for GNU Guix
wrote:
> Becaus (gnu packages golang) and (gnu packages check) use each other, this
-^
Typo
s/Becaus/Because I guess
> avoids an undefined symbol.
>
> * gnu/packages/check.scm (go-github-com-robfig-cron-1
Liliana Marie Prikler writes:
> Am Mittwoch, dem 01.03.2023 um 02:58 + schrieb Csepp:
>> emacs-org-roam is installed in my default profile and all the other
>> emacs packages work with the emacs-next-pgtk package in the same
>> profile.
>> guix shell emacs-org-roam emacs-next-pgtk does not
Hi,
On +2023-03-01 12:16:56 +0100, Csepp wrote:
[...]
> How the hell would my paths affect what's in the bin folder? Like, the
> flatpak binary is literally not present in the profile, that's why it's
> not showing up in $PATH.
Could something in one of your path directories
accidentally have go
Hi,
Simon Tournier skribis:
> 1. From my point of view, the transformations are functions that you
> compose. The composition rule is not commutative maybe neither
> associative. Writing down how each function (transformation)
> composes with the others allows to specify the compo
Hi,
Ludovic Courtès skribis:
> Maxim Cournoyer skribis:
[...]
>> It seems to me that the rewriting options should be honored on any
>> packages being manipulated, whether they come from the Guix collection,
>> a file, a manifest or another means.
>
> I’m not convinced; I think manifests shoul
b...@bokr.com writes:
> Hi,
>
> On +2023-03-01 12:16:56 +0100, Csepp wrote:
> [...]
>> How the hell would my paths affect what's in the bin folder? Like, the
>> flatpak binary is literally not present in the profile, that's why it's
>> not showing up in $PATH.
>
> Could something in one of your
Hi Ludovic,
Ludovic Courtès writes:
> Hi,
>
> Ludovic Courtès skribis:
>
>> Maxim Cournoyer skribis:
>
> [...]
>
>>> It seems to me that the rewriting options should be honored on any
>>> packages being manipulated, whether they come from the Guix collection,
>>> a file, a manifest or another
Hi,
> This is way worse: (gnu packages golang) cannot be loaded at all!
> This is caused by a cycle, (gnu packages golang) uses (gnu packages
> check) and vice-versa, and go-github-com-robfig-cron is defined in (gnu
> packages golang)! So depending on whether you first use (gnu packages
> check) o
> Using (gnu packages check) then (gnu packages golang) doesn't make the
> error appear. The solution imo, esp. since (gnu packages check) already
> uses (gnu packages golang), is to have the variant package defined
> alongside the parent. Here is a patch that should fix this.
To clarify: I do th
Am Mittwoch, dem 01.03.2023 um 05:00 + schrieb Adam Faiz:
> > Looking at the vala source code, we can bootstrap the current
> > version from 0.39.5.8, which appears to be between release cycles –
> > 0.39.6 already requires it, whereas 0.39.5 bootstraps from 0.25.1.
> > I'm not sure how to get
Hi again,
Winter writes:
> In addition to those, I wonder why `guix build` shows that the cyclic package
> can't be found, rather than throwing an error as `guix import` does. Maybe
> it's worth fixing that, if possible, to not cause (worse) confusion?
This is because you should be trying to
Howdy,
Josselin Poiret skribis:
> Ludovic Courtès writes:
>
>> Look at this weird phenomenon.
>>
>> First, with ‘guix build’, everything works as expected:
>> [...]
>> But now ‘guix shell’ (same revision) wants to build ungoogled-chromium:
>> [...]
>> Why does ‘guix shell’ want to build a diffe
The r-maaslin2 package builds example plots in PNG and PDF format. The
scatter plots and box plots are not reproducible as the points are not
plotted in deterministic order.
--
Ricardo
On 2023-03-01, Josselin Poiret wrote:
> Vagrant Cascadian writes:
>> Tried the guix installer 1.4.0, and it seemed to be going smoothly,
>> downloading substitutes... but eventually timed out waiting for
>> substitutes...
>>
>> The "Resume" option for the install dropped me back to selecting local
Am Mittwoch, dem 01.03.2023 um 17:11 +0100 schrieb Csepp:
>
> b...@bokr.com writes:
>
> > Hi,
> >
> > On +2023-03-01 12:16:56 +0100, Csepp wrote:
> > [...]
> > > How the hell would my paths affect what's in the bin folder?
> > > Like, the flatpak binary is literally not present in the profile,
20 matches
Mail list logo
