bug#60803: Cuirass stopped processing jobs for aarch64-linux and x86_64-linux

2023-01-13 Thread Marius Bakke
Hello Guix, Cuirass has stopped processing (old) jobs for aarch64 and x86_64. After digging through the database it's because (db-get-pending-build ...) returns a build that is missing from the Jobs table: WITH pending_dependencies AS (SELECT Builds.id, count(dep.id) as deps FROM Builds

bug#60786: cross-kernel-headers can produce broken packages

2023-01-13 Thread Maxim Cournoyer
Hello, Maxim Cournoyer writes: > Hello, > > This issue was triggered by having make-uboot-package uses #:target [0], > but it already exists on current master. I've spent some time narrowing > down the issue, and it is caused by the package returned by > cross-kernel-headers in (gnu packages

bug#60566: [PATCH] environment: Fix '--emulate-fhs' option overriding $PATH.

2023-01-13 Thread John Kehayias via Bug reports for GNU Guix
Hi Ludo’, On Sat, Jan 07, 2023 at 12:03 AM, Ludovic Courtès wrote: > To be safe, you need to account for (getenv "PATH") returning #f, and > not add a trailing colon in that case. > Ah, right. I think this would only happen if somehow unsetting PATH and preserving it? As 'guix shell' already

bug#59913: [tentative PATCH] Failure to guix pull on aarch64 since recent make-linux-libre*

2023-01-13 Thread Maxim Cournoyer
Hello, Ludovic Courtès writes: > Hi, > > Pierre Langlois skribis: > >> I'm not sure I follow, I'd suggest to revert the revert and then apply a >> fix in the same commit, that way it can easily be reverted again if it's >> problematic, that's probably what you meant already? > > Sounds good to

bug#60786: cross-kernel-headers can produce broken packages

2023-01-13 Thread Maxim Cournoyer
Hello, This issue was triggered by having make-uboot-package uses #:target [0], but it already exists on current master. I've spent some time narrowing down the issue, and it is caused by the package returned by cross-kernel-headers in (gnu packages cross-base) being produced with a bogus

bug#60782: Channels and dependency confusion

2023-01-13 Thread Simon Tournier
Hi, On ven., 13 janv. 2023 at 14:48, Ludovic Courtès wrote: > Nothing, because the ‘guix’ channel always comes first in the module > search path (see ‘%package-module-path’ in (gnu packages)). Good. > > Now same scenario, but with references to another channel, for example > (@ (past packages

bug#60141: Follow-up

2023-01-13 Thread Andrews, Kyle (KC)
My system administrator let me know that the terminal I was presented with was sandboxed by RStudio Server (not running on Guix) and that this was responsible for causing the error. I was able to run the hello command from an unsandboxed shell. I was also able to pull the latest version of

bug#59913: [tentative PATCH] Failure to guix pull on aarch64 since recent make-linux-libre*

2023-01-13 Thread Maxim Cournoyer
Hi Pierre, Pierre Langlois writes: > Hi Guix! > > I've been getting errors while running `guix pull' on an aarch64 system, > during the final guix-package-cache step: > > (repl-version 0 1 1) > Generating package cache for > '/gnu/store/m8in1imi93snq711d7568dj9hlrx4diz-profile'... > >

bug#60782: Channels and dependency confusion

2023-01-13 Thread Ludovic Courtès
In the light of the “dependency confusion” attack on PyTorch¹, one might wonder how such a thing could affect Guix. The threat model is quite different though because the ‘guix’ channel is peer-reviewed and curated whereas PyPI isn’t. Yet, one way to “translate” the attack to Guix is by looking