Yes, it can be closed.
Regards.
El 5/6/24 a las 18:54, Simon Tournier escribió:
[No suele recibir correo electrónico de zimon.touto...@gmail.com. Descubra por
qué esto es importante en https://aka.ms/LearnAboutSenderIdentification ]
Hi,
On Thu, 04 Apr 2024 at 18:04, Javier Vaquero Martínez
👍!
Le 05/06/2024 à 19:43, Simon Tournier a écrit :
Hi,
On Wed, 5 Jun 2024 at 19:30, Alexandre Hannud Abdo wrote:
I no longer have easy access to the other machine, it belonged to a colleague...
So closing?
Cheers,
simon
Hi Oleg,
[...]
>> Are these chown still useful in the activation snippet?
>>
>> (define (nix-activation _)
>> ;; Return the activation gexp.
>> #~(begin
>> (use-modules (guix build utils)
>>(srfi srfi-26))
>> (for-each (cut mkdir-p <>) '("/nix/store" "/nix/var/
* gnu/packages/base.scm (patch): Rename to...
(patch/pinned): ... this. Hide package.
(patch): New variable.
* gnu/packages/commencement.scm (patch-mesboot): Inherit from patch/pinned.
(patch-boot0): Likewise.
(%final-inputs): Replace patch with patch/pinned.
* gnu/packages/lisp.scm (cl-asdf): Lik
Hi Simon,
Simon Tournier writes:
> Hi,
>
> On Wed, 05 Jun 2024 at 18:04, Ludovic Courtès wrote:
>
>> What about renaming ‘patch’ to ‘patch/pinned’ and having ‘patch’ point
>> to the new version?
>>
>> Internally, we’d refer to ‘patch/pinned’ in (guix packages), but user
>> code etc. would refer
* gnu/packages/unicode.scm (ucd): Update to 15.1.0.
Change-Id: I0828544c35eef90a8f76c2084362ee4594189244
---
(no changes since v1)
gnu/packages/unicode.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/unicode.scm b/gnu/packages/unicode.scm
index 23f08a2aa
Also fix the commands, which would fail due to not finding their
implementation scripts.
* gnu/packages/patches/gnulib-bootstrap.patch: New patch.
* gnu/local.mk (dist_patch_DATA): Register it.
* gnu/packages/build-tools.scm (gnulib): Update to 2024-05-30-1.ac4b301.
[source]: Apply patch.
[phases]
Hi,
On Wed, 5 Jun 2024 at 19:30, Alexandre Hannud Abdo wrote:
> I no longer have easy access to the other machine, it belonged to a
> colleague...
So closing?
Cheers,
simon
Ni! Well, at least with my current setup, both commands finished fine. Or did
you want their outputs?
I no longer have easy access to the other machine, it belonged to a colleague...
.~´
Le 05/06/2024 à 16:43, Simon Tournier a écrit :
Hi Alexandre,
On Wed, 05 Jun 2024 at 02:05, Alexandre Han
Hi,
Thanks for the report.
On Thu, 04 Apr 2024 at 12:53, Charles MacDonald via Bug reports for GNU Guix
wrote:
>> guix substitute: warning: while fetching
>> https://ci.guix.gnu.org/nar/lzip/21wnzvrrvn100w3q0bb5c894hqyn5b5d-guile-lzma-0.1.1:
>>
>> server is somewhat slow
>> guix substitute:
Hi,
Thanks for the report.
On Thu, 04 Apr 2024 at 11:37, casket_imagery.01--- via Bug reports for GNU Guix
wrote:
> I was trying to update Gix package manager on a fresh Debian instance
> in ProxMox, and as I was doing so, I got the below error. As requested
> by the script, I am sending you t
Hi,
On Sat, 25 May 2024 at 11:31, Ludovic Courtès wrote:
>> But, I do have the given key in my '/etc/guix/acl', and this works:
>
> Are /etc/guix/acl and /etc/guix world-readable?
I had been bitten by this recently. And I have not found any mention
about that in the manual. Maybe it could hel
Hi,
On Thu, 04 Apr 2024 at 18:04, Javier Vaquero Martínez wrote:
> So I managed to solve this. It turns out that some environment variables
> where making this error to happen. Running in an isolated environment
> with `guix shell -C r r-sf -- r` solves the problem.
Thanks for letting us know
Hi,
On Wed, 05 Jun 2024 at 18:04, Ludovic Courtès wrote:
> What about renaming ‘patch’ to ‘patch/pinned’ and having ‘patch’ point
> to the new version?
>
> Internally, we’d refer to ‘patch/pinned’ in (guix packages), but user
> code etc. would refer to ‘patch’ and thus get the latest version.
I
Hi Alexandre,
On Wed, 05 Jun 2024 at 02:05, Alexandre Hannud Abdo wrote:
>> Using 6ba29e0, it works for me.
>
> I saw the issue on two different machines, one with GuixSD another a
> Debian with Guix freshly installed.
Is it the same ’guix describe’ for the two machines? And the same
revision
Hi,
CC: core team
On Wed, 24 Apr 2024 at 16:43, Simon Tournier wrote:
> Out of any network, I get this error:
>
> --8<---cut here---start->8---
> $ guix time-machine --commit=1971d11d -- describe
> guix time-machine: error: failed to load
> '/home/simon/.con
Hi Maxim,
Maxim Cournoyer skribis:
> Ludovic Courtès writes:
[...]
>> Unless I’m mistaken, this will have practically no effect because Patch
>> is a build-time-only dependency.
>>
>> My recommendation would be to not add a ‘replacement’ field at all.
>> Instead, you could add a new ‘patch/la
Hello,
Am Tue, Jun 04, 2024 at 03:59:53PM +0200 schrieb Ludovic Courtès:
> I’m happy to report that this bug should be fixed in the snapshot
> recently deployed on ci.guix.gnu.org. The fix is here:
>
> https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/commit/?id=12d79854ee7685b356a72ca37
18 matches
Mail list logo
