bug#31841: ./pre-inst-env guix system no longer works without ~/.config/guix

Hi Ludo’, On 06/17/2018 at 22:53 Ludovic Courtès writes: > Hello, > > Mark H Weaver skribis: > >> I should emphasize that when running Guix this way, if you wish to avoid >> running 'guix pull', it's important to always keep at least one >> known-good development environment for Guix saved as a

bug#31786: 'pre-inst-env guix --version' is not updated by new commits"

On 06/16/2018 at 00:24 Ricardo Wurmus writes: > Ricardo Wurmus writes: > >>> Proposed (revised) footnote: >>> >>> (3) The Guix version in the Guix build is set by './bootstrap'. Thus, >>> the version reported by './pre-inst-env guix --version' is not updated >>> by subsequent 'git pull; make' ste

bug#31841: ./pre-inst-env guix system no longer works without ~/.config/guix

On 06/15/2018 at 18:51 Ludovic Courtès writes: > OK to close this issue? > > Ludo’. Hi Ludo’, Based on this thread I am now making guix like this ... guix environment guix --ad-hoc guile-sqlite3 --root=build-env -- make [MAKECMDGOALS] ... and using it like this ... source build-env/etc/profi

bug#31841: ./pre-inst-env guix system no longer works without ~/.config/guix

On 06/15/2018 at 08:56 Rutger Helling writes: > I'm having the same problem. I think being able to run Guix entirely > from a git checkout is one of the best things about it and it's pretty > essential that we keep that possibility for people who want it. +1

bug#31367: ERROR: In procedure scm-error: no code for module (guix build utils)

This just appears in the last day or so. Running guix (GNU Guix) 0.14.0.4837-d6ed4 I see ... cd guix && guix environment guix -- make The following derivations will be built: /gnu/store/mcfys0glgv1hnq5mrcs9xnmn4bpzr3ys-profile.drv /gnu/store/qikmbskc6598vld2lhb2pn30h1rwxgc8-xdg-mime-database

bug#31303: Acknowledgement (substitute: guix substitute: error: TLS error in procedure 'handshake')

bug#31303: substitute: guix substitute: error: TLS error in procedure 'handshake'

On 04/29/2018 at 10:19 Carlo Zancanaro writes: > Hey George, > > On Sat, Apr 28 2018, George myglc2 Clemmer wrote: >> g1@sysi17 ~ [env]$ guix environment >> --substitute-urls=https://g1.local:8080 > > The guix substitute command only runs a normal http server, so you

bug#31303: substitute: guix substitute: error: TLS error in procedure 'handshake'

On 04/28/2018 at 15:16 George myglc2 Clemmer writes: > I am attempting to supply substitutes from a GuixSD install (g1) to a > 'guix system vm-image' (sysi17.local). I did this on g1 ... Oops, here are configs (sys.scm was used for g1)... sys.scm Description: Binary d

bug#31303: substitute: guix substitute: error: TLS error in procedure 'handshake'

I am attempting to supply substitutes from a GuixSD install (g1) to a 'guix system vm-image' (sysi17.local). I did this on g1 ... g1@g1 ~$ sudo guix publish guix publish: warning: server running as root; consider using the '--user' option! publishing /gnu/store on 0.0.0.0, port 8080 ... and I ge

bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error

On 04/26/2018 at 10:54 Marius Bakke writes: > I believe this should be fixed with > 28cae3389146ee575e29c6dfd77987883503568e. Again sorry for the breakage, > and thank you for reporting these issues :-) Hi Marius, Yes that fixed it. No need to be sorry. Many thanks! - George

bug#31268: 'guix system vm-image' hangs

On 04/26/2018 at 03:37 Eric Bavier writes: > Hi George, > > I've seen the same lately with 'guix system vm': > > On Wed, 25 Apr 2018 21:39:30 -0400 > George myglc2 Clemmer wrote: > >> 'guix system vm-image' hangs on guix (GNU Guix) 0.14.0.4

bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error

On 04/24/2018 at 21:36 Mark H Weaver writes: > I'm closing this bug now, but feel free to reopen it if you find that > there are still problems. > >Mark Hello Mark, Still see the problem. Using "b24b19e3f gnu: retroarch: Update to 1.7.2." to build "guix (GNU Guix) 0.14.0.4418-b24b1" ...

bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error

Commit ... 217b8c2e0 * gnu: perl: Replace with 5.26.2 [fixes CVE-2018-{6797,6798,6913}]. ... caused the attached perl script that worked like this ... g1@g1 ~/.mail-mirror$ guix environment --ad-hoc perl perl-timedate make wget g1@g1 ~/.mail-mirror [env]$ perl mb2md-3.20.pl Usage: mb2md -

