On Wed, Mar 10 2021, zimoun wrote:
> Using the command “guix weather --display-missing” at commit 6bed29b, I
> identify 180 packages ghc-* which are missing. Then I locally rebuild
> all of them and they build successfully. The only one broken is:
>
> ghc-haddock
>
> Therefore, is it possible
Hi,
On Tue, 23 Mar 2021 at 11:32, Xinglu Chen wrote:
>> And if someone is in the mood to check why ghc-haddock is broken. :-)
>
> This was an issue with upstream[1], it has since been fixed but the
> releases that include the fix are only built for GHC 8.8 or later.
Thanks! Much appreciated.
On Tue, Mar 23 2021, zimoun wrote:
> Hi,
>
> On Tue, 23 Mar 2021 at 11:32, Xinglu Chen wrote:
>
>>> And if someone is in the mood to check why ghc-haddock is broken. :-)
>>
>> This was an issue with upstream[1], it has since been fixed but the
>> releases that include the fix are only built for G
In general my opinion is that backporting fixes is time-consuming and
that if we have to do it each time I wont be able to keep up with the
load. I'd rather update things to a version that already includes fixes
and is supported by upstream even at the cost of world rebuilds. I
can't deal with upst
Hello!
Ludovic Courtès skribis:
> Ludovic Courtès skribis:
>
>> Over the last few days I’ve been head-down working on
>> ‘wip-build-systems-gexp’, the mythical branch that brings gexps to build
>> systems and packages, so we can say goodbye to
>> ‘build-expression->derivation’. And… it’s quite
Hi Chris,
Chris Marusich skribis:
> How shall we build the binary tarball for the release? Of course,
> anybody with a copy of the (source) release tarball can build their own
> guix binary by invoking "make guix-binary.powerpc64le-linux.tar.xz"
> themselves. However, for convenience, it would
Hello!
I have powerful machines at hand and I would like to share them through
the GNU Guix offloading facility so that they are easy to use.
The problem is that setting up offloading requires my machine to trust
each and every client's store public key which means they can spoof
results of deriv
On Tue, 2021-03-23 at 14:42 +0100, Ludovic Courtès wrote:
> Like Efraim wrote, the person who makes the release (I’m afraid it’ll
> be
> me) needs to be able to offload to a “trustworthy” machine for that
> platform.
>
> If we can do that, we should adjust the ‘release’ target in
> ‘Makefile.am’ t
Ludo',
Ludovic Courtès 写道：
Like Efraim wrote, the person who makes the release (I’m afraid
it’ll be
me) needs to be able to offload to a “trustworthy” machine for
that
platform.
Define trustworthy? The project has access to an 8-core POWER9 VM
from OSUOSL, currently running Debian, to whic
Hi,
Mark H Weaver skribis:
> Andreas Enge writes:
>> And please let us agree that in the future, we only backport fixes in grafts
>> and do not update version numbers.
>
> I agree that in this particular case, that's what should have been done,
> and that we should still try to do it. It will
Hi,
Gurjeet Singh skribis:
> Does a self-contained GuixSD installer exist? I tried running GuixSD
> in a VM (in VBox, on macOS), and for that I downloaded the ISO image.
> The ISO image, after a few prompts, then tries to install everything
> from the internet.
The Guix System (formerly known a
Hello Mark and Léo,
Am Mon, Mar 22, 2021 at 05:12:35PM -0400 schrieb Mark H Weaver:
> However, I think it would be going too far to adopt your proposal as a
> general rule for all grafts. In some cases, it can clearly be seen that
> an upstream release includes little more than bug fixes. For ex
On Tue, 2021-03-23 at 15:22 +0100, Andreas Enge wrote:
> I wrote in my bug report https://issues.guix.gnu.org/47315; grafts
> with
> different version numbers lead to a command line behaviour that is
> not
> understandable:
>
> $ guix package -A imagemagick
> imagemagick 6.9.12-2g out,doc
Hello!
There's lots of packages in GNU Guix and maintaining all of them is
tedious, even if we have tooling, there's only so much we can do.
I want to have a secure and reliable system, I would also like to only
depend on packages I know are easy to maintain for GNU Guix
contributors.
I would li
On 2021-03-23 16:00, Léo Le Bouter wrote:
Hello!
There's lots of packages in GNU Guix and maintaining all of them is
tedious, even if we have tooling, there's only so much we can do.
I want to have a secure and reliable system, I would also like to only
depend on packages I know are easy to mai
raingloom writes:
>
> What about a Liberapay for Guix? Could also be used to pay developers.
>
I'd be game for something like this. We could have a guix membership.
Drew Devault has a "secret irc" channel for paying patreons. Perhaps we
could advertise a guix membership on the guix site. When
Ludovic Courtès writes:
> Hi,
>
> Gurjeet Singh skribis:
>
>> Does a self-contained GuixSD installer exist? I tried running GuixSD
>> in a VM (in VBox, on macOS), and for that I downloaded the ISO image.
>> The ISO image, after a few prompts, then tries to install everything
>> from the internet
Ludovic Courtès writes:
> Hello!
>
> Ludovic Courtès skribis:
>
>> Ludovic Courtès skribis:
>>
>>> Over the last few days I’ve been head-down working on
>>> ‘wip-build-systems-gexp’, the mythical branch that brings gexps to build
>>> systems and packages, so we can say goodbye to
>>> ‘build-e
On Tue, Mar 23, 2021 at 03:38:02PM +0100, Léo Le Bouter wrote:
> For this, the problem is not grafting but that the replacement package
> definition has been made public, this is an "issue" (?) that is known
> and I try to not make replacement package definitions public now.
The replacement should
Tobias Geerinckx-Rice writes:
> Ludovic Courtès 写道：
>> Like Efraim wrote, the person who makes the release (I’m afraid
>> it’ll be
>> me) needs to be able to offload to a “trustworthy” machine for that
>> platform.
>
> Define trustworthy? The project has access to an 8-core POWER9 VM
> from OSUO
On Tue, Mar 23, 2021 at 02:34:52PM +0100, Léo Le Bouter wrote:
> In general my opinion is that backporting fixes is time-consuming and
> that if we have to do it each time I wont be able to keep up with the
> load. I'd rather update things to a version that already includes fixes
> and is supported
On Mon, Mar 22, 2021 at 02:44:04PM +0100, raingloom wrote:
> What about a Liberapay for Guix? Could also be used to pay developers.
Some of us already have Liberapay accounts.
hi everyone! i've packed golang lib with guix, but cannot use it inside
guix_env (guix environment --ad-hoc go go-lib-i-packed). why this may happen?
Léo Le Bouter writes:
> There's lots of packages in GNU Guix and maintaining all of them is
> tedious, even if we have tooling, there's only so much we can do.
>
> I want to have a secure and reliable system, I would also like to only
> depend on packages I know are easy to maintain for GNU Guix
Hi,
I'm having trouble importing a package from hackage, so I tried to debug
the import source code. After cloning guix I found that I can't start a pure
environment:
guix environment guix --pure --ad-hoc help2man git strace
Command 'lesspipe' is available in the following places
* /bin/lessp
raingloom writes:
> On Sat, 20 Mar 2021 12:19:11 +0100
> Ludovic Courtès wrote:
>
>> Hi,
>>
>> Mark H Weaver skribis:
>>
>> > Ultimately, I gave up. In my opinion, Guix has never achieved
>> > usability as a desktop system on non-Intel systems. Therefore, the
>> > Guix community is unable
Hi Leo,
Leo Famulari writes:
> On Tue, Mar 23, 2021 at 03:38:02PM +0100, Léo Le Bouter wrote:
>> For this, the problem is not grafting but that the replacement package
>> definition has been made public, this is an "issue" (?) that is known
>> and I try to not make replacement package definition
Hi Ludovic,
Ludovic Courtès writes:
> Mark H Weaver skribis:
>
>> Andreas Enge writes:
>>> And please let us agree that in the future, we only backport fixes in grafts
>>> and do not update version numbers.
>>
>> I agree that in this particular case, that's what should have been done,
>> and t
Hi Andreas,
Andreas Enge writes:
> these are very good arguments, which I understand and share. But moving
> to another version is problematic even when there is no soname bump, as
> I wrote in my bug report https://issues.guix.gnu.org/47315; grafts with
> different version numbers lead to a com
Joshua Branson writes:
> raingloom writes:
>>
>> What about a Liberapay for Guix? Could also be used to pay developers.
>>
>
> I'd be game for something like this. We could have a guix membership.
> Drew Devault has a "secret irc" channel for paying patreons. Perhaps we
> could advertise a gui
> Doesnt /dev/stdin work?
>
> The only reason it could not is that somehow the file descriptor needs
> to be seekable.
>
> Léo
This doesn't work for me, with `cat | guix build -f /dev/stdin`
i get "guix build: error: failed to load '/dev/stdin': No such file or
directory"
> Doesnt /dev/stdin work?
>
> The only reason it could not is that somehow the file descriptor needs
> to be seekable.
>
> Léo
This doesn't work for me, with `cat | guix build -f /dev/stdin`
i get "guix build: error: failed to load '/dev/stdin': No such file or
directory"
Le 23 mars 2021 18:25:38 GMT-04:00, c4t0 a écrit :
>
>Hi,
>
>I'm having trouble importing a package from hackage, so I tried to
>debug
>the import source code. After cloning guix I found that I can't start a
>pure environment:
>
>guix environment guix --pure --ad-hoc help2man git strace
>Comman
Hi,
The (guix build julia-build-system) contains this:
--8<---cut here---start->8---
;; Actual precompilation:
(invoke-julia
;; When using Julia as a user, Julia writes precompile cache to the first
;; entry of the DEPOT_PATH list (by default,
Hi!
I'm having problems with 'guix import' in my environment:
$guix import hackage -t ghc-events
Syntax error: unexpected token : common (at line 44, column 0)
Syntax error: unexpected end of input
guix import: error: failed to download cabal file for package 'ghc-events'
so I cloned guix, and:
On Tue, Mar 23, 2021 at 07:05:42PM -0400, Mark H Weaver wrote:
> Also, I'm not sure why you qualify your suggestion with "in this case".
> What is it that distinguishes ImageMagick from, e.g. glib, for purposes
> of this question? Would it be any less bad for "guix install glib" to
> install a gli
Hi,
FYI, I have merged wip-ppc64le-for-master to master and closed bug
47182. I have also deleted the wip-ppc64le-for-master branch.
Later this week, I will update the manual to mention that
powerpc64le-linux is supported, and I will update the "release" target
of the Makefile so that we can mak
37 matches
Mail list logo
