bug#39513: [core-updates] git-minimal fails to build
Tested with core-updates at commit 2073b55e6b964cb8ca15e8c74cb32dac00f05f0d. The build of git-minimal fails like: --8<---cut here---start->8--- phase `compress-documentation' succeeded after 0.0 seconds output (`/gnu/store/51p6w7pd8c6ykz4bgh559bz5y96ixz51-git-minimal-2.25.0') is not allowed to refer to path `/gnu/store/a5x90i0354ddmdlbmkdp83sfxdn038sm-bash-5.0.11' @ build-failed /gnu/store/czdijvh3k8l5bvrjd1xdpmbdscdjgf81-git-minimal-2.25.0.drv - 1 output (`/gnu/store/51p6w7pd8c6ykz4bgh559bz5y96ixz51-git-minimal-2.25.0') is not allowed to refer to path `/gnu/store/a5x90i0354ddmdlbmkdp83sfxdn038sm-bash-5.0.11' derivation '/gnu/store/czdijvh3k8l5bvrjd1xdpmbdscdjgf81-git-minimal-2.25.0.drv' offloaded to '10.42.0.199' failed: build of `/gnu/store/czdijvh3k8l5bvrjd1xdpmbdscdjgf81-git-minimal-2.25.0.drv' failed build of /gnu/store/czdijvh3k8l5bvrjd1xdpmbdscdjgf81-git-minimal-2.25.0.drv failed View build log at '/var/log/guix/drvs/cz/dijvh3k8l5bvrjd1xdpmbdscdjgf81-git-minimal-2.25.0.drv.bz2'. --8<---cut here---end--->8--- Reading about how "bash-for-tests" is in inputs rather than native-inputs (due to: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31952) and the workaround proposed therein makes me think that 2073b55e6b964cb8ca15e8c74cb32dac00f05f0d has caused the workaround to stop working. Maxim
bug#39466: i3 - choosing to write a new config leaves one
"Can you give more details about what goes wrong? Instructions to reproduce? This report is too vague." Yes, sorry about that. Instructions: 1. Boot freshly installed/updated Guix with i3 installed. 2. At the login screen, bottom right, note the following error in red: "Error: status_command not found or is missing a library dependency (exit 127). 3. From the i3 first configuration window, type the key "Yes, generate the config." 4. Choose "Win as a default modifier." 5. Note that the login screen freezes.
bug#39387: Builds are *not* offloaded when using the "--keep-failed" or -K option.
Hello Ludovic! Ludovic Courtès writes: > Maxim Cournoyer skribis: > >> Still, it'd be nice to have an option to keep failed build on the >> *remote* machines. I don't think that's possible currently? > > In some cases it’s not even desirable because you could fill up /tmp > without noticing. > > But note that another option is to do: > > GUIX_DAEMON_SOCKET=ssh://remote.example.org guix build foo -K > > WDYT? > > Ludo’. This fulfill my use case well and appears to be sufficiently documented already. We're gold! Thank you, Maxim
bug#39511: github tokens being deprecated
$ guix refresh
...
Backtrace:
12 (apply-smob/1 #)
In ice-9/boot-9.scm:
705:2 11 (call-with-prompt _ _ #)
In ice-9/eval.scm:
619:8 10 (_ #(#(#)))
In guix/ui.scm:
1808:12 9 (run-guix-command _ . _)
In ice-9/boot-9.scm:
829:9 8 (catch _ _ # ?)
829:9 7 (catch _ _ # ?)
In guix/store.scm:
625:10 6 (call-with-store _)
1848:24 5 (run-with-store # ?)
In guix/scripts/refresh.scm:
541:14 4 (_ _)
In srfi/srfi-1.scm:
640:9 3 (for-each # ?)
In guix/scripts/refresh.scm:
344:2 2 (check-for-package-update # ?)
In guix/import/github.scm:
237:25 1 (latest-release #)
In unknown file:
0 (scm-error misc-error #f "~A" ("Error downloading rel?") ?)
ERROR: In procedure scm-error:
Error downloading release information through the GitHub
API. This may be fixed by using an access token and setting the environment
variable GUIX_GITHUB_TOKEN, for instance one procured from
https://github.com/settings/tokens
after github token acquired:
$ guix refresh
...
guix refresh: warning: input 'Carp' of perl-xml-compile is in Perl core
gnu/packages/xml.scm:1113:13: tinyxml2 would be upgraded from 7.0.1 to 7.1.0
following redirection to
`https://api.github.com/repositories/7715820/releases?access_token=728ec76dc9ea4344b57ba6be86674ed9e0135090'...
gnu/packages/xdisorg.scm:1731:13: python-pyperclip would be upgraded
from 1.6.4 to 1.7.0
and then an email from github.com:
Hi @mwette,
On February 8th, 2020 at 14:37 (UTC) your personal access token (guix/bluefin)
using GNU Guile was used as part of a query parameter to access an endpoint
through the GitHub API:
https://api.github.com/repositories/32202720/releases
Please use the Authorization HTTP header instead, as using the `access_token`
query parameter is deprecated and will be removed July 1st, 2020.
Depending on your API usage, we'll be sending you this email reminder once
every 3 days for each token and User-Agent used in API calls made on your
behalf.
Just one URL that was accessed with a token and User-Agent combination will be
listed in the email reminder, not all.
Visithttps://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/#authenticating-using-query-parameters
for more information.
Thanks,
The GitHub Team
bug#39510: Cannot build guix from git
Nevermind, it was caused by a local change in the repository. Le Sat, 8 Feb 2020 14:23:44 +0100, Julien Lepiller a écrit : > Hi Guix, > > I just tried to build guix after a make clean-go, and it fails with > the following errors (from a guix environment guix run from the latest > master): > > ... > [ 6%] LOAD guix/build/download.scm > [ 6%] LOAD guix/build/download-nar.scm > WARNING: (guix build download-nar): `dump-port*' imported from both > (guix serialization) and (guix progress) > [ 6%] LOAD guix/build/cargo-build-system.scm > [ 6%] LOAD guix/build/cargo-utils.scm > ... > [ 11%] LOAD guix/scripts/import.scm > [ 11%] LOAD guix/scripts/package.scm > ;;; Failed to autoload canonical-package in (gnu packages base): > ;;; error: gnu-make: unbound variable > [ 11%] LOAD guix/scripts/install.scm > [ 11%] LOAD guix/scripts/remove.scm > ... > [ 11%] LOAD guix/scripts/hash.scm > [ 11%] LOAD guix/scripts/pack.scm > error: failed to load 'guix/scripts/pack.scm': > ice-9/eval.scm:293:34: no binding `zip' to hide in module (gnu > packages compression) > > >
bug#39510: Cannot build guix from git
Hi Guix, I just tried to build guix after a make clean-go, and it fails with the following errors (from a guix environment guix run from the latest master): ... [ 6%] LOAD guix/build/download.scm [ 6%] LOAD guix/build/download-nar.scm WARNING: (guix build download-nar): `dump-port*' imported from both (guix serialization) and (guix progress) [ 6%] LOAD guix/build/cargo-build-system.scm [ 6%] LOAD guix/build/cargo-utils.scm ... [ 11%] LOAD guix/scripts/import.scm [ 11%] LOAD guix/scripts/package.scm ;;; Failed to autoload canonical-package in (gnu packages base): ;;; error: gnu-make: unbound variable [ 11%] LOAD guix/scripts/install.scm [ 11%] LOAD guix/scripts/remove.scm ... [ 11%] LOAD guix/scripts/hash.scm [ 11%] LOAD guix/scripts/pack.scm error: failed to load 'guix/scripts/pack.scm': ice-9/eval.scm:293:34: no binding `zip' to hide in module (gnu packages compression)
bug#39402: set-xorg-configuration pulls in unsupported packages on target architecture
I did a little bit more experimenting and can see it's not
set-xorg-configuration that is the problem, it goes deeper.
Perhaps it's `xorg-configuration` itself?
Here's my full config at the minute, now trying with `xorg-start-command`,
which has the same problem:
```
(use-modules (guix download)
(guix git-download)
(guix packages)
(gnu)
(gnu bootloader u-boot)
(gnu packages linux)
(gnu packages bootloaders)
(gnu packages libusb)
(gnu packages certs)
(gnu packages bootloaders)
(gnu packages suckless)
(gnu packages xdisorg)
(gnu packages gnome)
(gnu packages xorg)
(gnu services xorg)
(gnu services dbus)
(gnu services sound)
(gnu services networking)
(gnu services avahi)
(gnu services desktop)
(guix build-system trivial))
(use-service-modules desktop)
;; bootloader ---
(define-public u-boot-pinebook-pro-rk3399
(let ((base (make-u-boot-package "pinebook_pro-rk3399" "aarch64-linux-gnu")))
(package
(inherit base)
(source (origin
(method url-fetch)
(uri (string-append
"ftp://ftp.denx.de/pub/u-boot/;
"u-boot-" (package-version base)".tar.bz2"))
(sha256
(base32
"1w9ml4jl15q6ixpdqzspxjnl7d3rgxd7f99ms1xv5c8869h3qida"))
;; need a rather large patch, based on commit:
;; 3034b8864e47bfbf6f0330dc67620a2a71cfe3f8
;; from git.eno.space/pbp-uboot.git
(patches '("./patches/uboot-pinebook-pro-rk3399.patch"
(arguments
(substitute-keyword-arguments
(package-arguments base)
((#:phases phases)
`(modify-phases ,phases
(add-after
'unpack 'set-environment
(lambda* (#:key inputs #:allow-other-keys)
(setenv "BL31" (string-append (assoc-ref inputs
"firmware")
"/bl31.elf"))
#t))
;; Phases do not succeed on the bl31 ELF.
(delete 'strip)
(delete 'validate-runpath)
(native-inputs
`(("firmware" ,arm-trusted-firmware-rk3399)
,@(package-native-inputs base))
(define u-boot-pinebook-pro-bootloader
(bootloader
(inherit u-boot-rockpro64-rk3399-bootloader)
(package u-boot-pinebook-pro-rk3399)))
;(define
u-boot-pinebookpro-rk3399-bootloader
;; SD and eMMC use the same format
; (bootloader
; (inherit u-boot-bootloader)
; (package u-boot-rockpro64-rk3399)
; (installer
install-rockpro64-rk3399-u-boot)))
;; linux kernel ---
(define kernel-config
(string-append (dirname (current-filename)) "/kernel.config"))
;; we need a custom patched kernel for now
;; hopefully the changes get mainlined soon
(define linux-pbp
(let ((repo "gitlab.manjaro.org/tsys/linux-pinebook-pro")
(commit "b262e709c608c1a5acefca280a2899acab9a802b")
(revision "3"))
(package
(inherit linux-libre)
(name "linux-pbp")
(version (git-version "5.5.0" revision commit))
(native-inputs
`(("kconfig" ,kernel-config)
,@(assoc-remove! (package-native-inputs linux-libre) "kconfig")))
(source (origin
(method url-fetch)
(uri (string-append
"https://; repo "/repository/archive.tar.gz?ref=" commit))
(sha256
(base32
"087qla48jqwa1bwn6d3qriizjfnv2xvl7q8akjmrkgfa46a5lrxr")))
(operating-system
(kernel linux-pbp)
(host-name "pinebook-pro")
(timezone "Europe/Copenhagen")
(locale "en_US.utf8")
(keyboard-layout (keyboard-layout "us" "altgr-intl"))
(bootloader
(bootloader-configuration
(target "/dev/mmcblk1boot0")
(bootloader u-boot-pinebook-pro-bootloader)))
(initrd-modules '()); (delq "ahci" %base-initrd-modules))
(file-systems (append
(list
(file-system
(device "/dev/mmcblk1p1")
(mount-point "/boot")
(type "vfat"))
(file-system
(device "/dev/mmcblk1p2")
(mount-point "/")
(type "ext4")))
%base-file-systems))
;; This is where user accounts are specified. The "root"
;; account is implicit, and is initially created with the
;; empty password.
(users
(cons
(user-account
(name "rock")
(group "users")
;; Adding the account to the "wheel" group
;; makes it a