bug#31113: mcron ERROR: In procedure mktime:

Oops, forgot to attach the system config (actually my /etc/gen/x/016/sys.scm) sys.scm Description: Binary data

bug#31113: mcron ERROR: In procedure mktime:

Hello, somewhere between March ~17 (commit be5ed1421 gnu: Add terraform-docs.) and April ~5 (commit cfb55cfc4 gnu: Add java-native-access-platform.) mcron-service stopped working and started throwing errors like ... #+BEGIN_EXAMPLE ERROR: In procedure mktime: Wrong type (expecting exact integer):

bug#30622: Status: "Service ssh-daemon could not be started." in desktop VM image

On 04/06/2018 at 02:06 Chris Marusich writes: > myg...@gmail.com writes: > >> As of guix (GNU Guix) 0.14.0.4032-cfb55 I can't reproduce this so I >> suggest it be closed. TIA - George > > Before we close it, could you try reproducing this with both "guix > system vm" and "guix system vm-image"?

bug#23001: emacs in X has icons missing and throws warnings in tty

On 04/05/2018 at 19:24 myg...@gmail.com writes: > In guix (GNU Guix) 0.14.0.4032-cfb55 the attached config no longer > produces these errors, so I think this should be closed. > > TIA - George Note: installation of dbus is not required & this config works too ... eservx Description: Binary dat

bug#23001: emacs in X has icons missing and throws warnings in tty

In guix (GNU Guix) 0.14.0.4032-cfb55 the attached config no longer produces these errors, so I think this should be closed. TIA - George eserv Description: Binary data

bug#26706: mingetty consumes 40% CPU printing the login prompt over and over

As of guix (GNU Guix) 0.14.0.4032-cfb55 I can't reproduce this, and haven't seen it since ~ when first reported, so I suggest it be closed. TIA - George

bug#30622: Status: "Service ssh-daemon could not be started." in desktop VM image

As of guix (GNU Guix) 0.14.0.4032-cfb55 I can't reproduce this so I suggest it be closed. TIA - George

bug#30613: 'avahi-resolve .local' works but 'ssh .local' fails w/ "Name or service not known"

Hi Ludo’, On 03/18/2018 at 00:23 Ludovic Courtès writes: > I believe this is fixed by commit > b34ac8248205d64b4023412e61512dfefe44cb9e. Yes thank you. That fixed it here too. - George

bug#30843: make check FAIL: tests/elpa & .guile-real: segfault

grep g1@g1 make.log g1@g1 ~/src/guix [env]$ sudo git clean -dfx g1@g1 ~/src/guix [env]$ ./bootstrap g1@g1 ~/src/guix [env]$ ./configure --localstatedir=/var --sysconfdir=/etc g1@g1 ~/src/guix [env]$ make -j 10 g1@g1 ~/src/guix [env]$ make -j 10 check g1@g1 ~/src/guix [env]$ *** ./test-suite.log =

bug#30467: GuixSD fails to display login prompt on headless server

commit ... c32e3dded * services: agetty: Call default-serial-port only when starting. ... fixed this here, thanks - George

bug#30589: serial login not working

On 03/08/2018 at 12:16 Danny Milosavljevic writes: > Please try current master now. Hi Danny, Yes that fixed it here, thanks. - George guix (GNU Guix) 0.14.0.3087-3e25d

bug#30589: serial login not working

On 02/23/2018 at 21:19 George myglc2 Clemmer writes: > The recent move of agetty-service into #base-services caused serial > login to stop working here. I can confirm that reverting ... 7e0a6fac0 * services: mingetty: Move tty optionality to agetty. 5a9902c8a * services: agetty: Add

bug#30613: 'avahi-resolve .local' works but 'ssh .local' fails w/ "Name or service not known"

On 02/26/2018 at 09:09 George myglc2 Clemmer writes: > Running the attached config in a QEMU image, 'avahi-resolve > .local' works but 'ssh .local' fails w/ "Name or service not > known". > > E.g, ... > > g1@server02 ~$ avahi-resolve --name nem

bug#30467: GuixSD fails to display login prompt on headless server

On 02/27/2018 at 12:08 Danny Milosavljevic writes: > Does > > sudo -i > echo foo >/dev/tty1 > > work and print something there? Shows no error and nothing on the VGA. > What is output of the command "dmesg" ? > > Also, please try > > ps -ef |grep mingetty Please see attached. TIA, George d

bug#30622: "Service ssh-daemon could not be started." in desktop VM image

