bug#22514: emacs INFO pages have "?"s instead of "'"s

In emacs INFO pages, single quotes "'" appear as question marks "?" and 'echo $LANG' returns a blank line. I am running guixSD on a headless server & logging in via the iTerm2 terminal emulator running on Max OS X... e.g. 'ssh' & 'emacs -nw' When I log into an identical server running Debian 8, e

bug#22514: emacs INFO pages have "?"s instead of "'"s

myglc2 writes: > In emacs INFO pages, single quotes "'" appear as question marks "?" and > 'echo $LANG' returns a blank line. Note/clarification: the problem is only with user accounts. root emacs INFO "'" quotes are normal and 'e

bug#22514: emacs INFO pages have "?"s instead of "'"s

l...@gnu.org (Ludovic Courtès) writes: > retitle 22514 Missing environment variables when logging in via SSH > merge 22513 22175 > thanks > > myglc2 skribis: > >> In emacs INFO pages, single quotes "'" appear as question marks "?" and >>

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

with magit installed on guixSD following the config shown further below. With init.el containing ... V (add-to-list 'load-path "/run/current-system/profile/share/emacs/site-lisp") (require 'guix-init nil t) ^^

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

Alex Kost writes: > myglc2 (2016-02-04 07:15 +0300) wrote: > >> with magit installed on guixSD following the config shown further below. >> >> With init.el containing ... >> >> V >> (a

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

Alex Kost writes: > myglc2 (2016-02-04 18:16 +0300) wrote: > >> So, should I put ... >> >> '(guix-emacs-load-autoloads "/run/current-system/profile")' >> >> ... in init.el, in which case guix INFO should say so. > > Well, you can do

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

Alex Kost writes: > myglc2 (2016-02-05 02:40 +0300) wrote: > > [...] >>> Right now I can't check it, but I think if you start emacs like this: >>> >>> EMACSLOADPATH=/etc/emacs: emacs >>> >>> you'll get "M-x guix-…" comm

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

Alex Kost writes: [...] > The purpose of "M-x guix-edit" Emacs command (and "guix edit" shell > command) is just to show you the source code of the package. This > source is usually placed in the store, and you shouldn't edit it. If > you are going to contribute to guix, (info "(guix) Building

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

Andreas Enge writes: > On Sun, Feb 07, 2016 at 01:04:40PM -0500, myglc2 wrote: >> TYPO: >> "edit" (last line above) should be replaced with "view", "inspect", or >> "examine". >> RENAME: >> Calling these functions '

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

Andreas Enge writes: > On Sun, Feb 07, 2016 at 02:22:36PM -0500, myglc2 wrote: >> But, AIUI, this goes against the guix concept of an immutable store. >> To describe and name this function to imply that one could/should edit >> recipes in the store based on the "corne

bug#22593: 'make check' fails

guixSD installed on a server. make check fails for user glc but succeeds for user glc3. make.check.fail.log Description: Binary data test-suite.log Description: Binary data make.check.log Description: Binary data

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

Alex Kost writes: > Alex Kost (2016-02-04 23:00 +0300) wrote: > > [...] >> So to recap, you found 2 issues: >> >> 1. Emacs packages installed in a system profile are not automatically >>added to 'load-path'. > > Fixed in commit 004ea62¹. However, it will take effect when the new > source of

bug#22598: 'info guix' fails on guixSD

'man guix' is quite likely the first thing a new user types. The man page is a stub to 'info guix'... GUIX(1) [...] If the info and guix programs are properly installed at your site, the command info guix should give you access to the complete manual. Howeve

bug#22600: 'Globally-Visible Packages' not shown by 'M-x guix-installed-packages'

In guixSD, 'Globally-Visible Packages' packages installed accoding to '7.2.1 Using the Configuration System' are not shown by 'M-x guix-installed-packages' and are shown as uninstalled in the 'M-x guix-all-packages' 'list' buffers.

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

Alex Kost writes: > myglc2 (2016-02-07 21:04 +0300) wrote: > >> From guix INFO: >> >> 6.2 Invoking ‘guix edit’ >> [...] >> launches the program specified in the ‘VISUAL’ or in the ‘EDITOR’ >> environment variable to edit the recipe of GCC 4.8.4 and th

bug#22600: 'Globally-Visible Packages' not shown by 'M-x guix-installed-packages'

l...@gnu.org (Ludovic Courtès) writes: > Alex Kost skribis: > >> myglc2 (2016-02-08 18:08 +0300) wrote: >> >>> In guixSD, 'Globally-Visible Packages' packages installed accoding to >>> '7.2.1 Using the Configuration System' are not sho

bug#22593: 'make check' fails

l...@gnu.org (Ludovic Courtès) writes: > myglc2 skribis: > >> tests/store.scm:705: FAIL verify-store >> tests/store.scm:722: FAIL verify-store + check-contents > > Here we see two failures… > >>

bug#22607: doc install from *Guix Package Info: profile* fails

Running: guixSD. Scenario: Finding and installing doc for a package (ncurses) used by a by a global package (emacs) I hit the following error. FWIW, IMHO, this functionality, and the ease with which it is available, is truly awesome! This failed for both user and root. Common steps

bug#22607: doc install from *Guix Package Info: profile* fails

Alex Kost writes: > myglc2 (2016-02-09 19:49 +0300) wrote: > >> Running: guixSD. >> >> Scenario: Finding and installing doc for a package (ncurses) used by a >> by a global package (emacs) I hit the following error. > > A-a-a! What you tried is more or less t

bug#22600: 'Globally-Visible Packages' not shown by 'M-x guix-installed-packages'

Alex Kost writes: > myglc2 (2016-02-09 05:29 +0300) wrote: > [...] >> My concern is that this experience might leave a new user thinking, >> "Geez, I know back in the fog of the USB install I added packages. What >> kind of package manager is this? It doesn&

bug#22607: doc install from *Guix Package Info: profile* fails

Alex Kost writes: [...] > After all I see why you were confused. Emacs interface has always been > aimed only for a user profile. "M-x guix-system-generations" was added > very recently just to show what systems you have and what global > packages they contain, and by accident you can perform th

bug#22607: doc install from *Guix Package Info: profile* fails

l...@gnu.org (Ludovic Courtès) writes: [...] > As a side note, I think it would be very helpful if you could spend more > time to make your messages concise and to-the-point. Will do! > I understand it’s not always easy, but it would increase throughput > and probably reduce frustration as well!

bug#22600: 'Globally-Visible Packages' not shown by 'M-x guix-installed-packages'

Alex Kost writes: [...] > I don't understand what "w/wo user mods" means, That "official" guix recipes in local repo may be modified. Revised table: ** Sources of and ways to install packages in guixSD | Recipe source | avail to | recipe upgrade | location | package install

bug#22650: guixSD default umask is 0000

out of the box, umask should default to something more typical.

bug#22651: Up: GNU Guix doc produces 404 page not found

Start on https://www.gnu.org/software/guix/download/ click 'Installation instructions.' and 'Up' 3 times lands on 'https://www.gnu.org/software/guix/manual/dir/index.html' which produces '404 - Page Not Found' error

bug#22546: Download-Page is "hiding" what the options actually are

l...@gnu.org (Ludovic Courtès) writes: > Robin Vobruba skribis: > >> Being new to Guix, i went to the Download page: >> https://www.gnu.org/software/guix/download/ >> >> immediately saw the 3 big options >> read their title/names >> was confused what the difference might be between "GuixSD" and "

bug#22695: Binary Installation bugs and suggestions

I attempted to perform 'Binary Installation' on Debian 8 following ... https://www.gnu.org/software/guix/manual/html_node/Binary-Installation.html#Binary-Installation last updated November 04, 2015 Bugs: A) The 4 occurrences of '~root' should be replaced with '/root' B) What does 'On hosts us

bug#22695: Binary Installation bugs and suggestions

Ricardo Wurmus writes: > myglc2 writes: > >> I attempted to perform 'Binary Installation' on Debian 8 following ... >> >> https://www.gnu.org/software/guix/manual/html_node/Binary-Installation.html#Binary-Installation >> >> last updated Novembe

bug#22695: Binary Installation bugs and suggestions

Ricardo Wurmus writes: > myglc2 writes: > >> The use case I had in mind is that sysadmin uses Guix to provide a >> specific Guix environment to support 1 or more "dumb" application users >> (e.g, provide a stable specific version of R to a project team for t

bug#22695: Binary Installation bugs and suggestions

Jookia <166...@gmail.com> writes: > On Tue, Feb 16, 2016 at 05:51:37PM +0100, Andreas Enge wrote: >> I had the same experience on my arm machines. So this might be a real bug. >> Or does one need to do more than copy the file and reboot? > > You need to run 'systemctl start guix-daemon'. on Debia

bug#22650: guixSD default umask is 0000

l...@gnu.org (Ludovic Courtès) writes: > I can’t reproduce this. For instance, in the system created with: > > guix system vm gnu/system/examples/bare-bones.tmpl > > ‘umask’ returns 0022. > > Could it be that your user accounts have shell startup files like > ~/.bashrc that specify a different

bug#22650: guixSD default umask is 0000

l...@gnu.org (Ludovic Courtès) writes: > myglc2 skribis: > >> glc@g1 ~$ ssh glc4@g1 >> glc4@g1's password: >> glc4@g1 ~$ umask >> > > Oh indeed, I can reproduce it. > > The problem is that lshd resets the umask when it starts (in > sr

bug#22872: make check fails on commit caeadfd

Please see make.check.caeadfd.log. I can provide the associated test-suite.log (99 MB), or sub-sections if they are of interest. FWIW, the previous commit, c22a132, passes. make.check.caeadfd.log Description: Binary data

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

Alex Kost writes: [...] >> So, should I put ... >> >> '(guix-emacs-load-autoloads "/run/current-system/profile")' >> >> ... in init.el, in which case guix INFO should say so. > > Well, you can do it as a temporary workaround, but we'll fix it soon (I > mean the system profile will also be inspecte

bug#22927: system-installed emacs does not find system-installed fonts

Not technically not a bug because the doc says ... 2.6.2 X11 Fonts The ‘fontconfig’ package in Guix looks for fonts in ‘$HOME/.guix-profile’ by default. Thus, to allow graphical applications installed with Guix to display fonts, you have to install fonts with Guix as well. But it does seem coun

bug#22930: X11 forwarding fails without /tmp/.X11-unix directory

Example: using guix commit 59a4dd5 with openssh xauth & emacs in the user profile (c02glc.scm) and a minimal system profile (c02system.scm), after a reboot we see ... nemo:~ $ ssh g1 glc@g1's password: X11 forwarding request failed on channel 0 ... and in /var/log/messages ... Mar 6 19:23:35 lo

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

Alex Kost writes: [...] > No, I mean it is fixed in the current master, but as I wrote¹ it will > take effect only after we update our "guix" package. Currently it is > "guix-devel" package at commit c3f29bc², which is older then commit > 004ea62 (that fixed this issue). > > After we update "gu

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

Alex Kost writes: > myglc2 (2016-03-07 23:03 +0300) wrote: > >> Alex Kost writes: >> >> [...] >> >>> No, I mean it is fixed in the current master, but as I wrote¹ it will >>> take effect only after we update our "guix" package. Currentl

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

Alex Kost writes: > myglc2 (2016-03-08 16:49 +0300) wrote: > >> Alex Kost writes: >> >>> myglc2 (2016-03-07 23:03 +0300) wrote: >>> > [...] >>>> I re-read your earlier posts. AIUI now, in order to use the latest guix >>>> emacs

bug#22974: make check FAIL: tests/store

git checkout: * master ce6027b gnu: nautilus: Don't propagate gtk+. == GNU Guix 0.9.1: ./test-suite.log == # TOTAL: 61 # PASS: 60 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test

bug#22974: make check FAIL: tests/store

l...@gnu.org (Ludovic Courtès) writes: > myglc2 skribis: > >> tests/store.scm:740: FAIL verify-store >> tests/store.scm:757: FAIL verify-store + check-contents > > Does this pass after ‘make recheck’? > > If not, could you try: > > rm -rf test-tmp

bug#22981: guix-edit does not find git checkout directory

Situation: GuixSD sysetm managaed by user glc using a git checkout in /home/glc/sre/guix. Problem: When I follow the manual to set up a vanila user (glc5) with a separate git checkout in /home/glc5/src/guix, guix-edit does not find the checkout source. Note: I followed comments from the #guix ir

bug#22981: guix-edit does not find git checkout directory

Alex Kost writes: > myglc2 (2016-03-11 00:56 +0300) wrote: > >> Situation: GuixSD sysetm managaed by user glc using a git checkout in >> /home/glc/sre/guix. >> >> Problem: When I follow the manual to set up a vanila user (glc5) with a >> separate git checko

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

When running GuixSD on a headless server ... ssh emacs ... produces emacs running in X but ... - all of the menu icons are missing except one ('file drawers') - lots of messages are shooting in the tty session (sample below). This actually doesn't bother me because, hey, who uses the stinking

bug#22981: guix-edit does not find git checkout directory

Alex Kost writes: > myglc2 (2016-03-11 17:45 +0300) wrote: > >> Alex Kost writes: > [...] >>> Anyway, you can configure any directory for "M-x guix-edit" by setting >>> 'guix-directory' variable. See (info "(guix) Emacs Commands"

bug#22981: guix-edit does not find git checkout directory

Alex Kost writes: > myglc2 (2016-03-13 05:00 +0300) wrote: > > [...] >> You probably already thought of this: Can guix be made easier to use by >> converting some of the state-full guix configuration into guix recipe >> inputs? > > Sorry, my knowledge in

bug#23072: GuixSD SSD install hangs at clocksource

I tried to upgrade my headless server running GuixSD from to HD to SSD. First I shot myself in the foot doing 'guix init' on the SSD. Possibly by labeling the SSD root using the same label as the system HD root, or maybe I miss-specified the bootloader device? Anyway, to dig myself out, I switche

bug#23072: GuixSD SSD install hangs at clocksource

Florian Paul Schmidt writes: > On 20.03.2016 20:56, myglc2 wrote: > >> - I did a near-identical install to a SSD (Kingston ssdnow300), see >> "c06system-ssd.scm.log". If installed on the 1st server this shows >> Guix welcome screen, loads the keyboard &

bug#22981: guix-edit does not find git checkout directory

l...@gnu.org (Ludovic Courtès) writes: > Alex Kost skribis: > >> Ludovic Courtès (2016-03-14 01:01 +0300) wrote: >> >>> myglc2 skribis: >>> >>>> Guix is "stateful" because, to use a git checkout, I have to set "state" >&

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

Alex Kost writes: > Alex Kost (2016-03-07 12:14 +0300) wrote: > >> myglc2 (2016-03-06 17:47 +0300) wrote: >> [...] >> >> No, I mean it is fixed in the current master, but as I wrote¹ it will >> take effect only after we update our "guix" packag

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

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#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#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#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#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#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"

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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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"

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#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#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#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#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#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#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#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#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#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#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#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

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 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/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: 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: 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

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

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#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#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#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#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#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#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 >>

  1   2   >