Hi Simon,
> does “guix build -n” fit your use-case?
Checking... yes! I hadn't even considered using "build" when building is
exactly what I do not want to happen. But yes, it works just fine.
> Well, ’package-output’ in (guix packages) is what you need, I guess.
And that works just fine as wel
Hi Simon,
>> does “guix build -n” fit your use-case?
>
> Checking... yes! I hadn't even considered using "build" when building is
> exactly what I do not want to happen. But yes, it works just fine.
Not quite:
$ guix build -n zziplib
substitute:
/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash
Hi,
In addition, I am also lost with this sequence:
1. dry-run openmpi list dependencies
2. do the wrong thing with the REPL
3. garbage collect
4. redo the dry-run and now the dependencies are not listed
Sorry Konrad, ’package-output’ is definitively wrong. Worse, the items
listed in the f
Hi Léo,
Regarding your commit:
> From 2e0ff59f0cd836b156f1ef2e78791d864ce3cfcd Mon Sep 17 00:00:00 2001
> From: Léo Le Bouter
> Date: Thu, 18 Mar 2021 11:12:51 +0100
> Subject: [PATCH] gnu: imagemagick/fixed: Redirect old sonames to new sonames.
>
> * gnu/packages/imagemagick.scm (imagemagick/f
Hi Mark,
On Thu, 18 Mar 2021 at 08:51, Mark H Weaver wrote:
> This is really nasty. Why is imagemagick grafted, anyway? I think it
> can simply be updated without causing many rebuilds, no?
--8<---cut here---start->8---
$ guix refresh -l imagemagick@6.9.11-
Earlier, I wrote:
> Why is imagemagick grafted, anyway? I think it can simply be updated
> without causing many rebuilds, no?
Actually, I see now that it would cause many more rebuilds than is
appropriate for master.
mhw@jojen ~$ guix refresh -l imagemagick
Building the following 1270 packag
Hi,
I've been struggling with GCC package definition for a while and I hope someone
can help me solve or improve what I think are issues in its definition.
I'm working on a R7RS-Small Scheme implementation that compiles to RISC-V
assembly and I'm finding many issues to create a RISC-V cross compi
Hi,
First, thanks to Chris and folks, powerpc64le-linux will be [1] in the
next release, great! Isn’t it? :-)
Then, ~95% of packages for x86_64 are substituables which is really
great too. Even, maybe more could be available. Well, if you want to
help, simply run:
guix weather --display-miss
Hi Guix,
I am going to write an mcron service for `guix home`[1][2] and before
proceding, I would like to get some suggestions on what the best
practices are for writing services in Guix.
Currently there seems to be two main ways to do this, the first one
is the define one or more records for the
On 2021-03-18, zimoun wrote:
> On Wed, 17 Mar 2021 at 11:08, Vagrant Cascadian wrote:
>
>> ... and I would expect this version to ship in Debian for another ~3-5
>> years, unless it gets removed from Debian bullseye before the upcoming
>> (real soon now) release!
>
> I could miss a point. In 3-5
Le 15 mars 2021 12:51:16 GMT-04:00, "Ludovic Courtès" a écrit :
>Hi Andrew,
>
>Andrew Tropin skribis:
>>
>> The question is: do we want and need at all `guix home` to be a part
>of
>> the guix? As for me, the tool seems like a natural addition to guix's
>> declarative configuration management
Hi Guix,
I'd like to invite you to a guix packaging meetup.
The format for the meetup will involve talking over LibreMiami's mumble
instance while mob programming over tmate.
Feel free to package with us, watch via the livestream, or just chat over the
mumble.
Here's the meeting link with m
On Thu, Mar 18, 2021 at 09:00:20AM -0700, Vagrant Cascadian wrote:
> Except for issues like the openssl bug which causes build failure due to
> certificate expiry in the test suite basically would break guix pull in
> those cases... maybe that is a deal breaker for the Debian packaged
> guix...
To
On Thu, Mar 18, 2021 at 09:40:04AM -0400, Mark H Weaver wrote:
> I knew this couldn't be right, but I thought I remembered it having
> fewer dependencies. Oh well. Sorry for the noise.
It's relatively new that ImageMagick is depended on by so many packages.
I think we should look into this and s
Hello,
core-updates is still in a pretty bad state.
I'd be glad to merge Raghav's patches (which he already reworked to be current
for core-updates!) to core-updates--but right now, Guix packages don't build
BEFORE or after applying these patches to core-updates.
Please, let's do something abo
Hi Danny,
> (3) libusb-for-axoloti build failure (guix build axoloti-patcher-next)
This has been fixed in 1daedaa8646696783c88553e03035d547fd001ca.
> (5) download failed
> "https://bioconductor.org/packages/release/bioc/src/contrib/DelayedArray_0.16.1.tar.gz";
> 404 "Not Found"
This was fixed
http://jehanne.io/2021/01/06/gcc_on_jehanne.html
Should support more architectures than Hurd ;)
Anyways, just throwing this out there, as I - and I imagine every
other contributor - have some more pressing projects.
It probably wouldn't be able to run most packages and services without
some sign
Under "6.7 Declaring Channel Dependencies" the examples show names being
quoted, such as (name 'some-collection) however this causes guix pull to
fail. I don't remember the exact error but it was failing the "match"
statement under "resolve-dependencies" in "guix/channels.scm".
(name "some-collect
Hello Guix devel,
When `guix system init` fails, there are a number of possible causes of failure:
* Packages being downloaded are so broken that they cannot actually be built.
* QC should filter this out.
* The hardware being installed on is broken, usually a failure of the storage
device bei
Hi simon,
zimoun writes:
> First, thanks to Chris and folks, powerpc64le-linux will be [1] in the
> next release, great! Isn’t it? :-)
I'm very excited about this! Efraim was able to rework our patches so
they could be applied to master without rebuilding the entire world.
The patches are curr
20 matches
Mail list logo