On 02/26/2018 at 23:58 Danny Milosavljevic writes: >> root@desktop03 /gnu/store# sshd -d -f >> /gnu/store/ky9d1r3kj7yv6sbf8cjp23ym95lc5kss-sshd_config >> sshd re-exec requires execution with an absolute path > > Try > > $(which sshd) -d -f > /gnu/store/ky9d1r3kj7yv6sbf8cjp23ym95lc5kss-sshd_confi

bug#30622: "Service ssh-daemon could not be started." in desktop VM image

sshd fails to start in a desktop config (destop03.scm, attached) The shepherd.log contains (full log attached) ... g1@g1 ~/bug/sshtoXFCE/log$ grep could shepherd.log 2018-02-26 18:07:47 Service user-homes could not be started. 2018-02-26 18:07:48 Service term-auto could not be started. 2018-02-26

bug#30467: GuixSD fails to display login prompt on headless server

On 02/26/2018 at 17:32 Danny Milosavljevic writes: > Try the attached one... g1@g1 ~/bug/bug#30467-vga-no-login$ sudo fbset mode "1280x1024" geometry 1280 1024 1280 1024 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode g1@g1 ~/bug/bug#30467-vga-no-login$

bug#30467: GuixSD fails to display login prompt on headless server

Hi Danny, On 02/24/2018 at 14:51 Danny Milosavljevic writes: >> > Is there still a cursor? >> >> NO. > > That's... bad. > > The tool I'd need to debug this (fbset) is not available in Guix. > > And my guix git checkout is a little under construction. > > So can you please try to guix package -

bug#30613: 'avahi-resolve .local' works but 'ssh .local' fails w/ "Name or service not known"

Running the attached config in a QEMU image, 'avahi-resolve .local' works but 'ssh .local' fails w/ "Name or service not known". E.g, ... g1@server02 ~$ avahi-resolve --name nemo.local nemo.local fe80::1ccf:c589:7e5f:a21f g1@server02 ~$ ssh -vvv nemo.local OpenSSH_7.6p1, OpenSSL 1.0.2n 7 D

bug#30589: serial login not working

The recent move of agetty-service into #base-services caused serial login to stop working here. Previously this worked ... (agetty-service (agetty-configuration (tty "ttyS1") (baud-rate "115200"))) First I tried removing the lines above. The

bug#30467: GuixSD fails to display login prompt on headless server

On 02/22/2018 at 11:41 Danny Milosavljevic writes: > Hi George, > > On Wed, 21 Feb 2018 20:35:34 -0500 > George myglc2 Clemmer wrote: > >> I think we got side-tracked to the serial port when my real issue is >> with the VGA port. Maybe my bug report was not clear

bug#30573: qemu build failed on `/gnu/store...-gst-plugins-ugly-1.12.4.drv'

On 02/22/2018 at 13:40 Marius Bakke writes: > Can you build gst-plugins-ugly with -K and send the log of its test > suite? > > TIA! Thanks Marius. There is no test log. Here is the make log ... gst-plugins-ugly-K.log.gz Description: Binary data

bug#30573: qemu build failed on `/gnu/store...-gst-plugins-ugly-1.12.4.drv'

An attempt to build qemu failed on guix (GNU Guix) 0.14.0.2455-26737 with ... phase `build' failed after 6.9 seconds note: keeping build directory `/tmp/guix-build-gst-plugins-ugly-1.12.4.drv-3' builder for `/gnu/store/gj2ivcxyh8ksjl6rw70dx1d813vbfj46-gst-plugins-ugly-1.12.4.drv' failed with exi

bug#30467: GuixSD fails to display login prompt on headless server

In my previous message, please disregard comments that begin with ... > So I tried that with a build from today (guix (GNU Guix) > 0.13.0.5116-e272), and *no login* is raised on ttyS1 (My G46, sys.scm > attached). which is mistakenly based on an old commit :-|

bug#30467: GuixSD fails to display login prompt on headless server

