Re: guix pull: error: commit 3946540 not signed by an authorized key: 2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0

On 2022-08-06 23:06, Tobias Geerinckx-Rice wrote: I'm not aware of a technical reason to switch branch names. OK, having read up on the mood in #guix I think I understand the reference. But I don't think that would have been a good idea, and I wouldn't have supported it. Kind regards, T

Re: guix pull: error: commit 3946540 not signed by an authorized key: 2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0

(Aside: the immediate issue has been resolved! Pull to your heart's content. Pull for a friend.) On 2022-08-06 22:43, Vagrant Cascadian wrote: What a great opportunity to switch to using "main" instead of "master" anyways. :) I thought git was going to at some point make "main" the default

Re: guix pull: error: commit 3946540 not signed by an authorized key: 2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0

On 2022-08-06, Tobias Geerinckx-Rice wrote: > On 2022-08-06 20:48, Tobias Geerinckx-Rice wrote: >> guix pull: error: commit 39465409f0481f27d252ce25d2b02d3f5cbc6723 >> not signed by an authorized key: >> 2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0 > > I trie

Re: guix pull: error: commit 3946540 not signed by an authorized key: 2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0

On 2022-08-06 20:48, Tobias Geerinckx-Rice wrote: guix pull: error: commit 39465409f0481f27d252ce25d2b02d3f5cbc6723 not signed by an authorized key: 2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0 I tried a few other random things to wriggle out of this but I think we're stuck (which

guix pull: error: commit 3946540 not signed by an authorized key: 2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0

Hi all, If you try to guix pull now, this is what you'll see: guix pull: error: commit 39465409f0481f27d252ce25d2b02d3f5cbc6723 not signed by an authorized key: 2841 9AC6 5038 7440 C7E9 2FFA 2208 D209 58C1 DEB0 There is and was no security risk. This is Guix working as intended

Re: guix pull: error: getting attributes of path: No such file or directory

;;; note: source file /usr/share/guile/site/2.2/json.scm > > ;;; newer than compiled /usr/lib64/guile/2.2/site-ccache/json.go > > Updating channel 'guix' from Git repository at > > 'https://git.savannah.gnu.org/git/guix.git'... > > Building from this channel: > > guix

Re: guix pull: error: getting attributes of path: No such file or directory

rom Git repository at > 'https://git.savannah.gnu.org/git/guix.git'... > Building from this channel: > guix https://git.savannah.gnu.org/git/guix.git16ef7b4 > guix pull: error: getting attributes of path > `/gnu/store/1f2frr4fcdb8gib7x3akr6vz3562g73v-i18n.scm': No such file > or

guix pull: error: getting attributes of path: No such file or directory

/json.scm ;;; newer than compiled /usr/lib64/guile/2.2/site-ccache/json.go Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... Building from this channel: guix https://git.savannah.gnu.org/git/guix.git16ef7b4 guix pull: error: getting

Re: guix pull error after install i686 1.2.0

On Tue, Apr 13, 2021 at 08:26:32PM -0400, Bone Baboon wrote: > Thank you for sharing that link. It inspired several tests that I > conducted which helped me solve the problem. The issue was that the > date was significantly incorrect. > > I was able to fix this with `sudo date --set='-MM-DD

Re: guix pull error after install i686 1.2.0

Leo Famulari writes: > On Sun, Apr 11, 2021 at 03:04:14PM -0400, Leo Famulari wrote: >> It's expected that, before the first `guix pull`, the origin is not >> known. The per-user view of Guix, with provenance tracking, is created >> on the first `guix pull`. >> >> However, the version string

Re: guix pull error after install i686 1.2.0

Leo Famulari writes: >> The output of `guix describe`: >> ``` >> guix describe: error: failed to determine origin >> hint: Perhaps this `guix' command was not obtained with `guix pull'? Its >> version string is 1.2.0rc2-1.0d4b1af. >> ``` > > This isn't quite right. > > It's expected that,

Re: guix pull error after install i686 1.2.0

On Sun, Apr 11, 2021 at 03:04:14PM -0400, Leo Famulari wrote: > It's expected that, before the first `guix pull`, the origin is not > known. The per-user view of Guix, with provenance tracking, is created > on the first `guix pull`. > > However, the version string should be 1.2.0. Something has

Re: guix pull error after install i686 1.2.0

tructions in the manual section Installing Guix in a VM. > The output of `guix pull`: > ``` > Updating channel 'guix' from Git repository at > 'https://git.savannah.gnu.org/git/guix.git'... > guix pull: error: Git error: the SSL certificate is invalid > ``` I logged in as a r

Re: guix pull error after install i686 1.2.0

u.org/git/guix.git'... guix pull: error: Git error: the SSL certificate is invalid ``` I am running `guix pull` from a Linux console virtual terminal. I am running `guix pull` as a regular user (not root). `which guix` outputs "/run/current-system/profile/bin/guix". The output of `guix describ

Re: guix pull error after install i686 1.2.0

On Sat, Apr 10, 2021 at 11:33:12AM +0200, Vincent Legoll wrote: > But I remember having seen an (default checked) option > to install certificates when choosing packages to install. > > Let me power it up and check... > > I have the "nss-certs" package installed from /etc/config.scm `guix pull`

Re: guix pull error after install i686 1.2.0

On Sat, Apr 10, 2021 at 12:28:20AM -0400, Bone Baboon wrote: > I have just installed Guix on a computer using: > https://ftp.gnu.org/gnu/guix/guix-system-install-1.2.0.i686-linux.iso.xz > > When I run `guix pull` I get this error message "guix pull: error: Git > error:

Re: guix pull error after install i686 1.2.0

Vincent Legoll writes: > I remember having seen an (default checked) option > to install certificates when choosing packages to install. > I have the "nss-certs" package installed from /etc/config.scm > > This may be what you're missing. I reinstalled Guix on the laptop. During the graphical

Re: guix pull error after install i686 1.2.0

which had an old guix install (~1 year old). > When I run `guix pull` I get this error message "guix pull: error: Git > error: the SSL certificate is invalid". And I can guix pull & guix system reconfigure. I reinstalled because I saw that same error message, from the old guix i

guix pull error after install i686 1.2.0

I have just installed Guix on a computer using: https://ftp.gnu.org/gnu/guix/guix-system-install-1.2.0.i686-linux.iso.xz When I run `guix pull` I get this error message "guix pull: error: Git error: the SSL certificate is invalid".

Re: guix pull: error: corrupt input while restoring archive

Andreas Enge writes: >> I am still curious what happened before, in case the previous error >> appears again. > > Other people have experienced the same problem; apparently it was a bug > that has been fixed in the meantime. So as "guix pull" finally succeeded, > you should not see it again.

Re: guix pull: error: corrupt input while restoring archive

Hello Simon, Am Wed, Mar 31, 2021 at 09:53:20AM +0200 schrieb Simon Josefsson via: > Minutes after posting the above, 'guix pull' works again after having > been broken in the above way for at least a week. I never realized that > asking for help on this list would solve things this quickly!

Re: guix pull: error: corrupt input while restoring archive

Simon Josefsson via writes: > Hi. I have a machine that have been running Guix for a couple of years > and since November I rely on unattended-upgrades to keep it updated. I > have stopped doing manual upgrades but may have done it on reflex a > couple of times since November. Now when I run

guix pull: error: corrupt input while restoring archive

substitution of /gnu/store/nvx8kkadjl81k5h544y4kahz6jlzqqyl-guix-system-tests failed guix pull: error: corrupt input while restoring archive from # root@hamster ~# unattended-upgrade-logs.tar.bz2 Description: Binary data signature.asc Description: PGP signature

guix pull: error: corrupt input while restoring archive

substitution of /gnu/store/nvx8kkadjl81k5h544y4kahz6jlzqqyl-guix-system-tests failed guix pull: error: corrupt input while restoring archive from # root@hamster ~# unattended-upgrade-logs.tar.bz2 Description: Binary data signature.asc Description: PGP signature

Re: Problem with guix pull (error when generating cashe for a package)

On Tuesday, 29 September 2020 19:04, zimoun wrote: > Hi, > > On Mon, 21 Sep 2020 at 07:18, Todor Kondić tk.c...@protonmail.com wrote: > > > Hi, > > Doing a pull this morning (guix pull -c4) results in this error: > > (repl-version 0 1 1) > > Generating package cache for > >

Re: Problem with guix pull (error when generating cashe for a package)

Hi, On Mon, 21 Sep 2020 at 07:18, Todor Kondić wrote: > Hi, > > Doing a pull this morning (guix pull -c4) results in this error: > (repl-version 0 1 1) > Generating package cache for > '/gnu/store/9h588g8m8rz57yy465gi32m0822s1nsd-profile'... > (exception unbound-variable (value #f) (value

Re: Problem with guix pull (error when generating cashe for a package)

‐‐‐ Original Message ‐‐‐ On Monday, 21 September 2020 09:18, Todor Kondić wrote: > Hi, > > Doing a pull this morning (guix pull -c4) results in this error: > (repl-version 0 1 1) > Generating package cache for > '/gnu/store/9h588g8m8rz57yy465gi32m0822s1nsd-profile'... > (exception

Problem with guix pull (error when generating cashe for a package)

Hi, Doing a pull this morning (guix pull -c4) results in this error: (repl-version 0 1 1) Generating package cache for '/gnu/store/9h588g8m8rz57yy465gi32m0822s1nsd-profile'... (exception unbound-variable (value #f) (value "Unbound variable: ~S") (value (r-preprocesscore)) (value #f)) I thought

Re: guix pull: error: Git error: invalid content-type: 'text/plain'

Hello, Le mardi 15 septembre 2020 à 09:08 +0200, Jelle Licht a écrit : > I know this error! I had it happen to me way back when libgit tries > to > work with a remote that exposes the older http-based git protocol. > AFAIK > (but this was some time ago) libgit does not support this. It is weird

Re: guix pull: error: Git error: invalid content-type: 'text/plain'

divoplade writes: > Hello guix, > > I have set up a few packages of mine at > https://divoplade.fr/divoplade-site.git > > If you clone it, it works: > > git clone https://divoplade.fr/divoplade-site.git > > But if I add this URL as a guix channel, I get: > >

Re: guix pull: error: Git error: invalid content-type: 'text/plain'

this URL as a guix channel, I get: > > guix pull: error: Git error: invalid content-type: 'text/plain' > > This is the first time I get this error, as far as I remember. How do I > get this to work? > > Best regards > > divoplade > It looks like it's trying to fetch

guix pull: error: Git error: invalid content-type: 'text/plain'

Hello guix, I have set up a few packages of mine at https://divoplade.fr/divoplade-site.git If you clone it, it works: git clone https://divoplade.fr/divoplade-site.git But if I add this URL as a guix channel, I get: guix pull: error: Git error: invalid content-type: 'text/plain

guix pull: error: Git error: failed to connect to git.savannah.gnu.org: Address family not supported by protocol

x.git file with the following error message : ​ /gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) user with UID 120300 not found Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... guix p

Re: guix pull: error: glibc-bootstrap-system-2.2.5.patch: patch not found

On Mon, 11 May 2020 12:44:55 -0500 Efraim Flashner wrote > On Mon, May 11, 2020 at 09:03:45AM -0500, sirgazil wrote: > > On Sun, 10 May 2020 07:26:43 -0500 Efraim Flashner > > wrote > > > > > > I recently upgraded my kids' computer post-core-update merge and I ran

Re: guix pull: error: glibc-bootstrap-system-2.2.5.patch: patch not found

On Mon, May 11, 2020 at 09:03:45AM -0500, sirgazil wrote: > On Sun, 10 May 2020 07:26:43 -0500 Efraim Flashner > wrote > > > > I recently upgraded my kids' computer post-core-update merge and I ran > > into the same issue. The trick was to make sure to use > >

Re: guix pull: error: glibc-bootstrap-system-2.2.5.patch: patch not found

On Sun, 10 May 2020 07:26:43 -0500 Efraim Flashner wrote > > I recently upgraded my kids' computer post-core-update merge and I ran > into the same issue. The trick was to make sure to use > ~/.configure/guix/bin/guix for 'guix pull' and not >

Re: guix pull: error: glibc-bootstrap-system-2.2.5.patch: patch not found

nnah.gnu.org/git/guix.git'... > Building from this channel: > guix https://git.savannah.gnu.org/git/guix.git 36cf1ee > guix pull: error: glibc-bootstrap-system-2.2.5.patch: patch not found > > > And I get this error when I try guix describe with that use

guix pull: error: glibc-bootstrap-system-2.2.5.patch: patch not found

pull, and got this error: $ LANG=C guix pull Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... Building from this channel: guix https://git.savannah.gnu.org/git/guix.git 36cf1ee guix pull: error: glibc-bootstrap-system-2.2.5.patch

guix pull error with custom channel news file

Hi! I tried added a news file to a channel and got this error: --8<---cut here---start->8--- (repl-version 0 0) (exception unbound-variable (value #f) (value "Unbound variable: ~S") (value (channel-news)) (value #f)) --8<---cut

Re: guix pull: error: getting status of /var/guix/gcroots

On Thu, 6 Feb 2020 at 22:20, Jimmy Thrasibule wrote: > > I do not have carefully look to your files, but the issue should be: > > - wrong permission > > - /var/guix is not exposed > > Well the folder exists and is owned by root. Where does it exist? On your local machine running Guix? Have

Re: guix pull: error: getting status of /var/guix/gcroots

> Do you have any possibility to run guix pull with strace? Unfortunately containers are not given PTRACE privileges during the build phase so I cannot call strace. > I do not have carefully look to your files, but the issue should be: > - wrong permission > - /var/guix is not exposed Well

Re: guix pull: error: getting status of /var/guix/gcroots

come from this file: https://bitbucket.org/x237net/alpine-guix/src/master/src/Dockerfile > guix pull: error: getting status of /var/guix/gcroots: Operation not > permitted I do not have carefully look to your files, but the issue should be: - wrong permission - /var/guix is not expose

Re: guix pull: error: getting status of /var/guix/gcroots

Hi Jimmy! I guess they are reducing the capabilities allowed to their build platform but I can really tell what operation is guix pull attempting in this particular case. Do you have any possibility to run guix pull with strace? strace is a program that logs all the system calls [1] of

guix pull: error: getting status of /var/guix/gcroots

. However, when I push the container to hub.docker.com it fails to build the image with the following error message: guix pull: error: getting status of /var/guix/gcroots: Operation not permitted Again, I successfully built the image on different local systems and my other container [x237net

Re: guix pull: error: symlink: File exists

Hi Jimmy, On Mon, 20 Jan 2020 at 10:30, Jimmy Thrasibule wrote: > OK, so following the discussion at https://issues.guix.info/issue/39195, my > container was missing the $USER environment variable so Guix was failing > back to the "default" profile. Once $USER is set to "root" my current user >

Re: guix pull: error: symlink: File exists

1 root root39 Jan 19 18:37 current -> > /var/guix/profiles/default/current-guix > # guix pull > Migrating profile generations to '/var/guix/profiles/per-user/root'... > guix pull: error: symlink: File exists: > "/var/guix/profiles/per-user/r

Re: guix pull: error: symlink: File exists

tion and the > installation script [2]. Everything is working fine however, when I run > ``guix pull`` in the generated image, I got the following error: > > > Migrating profile generations to '/var/guix/profiles/per-user/root'... > guix pull: error: symlink: File ex

guix pull: error: symlink: File exists

``guix pull`` in the generated image, I got the following error: Migrating profile generations to '/var/guix/profiles/per-user/root'... guix pull: error: symlink: File exists: " /var/guix/profiles/per-user/root/current-guix" This issue has already been discussed at [3] but the

Re: guix pull error: symlink

Giovanni Biscuolo writes: > unfortunately "guix pull" failed since it started building > gcc-cross-boot-0-5.5.0.drv and was killed by OOM > > note that on subsequent test I made "guix pull --dry-run" but the pull > always triggers a build: Try also “--no-grafts”. Together with “--dry-run” it

Re: guix pull error: symlink

': 1 dependencies couldn't be built cannot build derivation `/gnu/store/1wp0jy2sdxgyn0mxvds75jan2c0az0q0-glibc-2.28.drv': 1 dependencies couldn't be built building /gnu/store/8qsid2pqlav3454pzw783j6zy2n0j2l6-perl-boot0-5.28.0.drv... cannot build derivation `/gnu/store/cz4sr5whzf3qhp8c47bzlfzcxxwl

Re: guix pull error: symlink

Giovanni Biscuolo writes: > gbiscuolo@guixsdtest:~$ guix pull > Migrating profile generations to '/var/guix/profiles/per-user/gbiscuolo'... > guix pull: error: symlink: File exists: > "/var/guix/profiles/per-user/gbiscuolo/current-guix-1-link" > > please how can I fi

guix pull error: symlink

t;8--- gbiscuolo@guixsdtest:~$ guix pull Migrating profile generations to '/var/guix/profiles/per-user/gbiscuolo'... guix pull: error: symlink: File exists: "/var/guix/profiles/per-user/gbiscuolo/current-guix-1-link" --8<---cut here---end-

Re: Guix pull error

Thank you, Ludovic, for your attention. That exact. New try gave acceptable result. And now I am able to keep trying to configure touchpad tap... https://lists.gnu.org/archive/html/help-guix/2018-10/msg00137.html # guix pull

Guix pull error

Hello, Guix Help! I watch an issue. Trying to roll-back and choose another kernel in grub I have no changes. Guix says 'Wrong type to upply: #t' # guix pull  --substitute-urls=https://berlin.guixsd.org Updating channel 'guix' from Git repository at

Re: guix pull error : In procedure make_objcode_from_file: object file too small (0 bytes)

Hi, tk0 skribis: > After having to roll back from a weird situation -- in which guix developed a > problem mounting my virtual filesystem at boot -- doing a 'guix pull' > produces the following error: Could you send the whole ‘guix pull’ output, so we see the context?