bug#48796: closed (Re: bug#48796: Guix on Debian 11 - Cant run or find applications from Guix)

2022-10-14 Thread bo0od via Bug reports for GNU Guix
Everything is explained well in the past posts but no fixation proposed. Saying need info while all the info there is just ridiculous, closing the bug is just a bug skip not fix which lead to either more comments here or duplicates tickets else where. Unless there is a policy saying guix for

bug#25018: GC incorrectly removes the temporary root file of the calling process

2022-10-14 Thread Ludovic Courtès
Hi Maxim, (Stripping Cc:.) Ludovic Courtès skribis: > Thank you! (Your bug triage work is much appreciated!) We could turn > the example here in a unit test; the only downside is that running the > GC in a test is expensive. Actually, there are tests that most likely relied on the previous

bug#58526: bug report upgrading Guix from 1.0.1 to 1.3

2022-10-14 Thread Maxime Devos
On 14-10-2022 20:08, Timothée Flutre wrote: Hello, I have a computer with Ubuntu 22.04.1 LTS". Some time ago, I installed Guix to try it out, which I finally did not for various reasons. But hearing the talk of K. Hinsen last month convinced me of giving it another try. I hence started

bug#57764: Corrupted store on top on Debian, you want the output

2022-10-14 Thread jbranso--- via Bug reports for GNU Guix
October 14, 2022 7:48 AM, "Maze" wrote: > jbra...@dismail.de writes: > >> September 15, 2022 2:59 AM, "Maze" wrote: >> >>> I corrupted my store and it says you want the guix pull output, so >>> please find it at the end of this message. Mostly I send it because guix >>> asks, but (see below)

bug#57878: Minimal reproducible setup

2022-10-14 Thread Liliana Marie Prikler
Am Freitag, dem 14.10.2022 um 18:07 +0200 schrieb zimoun: > Hi Liliana, > > Maybe it could be worth to have that in the manual too, no?  For > example, under ’Application setup, Emacs packages’ [1]. Would you prefer a paragraph, a note, or a footnote?

bug#58526: bug report upgrading Guix from 1.0.1 to 1.3

2022-10-14 Thread Timothée Flutre
Hello, I have a computer with Ubuntu 22.04.1 LTS". Some time ago, I installed Guix to try it out, which I finally did not for various reasons. But hearing the talk of K. Hinsen last month convinced me of giving it another try. I hence started by upgrading Guix, like this: sudo -i guix pull >&

bug#57878: Minimal reproducible setup

2022-10-14 Thread zimoun
Hi Liliana, On mer., 12 oct. 2022 at 21:42, Liliana Marie Prikler wrote: > In Guix, this is more or less a user choice – we advertised the > transformation by which you can opt-in to AOT compilation in a news > entry. Also, enforcing ahead-of-time compilation does not fix the more > pressing

bug#58375: Installer does not show what is being downloaded

2022-10-14 Thread Mathieu Othacehe
Hey, > If we really want to capture the output of ‘guix system init’, then we > need to open a pseudo-terminal with ‘openpty’ & co. instead of ‘pipe’ in > ‘run-external-command-with-handler’. That may be relatively easy > actually. So I implemented your proposal. It seems to be working quite

bug#57878: Minimal reproducible setup

2022-10-14 Thread Max Brieiev
I am new to Guix. My issue is related to the native compilation too, however it manifests itself differently. The build of emacs-next goes well. However, when I start Emacs it throws lots of errors, most of which are like this: Deleting /tmp/comp-lambda-RCGJQI.eln comp--native-compile:

bug#57878: Minimal reproducible setup

2022-10-14 Thread Max Brieiev
Liliana Marie Prikler writes: > From personal experience, no. Even if you compile code ahead of time, > there seem to be some leftovers that are deferred. guix-emacs.el is an > oversight, but apart from that I also other leftovers (possibly from > init.el?) AFAIU, the compiler is invoked any

bug#58419: Grafting order depends on store connection state

2022-10-14 Thread Ludovic Courtès
Hi, Josselin Poiret skribis: > (let ((right (with-store store (run-with-store store (package->derivation > (specification->package >"password-store") > (wrong (with-store

bug#58149: guix pull error

2022-10-14 Thread zimoun
Hi Bengt, On ven., 07 oct. 2022 at 04:40, b...@bokr.com wrote: > On +2022-10-04 12:11:52 +0200, Ludovic Courtès wrote: >> Matthieu Haefele skribis: >> > Starting download of >> > /gnu/store/f2j6pi0d18pbz35ypflp61wzhbfcr8dp-linux-libre-4.14.67-gnu.tar.xz >> > From >> >

bug#57764: Corrupted store on top on Debian, you want the output

2022-10-14 Thread Maze
jbra...@dismail.de writes: > September 15, 2022 2:59 AM, "Maze" wrote: > >> I corrupted my store and it says you want the guix pull output, so >> please find it at the end of this message. Mostly I send it because guix >> asks, but (see below) at least 2 things broke on that machine, not sure

bug#58508: gtg package (Getting Things GNOME) doesn't run

2022-10-14 Thread Christopher Baines
Pkill9 writes: > This is the error I get when running: > > guix environment --ad-hoc gtg -- gtg > > ``` > Traceback (most recent call last): > File "/gnu/store/0x46vnn6nk10dmkjvg9jmzqx65pmjs4r-gtg-0.6/bin/.gtg-real", > line 76, in > gi.require_version('GtkSource', '4') > File >

bug#58508: gtg package (Getting Things GNOME) doesn't run

2022-10-14 Thread Pkill9
This is the error I get when running: guix environment --ad-hoc gtg -- gtg ``` Traceback (most recent call last): File "/gnu/store/0x46vnn6nk10dmkjvg9jmzqx65pmjs4r-gtg-0.6/bin/.gtg-real", line 76, in gi.require_version('GtkSource', '4') File

bug#58485: [shepherd] Restarting guix-publish fails

2022-10-14 Thread Liliana Marie Prikler
Am Freitag, dem 14.10.2022 um 08:18 +0200 schrieb Lars-Dominik Braun: > Hi, > > > Ahh, so the issue is that shepherd waits neither for the process to > > be > > actually killed nor for the socket to become available, isn't it? > I would argue it’s the former, but having either of them would solve

bug#58290: guile ssh error on guix deploy

2022-10-14 Thread Andrew Tropin
On 2022-10-08 14:39, Ludovic Courtès wrote: > Hi! > > Andrew Tropin skribis: > >> From time to time I get the following error, the only thing I change is >> IPv6 config in static-networking service. Sometimes it fails, but after >> a few more attempts with the same config it deploys

bug#58485: [shepherd] Restarting guix-publish fails

2022-10-14 Thread Lars-Dominik Braun
Hi, > Ahh, so the issue is that shepherd waits neither for the process to be > actually killed nor for the socket to become available, isn't it? I would argue it’s the former, but having either of them would solve the problem, I think. Lars