Hi,
I had some problems getting current ansible package to work. It seems that
the bin/ansible script which is created as part of the python-build-system
via a call to `wrap-program' interferes with certain expectations ansible
has regarding how it and its subcommands are called.
This mechanism d
Leo Famulari transcribed 1.6K bytes:
> On Tue, May 02, 2017 at 04:15:52PM +, ng0 wrote:
> > Hi,
> > I just noticed that stagit's example.sh has a patched shebang.
> > While I would assume that everyone notices when this fails,
> > it would probably be good to not make too optimistic assumptions
On Tue, May 02, 2017 at 04:15:52PM +, ng0 wrote:
> Hi,
> I just noticed that stagit's example.sh has a patched shebang.
> While I would assume that everyone notices when this fails,
> it would probably be good to not make too optimistic assumptions
> and keep #!/bin/sh in the file.
I think tha
Ludovic Courtès writes:
> Clément Lassieur skribis:
>
>> I tried to patch 'patch-and-repack', but it triggers a full
>> rebuild... WDYT?
>
> Right, it’s expected to trigger a full rebuild, so this should be fixed
> in ‘core-updates’.
Yes, but is there a way to test the patch on one package wit
Hi!
Clément Lassieur skribis:
> I think the code is in guix/packages.scm (patch-and-repack). Here is my
> understanding of what happens: the presence of the snippet leads to 3
> things:
>
> 1. extraction of the archive,
> 2. modification of some files (because of patches or snippet),
> 3. compr
Hello,
Mark H Weaver skribis:
> While trying to update my GuixSD system in the last hour, I found that
> every attempt by the substituter to download NARs resulted in a 500
> "Internal Server Error":
[...]
> Bypassing the mirror didn't help:
Did you try talking directly to ‘guix publish’ (loc