Hi Danny, I think we got side-tracked to the serial port when my real issue is with the VGA port. Maybe my bug report was not clear. Let me clarify ... My headless server stopped displaying the console tty login *on the VGA port* somewhere between (GNU Guix) 0.13.0.4589-74bea6 (my G18) and (GNU G

bug#30467: GuixSD fails to display login prompt on headless server

Hi Danny, On 02/16/2018 at 00:53 Danny Milosavljevic writes: > Hi George, > > On Thu, 15 Feb 2018 16:29:11 -0500 > George myglc2 Clemmer wrote: >> FWIW, I don't see agetty running ... > > What happens when you run manually: > > agetty /dev/ttyS1 > > Doe

bug#30467: GuixSD fails to display login prompt on headless server

On 02/15/2018 at 21:29 George myglc writes: > Hi Danny & Leo, > > Thanks for the quick response! > > On 02/15/2018 at 15:54 Danny Milosavljevic writes: [...] >> Also, you have >> >> (kernel-arguments '("console=ttyS1,115200")) >> >> AND >> >> (agetty-service (agetty-configuration (tty "ttyS1") >

bug#30467: GuixSD fails to display login prompt on headless server

Hi Danny & Leo, Thanks for the quick response! On 02/15/2018 at 15:54 Danny Milosavljevic writes: > Hi George, > > Leo added a comment to the services/base.scm code: > > ;;; FIXME This doesn't work as expected. According to agetty(8), if this > option > ;;; is not passed, then the default is 'a

bug#30467: GuixSD fails to display login prompt on headless server

GuixSD fails to display login prompt on headless server This was working in (GNU Guix) 0.13.0.4589-74bea6 ae0307f7c tests: Adjust to new unbound-variable error message. It fails in guix (GNU Guix) 0.13.0.5042-6e385. 6e385b76e gnu: mongodb: Use scons-build-system. System Generation on g1: 19

bug#30396: nscd segfaults on attempt to ssh to .local host

On 02/09/2018 at 22:56 Ludovic Courtès writes: > George myglc2 Clemmer skribis: > >> On 02/09/2018 at 14:18 Ludovic Courtès writes: >> >>> For now I’ve pushed a workaround in >>> a68fdfea96370c8a4b95af1fcd6e2fd7eb72da29, which basically downgrades to >>

bug#30396: nscd segfaults on attempt to ssh to .local host

On 02/09/2018 at 14:18 Ludovic Courtès writes: > For now I’ve pushed a workaround in > a68fdfea96370c8a4b95af1fcd6e2fd7eb72da29, which basically downgrades to > 0.10 until upstream comes up with a fix. FWIW, nss-mdns-0.10 segfaults also ... g1@g1 ~$ ssh g1.local ; date ssh: Could not resolve hos

bug#30396: nscd segfaults on attempt to ssh to .local host

On 02/09/2018 at 14:18 Ludovic Courtès writes: > For now I’ve pushed a workaround in > a68fdfea96370c8a4b95af1fcd6e2fd7eb72da29, which basically downgrades to > 0.10 until upstream comes up with a fix. OK, I knew it needed to go upstream but I also thought it must have worked at some point. Thank

bug#30396: nscd segfaults on attempt to ssh to .local host

Hello, On 02/08/2018 at 22:30 Ludovic Courtès writes: > Hi, > > George myglc2 Clemmer skribis: > >> g1@g1 /root/con/30$ ssh e3a.local ; date >> ssh: Could not resolve hostname e3a.local: Name or service not known >> Thu Feb 8 13:06:23 EST 2018 >> >>

bug#30396: nscd segfaults on attempt to ssh to .local host

nscd segfaults on attempt to ssh to .local host ... g1@g1 /root/con/30$ ssh e3a.local ; date ssh: Could not resolve hostname e3a.local: Name or service not known Thu Feb 8 13:06:23 EST 2018 g1@g1 /root/con/30$ cat /var/log/messages | tail Feb 8 13:06:00 localhost dhclient: DHCPDISCOVER on enp

bug#30166: guix system vm-image produces ERROR: In procedure copy-file: Success

On 01/19/2018 at 14:25 Ludovic Courtès writes: > Hi, > > George myglc2 Clemmer skribis: > >> guix system vm-image -M 4 -c 4 /home/g1/www/VM-on-GuixSD/vm/ggg8/v1.scm >> --image-size=5GB > > [...] > >> `/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9

bug#30166: guix system vm-image produces ERROR: In procedure copy-file: Success

Please see below ... guix system vm-image -M 4 -c 4 /home/g1/www/VM-on-GuixSD/vm/ggg8/v1.scm --image-size=5GB substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0% The following derivations will be built: /gnu/store/77pccgn92j05cn5sl9qgf372h3w090ig-qemu-image

bug#30142: pipe of 'guix --version' produces error

EXAMPLE: *** g1@g1 ~/www/VM-on-GuixSD$ guix --version | head -n 1 guix (GNU Guix) 0.14.0.617-e2f37 Backtrace: 5 (primitive-load "/gnu/store/nxdxbad50ydp1nhmgzvlwbk0jkkdc28r-guix-0.14.0-3.f76ff98/bin/.guix-real") In guix/ui.scm: 390:2 4 (show-version-and-exit _) In ice-9/format.

bug#25296: fully functional desktop installation

On 01/15/2018 at 14:26 Mathieu Lirzin writes: [...] > IMHO Guix should mimic what Debian is doing in this particular case. > Meaning having desktop packages that contain a “full” desktop with > default applications for common usages. +1 Benefit: Helps "less-hackerly" users get started.

bug#29512: build of git-2.15.0.drv failed

On 12/01/2017 at 11:33 Ludovic Courtès writes: ... > > To me that sounds like an issue when running tests in parallel. Commit > c03ba83c17c91e34e811a909fae0f63aab701ff9 ensures test run sequentially, > which hopefully solves the problem. That fixed it here. Thanks. - George

bug#29512: build of git-2.15.0.drv failed

Hmm... I have discovered that that works when I don't use the multi-job/multi-core options, e.g., as previously reported, this fails ... g1@g1 ~/src/guix$ guix package -M 4 -c 4 -m ../g1.scm But this ... g1@g1 ~/src/guix$ guix package -m ../g1.scm works. So maybe it's a git bug as opposed to

bug#29512: build of git-2.15.0.drv failed

Running guix from clean make check on ... 6e385b76e (HEAD -> master, origin/master, origin/HEAD) gnu: mongodb: Use scons-build-system. ... guix package failed ... guix package: error: build failed: build of `/gnu/store/r3rijd3pmkfdmg3h4spyb24az3xiylc4-git-2.15.0.drv' failed Details: g1@g1 ~/

bug#23001: emacs in X has icons missing and throws warnings in tty

Updating this for what I see in guix (GNU Guix) 0.13.0.4589-74bea6 On 03/12/2016 at 19:43 myglc2 writes: > When running GuixSD on a headless server ... > > ssh > emacs > > ... produces emacs running in X but ... > > - all of the menu icons are missing except one ('

bug#29245: make check 4 FAIL:'s on 74bea6a03 gnu: linux-libre: Update to 4.13.12.

On 11/11/2017 at 15:38 Ludovic Courtès writes: > Hi, > > myglc2 skribis: > >> >> Testsuite summary for GNU

bug#29072: The usability of Guix configurations

On 11/06/2017 at 17:16 Leo Famulari writes: > On Mon, Nov 06, 2017 at 03:12:11PM -0500, myglc2 wrote: >> My system recently broke when I did an upgrade. I reported what I >> thought was a bug (bug#29072) but it turned out that, because qemu >> package code had been moved, my

bug#29072: The usability of Guix configurations

Please note: these replies are separated by topics in an effort to make the threads more topical ... On 11/06/2017 at 17:16 Leo Famulari writes: > On Mon, Nov 06, 2017 at 03:12:11PM -0500, myglc2 wrote: [...] >> Guix config errors are reported as raw scheme errors which are not >>

bug#29072: The usability of Guix configurations

Please note: these replies separated by topics in an effort to make the threads more topical ... On 11/06/2017 at 22:16 Leo Famulari writes: > On Mon, Nov 06, 2017 at 03:12:11PM -0500, myglc2 wrote: >> My system recently broke when I did an upgrade. I reported what I >> thought

bug#29072: The usability of Guix configurations

My system recently broke when I did an upgrade. I reported what I thought was a bug (bug#29072) but it turned out that, because qemu package code had been moved, my system configuration had become broken ;-( Confronted with my situation, helpful developers said "The package code was moved in commi

bug#29072: guix system: error: qemu-CVE-2017-7493.patch: patch not found

On 11/05/2017 at 19:46 Efraim Flashner writes: > On Sat, Nov 04, 2017 at 07:50:10PM -0400, myglc2 wrote: >> On 11/01/2017 at 22:44 Leo Famulari writes: >> >> > On Wed, Nov 01, 2017 at 10:40:47PM -0400, myglc2 wrote: >> >> On 11/01/2017 at 11:27 Leo Famular

bug#29072: guix system: error: qemu-CVE-2017-7493.patch: patch not found

On 11/01/2017 at 22:44 Leo Famulari writes: > On Wed, Nov 01, 2017 at 10:40:47PM -0400, myglc2 wrote: >> On 11/01/2017 at 11:27 Leo Famulari writes: >> >> > On Wed, Nov 01, 2017 at 10:40:28AM -0400, myglc2 wrote: >> >> Binary file ./gnu/packages/qemu.go ma

bug#29072: guix system: error: qemu-CVE-2017-7493.patch: patch not found

On 11/01/2017 at 11:27 Leo Famulari writes: > On Wed, Nov 01, 2017 at 10:40:28AM -0400, myglc2 wrote: >> Binary file ./gnu/packages/qemu.go matches > > Try deleting this compiled qemu.go and then try again. Thank you Leo. I deleted ./gnu/packages/qemu.go and re-

bug#29072: guix system: error: qemu-CVE-2017-7493.patch: patch not found

On 10/30/2017 at 20:31 Leo Famulari writes: > On Mon, Oct 30, 2017 at 04:34:08PM -0400, myglc2 wrote: >> After a clean guix make, guix system build produced this error ... >> >> root@g1 ~/con/15# guix system --cores=4 --max-jobs=4 -K --on-error=debug >> build sys.scm

bug#29072: guix system: error: qemu-CVE-2017-7493.patch: patch not found

After a clean guix make, guix system build produced this error ... root@g1 ~/con/15# guix system --cores=4 --max-jobs=4 -K --on-error=debug build sys.scm guix system: error: qemu-CVE-2017-7493.patch: patch not found VERSION INFO: root@g1 ~/con/15# guix --version guix (GNU Guix) 0.13.0.4202-1f6f

bug#27137: make check 'FAIL: tests/guix-package-net'

On 05/30/2017 at 17:45 Ludovic Courtès writes: > Hi myglc2, > > myglc2 skribis: > >> + test t-profile-21734-2-link = t-profile-21734-2-link >> + guix package -p t-profile-21734 --switch-generation=-1 >> accepted connection from pid 30492, user g1 >> swi

bug#27137: make check 'FAIL: tests/guix-package-net'

'make check' failed on commit: 98b9732cb gnu: asciinema: Update to 1.4.0. Failure: g1@g1 ~/src/guix$ cd ~/src/guix && guix environment -M 4 -c 4 -e "(@ (gnu packages package-management) guix)" [...] g1@g1 ~/src/guix [env]$ make -j 10 [...] g1@g1 ~/src/guix [env]$ make -j check [...]

bug#25852: Users not updating their installations of Guix

On 05/12/2017 at 10:29 Ludovic Courtès writes: > Ricardo Wurmus skribis: > >> Ludovic Courtès writes: >> >>> myglc2 skribis: >>> >>>> How about extending this ... >>>> >>>>> + (warning (G_ "Your Guix installat

bug#25852: Users not updating their installations of Guix

On 05/10/2017 at 15:12 Ludovic Courtès writes: > Hi there, > > Mark H Weaver skribis: > >> l...@gnu.org (Ludovic Courtès) writes: >> >>> Mark H Weaver skribis: >>> We could simply issue a warning if the version of guix currently in use is more than N hours old, on the assumption that a

bug#26706: mingetty consumes 40% CPU printing the login prompt over and over

I noticed that my headless server running GuixSD was busy when I am not doing anything. When I looked at top I saw mingetty consuming 40% CPU ... $ top -o %CPU -n 1 | head -n 25 top - 20:44:13 up 5 days, 12:58, 3 users, load average: 0.33, 0.33, 0.35 Tasks: 192 total, 1 running, 191 sleeping,

bug#26370: v0.12.0-2730-gfc5b12879 'guix system build' hangs on linux-libre-4.10.8

On 04/05/2017 at 19:31 Marius Bakke writes: > Leo Famulari writes: > >> On Wed, Apr 05, 2017 at 10:55:45AM -0400, myglc2 wrote: >>> HOSTCC scripts/mod/modpost.o >>> HOSTCC scripts/mod/file2alias.o >>> HOSTCC scripts/extract-cert >>> HOST

bug#26370: v0.12.0-2730-gfc5b12879 'guix system build' hangs on linux-libre-4.10.8

'guix system build sys.scm' hangs (please see build1.txt) I'm running on guixSD using guix built from git checkout ... : guix (GNU Guix) 0.12.0 : Copyright (C) 2017 the Guix authors : License GPLv3+: GNU GPL version 3 or later : This is free software: you are fr

bug#24141: RAID reconfigure ERROR: Wrong type (expecting string): ("/dev/sdb1" "/dev/sdc1")

On 08/03/2016 at 10:31 myglc2 writes: > This is a followup to bug#24135. > > Note: This may duplicate, Gmane swallowed my reply yesterday. > > With bug#24135 commits in place the system reconfigure completes w/ > 'Installation finished. No error reported.' _bu

bug#23072: GuixSD SSD install hangs at clocksource

On 01/11/2017 at 23:31 Ludovic Courtès writes: > myglc2 skribis: > >> Florian Paul Schmidt writes: >> >>> On 20.03.2016 20:56, myglc2 wrote: >>> >>>> - I did a near-identical install to a SSD (Kingston ssdnow300), see >>>> "

bug#25444: 'guix system init' on GuixSD w/ RAID target produces "guix system: error: failed to register"

On 01/15/2017 at 20:19 Ludovic Courtès writes: > myglc2 skribis: > >> On 01/14/2017 at 14:44 Ludovic Courtès writes: >> >>> Hi, >>> >>> myglc2 skribis: >>> >>>> root@g1 ~# guix system init system/g1.00.scm /mnt/md0 >

bug#25444: 'guix system init' on GuixSD w/ RAID target produces "guix system: error: failed to register"

On 01/14/2017 at 14:44 Ludovic Courtès writes: > Hi, > > myglc2 skribis: > >> root@g1 ~# guix system init system/g1.00.scm /mnt/md0 >> [...] >> initializing operating system under '/mnt/md0'... >> copying >> '/gnu

bug#25444: 'guix system init' on GuixSD w/ RAID target produces "guix system: error: failed to register"

** summary Running 'guix system init' on GuixSD with RAID target device produces errors like ... root@g1 ~# guix system init system/g1.00.scm /mnt/md0 [...] initializing operating system under '/mnt/md0'... copying '/gnu/store/0m0clxj69xrxb76kyh3ral8lkfb0vx8c-linux-libre-4.9.2'.

bug#24130: RAID config boot hangs at [...] Clocksource: Switched to clocksource tsc

On 01/11/2017 at 23:14 Ludovic Courtès writes: > Could you tell me if this bug is still relevant? Hi Ludo’, Sorry for the delay, I had to swap hardware around to revisit this. I am now able to assemble 3 arrays as shown below, so I think you should close the bug. config: (define md0 (mapped

bug#24129: RAID config boot hangs at [...] Clocksource: Switched to clocksource tsc

myglc2 writes: > > And /var/log/sheperd.log contains: > > 2016-08-01 18:15:13 Service root has been started. > 2016-08-01 18:15:13 ERROR: In procedure scm-error: > 2016-08-01 18:15:13 ERROR: no code for module (gnu build file-systems) In a valiant effort at self help I read

bug#24156: QEMU '-net bridge' --> "qemu-system-x86_64: -net bridge: bridge helper failed"

Motivation: bridging or routing is required to enable a connection to be made inward to a QEMU VM. TAP seems like the best of the available solutions. But connecting to a TAP device produces an error when the QEMU bridge helper fails. Example: g1@g1 ~/src/vmb$ qemu-system-x86_64 -net user -net b

bug#24141: RAID reconfigure ERROR: Wrong type (expecting string): ("/dev/sdb1" "/dev/sdc1")

This is a followup to bug#24135. Note: This may duplicate, Gmane swallowed my reply yesterday. With bug#24135 commits in place the system reconfigure completes w/ 'Installation finished. No error reported.' _but_ shows an embedded error ... ERROR: Wrong type (expecting string): ("/dev/sdb1" "

bug#24135: guix system reconfigure fails on successful build

An ongoing attempt to configure RAID. It builds OK but fails on reconfigure. Yesterday the same config built and configured but failed to boot: bug#24129: RAID config boot hangs at [...] Clocksource: Switched to clocksource tsc Guix version info appears at the bottom of the log. system40.log

bug#24130: RAID config boot hangs at [...] Clocksource: Switched to clocksource tsc

I am attempting to set up RAID. First, following the doc, I ended up with system39.scm, attached, excerpt below: (operating-system (host-name "g1") (timezone "America/New_York") (locale "en_US.utf8") (bootloader (grub-configuration (device "/dev/sda"))) (initrd (lambda (fs . args)

bug#24129: RAID config boot hangs at [...] Clocksource: Switched to clocksource tsc

Note: I forgot that gmane is swallowing my posts to bug-guix and posted this via gmane, so now I am resending by mail. Sorry if this duplicates! I am attempting to set up RAID. First, following the doc, I ended up with system39.scm, attached, excerpt below: (operating-system (host-name "g1")

bug#24120: ERROR: In procedure struct-ref: Argument 1 out of range: 10

l...@gnu.org (Ludovic Courtès) writes: > “rm -rf ~/.cache/guile/ccache” would solve the problem, but could you > instead try the attached patch and see if it solves the problem? The patch works, Thank you! - George

bug#24120: ERROR: In procedure struct-ref: Argument 1 out of range: 10

building guix from git checkout on GuixSD using guix pull. Please see details below. Commentary: In bug#23973 'make clean-go' fixed this error. Am I missing something? PS: posted similar bugs twice over the last 2 days via gmane, which is swallowing my bug-guix posts, but not other ones. If gma

bug#24049: GuixSD - problem with X11 forwarding

This is still open so I am moving it from user to bugs ... From: myglc2 Subject: Re: guixSD - problem with X11 forwarding Newsgroups: gmane.comp.gnu.guix.user To: help-g...@gnu.org Date: Mon, 29 Feb 2016 21:12:51 -0500 (20 weeks, 2 days, 14 hours ago) l...@gnu.org (Ludovic Courtès) writes

bug#23973: 'guix environment guix' fails with "Argument 1 out of range: 10"

A fix for this was helpfully provided in #guix irc by ... myglc2: ludovic noted that recent commits have caused the ABI to change which requires rebuilding from scratch. have you done so? [13:07] make clean-go

bug#23973: 'guix environment guix' fails with "Argument 1 out of range: 10"

Somewhere between '7a7d6b2 gnu: linux-libre: Update to 4.6.4.' and '7a7d6b2 gnu: linux-libre: Update to 4.6.4.' 'guix environment guix' stopped working for me. g1@g1 ~/src/guix$ guix environment guix ;;; note: source file /home/g1/.config/guix/latest/guix/packages.scm ;;; newer than com

bug#23960: lshd: X11 forwarding request failed on channel 0

myglc2 writes: > From 'Re: guixSD - problem with X11 forwarding' in help-g...@gnu.org > > myglc2 writes: > >> l...@gnu.org (Ludovic Courtès) writes: >> >>> myglc2 skribis: >>> >>>> On guixSD, with no packages installed in the

bug#23960: lshd: X11 forwarding request failed on channel 0

>From 'Re: guixSD - problem with X11 forwarding' in help-g...@gnu.org myglc2 writes: > l...@gnu.org (Ludovic Courtès) writes: > >> myglc2 skribis: >> >>> On guixSD, with no packages installed in the login user profile, I get >>

bug#23836: bae0636 bournish: Add 'wc' command. make check FAIL: 9

l...@gnu.org (Ludovic Courtès) writes: > myglc2 skribis: > >> FAIL: tests/substitute.scm > > Ooh, my bad. Fixed in 934c5d5b28f74ab2fe187ad727e4b56cfda6def8. > Now I see ... Testsuite summar

bug#23838: Guix on Debian 8.3 'guix system vm ...' -> "ERROR: qemu failed "qemu-system-x86_64"

myglc2 writes: > l...@gnu.org (Ludovic Courtès) writes: >> >> Usually, /dev/kvm is has “kvm” as its group and is group-writable. So >> all you need is to add the guixbuild* users to the “kvm” group. > > Thank you, so I did this ... > > adduser guixbuilder1

bug#23838: Guix on Debian 8.3 'guix system vm ...' -> "ERROR: qemu failed "qemu-system-x86_64"

l...@gnu.org (Ludovic Courtès) writes: > > Usually, /dev/kvm is has “kvm” as its group and is group-writable. So > all you need is to add the guixbuild* users to the “kvm” group. Thank you, it does. > The manual mentions this pitfall (info "(guix) Invoking guix system") > but I guess it’s easily

bug#23838: Guix on Debian 8.3 'guix system vm ...' -> "ERROR: qemu failed "qemu-system-x86_64"

Apologies in advance if I missed a required step & this is operator error as it is my first attempt to use QEMU/Debian. Running Guix on Debian 8.3, I set up qemu like this ... su apt-get update apt-get upgrade apt-get install qemu apt-get install qemu-kvm apt-get install libvirt-bin adduser g1

bug#23836: bae0636 bournish: Add 'wc' command. make check FAIL: 9

l...@gnu.org (Ludovic Courtès) writes: > Hello, > > myglc2 skribis: > >> Running Guix on Debian 8.3 from git bae0636 bournish: Add 'wc' command. > >> test-name: query narinfo without signature >> location: /home/g1/dev/guix/tests/substitute.scm:17

bug#23836: bae0636 bournish: Add 'wc' command. make check FAIL: 9

Running Guix on Debian 8.3 from git bae0636 bournish: Add 'wc' command. Testsuite summary for GNU Guix 0.10.0 # TOTAL: 582 # PASS: 558 # SKIP:

bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change

Alex Kost writes: > myglc2 (2016-02-08 21:29 +0300) wrote: > >> Alex Kost writes: >> >>> myglc2 (2016-02-07 21:04 +0300) wrote: >>> >>>> From guix INFO: >>>> >>>> 6.2 Invoking ‘guix edit’ >>>> [...] >>>

bug#23001: emacs in X has icons missing and throws warnings in tty

Chris Marusich writes: > Hi, > > I'm using emacs in X on my GuixSD (version 0.10.0) laptop (not a > headless server), and all the icons seem to be showing up correctly for > me by default. > > I think the adwaita icons are provided by the package adwaita-icon-theme > (although gnome-themes-standa

bug#22550: (require 'magit) produces error: "no such file or directory" "dash"

Alex Kost writes: > myglc2 (2016-03-25 18:20 +0300) wrote: > [...] > > Use (require 'guix-autoloads nil t) instead. Nowadays, the only thing > 'guix-init' does is it requires 'guix-autoloads'. > [...] > > The rest looks good to me, I use pretty m

  1   2   >