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

[myglc2]

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 GC root.  Toward
>> that end, when I run "guix environment guix" to update my development
>> environment profile, I make sure to preserve my previous profile as a GC
>> root until I'm confident that my new profile is working.
>
> The “make as-derivation” command aims to help with this bootstrapping
> problem: given an already installed Guix, it builds your checkout and
> its dependencies like ‘guix pull’ would do.  Thus, you can run:
>
>   $(make as-derivation)/bin/guix environment guix

Nice! This is news to me. Thank you for pointing it out.

Does 'make as-derivation' set the "current" symlink normally set by
'guix pull'?

TIA - George

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

[myglc2]

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' steps. To update the version (and rebuild
>>> everything), use 'git clean -dfx; ./bootstrap; ./configure; make'.
>>
>> I’m wary of adding this for similar reasons that Ludo wrote earlier.  In
>> my opinion this ends up cluttering the manual with notes and what I
>> consider to be only tangentially relevant for readers of the manual.
>
> An alternative might be to change the output of “guix --version” in the
> presence of GUIX_UNINSTALLED, which is set by “pre-inst-env”.  This
> could be a simple change in “show-version-and-exit” that would use
> something other than “%guix-version” when GUIX_UNINSTALLED is set.
>
> What do others think?
>
> --
> Ricardo

I like it.

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

[myglc2]

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/profile
./pre-inst-env guix COMMAND ARGS...

... and I am sure you can predict what I will say next ;-)

How about putting this in the doc?

- George

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

[myglc2]

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)

[George myglc2 Clemmer]

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.drv
   /gnu/store/izxixb30i4r79gahirb4nj5ay0z8nzv1-info-dir.drv
   /gnu/store/bdg4x3925r9l3458li48hp1i26shd7yw-manual-database.drv
Backtrace:
  10 (primitive-load "/gnu/store/611mdvnasj59v5j46g8mhq7aw0g?")
In ice-9/eval.scm:
   721:20  9 (primitive-eval (begin (use-modules (guix build #) ?) ?))
In ice-9/psyntax.scm:
  1235:36  8 (expand-top-sequence ((begin (use-modules (# # ?) ?) ?)) ?)
  1182:24  7 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
  1182:24  6 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
   285:10  5 (parse _ (("placeholder" placeholder)) (()) _ c (eval) ?)
In ice-9/boot-9.scm:
  3365:20  4 (process-use-modules _)
   222:17  3 (map1 (((guix build utils)) ((srfi srfi-1)) ((srfi ?)) ?))
  3366:31  2 (_ ((guix build utils)))
   2791:6  1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ ?)
In unknown file:
   0 (scm-error misc-error #f "~A ~S" ("no code for modu?" ?) ?)

ERROR: In procedure scm-error:
no code for module (guix build utils)
Creating manual page database...
builder for `/gnu/store/izxixb30i4r79gahirb4nj5ay0z8nzv1-info-dir.drv' failed 
with exit code 1
cannot build derivation 
`/gnu/store/mcfys0glgv1hnq5mrcs9xnmn4bpzr3ys-profile.drv': 1 dependencies 
couldn't be built
guix environment: error: build failed: build of 
`/gnu/store/mcfys0glgv1hnq5mrcs9xnmn4bpzr3ys-profile.drv' failed
make: *** [Makefile:9: guix/] Error 1

FWIW, guix (GNU Guix) 0.14.0-11.ab85cf7 doesn't generate the error.

HTH - George

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

[George myglc2 Clemmer]

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

[myglc2]

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
> have to use http://, not https://. I think the other servers you
> mention are behind proxies which handle the SSL part and forward the
> requests on to the substitute process.
>
> Does it work if you run this instead?
>
>  guix environment --substitute-urls=http://g1.local:8080
>
> Carlo

LOL, yes it does!

Duh, I guess I was so impressed by all the HTTPS's in "3.3.3 Substitute
Authentication" that I couldn't see the HTTP's in "5.11 Invoking ‘guix
publish’" ;-)

Many thanks - George

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

[George myglc2 Clemmer]

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 data


sysi17.scm
Description: Binary data

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

[George myglc2 Clemmer]

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 get this error on sysi17 ...

g1@sysi17 ~ [env]$ guix environment --substitute-urls=https://g1.local:8080
substitute: guix substitute: error: TLS error in procedure 'handshake': An 
unexpected TLS packet was received.
guix environment: error: corrupt input while restoring archive from #

... which looks like this on g1 ...

In ice-9/boot-9.scm:
841:4  4 (with-throw-handler _ _ _)
In web/server/http.scm:
   127:28  3 (_)
In web/request.scm:
   205:31  2 (read-request # _)
In web/http.scm:
   1141:6  1 (read-request-line _)
In ice-9/boot-9.scm:
   752:25  0 (dispatch-exception _ _ _)
Bad request: Bad Request-Line:

"\x16\x03\x01\x00ò\x01\x00\x00î\x03\x03Zäº\x17<À\x9aËù»ò\x8c\x12n8y:\x16¸q\x0fá\x87Gtéc´8¿±<\x00\x00rÀ,À\x87Ì©À\xadÀ"

The keys are setup this way ...

g1@g1 ~$ cat /etc/guix/signing-key.pub
(public-key
 (ecc
  (curve Ed25519)
  (q #C38DCF2B0EBE663B9450BEFB0E77DFAF6643E8E971318F7002721076ED9C9788#)
  )
 )

g1@sysi17 ~ [env]$ sudo cat /etc/guix/acl
Password:
(acl
 (entry
  (public-key
   (ecc
(curve Ed25519)
(q #C38DCF2B0EBE663B9450BEFB0E77DFAF6643E8E971318F7002721076ED9C9788#)
)
   )
  (tag
   (guix import)
   )
  )
  [...]
 )

sysi17 has no trouble reaching hydra ...

g1@sysi17 ~ [env]$ guix environment
--substitute-urls=https://mirror.hydra.gnu.org --dry-run hello
substitute: updating list of substitutes from
'https://mirror.hydra.gnu.org'... 100.0%
[...]

or pinging g1...
g1@sysi17 ~ [env]$ ping g1.local
PING g1.local (192.168.1.7): 56 data bytes
64 bytes from 192.168.1.7: icmp_seq=0 ttl=64
[...]

Both systems were configured using ...

guix (GNU Guix) 0.14.0.4439-eb88e

... which was built from ...

5b862761f2a60af79b4c16851454a5e792ef4f56 gnu: guix: Update to ab85cf7.

... with 4.16.4 reverted ...

ba39d3280759fb20a4ff0092a5afac721a5fa769 "gnu: linux-libre: Update to 4.16.4."

TIA - George

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

[George myglc2 Clemmer]

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

[George myglc2 Clemmer]

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 <myg...@gmail.com> wrote:
>
>> 'guix system vm-image' hangs on guix (GNU Guix) 0.14.0.4439-eb88e built
>> from source today. Please see log except below. It worked on guix (GNU
>> Guix) 0.14.0.4196-2c92a. built <2018-04-18 Wed>
>>
>> TIA - George
>>
> [...]
>> environment variable `PATH' set to 
>> `/gnu/store/1n3cvnxrz1m6jqc09d9m1grbfbs91kmv-qemu-minimal-2.12.0/bin:/gnu/store/h8670f6j1rawhhaz8wvdy5gv79lny0am-parted-3.2/sbin:/gnu/store/nm305rpb2mvridkyj4l3636nc9ql4lf9-e2fsprogs-1.43.6/bin:/gnu/store/nm305rpb2mvridkyj4l3636nc9ql4lf9-e2fsprogs-1.43.6/sbin:/gnu/store/0sq2nflm42x0znkv44add0gk82khkcb6-dosfstools-4.1/sbin:/gnu/store/0hl513mnpkhszm2hjai2w9cxmpxs0vgq-sed-4.4/bin:/gnu/store/1h44pkgdd7n6s3i2vjh54awsvfmc219j-grep-3.1/bin:/gnu/store/kgzvfby2ggi1xawsh5vjh4s93qk2dp9k-coreutils-8.28/bin:/gnu/store/k7r2m2wgj8x8jjhccwjsiimp0dlzxb7i-findutils-4.6.0/bin:/gnu/store/ahxc89r6npzf2bbl8yg5vdjicskzzjf3-gawk-4.1.4/bin:/gnu/store/cwwvdxd9d778a2xp8vbb38vl62rx992g-guix-0.14.0-11.ab85cf7/bin:/gnu/store/cwwvdxd9d778a2xp8vbb38vl62rx992g-guix-0.14.0-11.ab85cf7/sbin'
>> creating partition table with 2 partitions (10190.0 MiB, 40.0 MiB)...
>> [1.344115] tsc: Refined TSC clocksource calibration: 3392.348 MHz
>> [1.344865] clocksource: tsc: mask: 0x max_cycles: 
>> 0x30e6121e742, max_idle_ns: 440795321217 ns
>> [1.856062] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>>   C-c C-c
>
> Same log output on my end.
>
>> g1@g1 ~/src/vm/vms/sysi20$ guix --version
>> guix (GNU Guix) 0.14.0.4439-eb88e
>>
>
> I bisected the git repo to commit:
>
> ```
> commit ba39d3280759fb20a4ff0092a5afac721a5fa769
> Author: Mark H Weaver <m...@netris.org>
> Date:   Tue Apr 24 16:51:45 2018 -0400
>
> gnu: linux-libre: Update to 4.16.4.
>
> * gnu/packages/linux.scm (%linux-libre-version): Update to 4.16.4.
> (%linux-libre-hash): Update hash.
>
> ```
>
> Perhaps we should open a bug.
>
> `~Eric

Thank you Eric! Actually I meant to send it to bug-guix@gnu.org
before. Here is something that fails here.

guix system vm-image --image-size=10G sysi19.scm



sysi19.scm
Description: Binary data

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

[myglc2]

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

g1@g1 ~/src/guix$ guix environment --ad-hoc perl perl-timedate make
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 
100.0%
The following derivations will be built:
   /gnu/store/ayrxnbdb7b6fksg2bmf0f1zx6cynxzhh-profile.drv
   /gnu/store/xhzz6r8y2kqr6d58dlm2ijylb8z3q2s5-info-dir.drv
   /gnu/store/bxq1by3s2x0r742mz0h03wbr228gms0y-ca-certificate-bundle.drv
   /gnu/store/36l3lw3dlp239ds0giv9w1zn92j80g3n-fonts-dir.drv
   /gnu/store/5k76cb350q3ym35pn1jd9rd8gx37hqn0-manual-database.drv
Creating manual page database...
794 entries processed in 0.8 s
g1@g1 ~/src/guix [env]$ perl ~/.mail-mirror/mb2md-3.20.pl
Can't locate Date/Parse.pm in @INC (you may need to install the Date::Parse 
module) (@INC contains: 
/gnu/store/7dckxj5l8kxcacm56k0yn3r62hrsj4if-profile/lib/perl5/site_perl/5.26.2/x86_64-linux-thread-multi
 /gnu/store/7dckxj5l8kxcacm56k0yn3r62hrsj4if-profile/lib/perl5/site_perl/5.26.2 
/gnu/store/7dckxj5l8kxcacm56k0yn3r62hrsj4if-profile/lib/perl5/site_perl 
/gnu/store/ynk3rg3i791i6k7rz2imbyj9wyfjrnrc-perl-5.26.2/lib/perl5/site_perl/5.26.2/x86_64-linux-thread-multi
 
/gnu/store/ynk3rg3i791i6k7rz2imbyj9wyfjrnrc-perl-5.26.2/lib/perl5/site_perl/5.26.2
 
/gnu/store/ynk3rg3i791i6k7rz2imbyj9wyfjrnrc-perl-5.26.2/lib/perl5/5.26.2/x86_64-linux-thread-multi
 /gnu/store/ynk3rg3i791i6k7rz2imbyj9wyfjrnrc-perl-5.26.2/lib/perl5/5.26.2) at 
/home/g1/.mail-mirror/mb2md-3.20.pl line 385.
BEGIN failed--compilation aborted at /home/g1/.mail-mirror/mb2md-3.20.pl
line 385.

The offencing script is attached.

TIA - George



mb2md-3.20.pl
Description: Binary data

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

[George myglc2 Clemmer]

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 -h
   mb2md [-c] -m [-d destdir]
   mb2md [-c] -s sourcefile [-d destdir]
   mb2md [-c] -s sourcedir [-l wu-mailboxlist] [-R|-f somefolder] [-d 
destdir] [-r strip_extension]
g1@g1 ~/.mail-mirror [env]$


... to stop working ...

g1@g1 ~/.mail-mirror$  guix environment --ad-hoc perl perl-timedate make wget
g1@g1 ~/.mail-mirror [env]$  perl mb2md-3.20.pl
Can't locate Date/Parse.pm in @INC (you may need to install the Date::Parse 
module) (@INC contains: 
/gnu/store/wpwb4ig3qhv3m7axjlid2c0f1jqzp09p-profile/lib/perl5/site_perl/5.26.2/x86_64-linux-thread-multi
 /gnu/store/wpwb4ig3qhv3m7axjlid2c0f1jqzp09p-profile/lib/perl5/site_perl/5.26.2 
/gnu/store/wpwb4ig3qhv3m7axjlid2c0f1jqzp09p-profile/lib/perl5/site_perl 
/gnu/store/ynk3rg3i791i6k7rz2imbyj9wyfjrnrc-perl-5.26.2/lib/perl5/site_perl/5.26.2/x86_64-linux-thread-multi
 
/gnu/store/ynk3rg3i791i6k7rz2imbyj9wyfjrnrc-perl-5.26.2/lib/perl5/site_perl/5.26.2
 
/gnu/store/ynk3rg3i791i6k7rz2imbyj9wyfjrnrc-perl-5.26.2/lib/perl5/5.26.2/x86_64-linux-thread-multi
 /gnu/store/ynk3rg3i791i6k7rz2imbyj9wyfjrnrc-perl-5.26.2/lib/perl5/5.26.2) at 
mb2md-3.20.pl line 385.
BEGIN failed--compilation aborted at mb2md-3.20.pl line 385.
g1@g1 ~/.mail-mirror [env]$

TIA - George



mb2md-3.20.pl
Description: Binary data

bug#31113: mcron ERROR: In procedure mktime:

[George myglc2 Clemmer]

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:

[George myglc2 Clemmer]

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): 45.0
Backtrace:
   4 (primitive-load "/gnu/store/422ngw911hz62510b33wdvrp1a6?")
   In mcron/base.scm:
  103:25  3 (add-job # ?)
   In mcron/job-specifier.scm:
  251:32  2 (_ 1523292689)
   In mcron/vixie-time.scm:
  381:15  1 (_ _)
   In unknown file:
  0 (mktime #(0 45.0 +inf.0 9 3 118 1 98 1 14400 "EDT") #)
ERROR: In procedure mktime:
...
#+END_EXAMPLE

Please see system config attached (my /etc/gen/x/010/sys.scm)

TIA - George

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

[myglc2]

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

Hi Chris, yes it works here both ways. Thanks, George

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

[myglc2]

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 data

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

[myglc2]

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

[myglc2]

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

[myglc2]

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"

[myglc2]

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

[George myglc2 Clemmer]

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

   GNU Guix 0.14.0.3463-be5ed-dirty: ./test-suite.log


# TOTAL: 766
# PASS:  755
# SKIP:  10
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

[...]

FAIL: tests/elpa


test-name: elpa->guix-package test 1
location: /home/g1/src/guix/tests/elpa.scm:103
source:
+ (test-assert
+   "elpa->guix-package test 1"
+   (eval-test-with-elpa "auctex"))
random seed for tests: 1521330420

Starting download of /tmp/guix-file.OeUgKR
>From https://elpa.gnu.org/packages/auctex-11.88.6.tar...
 auctex-11.88.6.tar  4.6MiB   0B/s 00:00 [  ]   
0.0% auctex-11.88.6.tar  4.6MiB   779KiB/s 00:00 [  
]   1.4% auctex-11.88.6.tar  4.6MiB   1.7MiB/s 00:00 [## 
   ]  15.1% auctex-11.88.6.tar  4.6MiB   2.3MiB/s 00:01 [##  
  ]  35.6% auctex-11.88.6.tar  4.6MiB   2.4MiB/s 00:01 
[# ]  54.8% auctex-11.88.6.tar  4.6MiB   2.7MiB/s 
00:01 [##]  80.9% auctex-11.88.6.tar  4.6MiB   
2.9MiB/s 00:02 [##] 100.0%

;;; (fail (package (name "emacs-auctex") (version "11.88.6") (source (origin 
(method url-fetch) (uri (string-append "https://elpa.gnu.org/packages/auctex-; 
version ".tar")) (sha256 (base32 
"1pmki8hdjjikxlvip3pzi350bln3gcimr27yjf0xfwjvnp5hh9nc" (build-system 
emacs-build-system) (home-page "http://www.gnu.org/software/auctex/;) (synopsis 
"Integrated environment for *TeX*") (description "This is the AUCTeX 
description.") (license license:gpl3+)) #f)
actual-value: #f
result: FAIL
***

Note: There was a guile segfault at about the same time ...

Mar 17 20:52:09 localhost vmunix: [202122.544472] .guile-real[13130]: segfault 
at 7b ip 0057885d sp 7ffc1ac3a1b0 error 4 in 
.guile-real[40+38a000]

Version info:

g1@g1 ~/src/guix$ git log -n 1 --oneline
be5ed1421 (HEAD -> master, origin/master, origin/HEAD) gnu: Add terraform-docs.
g1@g1 ~/src/guix$ guix --version
guix (GNU Guix) 0.14.0.3463-be5ed-dirty
Copyright (C) 2018 the Guix authors
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
g1@g1 ~/src/guix$ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add ..." to update what will be committed)
  (use "git checkout -- ..." to discard changes in working directory)

modified:   po/guix/cs.po
modified:   po/guix/da.po
modified:   po/guix/de.po
modified:   po/guix/eo.po
modified:   po/guix/fr.po
modified:   po/guix/hu.po
modified:   po/guix/pl.po
modified:   po/guix/pt_BR.po
modified:   po/guix/sr.po
modified:   po/guix/vi.po
modified:   po/guix/zh_CN.po
modified:   po/packages/da.po
modified:   po/packages/de.po
modified:   po/packages/eo.po
modified:   po/packages/fr.po
modified:   po/packages/hu.po
modified:   po/packages/pl.po
modified:   po/packages/pt_BR.po
modified:   po/packages/sr.po
modified:   po/packages/vi.po
modified:   po/packages/zh_CN.po

no changes added to commit (use "git add" and/or "git commit -a")
g1@g1 ~/src/guix$

HTH - George

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

[myglc2]

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

bug#30589: serial login not working

[George myglc2 Clemmer]

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

[myglc2]

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 agetty instance to base services. Make its 
tty optional.

... "fixes" the problem here.

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

[George myglc2 Clemmer]

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#30589: serial login not working

[George myglc2 Clemmer]

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. Then I tried ...

(define %my-services
  (modify-services %base-services
   (agetty-service-type config =>
(agetty-configuration
 (tty "ttyS1")
 (baud-rate "115200")

I can confirm that ...

root@g1 /home/g1# sudo echo 123 > /dev/ttyS1

... produces "123" on the serial line.

guix (GNU Guix) 0.14.0.2487-58246

config attached (my G54)

TIA - George

sys.scm
Description: Binary data

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

[George myglc2 Clemmer]

On 02/22/2018 at 11:41 Danny Milosavljevic writes:

> Hi George,
>
> On Wed, 21 Feb 2018 20:35:34 -0500
> George myglc2 Clemmer <myg...@gmail.com> 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. Let me clarify ...
>
> Oh, that changes things.  Ludo is debugging some silly UTF-8 problem
> with the virtual terminals on the VGA port right now - might be related,
> or not.  Who knows...

Well this problem goes back to November. The problem first appears in
my generation 19 ...

 19GNU with Linux-Libre 4.14.2 (beta)   61 2017-11-30 
19:18:15
 18GNU with Linux-Libre 4.13.12 (beta)  62 2017-11-11 
13:05:56

... which  correspond to ...

19 (GNU Guix) 0.13.0.5042-6e385
18 (GNU Guix) 0.13.0.4589-74bea6

Note: The results cited below are WRT my most recent build done
yesterday, guix (GNU Guix) 0.14.0.2455-26737.

>> GNU with Linuxlibre ..." for a couple seconds, and then 4) a blank.
>
> Is there still a cursor?

NO.

> What happens when you don't use the serial (so no console=...)

The VGA displays ...

- BIOS prompt
- grub menu
- 'Booting GNU linux-libre ...'
- ~1 seconds of messages
- Blank screen w/ no cursor

... which differers in that there are a couple seconds of boot messages.

> and then
> try to write something to /dev/console ?  It should show up somewhere.
> Where?  On the VGA port?

/home/g1# echo 123 > /dev/console

... shows nothing on the VGA or serial.

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

[George myglc2 Clemmer]

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'

[George myglc2 Clemmer]

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 exit code 1
note: keeping build directory `/tmp/guix-build-gst-libav-1.12.4.drv-0'
cannot build derivation 
`/gnu/store/rsz1v5bkwwj5arb21gs9h1ifl82cirjb-spice-0.14.0.drv': 1 dependencies 
couldn't be built
cannot build derivation 
`/gnu/store/sqh82dxywml5w7hv2ifdck6c8spkjqhg-qemu-2.11.1.drv': 1 dependencies 
couldn't be built
guix system: error: build failed: build of 
`/gnu/store/sqh82dxywml5w7hv2ifdck6c8spkjqhg-qemu-2.11.1.drv' failed

... larger log extract attached.

TIA - George



gst-plugins-ugly-1.12.4.drv.failed.log.gz
Description: Binary data

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

[George myglc2 Clemmer]

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
Guix) 0.13.0.5042-6e385 (My G19). In the later version, when I reboot
the VGA displays 1) the BIOS prompt, 2) the grub boot menu, 3) "Booting
GNU with Linuxlibre ..." for a couple seconds, and then 4) a blank.

In either version, this config ...

(agetty-service (agetty-configuration (tty "ttyS1")
(baud-rate "115200")))

... causes a login prompt to be raised on ttyS1 which, on my system, is
mapped to IPMI Serial over Lan (SOL). However recently you said ...

On 02/15/2018 at 15:54 Danny Milosavljevic writes:

> In the long run please remove your agetty-service, it should automatically 
> appear
> (it recovers the settings from the "console" kernel-argument).

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).

However, if I *ignore your advice* a login prompt *is raised* on ttyS1
(My G45).

So, IIUC, it's not working the way you said it would, but it's not a
problem for me because I can just use the agetty-service.

Not sure your questions are still relevant, but here is what I see ...

On 02/17/2018 at 17:05 Danny Milosavljevic writes:

> What does
>
> stty -F /dev/ttyS1
>
> say?

g1@g1 ~/www$ sudo stty -F /dev/ttyS1
speed 115200 baud; line = 0;
-brkint -imaxbel

On 02/17/2018 at 17:04 Danny Milosavljevic writes:

> Huh, please try
>
> strace -f agetty /dev/ttyS1 >log 2>&1
>
> and send the log to the list...

(log.gz attached)

HTH - George



log.gz
Description: Binary data


sys.scm
Description: Binary data

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

[George myglc2 Clemmer]

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 <myg...@gmail.com> wrote:

>> FWIW, I don't see agetty running ...
>
> What happens when you run manually:
>
> agetty /dev/ttyS1
>
> Does it keep running?

No. /var/log/debug is also jammed like this ...

[...]
Feb 15 19:05:29 localhost vmunix: [5.890367] Creating 1 MTD partitions on 
"intel-spi":
Feb 15 19:05:29 localhost vmunix: [5.890370] 0x-0x0080 
: "BIOS"
Feb 15 19:05:29 localhost vmunix: [5.906526] [TTM] Initializing pool 
allocator
Feb 15 19:05:29 localhost vmunix: [5.910911] [TTM] Initializing DMA pool 
allocator
Feb 15 19:05:29 localhost vmunix: [6.023282] fbcon: astdrmfb (fb0) is 
primary device
Feb 15 19:05:29 localhost vmunix: [6.091450] Console: switching to colour 
frame buffer device 160x64
Feb 15 19:05:29 localhost vmunix: [6.099375] ipmi_si IPI0001:00: Found new 
BMC (man_id: 0x00, prod_id: 0xaabb, dev_id: 0x20)
Feb 15 19:05:30 localhost vmunix: [6.105342] pps pps0: new PPS source ptp0
Feb 15 19:05:30 localhost vmunix: [6.105363] igb :03:00.0: added PHC on 
eth0
Feb 15 19:05:30 localhost vmunix: [6.105363] igb :03:00.0: Intel(R) 
Gigabit Ethernet Network Connection
Feb 15 19:05:30 localhost vmunix: [6.105365] igb :03:00.0: eth0: 
(PCIe:2.5Gb/s:Width x1) d0:50:99:5b:d7:55
Feb 15 19:05:30 localhost vmunix: [6.105959] igb :03:00.0: eth0: PBA 
No: 001300-000
Feb 15 19:05:30 localhost vmunix: [6.105972] igb :03:00.0: Using MSI-X 
interrupts. 4 rx queue(s), 4 tx queue(s)
Feb 15 19:05:30 localhost vmunix: [6.149879] ipmi_si IPI0001:00: IPMI kcs 
interface initialized
Feb 15 19:05:30 localhost vmunix: [6.182426] ast :06:00.0: fb0: 
astdrmfb frame buffer device
Feb 15 19:05:30 localhost vmunix: [6.188672] IPMI SSIF Interface driver
Feb 15 19:05:30 localhost vmunix: [6.205279] intel_rapl: Found RAPL domain 
package
Feb 15 19:05:30 localhost vmunix: [6.209992] intel_rapl: Found RAPL domain 
core
Feb 15 19:05:30 localhost vmunix: [6.211999] [drm] Initialized ast 0.1.0 
20120228 for :06:00.0 on minor 0
Feb 15 19:05:30 localhost vmunix: [6.221483] intel_rapl: Found RAPL domain 
dram
Feb 15 19:05:30 localhost vmunix: [6.225945] intel_rapl: RAPL package 0 
domain package locked by BIOS
Feb 15 19:05:30 localhost vmunix: [6.232290] intel_rapl: RAPL package 0 
domain dram locked by BIOS
Feb 15 19:05:30 localhost vmunix: [6.323457] Error: Driver 'pcspkr' is 
already registered, aborting...
Feb 15 19:05:30 localhost vmunix: [6.351730] pps pps1: new PPS source ptp1
Feb 15 19:05:31 localhost vmunix: [6.355748] igb :04:00.0: added PHC on 
eth1
Feb 15 19:05:31 localhost vmunix: [6.360278] igb :04:00.0: Intel(R) 
Gigabit Ethernet Network Connection
Feb 15 19:05:31 localhost vmunix: [6.367150] igb :04:00.0: eth1: 
(PCIe:2.5Gb/s:Width x1) d0:50:99:5b:d7:54
Feb 15 19:05:31 localhost vmunix: [6.374341] igb :04:00.0: eth1: PBA 
No: 001300-000
Feb 15 19:05:31 localhost vmunix: [6.379472] igb :04:00.0: Using MSI-X 
interrupts. 4 rx queue(s), 4 tx queue(s)
Feb 15 19:05:31 localhost vmunix: [6.393246] igb :04:00.0 enp4s0: 
renamed from eth1
Feb 15 19:05:31 localhost vmunix: [6.424048] igb :03:00.0 enp3s0: 
renamed from eth0
Feb 15 19:05:31 localhost vmunix: [6.457010] Adding 10117460k swap on 
/dev/nvme0n1p2.  Priority:-2 extents:1 across:10117460k SSFS
Feb 15 19:05:31 localhost vmunix: [7.559634] IPv6: ADDRCONF(NETDEV_UP): 
enp3s0: link is not ready
Feb 15 19:05:31 localhost vmunix: [   10.412657] igb :03:00.0 enp3s0: igb: 
enp3s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 15 19:05:31 localhost vmunix: [   10.528283] IPv6: ADDRCONF(NETDEV_CHANGE): 
enp3s0: link becomes ready
Feb 15 19:08:06 localhost ntpd[368]: receive: Unexpected origin timestamp 
0xde309f65.f5541f08 does not match aorg 00. from 
server@162.210.110.4 xmt 0xde309f66.6426f9e7
Feb 15 19:10:26 localhost vmunix: [  349.762770] sysrq: SysRq : HELP : 
loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) 
kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) 
show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) 
show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V) 
show-blocked-tasks(w) dump-ftrace-buffer(z) 
Feb 15 19:13:39 localhost ntpd[368]: kernel reports TIME_ERROR: 0x41: Clock 
Unsynchronized
Feb 15 19:24:44 localhost -- MARK --
Feb 15 19:44:44 localhost -- MARK --
Feb 15 19:59:03 localhost vmunix: [ 3266.992550] sysrq: SysRq : HELP : 
loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) 
kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) 
show-memory-usage(m

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

[George myglc2 Clemmer]

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 'auto'. However, in my tests, when that
> ;;; option is selected, agetty never presents the login prompt, and the
> ;;; term-ttyS0 service respawns every few seconds.
> #$@(if local-line
>#~(#$(match local-line
>   ('auto "--local-line=auto")
>   ('always "--local-line=always")
>   ('never "-local-line=never")))
>#~())
>
> So try specifying local-line ?

Not clear what you wanted so I didn't try this.

> Also, can you try updating again?
>
> I've pushed some agetty consolidation to guix-master (only) today.

I did that, see below ...

> Also, you have
>
>  (kernel-arguments '("console=ttyS1,115200"))
>
> AND
>
> (agetty-service (agetty-configuration (tty "ttyS1")
>(baud-rate "115200")))
> Starting today, the second one will be automatically configured by
> %base-services.

I removed agetty-service but agetty didn't run, see below ...

> So please keep your config the same and reconfigure and let's see what
> happens.

I did git-pull & make to get guix (GNU Guix) 0.14.0.1879-06a9 and 'guix
system reconfigure' >>> the console is still blank.  (my G36)

> In the long run please remove your agetty-service, it should automatically 
> appear
> (it recovers the settings from the "console" kernel-argument).

Then I removed agetty-service, reconfigured and rebooted >>> the console
is still blank. (my G37, sys.scm attached)

FWIW, I don't see agetty running ...

g1@g1 ~$ pstree -a -A
shepherd --no-auto-compile/gnu/store/hjfwjz9g0jrjcyggybi
  |-dhclient -nw -pf /var/run/dhclient.pid enp4s0enp3
  |-guix-daemon --build-users-group guixbuild--
  |-mingetty --noclear tty6
  |-mingetty --noclear tty5
  |-mingetty --noclear tty4
  |-mingetty --noclear tty3
  |-mingetty --noclear tty2
  |-mingetty --noclear tty1
  |-nscd -f/gnu/store/gh3xhwgh927md5ifzdmg0cgpqc0as1sh-ns
  |   `-7*[{nscd}]
  |-ntpd -n -c/gnu/store/1l1yf5dss8r9pqxklaax32s6bkah09c
  |   `-{ntpd}
  |-sshd -D -f/gnu/store/7z8qc04s48cgzvpc77715r3ckh7qr
  [...]
  |-syslogd --rcfile/gnu/store/y5nrfbj52vlnj77iyk
  |-udevd
  `-8*[{shepherd}]

TIA - George



sys.scm
Description: Binary data

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

[George myglc2 Clemmer]

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:
 19GNU with Linux-Libre 4.14.2 (beta)   61 2017-11-30 
19:18:15
 18GNU with Linux-Libre 4.13.12 (beta)  62 2017-11-11 
13:05:56

I just noticed this or I would have reported sooner.

Can check/test on either generation if it would be of help.

TIA - George

config:


sys.scm
Description: Binary data

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

[myglc2]

On 02/09/2018 at 22:56 Ludovic Courtès writes:

> George myglc2 Clemmer <myg...@gmail.com> 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
>>> 0.10 until upstream comes up with a fix.
>>
>> FWIW, nss-mdns-0.10 segfaults also ...

ARGH!... my mistake, I was looking at ...

g1@g1 ~$   guix gc -R $(readlink -f /run/current-system) | grep nss-mdns
/gnu/store/mvjz94idlcralc0bmqvrbrxx89w0narf-nss-mdns-0.10

... bug I had not rebooted/restarted herd.  Many thanks - George

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

[George myglc2 Clemmer]

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 you for the workaround ;-) - George

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

[myglc2]

On 01/19/2018 at 14:25 Ludovic Courtès writes:

> Hi,
>
> George myglc2 Clemmer <myg...@gmail.com> skribis:
>
>> guix system vm-image -M 4 -c 4 /home/g1/www/VM-on-GuixSD/vm/ggg8/v1.scm 
>> --image-size=5GB
>
> [...]
>
>> `/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9iw-poppler-0.59.0/lib/libpoppler-cpp.la'
>>  -> 
>> `/fs/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9iw-poppler-0.59.0/lib/libpoppler-cpp.la'
>> `/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9iw-poppler-0.59.0/lib/libpoppler.so.70.0.0'
>>  -> 
>> `/fs/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9iw-poppler-0.59.0/lib/libpoppler.so.70.0.0'
>> ERROR: In procedure copy-file:
>> ERROR: In procedure copy-file: Success
>
> Most likely this is because 5GB is not enough.
>
> Can you try *without* the ‘--image-size’ option?  This will let ‘guix
> system’ determine the image size automatically.
>
> TIA,
> Ludo’.

Hi Ludo’, yes that fixed it, thanks. - George

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

[George myglc2 Clemmer]

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.drv
   /gnu/store/q1xb0mq5x4fxzz1yxdjxlg1g4snyj0kz-builder-in-linux-vm.drv
   /gnu/store/il22n187ai8yll6097flbvlabs77iyp4-linux-vm-loader.drv
   /gnu/store/cng0k9wp0zyjyfrarvymw9wwngc3x18k-parameters.drv
   /gnu/store/aaz95cp1baa4bcp7fljx8wb48fw6b4ys-init.drv
   /gnu/store/9p073wk4kgm1r1f3yizl8ms206xspsgx-raw-initrd.drv
   /gnu/store/3r3p4016xhlk5xh3mzhgiqc4dw9bynrh-system.drv
   /gnu/store/8hs0w9g3is0knichi53ls6mkg5sz5cdc-grub.cfg.drv
`/gnu/store/zs4irccfzrs2nkwrx3ra1bv4sm2k3cbl-linux-boot.scm' -> 
`contents/gnu/store/zs4irccfzrs2nkwrx3ra1bv4sm2k3cbl-linux-boot.scm'
`/gnu/store/qla5jhq1s4sq3r26z1bp2cr66vy9lk7s-e2fsck-static-1.43.6/sbin/e2fsck' 
-> 
`contents/gnu/store/qla5jhq1s4sq3r26z1bp2cr66vy9lk7s-e2fsck-static-1.43.6/sbin/e2fsck'
`/gnu/store/mv6445cazbhddm3wwc3053cpxjkf7q9m-records.scm' -> 
`contents/gnu/store/mv6445cazbhddm3wwc3053cpxjkf7q9m-records.scm'
[...]
`/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9iw-poppler-0.59.0/lib/libpoppler-glib.so.8'
 -> 
`/fs/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9iw-poppler-0.59.0/lib/libpoppler-glib.so.8'
`/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9iw-poppler-0.59.0/lib/libpoppler-cpp.la'
 -> 
`/fs/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9iw-poppler-0.59.0/lib/libpoppler-cpp.la'
`/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9iw-poppler-0.59.0/lib/libpoppler.so.70.0.0'
 -> 
`/fs/gnu/store/3vr7hais3mwd7hkllbhlwjbs6bk7d9iw-poppler-0.59.0/lib/libpoppler.so.70.0.0'
ERROR: In procedure copy-file:
ERROR: In procedure copy-file: Success

Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
GNU Guile 2.2.2
Copyright (C) 1995-2017 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(guile-user)>


guix --version
guix (GNU Guix) 0.14.0.1050-2cdf1




v1.scm
Description: Binary data

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

[George myglc2 Clemmer]

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.scm:
  1590:19  3 (format #t "Copyright ~a 2017 ~a" "(C)" "the Guix authors\n")
   261:19  2 (format:format-work "Copyright ~a 2017 ~a" ("(C)" "the Guix 
authors\n"))
70:10  1 (format:out-obj-padded _ _ _ _)
In unknown file:
   0 (display "the Guix authors\n" #)

ERROR: In procedure display:
ERROR: In procedure fport_write: Broken pipe
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.scm:
  1590:19  3 (format #t "Copyright ~a 2017 ~a" "(C)" "the Guix authors\n")
   261:19  2 (format:format-work "Copyright ~a 2017 ~a" ("(C)" "the Guix 
authors\n"))
70:10  1 (format:out-obj-padded _ _ _ _)
In unknown file:
   0 (display "the Guix authors\n" #)

ERROR: In procedure display:
ERROR: In procedure fport_write: Broken pipe
***

VERSION:
***
g1@g1 ~$ guix --version
guix (GNU Guix) 0.14.0.617-e2f37
Copyright (C) 2017 the Guix authors
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

bug#25296: fully functional desktop installation

[myglc2]

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

[myglc2]

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

[George myglc2 Clemmer]

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 a guix bug.

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

[George myglc2 Clemmer]

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 ~/src/guix$ guix package -M 4 -c 4 -m ../g1.scm
[...]
*** t9153-git-svn-rewrite-uuid.sh ***
not ok 4 - create new branches and tags
#
#   ( cd git_project &&
#   git svn branch -m "New branch 1" -d b_one New1 ) &&
#   ( cd svn_project &&
#   svn_cmd up && test -e b_one/New1/a.file ) &&
#
#   ( cd git_project &&
#   git svn branch -m "New branch 2" -d b_two New2 ) &&
#   ( cd svn_project &&
#   svn_cmd up && test -e b_two/New2/a.file ) &&
#
#   ( cd git_project &&
#   git svn branch -t -m "New tag 1" -d tags_A Tag1 ) &&
#   ( cd svn_project &&
#   svn_cmd up && test -e tags_A/Tag1/a.file ) &&
#
#   ( cd git_project &&
#   git svn tag -m "New tag 2" -d tags_B Tag2 ) &&
#   ( cd svn_project &&
#   svn_cmd up && test -e tags_B/Tag2/a.file )
#
# failed 1 among 4 test(s)
1..4
make[2]: *** [Makefile:49: t9141-git-svn-multiple-branches.sh] Error 1
make[2]: *** Waiting for unfinished jobs
ok 1 - load svn repo
ok 2 - verify uuid
# passed all 2 test(s)
1..2
ok 1 - initialize repo
ok 2 - clone
ok 3 - git svn gc runs
ok 4 - git svn mkdirs recreates empty directories after git svn gc
# passed all 4 test(s)
1..4
ok 1 - load svn dump
ok 2 - all svn merges became git merge commits
ok 3 - cherry picks did not become git merge commits
ok 4 - svn non-merge merge commits did not become git merge commits
ok 5 - commit made to merged branch is reachable from the merge
ok 6 - merging two branches in one commit is detected correctly
not ok 7 - everything got merged in the end # TODO known breakage
# still have 1 known breakage(s)
# passed all remaining 6 test(s)
1..7
make[2]: Leaving directory '/tmp/guix-build-git-2.15.0.drv-0/git-2.15.0/t'
make[1]: *** [Makefile:36: test] Error 2
make[1]: Leaving directory '/tmp/guix-build-git-2.15.0.drv-0/git-2.15.0/t'
make: *** [Makefile:2439: test] Error 2
phase `check' failed after 517.7 seconds
builder for `/gnu/store/r3rijd3pmkfdmg3h4spyb24az3xiylc4-git-2.15.0.drv' failed 
with exit code 1
guix package: error: build failed: build of 
`/gnu/store/r3rijd3pmkfdmg3h4spyb24az3xiylc4-git-2.15.0.drv' failed
g1@g1 ~/src/guix$ exit
exit

Full compressed log (300+K) available if needed.

HTH - George

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

[myglc2]

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 ('file drawers')

Icons are all OK now. Yeah!

> - lots of messages are shooting in the tty session (sample below).
[...]

Now only two messages are being generated ...


g1@g1 ~$ emacs
process 27189: D-Bus library appears to be incorrectly
set up; failed to read machine uuid: Failed to open "/etc/machine-id":
No such file or directory See the manual page for dbus-uuidgen to
correct this issue.

** (emacs-25-3:27189): WARNING **: Error retrieving accessibility bus
address: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.a11y.Bus was not provided by any .service files


Attempting to follow the instructions in the first message, I installed
dbus, but I don't see any dbus-uuidgen man page, or any other dbus man
pages.

The second message is referenced in bug#28088 ...

Subject: bug#28088: "The name org.a11y.Bus was not provided by any
.service files" with multiple applications

The messages seem harmless. Perhaps the bug should be downgraded?

Current config:



sys.scm
Description: Binary data


g1-emacs-dbus.scm
Description: Binary data

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

[myglc2]

On 11/11/2017 at 15:38 Ludovic Courtès writes:

> Hi,
>
> myglc2 <myg...@gmail.com> skribis:
>
>> 
>> Testsuite summary for GNU Guix 0.13.0.4589-74bea6
>> 
>> # TOTAL: 745
>> # PASS:  731
>> # SKIP:  10
>> # XFAIL: 0
>> # FAIL:  4
>> # XPASS: 0
>> # ERROR: 0
>> 
>
> I believe this is fixed by commits
> 4ad3a3f995dc9bd00edbe37eb773bf07d1ad14c0 and
> ae0307f7c2a6f382311a1cedcbbb3d35b6623bab.
>
> Can you check whether it works for you?
>
> Your test ‘test-suite.log’ file shows another failure in
> tests/guix-register.sh:
>
>   + sqlite3 /home/g1/src/guix/t-register-14509/var/guix/db/db.sqlite
>   Error: near line 1: database is locked
>
> I believe this one is due to too many parallel accesses stemming from
> “make -j10”, and can be worked around by using less parallelism (or
> doing “make recheck” if it fails anyway.)
>
> Thanks,
> Ludo’.

Thanks, that fixed it here. I'll let you close the bug. - George

bug#29072: The usability of Guix configurations

[myglc2]

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 system configuration had become broken
>> ;-(
>> 
>> Confronted with my situation, helpful developers said "The package code
>> was moved in commit xxx" (Leo) and "maybe you have a mistake in your
>> config (Efraim)."
>
> I'm sorry that my comment was not enough on its own!
>
>> Once I understood what had happened I wondered, "Gee, I have been using
>> guix for 18 months so why didn't I figure this out myself." ;-)
>> 
>> But a less committed user might say, "Wow, Guix breaks at random, error
>> messages are hard to understand, and support is difficult."  :-(
>
> Good point.
>
>> ISTM this raises issues and questions about Guix configuration
>> usability:
>
> Indeed.
>
>> Guix config errors are reported as raw scheme errors which are not
>> user-friendly, except, perhaps, to guile users ;-) Could we improve this
>> situation by adding config troubleshooting guidance to the doc?
>
> Yes, we do try to add helpful error messages, although obviously there
> is a lot more work to be done.
[...]
>
>> Guix config errors consume meaningful amounts of user and support
>> effort. I say this because a) it took quite a few iterations to figure
>> out what was wrong in my situation, and b) google search for '"no code
>> for module" guix' finds 613 hits, which will no doubt grow linearly with
>> number of Guix users unless something is done. So I wonder, could an
>> error handler that translates into more user-friendly terms reduce user
>> frustration, increase the rate of user self help, reduce support load,
>> and effectively pay for itself?
>
> That would be awesome!
>
>> Are the current Guix config errors usable by the average GNU/Linux
>> distribution user? If not, don't they need to be improved before we call
>> it 1.0?
>
> Based on how much time it's possible to spend on IRC helping people, I'd
> say there is lots of room for improvement in this area.
>
>> Does this mean that package code must not be moved after 1.0?
>
> A couple thoughts... it would be nice if the GuixSD configuration
> example templates used a filename agnostic method of resolving module
> imports. I'm not a strong enough Schemer to evaluate the situation or
> suggest a solution, but I think that the filenames should not be
> relevant at that level. Perhaps one could use
> 'specification->package+output',
> as demonstrated in the documentation of package manifests:
>
> https://www.gnu.org/software/guix/manual/html_node/Invoking-guix-package.html
>
There is a parallel solution 
>> Finally: Should I close bug#29072? ;-)
>
> The problem of the missing QEMU patch is resolved. The broader issue of
> confusing error messages could be continued here, or elsewhere. It's up
> to you :)

bug#29072: The usability of Guix configurations

[myglc2]

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
>> user-friendly, except, perhaps, to guile users ;-) Could we improve this
>> situation by adding config troubleshooting guidance to the doc?
>
> Yes, we do try to add helpful error messages, although obviously there
> is a lot more work to be done.

I didn't mean this point critically. Rather as a statement of fact. When
I said ...

>> Could we improve this situation by adding config troubleshooting
>> guidance to the doc?

... I was thinking something like ...

vv

Troubleshooting your config file:

If you get an error like:

ice-9/boot-9.scm:[...] no code for module (gnu packages )

You have either specified a package name that does not exist, or your
(use-package-modules ) does not contain the name
of a package module that contains the definition of .

You can determine which, if any, module contains a package definition by
yada yada yada

^^

... thinking that then there would be a search hit in the doc for 'no
code for module' which might enable some users to understand what they
are doing wrong.

WDYT? - George

bug#29072: The usability of Guix configurations

[myglc2]

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 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 commit xxx" (Leo) and "maybe you have a mistake in your
>> config (Efraim)."
>
> I'm sorry that my comment was not enough on its own!

Hey Leo,

Please understand that don't mean this as a complaint your reply, which
was helpful and I was very happy to receive.

I am just trying to step back and think about the bigger picture.

bug#29072: The usability of Guix configurations

[myglc2]

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 commit xxx" (Leo) and "maybe you have a mistake in your
config (Efraim)."

Once I understood what had happened I wondered, "Gee, I have been using
guix for 18 months so why didn't I figure this out myself." ;-)

But a less committed user might say, "Wow, Guix breaks at random, error
messages are hard to understand, and support is difficult."  :-(

ISTM this raises issues and questions about Guix configuration
usability:

Guix config errors are reported as raw scheme errors which are not
user-friendly, except, perhaps, to guile users ;-) Could we improve this
situation by adding config troubleshooting guidance to the doc?

Guix config errors consume meaningful amounts of user and support
effort. I say this because a) it took quite a few iterations to figure
out what was wrong in my situation, and b) google search for '"no code
for module" guix' finds 613 hits, which will no doubt grow linearly with
number of Guix users unless something is done. So I wonder, could an
error handler that translates into more user-friendly terms reduce user
frustration, increase the rate of user self help, reduce support load,
and effectively pay for itself?

Are the current Guix config errors usable by the average GNU/Linux
distribution user? If not, don't they need to be improved before we call
it 1.0?

Does this mean that package code must not be moved after 1.0?

Finally: Should I close bug#29072? ;-)

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

[myglc2]

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 Famulari writes:
>> >> 
[...]
>> > The 'gnu/packages/qemu.scm' file was removed from Guix in July 2017,
>> > with commit 59132b800093e486e4d81aed6b837e9ac76aa86c. The QEMU packages
>> > were moved into 'gnu/packages/virtualization.scm'.
>> >
[...]
>> 
>> root@g1 ~/con/15# guix system --cores=4 --max-jobs=4 -K --on-error=debug 
>> build sys.scm
>> guix system: error: failed to load 'sys.scm':
>> ice-9/boot-9.scm:2795:6: In procedure resolve-interface:
>> ice-9/boot-9.scm:2795:6: no code for module (gnu packages qemu)
>> 
>
> Can you post your sys.scm? It sounds like you might have a references to
> (gnu packages qemu) listed there.

Yes Efraim, that was it. Actually, Leo mentioned that qemu had moved
(above) but I failed to realize the implication for the config file.

Many thanks! - George

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

[myglc2]

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 matches 
>> >
>> > Try deleting this compiled qemu.go and then try again.
>> 
>> Thank you Leo.
>> 
>> I deleted ./gnu/packages/qemu.go and re-ran make.
>> 
>> Make failed to regenerate ./gnu/packages/qemu.go
>> 
>> So now I am really confused.
>
> The 'gnu/packages/qemu.scm' file was removed from Guix in July 2017,
> with commit 59132b800093e486e4d81aed6b837e9ac76aa86c. The QEMU packages
> were moved into 'gnu/packages/virtualization.scm'.
>
> I'm not an Autotools expert, but in cases like this I usually try `make
> clean && ./configure --localstatedir=/var && make`. Did you try
> something like that yet?

Thanks Leo.

I did a new git pull and a clean build as you suggested (please see the
grep of the make.log below for details)

Now when I try 'guix system build sys.scm I get ...

guix system: error: failed to load 'sys.scm':
ice-9/boot-9.scm:2795:6: In procedure resolve-interface:
ice-9/boot-9.scm:2795:6: no code for module (gnu packages qemu)

... please see details further below. Obviously something is calling
'gnu/packages/qemu.scm' but I don't understand what.

TIA - George

make.log

g1@g1 ~/src/guix$ grep g1@g1 make.log 
g1@g1 ~/src/guix$ guix environment -e "(@ (gnu packages package-management) 
guix)" -M 4 -c 4
g1@g1 ~/src/guix [env]$ git fetch
g1@g1 ~/src/guix [env]$ git pull
g1@g1 ~/src/guix [env]$ git status
g1@g1 ~/src/guix [env]$ rm -fr /home/g1/.cache/guile/ccache/*
g1@g1 ~/src/guix [env]$ make clean-go
g1@g1 ~/src/guix [env]$ ./bootstrap
g1@g1 ~/src/guix [env]$ ./configure --localstatedir=/var
g1@g1 ~/src/guix [env]$ make -j 10 check
g1@g1 ~/src/guix [env]$ ln -f -s -T ~/src/guix/ ~/.config/guix/latest
g1@g1 ~/src/guix [env]$ sudo ln -f -s -T ~/src/guix/ /root/.config/guix/latest
g1@g1 ~/src/guix [env]$ git status
g1@g1 ~/src/guix [env]$ git remote -vv
g1@g1 ~/src/guix [env]$ git branch -av | grep \*
g1@g1 ~/src/guix [env]$ exit
g1@g1 ~/src/guix$ exit
g1@g1 ~/src/guix$


root@g1 ~/con/15# guix system --cores=4 --max-jobs=4 -K --on-error=debug build 
sys.scm
guix system: error: failed to load 'sys.scm':
ice-9/boot-9.scm:2795:6: In procedure resolve-interface:
ice-9/boot-9.scm:2795:6: no code for module (gnu packages qemu)

entering debugger; type ',bt' for a backtrace
GNU Guile 2.2.2
Copyright (C) 1995-2017 Free Software Foundation, Inc.

Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.

Enter `,help' for help.
scheme@(#{ g440}#)> ,q
root@g1 ~/con/15# which guix
/run/current-system/profile/bin/guix
root@g1 ~/con/15# stat ~/.config/guix/latest | grep File:
  File: /root/.config/guix/latest -> /home/g1/src/guix/
root@g1 ~/con/15# 
root@g1 ~/con/15# git -C ~/.config/guix/latest status
On branch o-master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working tree clean
root@g1 ~/con/15# git -C ~/.config/guix/latest remote -vv
origin  git://git.savannah.gnu.org/guix.git (fetch)
origin  git://git.savannah.gnu.org/guix.git (push)
root@g1 ~/con/15# git -C ~/.config/guix/latest log -n 1 --oneline
46dea1241 (HEAD -> o-master, origin/master, origin/HEAD) gnu: icedtea: Update 
to 3.6.0 [security fixes].
root@g1 ~/con/15# exit
exit

Process shell finished

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

[myglc2]

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
>> guix system: error: qemu-CVE-2017-7493.patch: patch not found
>
> What about `git status`? Is the worktree in a consistent state? This
> patch file was removed in August 2017 [0] and nothing should refer to it
> anymore.
>
> [0] commit 2de7d137b3c6f528acb540a6ab3460627f484b0a

Thanks Leo.

git status is clean ...

g1@g1 ~/src/guix$ git status
On branch o-master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working tree clean
g1@g1 ~/src/guix$ git remote -vv
origin  git://git.savannah.gnu.org/guix.git (fetch)
origin  git://git.savannah.gnu.org/guix.git (push)
g1@g1 ~/src/guix$ 

emacs 'M-x grep find qemu-CVE-2017-7493.patch' produces ...

***
-*- mode: grep; default-directory: "~/src/guix/" -*- 
Grep started at Wed Nov  1 10:25:46  
 
find . -type f -exec grep --color -nH -e qemu-CVE-2017-74
Binary file ./gnu/packages/qemu.go matches   
./test-tmp/store/.links/0m1wjb06m31vw9jpimbmqkwxh1fzgyxag
./test-tmp/store/.links/0zk12m0jwp2n2380pq9x56mx71ry1dv42
./test-tmp/store/.links/0vrz62alwffjah2rj33wrwj7ypzbkv0pm
./test-tmp/store/.links/0xlcs15frjqbnhmcp2pv1ly9by84ncafn
./test-tmp/store/.links/00fiw7380k24qcq3k6pqgkz6j0c1l6ibw
./test-tmp/store/.links/066d4qpkxrf8p5vgay3x9bwn3zhzxp3gh
./test-tmp/store/.links/1z89050j89mz33c97b9bhvrb2h8972qyg
./test-tmp/store/.links/0cwv31pb892219rqgnmxzb950kd82b3mz
./test-tmp/store/.links/0bz2735f2x9f624yzmi6i3bryxsgn0qq7
./test-tmp/store/.links/0mvrdlqf3y989djjghinvsvsa80h250xm
./test-tmp/store/h5nhfi9941i4bh02s3sijgzqcxcswxrx-qemu-2.
./test-tmp/store/44p8aj7gqd97126gsw82anvhbbq2h080-qemu-2.
./test-tmp/store/0dkhz940aq4h1s6wg2lflhxswrpw93gs-qemu-2.
./test-tmp/store/xdmnickhpv89q568jhgrlkixnc873dx9-qemu-2.
./test-tmp/store/apspl851a4lv6fn94wcgwmvlmfn3m24l-qemu-2.
./test-tmp/store/zbiwif5nw7074bwbrzv3b93mybrbqjqc-qemu-2.
./test-tmp/store/i8h6n9p0rvl1ra3s1k1pz9q7z1rnqnyc-qemu-2.
./test-tmp/store/saq5a28g1c6gybnfdd3v1lilkil7kvjf-qemu-2.
./test-tmp/store/i9g8mrrzmbyfa4k5ra3alw69jw3bynz0-qemu-2.
./test-tmp/store/0jd1jrsm3387vl7yncr6988zw7a969a3-qemu-2.
Binary file ./test-tmp/db/db.sqlite matches  
 
Grep exited abnormally with code 1 at Wed Nov  1 10:25:49
***

In an attempt at self-help, I deleting ./test-tmp/*

But I am still getting this error.

TIA - George

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

[myglc2]

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-1f6f4
Copyright (C) 2017 the Guix authors
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

root@g1 ~/con/15# stat ~/.config/guix/latest | grep File:
  File: /root/.config/guix/latest -> /home/g1/src/guix/

root@g1 ~/con/15# git -C ~/.config/guix/latest describe
v0.13.0-4202-g1f6f4c40c

root@g1 ~/con/15# git -C ~/.config/guix/latest log -n 1 --oneline
1f6f4c40c (HEAD -> o-master, origin/master, origin/HEAD) gnu: Add r-tgconfig.

root@g1 ~/con/15# git -C /home/g1/src/guix branch -av | grep '*'
* o-master1f6f4c40c gnu: Add r-tgconfig.

SYS CONFIG:



sys.scm
Description: Binary data

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

[myglc2]

On 05/30/2017 at 17:45 Ludovic Courtès writes:

> Hi myglc2,
>
> myglc2 <myg...@gmail.com> 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
>> switched from generation 2 to 1
>> guix package: warning: Your Guix installation is 13 days old.
>> guix package: warning: Consider running 'guix pull' followed by
>> 'guix package -u' to get up-to-date packages and security updates.
>>
>> ++ readlink_base t-profile-21734
>> +++ readlink t-profile-21734
>> ++ basename t-profile-21734-1-link
>> + test t-profile-21734-1-link = t-profile-21734-1-link
>> ++ seq 1 3
>> + for i in `seq 1 3`
>> + guix package --bootstrap --roll-back -p t-profile-21734
>> accepted connection from pid 30827, user g1
>> guix package: error: profile 't-profile-21734' does not exist
>
> Could it be that a concurrent process removed ‘t-profile-21734’ behind
> our back?

I have no idea! This time I did ...

make -j check

... but I often do ...

make -j 10 check

... so I repeated ...

make -j 10 check

... a few times thinking maybe another test could delete the link, but
could not reproduce the error. BTW, from each 'make check' I do end up
with a dangling link like ...

t-profile-alt-10987-1-link ->
/home/g1/src/guix/test-tmp/store/hwr4xiqd60wrh033wvjljly50j6d39dg-profile

... is this normal?

> As you can see, that symlink was available just above.
> Or is it 100% reproducible when running
>
>   make check TESTS=tests/guix-package-net.sh
>
> ?

It is not reproducible ... except by deleting the profile while the test is
running ;-)

HTH - George

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

[myglc2]

'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
[...]

Testsuite summary for GNU Guix 0.12.0.3894-6f543

# TOTAL: 710
# PASS:  701
# SKIP:  8
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to bug-guix@gnu.org

make[4]: *** [Makefile:4416: test-suite.log] Error 1
make[4]: Leaving directory '/home/g1/src/guix'
make[3]: *** [Makefile:4524: check-TESTS] Error 2
make[3]: Leaving directory '/home/g1/src/guix'
make[2]: *** [Makefile:4764: check-am] Error 2
make[2]: Leaving directory '/home/g1/src/guix'
make[1]: *** [Makefile:4301: check-recursive] Error 1
make[1]: Leaving directory '/home/g1/src/guix'
make: *** [Makefile:4766: check] Error 2
g1@g1 ~/src/guix [env]$ exit

Commit:
===
g1@g1 ~/src/guix$ git -C ~/.config/guix/latest describe
v0.13.0-323-g98b9732cb
g1@g1 ~/src/guix$ stat ~/.config/guix/latest | grep File:
  File: /home/g1/.config/guix/latest -> /home/g1/src/guix/
g1@g1 ~/src/guix$

./test-suite.log



test-suite.log.gz
Description: Binary data

bug#25852: Users not updating their installations of Guix

[myglc2]

On 05/12/2017 at 10:29 Ludovic Courtès writes:

> Ricardo Wurmus <rek...@elephly.net> skribis:
>
>> Ludovic Courtès <l...@gnu.org> writes:
>>
>>> myglc2 <myg...@gmail.com> skribis:
>>>
>>>> How about extending this ...
>>>>
>>>>> +  (warning (G_ "Your Guix installation is getting old.  Consider
>>>>> +running 'guix pull' followed by '~a' to get up-to-date
>>>>> +packages and security updates.\n")
>>>>
>>>> ... to inform the user how old the installation is?
>>>
>>> Good idea.  I did that and pushed as
>>> 7fd952e05203d975fcb6cdabd2f742ade1b31b66.
>>
>> Does this do the right thing when .config/guix/latest points at a git
>> checkout?
>
> No it doesn’t, but I would argue that it unsupported.  ;-)
>
>> The mtime of the “.config/guix/latest” link on one of my machines is
>> from 2016, so Guix says it is too old, but it points to a git
>> checkout, which is recent.
>
> I would suggest:
>
>   export GUIX_DISTRO_AGE_WARNING=1000m
>
> as a workaround.  WDYT?

This alters guix's stock behavior if/when one switches back to using
'guix pull'. Maybe a better thing to do is the following each time you
update guix from a git checkout ...

ln -f -s -T ~/src/guix/ ~/.config/guix/latest
sudo ln -f -s -T ~/src/guix/ /root/.config/guix/latest

bug#25852: Users not updating their installations of Guix

[myglc2]

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 after N hours it's
 likely to be stale.  The default value of N might be in the range 48-96
 (2-4 days).  A quick perusal through the recent commit log on our master
 branch indicates that it's quite rare for 4 days to pass without a
 security update.

 What do you think?
>>>
>>> That sounds like an easy and reasonable approach.
>>>
>>> I wonder what would be the best place to emit this warning.  Upon ‘guix
>>> package -i’ maybe?
>>
>> Also "guix package -u" and the "guix system" commands that build
>> systems.  I suspect that many users run "guix pull" as their normal
>> users but never think to run it as root.
>
> If there are no objections, I’ll push the attached patch.  It sets a
> default value of 7 days (which I think is already more aggressive that
> what many are doing), which can be overridden with
> GUIX_DISTRO_AGE_WARNING.
>
> Ludo’.

How about extending this ... 

> +  (warning (G_ "Your Guix installation is getting old.  Consider
> +running 'guix pull' followed by '~a' to get up-to-date
> +packages and security updates.\n")

... to inform the user how old the installation is?

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

[myglc2]

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,   0 stopped,   0 zombie
%Cpu0  :   0.0/0.1 0[   
   ]
%Cpu1  :   0.1/2.9 3[|| 
   ]
%Cpu2  :   0.2/4.0 4[|||
   ]
%Cpu3  :   0.3/4.9 5[|||
   ]
%Cpu4  :   0.2/0.1 0[   
   ]
%Cpu5  :   0.2/4.6 5[|||
   ]
%Cpu6  :   0.2/4.3 5[|||
   ]
%Cpu7  :   0.3/4.1 4[|||
   ]
GiB Mem :  6.5/15.610   [   
   ]
GiB Swap:  0.0/9.649[   
   ]

  PID USER  PR  NIVIRTRES  %CPU %MEM TIME+ S COMMAND
  384 root  20   06.2m   0.3m  40.0  0.0   2386:36 S mingetty
7 root  20   00.0m   0.0m   6.7  0.0   2:20.86 S rcu_sched
 4154 g120   0  300.3m 135.1m   6.7  0.8   3:37.67 S emacs
 7431 root  20   00.0m   0.0m   6.7  0.0   0:26.07 S kworker/u16:2
 7539 root  20   00.0m   0.0m   6.7  0.0   0:06.54 S kworker/u16:0
1 root  20   0  130.1m  27.9m   0.0  0.2   0:03.22 S shepherd

If I plug in a console display, I see the login prompt is being rapidly
printed over and over. If I hit the console return key the printing
stops and mingetty stops using CPU.

I am running a relatively recent GuixSD built from git checkout ...

g1@g1 ~$ guix --version
guix (GNU Guix) 0.12.0
g1@g1 ~$ stat ~/.config/guix/latest | grep File:
  File: /home/g1/.config/guix/latest -> /home/g1/src/guix/
g1@g1 ~$ git -C ~/.config/guix/latest describe
v0.12.0-3191-g25a49294c
g1@g1 ~$ git -C ~/.config/guix/latest log -n 1 --oneline
25a49294c cache: Work around 'time-monotonic' bug in Guile 2.2.2.

Here is the system config:



sys.scm
Description: Binary data

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

[myglc2]

On 04/05/2017 at 19:31 Marius Bakke writes:

> Leo Famulari <l...@famulari.name> 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
>>>   HOSTLD  scripts/genksyms/genksyms
>>>   CC  arch/x86/purgatory/purgatory.o
>>>   AS  arch/x86/purgatory/stack.o
>>>   AS  arch/x86/purgatory/setup-x86_64.o
>>>   CC  arch/x86/purgatory/sha256.o
>>>   AS  arch/x86/purgatory/entry64.o
>>>   CC  arch/x86/purgatory/string.o
>>>   HOSTLD  scripts/mod/modpost
>>>   LD  arch/x86/purgatory/purgatory.ro
>>>   BIN2C   arch/x86/purgatory/kexec-purgatory.c
>>>   CHK include/generated/timeconst.h
>>>   CC  kernel/bounds.s
>>>   CHK include/generated/bounds.h
>>>   UPD include/generated/bounds.h
>>
>> The latest versions of linux-libre (4.10.8, 4.9.20, 4.4.59) are all
>> hanging around this point. However, they did build in the past:
>>
>> https://hydra.gnu.org/job/gnu/master/linux-libre-4.4.59.x86_64-linux
>> https://hydra.gnu.org/job/gnu/master/linux-libre-4.9.20.x86_64-linux
>> https://hydra.gnu.org/job/gnu/master/linux-libre-4.10.8.x86_64-linux
>>
>> And 4.10.7 hangs in the same way, so I think the issue is in an
>> unrelated change.
>
> Reverting dfee7daedb760f1b1d7506829ca31633f4173356 "gnu: bc: Update to
> 1.07" makes the build proceed.

Thanks Marius, that worked here too. Should I close the bug? - George

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

[myglc2]

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.'  _but_ shows an embedded
> error ...
>
> ERROR: Wrong type (expecting string): ("/dev/sdb1" "/dev/sdc1")
>
> ... and the system does not boot.
>
> This is really 2 bugs
>
> 1) a problem w/the RAID mechanism and/or my config
>
> 2) reconfigure should not complete when shepherd produces errors
>
> version info:
>
> guix (GNU Guix) 0.11.0
> root@g1 ~#   File: '/root/.config/guix/latest' -> '/home/g1/src/guix'
> root@g1 ~# v0.10.0-2118-g1061862
> root@g1 ~# 1061862 mapped-devices: raid-device-mapping: Avoid non-top-level 
> 'use-modules'.
> root@g1 ~# root@g1 ~# 
>
> reconfigure:
>
> root@g1 ~# guix system reconfigure system40.scm
> /gnu/store/nn051a04gas6x3g6xhbi8x0ca38akbzk-system
> /gnu/store/dsq79n5a8p21ca7zc38yzxzi9hk0mhzp-grub.cfg
> /gnu/store/zgm8s5z5y9dh0g36jqxh5i30js93irk5-grub-2.02beta3
> activating system...
> setting up setuid programs in '/run/setuid-programs'...
> populating /etc from /gnu/store/3vbg3i84k9z57kj5xwz91h08b59mh9yb-etc...
> usermod: no changes
> usermod: no changes
> usermod: no changes
> making '/gnu/store/nn051a04gas6x3g6xhbi8x0ca38akbzk-system' the current 
> system...
> guix system: unloading service 'device-mapping-/dev/md0'...
> shepherd: Removing service 'device-mapping-/dev/md0'...
> shepherd: Done.
> guix system: unloading service 'file-system-/mnt/md0'...
> shepherd: Removing service 'file-system-/mnt/md0'...
> shepherd: Done.
> guix system: loading new services: device-mapping-/dev/md0 
> file-system-/mnt/md0...
> shepherd: Evaluating user expression (register-services (primitive-load 
> "/gn...") #).
> guix system: error: exception caught while executing 'start' on service 
> 'device-mapping-/dev/md0':
> ERROR: Wrong type (expecting string): ("/dev/sdb1" "/dev/sdc1")
> Installing for i386-pc platform.
> Installation finished. No error reported.
>
> config and shepherd log attached.
>
> TIA - George

This is fixed AFAICT

FWIW, the comment in the code at mapped-devices.scm ...

  (sourcemapped-device-source);string

... is not current with the doc, which says ...

 ‘source’
  This is either a string specifying the name of the block
  device to be mapped, such as ‘"/dev/sda3"’, or a list of such
  strings when several devices need to be assembled for creating
  a new one.

bug#23072: GuixSD SSD install hangs at clocksource

[myglc2]

On 01/11/2017 at 23:31 Ludovic Courtès writes:

> myglc2 <myg...@gmail.com> skribis:
>
>> Florian Paul Schmidt <mista.ta...@gmx.net> 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 & mouse drivers, then hangs
>>>>   showing:
>>>> 
>>>>   "clocksource: Switched to clocksource tsc"
>>>
>>> This is just a shot in the dark, but I use SSD systems, too, and I
>>> noticed that the first boot of a guixsd installation hangs for a while
>>> collecting entropy before displaying a corresponding message IIRC and I
>>> faintly remember the "switching to clocksource" message. Did you try
>>> banging the keyboard? Maybe that's not possible on a headless server
>>> though. Did you let it sit for a while?
>>>
>>> Flo
>> Thanks Flo. Can't test that theory at the moment.  But I do have a
>> display attached (which is how I saw the "clocksource..." message).
>>
>> FWIW, in the HD install there is a prompt for keyboard input. It seems
>> like the SSD install hung before it reached that.  - George
>
> Any update on this bug?
>
>   http://bugs.gnu.org/23072
>
> Ludo’.

Hi Ludo,

I did experiments and I now see that this happens when the boot drive ID
has changed from what was specified as the grub-configuration device in
the most recent 'system init' or 'system reconfigure' operation.

This can happen, for example, when one moves drives around or when one
inserts a new drive in an empty lower SATA slot below drives holding
GuixSD.

This seemed like a bug to me because the doc says ...

   • Make sure the ‘grub-configuration’ form refers to the device you
 want to install GRUB on.

... but there is no mention that it affects boot operation.

Also I assumed, possibly wrongly, that GuixSD does not need the config
to tell it which device grub is on at boot because it is already running
on the boot device ;-)

So, I don't know ... Is this a bug or is this expected behavior.

If it is not a bug it seems like an opportunity to reduce the fragility
of GuixSD configurations.

HTH - George

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

[myglc2]

On 01/15/2017 at 20:19 Ludovic Courtès writes:

> myglc2 <myg...@gmail.com> skribis:
>
>> On 01/14/2017 at 14:44 Ludovic Courtès writes:
>>
>>> Hi,
>>>
>>> myglc2 <myg...@gmail.com> skribis:
>>>
>>>> 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'...
>>>> In execvp of /usr/local/sbin/guix-register: No such file or directory
>>>
>>> The crux of the problem is this last line.  It looks like the Guix
>>> installation is broken here.
>>>
>>> Could you check what happened to this ‘guix-register’ command?
>>
>> Thanks. I did a fresh guix pull and looked for guix-register. I couldn't
>> find it my PATH or in guix-latest. But I did find it in the globally
>> installed guix package.
>>
>> Then, just to be sure things hadn't magically fixed themselves, I reproduced
>> the crime ;-)
>
> [...]
>
>> copying '/gnu/store/1k2swlkbpf44d5fzgvrp5znafhw90xh7-grub-image.png'...
>> In execvp of /usr/local/sbin/guix-register: No such file or directory
>> guix system: error: failed to register 
>> '/gnu/store/1k2swlkbpf44d5fzgvrp5znafhw90xh7-grub-image.png' under '/mnt/md0'
>
> The problem is that somehow Guix is configured to look for
> /usr/local/sbin/guix-register (this location comes from
> guix/config.scm), but that file doesn’t exist.
>
> So you need to make /usr/local/sbin/guix-register a symlink to the right
> thing, or somehow fix the installation.

I was running guix built from Git checkout w/ clean working tree so I
don't know how my system got out of whack. The symlink approach worked
and the new system on new disks has ...

which guix-register
/run/current-system/profile/sbin/guix-register

... YEAH!! Happy camper George ;-)

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

[myglc2]

On 01/14/2017 at 14:44 Ludovic Courtès writes:

> Hi,
>
> myglc2 <myg...@gmail.com> skribis:
>
>> 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'...
>> In execvp of /usr/local/sbin/guix-register: No such file or directory
>
> The crux of the problem is this last line.  It looks like the Guix
> installation is broken here.
>
> Could you check what happened to this ‘guix-register’ command?

Thanks. I did a fresh guix pull and looked for guix-register. I couldn't
find it my PATH or in guix-latest. But I did find it in the globally
installed guix package.

Then, just to be sure things hadn't magically fixed themselves, I reproduced
the crime ;-)

HTH - George


LOOKING FOR guix-register

root@g1 ~# guix pull

Starting download of /tmp/guix-file.wg2stp
>From http://git.savannah.gnu.org/cgit/guix.git/snapshot/master.tar.gz...
 ….tar.gz   2.1MiB/s 00:05 | 10.8MiB transferred
unpacking '/gnu/store/j6c3hhijcn5q5yqydvz35y681ch5q7gb-guix-latest.tar.gz'...
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 
100.0%
The following derivation will be built:
   /gnu/store/nkay6hkzh2lz766v1fr3gcmjp0d0qkyj-guix-latest.drv
building path(s) `/gnu/store/7xl24l9hl73lyr35ff31wprjlfhylm7g-guix-latest'
copying and compiling to 
'/gnu/store/7xl24l9hl73lyr35ff31wprjlfhylm7g-guix-latest'...
loading...   24.0% of 567 filesrandom seed for tests: 1484413770
loading...   99.8% of 567 files
compiling... 98.8% of 567 files
updated GNU Guix successfully deployed under `/root/.config/guix/latest'

root@g1 ~# find . -name "guix-register"

root@g1 ~# stat ~/.config/guix/latest | grep File:
  File: '/root/.config/guix/latest' -> 
'/gnu/store/7xl24l9hl73lyr35ff31wprjlfhylm7g-guix-latest'

root@g1 ~# find /gnu/store/7xl24l9hl73lyr35ff31wprjlfhylm7g-guix-latest -name 
"guix-register"

root@g1 ~# echo $PATH
/home/g1/bin:/home/g1/bin:/root/.guix-profile/bin:/run/setuid-programs:/run/current-system/profile/bin:/run/current-system/profile/sbin

root@g1 ~# guix package -I

root@g1 ~# guix package --list-installed --profile=/run/current-system/profile 
| grep guix
emacs-guix  0.2.2   out 
/gnu/store/bqyhm280m61xwsbcy70jzmadwz19zgvb-emacs-guix-0.2.2
guix0.12.0-2.b291   out 
/gnu/store/53vamzdlzadg9x5zfpandzka87bsmkfh-guix-0.12.0-2.b291

root@g1 ~# find . 
/gnu/store/53vamzdlzadg9x5zfpandzka87bsmkfh-guix-0.12.0-2.b291 -name 
"guix-register"
/gnu/store/53vamzdlzadg9x5zfpandzka87bsmkfh-guix-0.12.0-2.b291/sbin/guix-register


REPRODUCING THE CRIME:

root@g1 ~# lsblk -f
NAMEFSTYPELABELUUID 
MOUNTPOINT
sdb 
├─sdb2  
├─sdb5  linux_raid_member g1:1 644cee85-566f-abce-84c5-5e6f9983c6f8 
│ └─md1 swap   448fd258-7d0e-45c3-b374-2a2f3be911e0 [SWAP]
├─sdb1  linux_raid_member g1:0 59340f87-fc27-638b-f1cd-42a9a6bdfad3 
│ └─md0 ext4  g1-root  415ba95b-7375-4f26-822c-d3d3e7a0f734 /mnt/md0
└─sdb6  linux_raid_member g1:2 1b0c8ab8-0dad-e743-e5c6-577fcd6419cd 
  └─md2 ext4  g1-bstg  02d1d054-fc65-4773-9597-890b56482b6a /mnt/md2
sdc 
├─sdc2  
├─sdc5  linux_raid_member g1:1 644cee85-566f-abce-84c5-5e6f9983c6f8 
│ └─md1 swap   448fd258-7d0e-45c3-b374-2a2f3be911e0 [SWAP]
├─sdc1  linux_raid_member g1:0 59340f87-fc27-638b-f1cd-42a9a6bdfad3 
│ └─md0 ext4  g1-root  415ba95b-7375-4f26-822c-d3d3e7a0f734 /mnt/md0
└─sdc6  linux_raid_member g1:2 1b0c8ab8-0dad-e743-e5c6-577fcd6419cd 
  └─md2 ext4  g1-bstg  02d1d054-fc65-4773-9597-890b56482b6a /mnt/md2
sda 
└─sda1  ext4  ssd-root ec3af1c3-2489-4400-acee-a57438b353d4 /

root@g1 ~# guix system init system/g1.00.scm /mnt/md0
guix system: error: failed to load 'system/g1.00.scm': No such file or directory
root@g1 ~# guix system init raid/bugs/25444/g1.00.scm /mnt/md0
/gnu/store/5p908dbxhy58qkrd972pvqyaxjm6yqx2-system
/gnu/store/0gsyrihzxi8zjx2vvkmhwhx9ypp2hdf0-grub.cfg
/gnu/store/b5sqah8g55sms20r98ladyiamwb0s1hy-grub-2.02beta3

initializing operating system under '/mnt/md0'...
copying '/gnu/store/1k2swlkbpf44d5fzgvrp5znafhw90xh7-grub-image.png'...
In execvp of /usr/local/sbin/guix-register: No such file or directory
guix system: error: failed to register 
'/gnu/store/1k2swlkbpf44d5fzgvrp5znafhw90xh7-grub-image.png' under '/mnt/md0'
root@g1 ~# 

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

[myglc2]

** 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'...
In execvp of /usr/local/sbin/guix-register: No such file or directory
guix system: error: failed to register 
'/gnu/store/0m0clxj69xrxb76kyh3ral8lkfb0vx8c-linux-libre-4.9.2' under '/mnt/md0'
[...]
guix system: error: failed to register 
'/gnu/store/1k2swlkbpf44d5fzgvrp5znafhw90xh7-grub-image.png' under '/mnt/md0'

Running Guix from git checkout and from guix pull produce similar errors.

Version info, logs, and config file are attached below.

** Running from git checkout:

*** Log

root@g1 /home/glc# lsblk -f
NAMEFSTYPELABELUUID 
MOUNTPOINT
sdb 
├─sdb2  
├─sdb5  linux_raid_member g1:1 644cee85-566f-abce-84c5-5e6f9983c6f8 
├─sdb1  linux_raid_member g1:0 59340f87-fc27-638b-f1cd-42a9a6bdfad3 
│ └─md0 ext4  g1-root  415ba95b-7375-4f26-822c-d3d3e7a0f734 /mnt/md0
└─sdb6  linux_raid_member g1:2 1b0c8ab8-0dad-e743-e5c6-577fcd6419cd 
  └─md2 ext4  g1-bstg  02d1d054-fc65-4773-9597-890b56482b6a /mnt/md2
sdc 
├─sdc2  
├─sdc5  linux_raid_member g1:1 644cee85-566f-abce-84c5-5e6f9983c6f8 
├─sdc1  linux_raid_member g1:0 59340f87-fc27-638b-f1cd-42a9a6bdfad3 
│ └─md0 ext4  g1-root  415ba95b-7375-4f26-822c-d3d3e7a0f734 /mnt/md0
└─sdc6  linux_raid_member g1:2 1b0c8ab8-0dad-e743-e5c6-577fcd6419cd 
  └─md2 ext4  g1-bstg  02d1d054-fc65-4773-9597-890b56482b6a /mnt/md2
sda 
└─sda1  ext4  ssd-root ec3af1c3-2489-4400-acee-a57438b353d4 /
root@g1 /home/glc# cd
root@g1 ~# guix system init system/g1.00.scm /mnt/md0
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 
100.0%
The following derivations will be built:
   /gnu/store/a9cpcsbqc0nj2r1qi8a8hzl7m6wnfn4d-system.drv
   /gnu/store/sgjyqs1nngzfra8j720lgpr7rhfrdbnj-grub.cfg.drv
   /gnu/store/rh0da4gw9hxskpn8zdxd4f20dd46mwrf-parameters.drv
   /gnu/store/v12bx159c461xy0yd7x5kra7hfb79f9a-shepherd-user-processes.scm.drv
   
/gnu/store/ddxwbsm2z82fz5ahy6an7mfx67ia9dfa-shepherd-user-file-systems.scm.drv
   
/gnu/store/6inqbx38yajns8dz06r8ij21y8j1gdyk-shepherd-device-mapping--dev-md1.scm.drv
   
/gnu/store/5wknmg4zf4kljwikbnhmwnb0aq6agcky-shepherd-device-mapping--dev-md2.scm.drv
   
/gnu/store/4l7p849pchaxfw628a95c08r2282gxxs-shepherd-file-system--mnt-bstg.scm.drv
   /gnu/store/syk6y0i21399lfnjwrvcffmk02xbph1h-shepherd.conf.drv
   /gnu/store/a9hmflqkh2nfns54xfjrwalnzzwzxfhw-activate-service.drv
   /gnu/store/7wvp80b2rdng391pdncdbc21lsw148fg-activate-service.drv
   /gnu/store/fbjknymwzdsf5pmsaqxmvn1hdvcinp1i-activate.drv
   /gnu/store/0rnp9pqyd7j2nd08hav57m3645brlmcv-boot.drv
   /gnu/store/hbhxxp5vfl0w63js2mrkpfy7zzg4pdly-etc.drv
   /gnu/store/a04l8ypqwakcv1cpqiq222clv032yk9a-init.drv
   /gnu/store/76649pq3r2sxjqcpghmp9sw31mhdzi5r-base-initrd.drv
[...]
/gnu/store/cb6nirh13zhnsrq85jh4xb6hh1i36vbh-system
/gnu/store/qbi85dpcnyg3vvpph8jsajfs4f0ahd0b-grub.cfg
/gnu/store/q0hvvcydv83hk104fimhj30asn291j9p-grub-2.02beta3

initializing operating system under '/mnt/md0'...
copying '/gnu/store/0m0clxj69xrxb76kyh3ral8lkfb0vx8c-linux-libre-4.9.2'...
In execvp of /usr/local/sbin/guix-register: No such file or directory
guix system: error: failed to register 
'/gnu/store/0m0clxj69xrxb76kyh3ral8lkfb0vx8c-linux-libre-4.9.2' under '/mnt/md0'
root@g1 ~# guix system build system/g1.00.scm
/gnu/store/cb6nirh13zhnsrq85jh4xb6hh1i36vbh-system
root@g1 ~# guix system init system/g1.00.scm
guix system: error: wrong number of arguments for action 'init'
root@g1 ~# guix system init system/g1.00.scm /mnt/md0
/gnu/store/cb6nirh13zhnsrq85jh4xb6hh1i36vbh-system
/gnu/store/qbi85dpcnyg3vvpph8jsajfs4f0ahd0b-grub.cfg
/gnu/store/q0hvvcydv83hk104fimhj30asn291j9p-grub-2.02beta3

initializing operating system under '/mnt/md0'...
copying '/gnu/store/0m0clxj69xrxb76kyh3ral8lkfb0vx8c-linux-libre-4.9.2'...
In execvp of /usr/local/sbin/guix-register: No such file or directory
guix system: error: failed to register 
'/gnu/store/0m0clxj69xrxb76kyh3ral8lkfb0vx8c-linux-libre-4.9.2' under '/mnt/md0'

*** Version

root@g1 ~# stat ~/.config/guix/latest | grep File:
  File: '/root/.config/guix/latest' -> '../../../home/g1/src/guix'
root@g1 ~# git -C ~/.config/guix/latest describe
v0.12.0-456-gb0a567640
root@g1 ~# guix --version
guix (GNU Guix) 0.12.0

** Running from guix pull

*** Log

root@g1 ~# guix system init system/g1.00.scm /mnt/md0

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

[myglc2]

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-device
   (source (list "/dev/sdb1" "/dev/sdc1"))
   (target "/dev/md0")
   (type raid-device-mapping)))
(define md1
  (mapped-device
   (source (list "/dev/sdb5" "/dev/sdc5"))
   (target "/dev/md1")
   (type raid-device-mapping)))
(define md2
  (mapped-device
   (source (list "/dev/sdb6" "/dev/sdc6"))
   (target "/dev/md2")
   (type raid-device-mapping)))
(operating-system
 (host-name "g1")
 (timezone "America/New_York")
 (locale "en_US.utf8")
 (bootloader (grub-configuration (device "/dev/sda")))
 (mapped-devices (list md0 md1 md2))
 ;; Add a kernel module for RAID-1.
 (initrd (lambda (file-systems . rest)
   (apply base-initrd file-systems
  #:extra-modules '("raid1")
  rest)))
 (file-systems (cons*
(file-system
 (device "ssd-root")
 (title 'label)
 (mount-point "/")
 (type "ext4"))
(file-system
 (title 'device)
 (device "/dev/md0")
 (dependencies (list md0))
 (mount-point "/mnt/md0")  
 (create-mount-point? #t)
 (type "ext4")
 )
(file-system
 (title 'device)
 (device "/dev/md2")
 (dependencies (list md2))
 (mount-point "/mnt/md2")  
 (create-mount-point? #t)
 (type "ext4")
 )
%base-file-systems))


guix version:

guix (GNU Guix) 0.12.0
v0.12.0-456-gb0a567640

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

[myglc2]

myglc2 <myg...@gmail.com> 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 the line above and thought
... maybe I should add ...

(use-modules (gnu build file-systems))

... to the config (system41.scm)

Unfortunately this didn't fix things but it did produce an interesting
result: 'guix system reconfigure system41.scm' hung but added new
generation. Hey! guix is not supposed to do that. I want my money back!!

Interestingly, when I set --verbosity=5, 'guix system ...' failed and
refrained from adding a new generation.

So, no fix, but maybe a wormhole to plug ;-)

Log attached.

system41.scm
Description: Binary data


system41.log
Description: Binary data

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

[myglc2]

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 bridge -net nic,model=virtio 
-enable-kvm -m 4096 -k en-us -display curses /home/g1/src/vmb/tmp/img6/vm.img
failed to parse default acl file 
`/gnu/store/1072khbm9124a8a1pyyyw4mr1p12jsfq-qemu-2.6.0/etc/qemu/bridge.conf'
qemu-system-x86_64: -net bridge: bridge helper failed

This error was produced with the attached 'img-tap' script. e.g., to
build the vm ...

./img-tap mk 1

To (attempt to) run the vm ..

./img-tap run 1


Running Guix built from git checkout on GuixSD:
stat ~/.config/guix/latest | grep File:
  File: '/home/g1/.config/guix/latest' -> '../../src/guix'
g1@g1 ~/src/vmb$ git -C ~/.config/guix/latest describe
v0.11.0-242-g7ccb874




img-tap
Description: Binary data

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

[myglc2]

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" "/dev/sdc1")

... and the system does not boot.

This is really 2 bugs

1) a problem w/the RAID mechanism and/or my config

2) reconfigure should not complete when shepherd produces errors

version info:

guix (GNU Guix) 0.11.0
root@g1 ~#   File: '/root/.config/guix/latest' -> '/home/g1/src/guix'
root@g1 ~# v0.10.0-2118-g1061862
root@g1 ~# 1061862 mapped-devices: raid-device-mapping: Avoid non-top-level 
'use-modules'.
root@g1 ~# root@g1 ~# 

reconfigure:

root@g1 ~# guix system reconfigure system40.scm
/gnu/store/nn051a04gas6x3g6xhbi8x0ca38akbzk-system
/gnu/store/dsq79n5a8p21ca7zc38yzxzi9hk0mhzp-grub.cfg
/gnu/store/zgm8s5z5y9dh0g36jqxh5i30js93irk5-grub-2.02beta3
activating system...
setting up setuid programs in '/run/setuid-programs'...
populating /etc from /gnu/store/3vbg3i84k9z57kj5xwz91h08b59mh9yb-etc...
usermod: no changes
usermod: no changes
usermod: no changes
making '/gnu/store/nn051a04gas6x3g6xhbi8x0ca38akbzk-system' the current 
system...
guix system: unloading service 'device-mapping-/dev/md0'...
shepherd: Removing service 'device-mapping-/dev/md0'...
shepherd: Done.
guix system: unloading service 'file-system-/mnt/md0'...
shepherd: Removing service 'file-system-/mnt/md0'...
shepherd: Done.
guix system: loading new services: device-mapping-/dev/md0 
file-system-/mnt/md0...
shepherd: Evaluating user expression (register-services (primitive-load 
"/gn...") #).
guix system: error: exception caught while executing 'start' on service 
'device-mapping-/dev/md0':
ERROR: Wrong type (expecting string): ("/dev/sdb1" "/dev/sdc1")
Installing for i386-pc platform.
Installation finished. No error reported.

config and shepherd log attached.

TIA - George



shepherd40.log
Description: Binary data


system40.scm
Description: Binary data

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

[myglc2]

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)
(apply base-initrd fs
   #:extra-modules '("raid1")
   #:mapped-devices '((mapped-device
   (source (list "/dev/sdb1" "/dev/sdc1"))
   (target "/dev/md0")
   (type raid-device-mapping))) 
  
   args)))
  (file-systems (cons (file-system
(device "ssd-root")
(title 'label)
(mount-point "/")
(type "ext4"))
  %base-file-systems))

In this config I was attempting to have the array assembled, but not
mounted after the boot. It did not look promissing that 'guix system
reconfigure system39.scm' did not assemble the array. Then as one might
expect, the resulting system boots but the array is not assembled.

After a couple helpful exchanges with Andreas on the devel list, I ended
up with system40.scm, attached, excerpt below:

(define md0
  (mapped-device
   (source (list "/dev/sdb1" "/dev/sdc1"))
   (target "/dev/md0")
   (type raid-device-mapping)))
(operating-system
  (host-name "g1")
  (timezone "America/New_York")
  (locale "en_US.utf8")
  (bootloader (grub-configuration (device "/dev/sda")))
  (mapped-devices (list md0))
  ;; Add a kernel module for RAID-1.
  (initrd (lambda (file-systems . rest)
(apply base-initrd file-systems
   #:extra-modules '("raid1")
   rest)))
  (file-systems (cons*
 (file-system
   (device "ssd-root")
   (title 'label)
   (mount-point "/")
   (type "ext4"))
 (file-system
   (title 'device)
   (device "/dev/md0")
   (dependencies (list md0))
   (mount-point "/mnt/md0")
   (create-mount-point? #t)
   (type "ext4"))
 %base-file-systems))


Here the intent is to have the array assembled and mounted after the
boot. It looked promissing when 'guix system reconfigure system40.scm'
assembled and mounted the array (see system40.log). But on reboot the
system hangs with the console showing:

[...] clocksource: Switched to clocksource tsc

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)
2016-08-01 18:15:13 
2016-08-01 18:15:13 Entering a new prompt.  Type `,bt' for a backtrace or `,q' 
to continue.
2016-08-01 18:15:13 GNU Guile 2.0.11
2016-08-01 18:15:13 Copyright (C) 1995-2014 Free Software Foundation, Inc.
2016-08-01 18:15:13 
2016-08-01 18:15:13 Guile comes with ABSOLUTELY NO WARRANTY; for details type 
`,show w'.
2016-08-01 18:15:13 This program is free software, and you are welcome to 
redistribute it
2016-08-01 18:15:13 under certain conditions; type `,show c' for details.
2016-08-01 18:15:13 
2016-08-01 18:15:13 Enter `,help' for help.

For this config, /var/log/messages (messages40.log) is also attached.

TIA - George




messages40.log
Description: Binary data


system40.log
Description: Binary data


system40.scm
Description: Binary data


system39.scm
Description: Binary data

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

[myglc2]

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")
  (timezone "America/New_York")
  (locale "en_US.utf8")
  (bootloader (grub-configuration (device "/dev/sda")))
  (initrd (lambda (fs . args)
(apply base-initrd fs
   #:extra-modules '("raid1")
   #:mapped-devices '((mapped-device
   (source (list "/dev/sdb1" "/dev/sdc1"))
   (target "/dev/md0")
   (type raid-device-mapping))) 
  
   args)))
  (file-systems (cons (file-system
(device "ssd-root")
(title 'label)
(mount-point "/")
(type "ext4"))
  %base-file-systems))

In this config I was attempting to have the array assembled, but not
mounted after the boot. It did not look promissing that 'guix system
reconfigure system39.scm' did not assemble the array. Then as one might
expect, the resulting system boots but the array is not assembled.

After a couple helpful exchanges with Andreas on the devel list, I ended
up with system40.scm, attached, excerpt below:

(define md0
  (mapped-device
   (source (list "/dev/sdb1" "/dev/sdc1"))
   (target "/dev/md0")
   (type raid-device-mapping)))
(operating-system
  (host-name "g1")
  (timezone "America/New_York")
  (locale "en_US.utf8")
  (bootloader (grub-configuration (device "/dev/sda")))
  (mapped-devices (list md0))
  ;; Add a kernel module for RAID-1.
  (initrd (lambda (file-systems . rest)
(apply base-initrd file-systems
   #:extra-modules '("raid1")
   rest)))
  (file-systems (cons*
 (file-system
   (device "ssd-root")
   (title 'label)
   (mount-point "/")
   (type "ext4"))
 (file-system
   (title 'device)
   (device "/dev/md0")
   (dependencies (list md0))
   (mount-point "/mnt/md0")
   (create-mount-point? #t)
   (type "ext4"))
 %base-file-systems))


Here the intent is to have the array assembled and mounted after the
boot. It looked promissing when 'guix system reconfigure system40.scm'
assembled and mounted the array (see system40.log). But on reboot the
system hangs with the console showing:

[...] clocksource: Switched to clocksource tsc

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)
2016-08-01 18:15:13 
2016-08-01 18:15:13 Entering a new prompt.  Type `,bt' for a backtrace or `,q' 
to continue.
2016-08-01 18:15:13 GNU Guile 2.0.11
2016-08-01 18:15:13 Copyright (C) 1995-2014 Free Software Foundation, Inc.
2016-08-01 18:15:13 
2016-08-01 18:15:13 Guile comes with ABSOLUTELY NO WARRANTY; for details type 
`,show w'.
2016-08-01 18:15:13 This program is free software, and you are welcome to 
redistribute it
2016-08-01 18:15:13 under certain conditions; type `,show c' for details.
2016-08-01 18:15:13 
2016-08-01 18:15:13 Enter `,help' for help.

For this config, /var/log/messages (messages40.log) is also attached.

TIA - George



messages40.log
Description: Binary data


system40.log
Description: Binary data


system40.scm
Description: Binary data


system39.scm
Description: Binary data

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

[myglc2]

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#23973: 'guix environment guix' fails with "Argument 1 out of range: 10"

[myglc2]

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 && make

Thank you!

myglc2 <myg...@gmail.com> writes:

> 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 compiled /home/g1/.config/guix/latest/guix/packages.go
> ;;; note: source file /home/g1/.config/guix/latest/guix/packages.scm
> ;;;   newer than compiled 
> /home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/guix/packages.scm.go
> ;;; note: source file /home/g1/.config/guix/latest/guix/gexp.scm
> ;;;   newer than compiled /home/g1/.config/guix/latest/guix/gexp.go
> ;;; note: source file /home/g1/.config/guix/latest/guix/gexp.scm
> ;;;   newer than compiled 
> /home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/guix/gexp.scm.go
> ;;; note: source file /home/g1/.config/guix/latest/guix/profiles.scm
> ;;;   newer than compiled /home/g1/.config/guix/latest/guix/profiles.go
> ;;; note: source file /home/g1/.config/guix/latest/guix/profiles.scm
> ;;;   newer than compiled 
> /home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/guix/profiles.scm.go
> ;;; note: source file 
> /home/g1/.config/guix/latest/gnu/system/linux-container.scm
> ;;;   newer than compiled 
> /home/g1/.config/guix/latest/gnu/system/linux-container.go
> ;;; note: source file /home/g1/.config/guix/latest/gnu/services.scm
> ;;;   newer than compiled /home/g1/.config/guix/latest/gnu/services.go
> ;;; note: source file /home/g1/.config/guix/latest/gnu/services.scm
> ;;;   newer than compiled 
> /home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/gnu/services.scm.go
> ;;; note: source file /home/g1/.config/guix/latest/guix/download.scm
> ;;;   newer than compiled /home/g1/.config/guix/latest/guix/download.go
> ;;; note: source file /home/g1/.config/guix/latest/guix/download.scm
> ;;;   newer than compiled 
> /home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/guix/download.scm.go
> ;;; note: source file /home/g1/.config/guix/latest/guix/git-download.scm
> ;;;   newer than compiled 
> /home/g1/.config/guix/latest/guix/git-download.go
> ;;; note: source file /home/g1/.config/guix/latest/guix/git-download.scm
> ;;;   newer than compiled 
> /home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/guix/git-download.scm.go
> Backtrace:
> In unknown file:
>?: 19 [primitive-load-path "gnu/packages/autotools" ...]
> In gnu/packages/autotools.scm:
>   24: 18 [#]
> In ice-9/boot-9.scm:
> 2951: 17 [define-module* (gnu packages autotools) #:filename ...]
> 2926: 16 [resolve-imports ((#) (#) (#) (#) ...)]
> 2864: 15 [resolve-interface (gnu packages bash) #:select ...]
> 2789: 14 [# autoload version #:key ensure)> # ...]
> 3065: 13 [try-module-autoload (gnu packages bash) #f]
> 2401: 12 [save-module-excursion # ice-9/boot-9.scm:3066:17 ()>]
> 3085: 11 [#]
> In unknown file:
>?: 10 [primitive-load-path "gnu/packages/bash" ...]
> In gnu/packages/bash.scm:
>   21: 9 [#]
> In ice-9/boot-9.scm:
> 2951: 8 [define-module* (gnu packages bash) #:filename ...]
> 2926: 7 [resolve-imports ((#) (#) (#) (#) ...)]
> 2864: 6 [resolve-interface (gnu packages readline) #:select ...]
> 2789: 5 [# autoload version #:key ensure)> # ...]
> 3065: 4 [try-module-autoload (gnu packages readline) #f]
> 2401: 3 [save-module-excursion # ice-9/boot-9.scm:3066:17 ()>]
> 3085: 2 [#]
> In unknown file:
>?: 1 [primitive-load-path "gnu/packages/readline" ...]
> In gnu/packages/readline.scm:
>   81: 0 [#]
>
> gnu/packages/readline.scm:81:12: In procedure #:
> gnu/packages/readline.scm:81:12: In procedure struct-ref: Argument 1 out of 
> range: 10
> g1@g1 ~/src/guix$ 

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

[myglc2]

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 compiled /home/g1/.config/guix/latest/guix/packages.go
;;; note: source file /home/g1/.config/guix/latest/guix/packages.scm
;;;   newer than compiled 
/home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/guix/packages.scm.go
;;; note: source file /home/g1/.config/guix/latest/guix/gexp.scm
;;;   newer than compiled /home/g1/.config/guix/latest/guix/gexp.go
;;; note: source file /home/g1/.config/guix/latest/guix/gexp.scm
;;;   newer than compiled 
/home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/guix/gexp.scm.go
;;; note: source file /home/g1/.config/guix/latest/guix/profiles.scm
;;;   newer than compiled /home/g1/.config/guix/latest/guix/profiles.go
;;; note: source file /home/g1/.config/guix/latest/guix/profiles.scm
;;;   newer than compiled 
/home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/guix/profiles.scm.go
;;; note: source file 
/home/g1/.config/guix/latest/gnu/system/linux-container.scm
;;;   newer than compiled 
/home/g1/.config/guix/latest/gnu/system/linux-container.go
;;; note: source file /home/g1/.config/guix/latest/gnu/services.scm
;;;   newer than compiled /home/g1/.config/guix/latest/gnu/services.go
;;; note: source file /home/g1/.config/guix/latest/gnu/services.scm
;;;   newer than compiled 
/home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/gnu/services.scm.go
;;; note: source file /home/g1/.config/guix/latest/guix/download.scm
;;;   newer than compiled /home/g1/.config/guix/latest/guix/download.go
;;; note: source file /home/g1/.config/guix/latest/guix/download.scm
;;;   newer than compiled 
/home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/guix/download.scm.go
;;; note: source file /home/g1/.config/guix/latest/guix/git-download.scm
;;;   newer than compiled /home/g1/.config/guix/latest/guix/git-download.go
;;; note: source file /home/g1/.config/guix/latest/guix/git-download.scm
;;;   newer than compiled 
/home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/src/guix/guix/git-download.scm.go
Backtrace:
In unknown file:
   ?: 19 [primitive-load-path "gnu/packages/autotools" ...]
In gnu/packages/autotools.scm:
  24: 18 [#]
In ice-9/boot-9.scm:
2951: 17 [define-module* (gnu packages autotools) #:filename ...]
2926: 16 [resolve-imports ((#) (#) (#) (#) ...)]
2864: 15 [resolve-interface (gnu packages bash) #:select ...]
2789: 14 [# # ...]
3065: 13 [try-module-autoload (gnu packages bash) #f]
2401: 12 [save-module-excursion #]
3085: 11 [#]
In unknown file:
   ?: 10 [primitive-load-path "gnu/packages/bash" ...]
In gnu/packages/bash.scm:
  21: 9 [#]
In ice-9/boot-9.scm:
2951: 8 [define-module* (gnu packages bash) #:filename ...]
2926: 7 [resolve-imports ((#) (#) (#) (#) ...)]
2864: 6 [resolve-interface (gnu packages readline) #:select ...]
2789: 5 [# # ...]
3065: 4 [try-module-autoload (gnu packages readline) #f]
2401: 3 [save-module-excursion #]
3085: 2 [#]
In unknown file:
   ?: 1 [primitive-load-path "gnu/packages/readline" ...]
In gnu/packages/readline.scm:
  81: 0 [#]

gnu/packages/readline.scm:81:12: In procedure #:
gnu/packages/readline.scm:81:12: In procedure struct-ref: Argument 1 out of 
range: 10
g1@g1 ~/src/guix$ 

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

[myglc2]

myglc2 <myg...@gmail.com> writes:

> From 'Re: guixSD - problem with X11 forwarding' in help-g...@gnu.org
>
> myglc2 <myg...@gmail.com> writes:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>>
>>> myglc2 <myg...@gmail.com> skribis:
>>>
>>>> On guixSD, with no packages installed in the login user profile, I get
>>>> 'X11 forwarding request failed on channel 0'
>>>
>>> [...]
>>>
>>>> debug1: channel 0: new [client-session]
>>>> debug1: Entering interactive session.
>>>> debug1: Requesting X11 forwarding with authentication spoofing.
>>>> debug1: Sending environment.
>>>> debug1: Sending env LANG = en_US.UTF-8
>>>> X11 forwarding request failed on channel 0
>>>
>>> Right, I see that as well.
>>>
>>> lshd gives some clues in /var/log/messages:
>>>
>>> Feb 23 18:14:09 localhost lshd[430]: lshd: Updating utmp for login failed 
>>> (errno = 2): No such file or directory 
>>> Feb 23 18:14:09 localhost lshd[430]: lshd: xauth invocation failed: exit 
>>> code: 127 
>>> Feb 23 18:14:33 localhost lshd[430]: lshd: Updating utmpx for logout failed 
>>> (errno = 2): No such file or directory 
>>> Feb 23 18:14:33 localhost lshd[430]: lshd: write_buffer: Attempt to write 
>>> data to closed buffer. 
>>> Feb 23 18:14:33 localhost lshd[430]: lshd: Disconnect for reason 11: 
>>> disconnected by user 
>>>
>>> Indeed, server_x11.c in lsh reads:
>>>
>>> #ifndef XAUTH_PROGRAM
>>> # define XAUTH_PROGRAM "/usr/X11R6/bin/xauth"
>>> #endif
>>>
>>> I believe this is fixed by commit da35acf.
>>>
>>> To give it a try, you can run (as root):
>>>
>>>   # guix pull
>>>   # herd stop ssh-daemon
>>>   # guix system reconfigure your-config.scm
>>
>> I tried the above. 'ssh -v ...' still produces results quoted above and
>> I see in /var/log/messages:
>>
>> Feb 29 20:43:54 localhost lshd[6959]: lshd: Failed to cd to `/tmp/.X11-unix' 
>> (errno = 2): No such file or directory 
>> Feb 29 20:43:54 localhost lshd[6959]: lshd: Updating utmp for login failed 
>> (errno = 2): No such file or directory 
>> Feb 29 20:45:35 localhost lshd[6959]: lshd: Updating utmpx for logout failed 
>> (errno = 2): No such file or directory 
>> Feb 29 20:45:35 localhost lshd[6959]: lshd: write_buffer: Attempt to write 
>> data to closed buffer. 
>> Feb 29 20:45:35 localhost lshd[6959]: lshd: Disconnect for reason 11: 
>> disconnected by user 
>> Feb 29 20:45:47 localhost lshd[6959]: lshd: Failed to cd to `/tmp/.X11-unix' 
>> (errno = 2): No such file or directory 
>> Feb 29 20:45:47 localhost lshd[6959]: lshd: Updating utmp for login failed 
>> (errno = 2): No such file or directory 
>>
>> I tried 'sudo mkdir /tmp/.X11-unix' which changed /var/log/messages to:
>>
>> Feb 29 20:54:04 localhost lshd[6959]: lshd: Updating utmp for login failed 
>> (errno = 2): No such file or directory 
>> Feb 29 20:54:09 localhost lshd[6959]: lshd: Updating utmpx for logout failed 
>> (errno = 2): No such file or directory 
>> Feb 29 20:54:09 localhost lshd[6959]: lshd: write_buffer: Attempt to write 
>> data to closed buffer. 
>> Feb 29 20:54:09 localhost lshd[6959]: lshd: Disconnect for reason 11: 
>> disconnected by user 
>>
>> and 'ssh -v ...' still produces the results quoted above.
>
> Don't think this is fixed yet. ssh in to GuixSD gives ...
>
> 'X11 forwarding request failed on channel 0'
>
> ... and on GuixSD in /var/log/messages I see ...
>
> Jul 12 16:25:42 localhost lshd[384]: lshd: Failed to cd to `/tmp/.X11-unix' 
> (errno = 2): No such file or directory 
> Jul 12 16:25:42 localhost lshd[384]: lshd: Updating utmp for login failed 
> (errno = 2): No such file or directory 
>
> ... or after ...
>
> sudo mkdir /tmp/.X11-unix
>
> ... I see ...
>
> Jul 12 16:21:53 localhost lshd[384]: lshd: Updating utmpx for logout failed 
> (errno = 2): No such file or directory 
> Jul 12 16:21:53 localhost lshd[384]: lshd: write_buffer: Attempt to write 
> data to closed buffer. 
> Jul 12 16:21:53 localhost lshd[384]: lshd: Disconnect for reason 11: 
> disconnected by user 
> Jul 12 16:22:00 localhost lshd[384]: lshd: Updating utmp for login failed 
> (errno = 2): No such file or directory 
>
> I am running from a git checkout ...
>
> g1@g1 ~/src/guix$ git branch -av | grep '* master'
> * master   0885881 gnu: obs: Remove compiler 
> flags for non-Intel hardware.
> g1@g1 ~/src/guix$ stat /home/g1/.config/guix/latest | grep File:
>   File: ‘/home/g1/.config/guix/latest’ -> ‘../../src/guix’
>
>
> system and user configs attached. TIA - George

Afterthought... when I do ...

sudo mkdir /tmp/.X11-unix
sudo chmod 777 /tmp/.X11-unix

... it works.

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

[myglc2]

>From 'Re: guixSD - problem with X11 forwarding' in help-g...@gnu.org

myglc2 <myg...@gmail.com> writes:

> l...@gnu.org (Ludovic Courtès) writes:
>
>> myglc2 <myg...@gmail.com> skribis:
>>
>>> On guixSD, with no packages installed in the login user profile, I get
>>> 'X11 forwarding request failed on channel 0'
>>
>> [...]
>>
>>> debug1: channel 0: new [client-session]
>>> debug1: Entering interactive session.
>>> debug1: Requesting X11 forwarding with authentication spoofing.
>>> debug1: Sending environment.
>>> debug1: Sending env LANG = en_US.UTF-8
>>> X11 forwarding request failed on channel 0
>>
>> Right, I see that as well.
>>
>> lshd gives some clues in /var/log/messages:
>>
>> Feb 23 18:14:09 localhost lshd[430]: lshd: Updating utmp for login failed 
>> (errno = 2): No such file or directory 
>> Feb 23 18:14:09 localhost lshd[430]: lshd: xauth invocation failed: exit 
>> code: 127 
>> Feb 23 18:14:33 localhost lshd[430]: lshd: Updating utmpx for logout failed 
>> (errno = 2): No such file or directory 
>> Feb 23 18:14:33 localhost lshd[430]: lshd: write_buffer: Attempt to write 
>> data to closed buffer. 
>> Feb 23 18:14:33 localhost lshd[430]: lshd: Disconnect for reason 11: 
>> disconnected by user 
>>
>> Indeed, server_x11.c in lsh reads:
>>
>> #ifndef XAUTH_PROGRAM
>> # define XAUTH_PROGRAM "/usr/X11R6/bin/xauth"
>> #endif
>>
>> I believe this is fixed by commit da35acf.
>>
>> To give it a try, you can run (as root):
>>
>>   # guix pull
>>   # herd stop ssh-daemon
>>   # guix system reconfigure your-config.scm
>
> I tried the above. 'ssh -v ...' still produces results quoted above and
> I see in /var/log/messages:
>
> Feb 29 20:43:54 localhost lshd[6959]: lshd: Failed to cd to `/tmp/.X11-unix' 
> (errno = 2): No such file or directory 
> Feb 29 20:43:54 localhost lshd[6959]: lshd: Updating utmp for login failed 
> (errno = 2): No such file or directory 
> Feb 29 20:45:35 localhost lshd[6959]: lshd: Updating utmpx for logout failed 
> (errno = 2): No such file or directory 
> Feb 29 20:45:35 localhost lshd[6959]: lshd: write_buffer: Attempt to write 
> data to closed buffer. 
> Feb 29 20:45:35 localhost lshd[6959]: lshd: Disconnect for reason 11: 
> disconnected by user 
> Feb 29 20:45:47 localhost lshd[6959]: lshd: Failed to cd to `/tmp/.X11-unix' 
> (errno = 2): No such file or directory 
> Feb 29 20:45:47 localhost lshd[6959]: lshd: Updating utmp for login failed 
> (errno = 2): No such file or directory 
>
> I tried 'sudo mkdir /tmp/.X11-unix' which changed /var/log/messages to:
>
> Feb 29 20:54:04 localhost lshd[6959]: lshd: Updating utmp for login failed 
> (errno = 2): No such file or directory 
> Feb 29 20:54:09 localhost lshd[6959]: lshd: Updating utmpx for logout failed 
> (errno = 2): No such file or directory 
> Feb 29 20:54:09 localhost lshd[6959]: lshd: write_buffer: Attempt to write 
> data to closed buffer. 
> Feb 29 20:54:09 localhost lshd[6959]: lshd: Disconnect for reason 11: 
> disconnected by user 
>
> and 'ssh -v ...' still produces the results quoted above.

Don't think this is fixed yet. ssh in to GuixSD gives ...

'X11 forwarding request failed on channel 0'

... and on GuixSD in /var/log/messages I see ...

Jul 12 16:25:42 localhost lshd[384]: lshd: Failed to cd to `/tmp/.X11-unix' 
(errno = 2): No such file or directory 
Jul 12 16:25:42 localhost lshd[384]: lshd: Updating utmp for login failed 
(errno = 2): No such file or directory 

... or after ...

sudo mkdir /tmp/.X11-unix

... I see ...

Jul 12 16:21:53 localhost lshd[384]: lshd: Updating utmpx for logout failed 
(errno = 2): No such file or directory 
Jul 12 16:21:53 localhost lshd[384]: lshd: write_buffer: Attempt to write data 
to closed buffer. 
Jul 12 16:21:53 localhost lshd[384]: lshd: Disconnect for reason 11: 
disconnected by user 
Jul 12 16:22:00 localhost lshd[384]: lshd: Updating utmp for login failed 
(errno = 2): No such file or directory 

I am running from a git checkout ...

g1@g1 ~/src/guix$ git branch -av | grep '* master'
* master   0885881 gnu: obs: Remove compiler 
flags for non-Intel hardware.
g1@g1 ~/src/guix$ stat /home/g1/.config/guix/latest | grep File:
  File: ‘/home/g1/.config/guix/latest’ -> ‘../../src/guix’


system and user configs attached. TIA - George



g1.scm
Description: Binary data


system.scm
Description: Binary data

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

[myglc2]

l...@gnu.org (Ludovic Courtès) writes:

> myglc2 <myg...@gmail.com> skribis:
>
>> FAIL: tests/substitute.scm
>
> Ooh, my bad.  Fixed in 934c5d5b28f74ab2fe187ad727e4b56cfda6def8.
>

Now I see ...

Testsuite summary for GNU Guix 0.10.0

# TOTAL: 582
# PASS:  564
# SKIP:  18
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0


... in this commit

[guix env] g1@e3b:~/.config/guix/latest$ git branch -av | grep '* master'
* master  d6e374a gnu: mafft: Update to 7.299.

Thanks! - George

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

[myglc2]

myglc2 <myg...@gmail.com> 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 kvm
...
>
> ... anyway, now I get ...
>
> g1@e3b:~/dev/vms$ guix system vm ../configs/c01system.scm --expose=$HOME 
> --share=$HOME/tmp=/exchange --verbosity=1
> substitute: warning: failed to install locale: Invalid argument
> /gnu/store/7rv558c43bwnmmkc85izv1b69ards5qy-run-vm.sh
> g1@e3b:~/dev/vms$ /gnu/store/7rv558c43bwnmmkc85izv1b69ards5qy-run-vm.sh
> qemu-system-x86_64: -virtfs 
> local,path=/home/g1/tmp,security_model=none,mount_tag=TAG_home_g1_tmp: 9pfs 
> Failed to initialize fs-driver with id:TAG_home_g1_tmp and export 
> path:/home/g1/tmp
> g1@e3b:~/dev/vms$

OOH! DUH! Nevermind ...

mkdir /home/g1/tmp

... fixes this.

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

[myglc2]

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 missed.

Thank you, so I did this ...

adduser guixbuilder1 kvm
adduser guixbuilder2 kvm
adduser guixbuilder3 kvm
adduser guixbuilder4 kvm
adduser guixbuilder5 kvm
adduser guixbuilder6 kvm
adduser guixbuilder7 kvm
adduser guixbuilder8 kvm

... but maybe the manual should say this ...

# 2.4.1 Build Environment Setup
# -
# [...]   
# On a GNU/Linux system, a build user pool may be created like this
# (using Bash syntax and the ‘shadow’ commands):
#
#  # groupadd --system guixbuild
#  # for i in `seq -w 1 10`;
#do
#  useradd -g guixbuild -G guixbuild,kvm   \
#  -d /var/empty -s `which nologin`\
#  -c "Guix build user $i" --system\
#  guixbuilder$i;
#done

... anyway, now I get ...

g1@e3b:~/dev/vms$ guix system vm ../configs/c01system.scm --expose=$HOME 
--share=$HOME/tmp=/exchange --verbosity=1
substitute: warning: failed to install locale: Invalid argument
/gnu/store/7rv558c43bwnmmkc85izv1b69ards5qy-run-vm.sh
g1@e3b:~/dev/vms$ /gnu/store/7rv558c43bwnmmkc85izv1b69ards5qy-run-vm.sh
qemu-system-x86_64: -virtfs 
local,path=/home/g1/tmp,security_model=none,mount_tag=TAG_home_g1_tmp: 9pfs 
Failed to initialize fs-driver with id:TAG_home_g1_tmp and export 
path:/home/g1/tmp
g1@e3b:~/dev/vms$

TIA, George

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

[myglc2]

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 kvm
adduser g1 libvirt


... then, as user g1, I checked that virsh commands work ...

g1@e3b:~/dev/vms$ virsh list --all
 IdName   State


g1@e3b:~/dev/vms$ virsh --connect qemu:///system list --all
 IdName   State


g1@e3b:~/dev/vms$ virsh version --daemon
Compiled against library: libvirt 1.2.9
Using library: libvirt 1.2.9
Using API: QEMU 1.2.9
Running hypervisor: QEMU 2.1.2
Running against daemon: 1.2.9


... then, using this version of guix ...

git branch -av | grep '* master'
* master  bae0636 bournish: Add 'wc' command.
g1@e3b:~/dev/guix$ stat /home/g1/.config/guix/latest | grep File:
  File: ‘/home/g1/.config/guix/latest’ -> ‘../../dev/guix’


... I tried making a guix vm ...

g1@e3b:~/dev/vms$ guix system vm ../configs/c01system.scm --expose=$HOME 
--share=$HOME/tmp=/exchange --verbosity=1
;;; note: source file /home/g1/.config/guix/latest/gnu/packages/screen.scm
;;;   newer than compiled 
/home/g1/.config/guix/latest/gnu/packages/screen.go
;;; compiling /home/g1/.config/guix/latest/gnu/packages/screen.scm
;;; compiled 
/home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/dev/guix/gnu/packages/screen.scm.go
substitute: warning: failed to install locale: Invalid argument
substitute: updating list of substitutes from 'http://hydra.gnu.org'... 100.0%
The following derivations will be built:
   /gnu/store/jz6mlhlz7f5sp4g93spac69bxfjpjbqg-run-vm.sh.drv
   /gnu/store/5f6zfsx0fa0bzkl4ynqb1lf5pk3m4rfs-qemu-image.drv
warning: failed to install locale: Invalid argument
building path(s) `/gnu/store/nbppjjb2kkb17nr8jqas7hchkg669nv9-qemu-image'
Formatting 'image.qcow2', fmt=qcow2 size=31457280 encryption=off 
cluster_size=65536 lazy_refcounts=off refcount_bits=16
Could not access KVM kernel module: Permission denied
failed to initialize KVM: Permission denied
Backtrace:
In ice-9/boot-9.scm:
 157: 10 [catch #t # ...]
In unknown file:
   ?: 9 [apply-smob/1 #]
In ice-9/boot-9.scm:
  63: 8 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
 432: 7 [eval # #]
In ice-9/boot-9.scm:
2401: 6 [save-module-excursion #]
4050: 5 [#]
1724: 4 [%start-stack load-stack #]
1729: 3 [#]
In unknown file:
   ?: 2 [primitive-load 
"/gnu/store/kfakhvdns3vjpivw6pk0bkdqafywr9s9-qemu-image-builder"]
In ./gnu/build/vm.scm:
 127: 1 [load-in-linux-vm 
"/gnu/store/9yprr0vmwnpvlkr2a0jgylpf9py6cf83-linux-vm-loader" ...]
In unknown file:
   ?: 0 [scm-error misc-error #f "~A ~S" ("qemu failed" "qemu-system-x86_64") 
#f]

ERROR: In procedure scm-error:
ERROR: qemu failed "qemu-system-x86_64"
environment variable `PATH' set to 
`/gnu/store/nk0z0qs8g3i03jfyi6hr2rwnd9pg2qnv-qemu-minimal-2.6.0/bin:/gnu/store/34j2zmi69mqwrslpyizbi9mcxmn2hzgb-coreutils-8.24/bin'
builder for `/gnu/store/5f6zfsx0fa0bzkl4ynqb1lf5pk3m4rfs-qemu-image.drv' failed 
with exit code 1
cannot build derivation 
`/gnu/store/jz6mlhlz7f5sp4g93spac69bxfjpjbqg-run-vm.sh.drv': 1 dependencies 
couldn't be built
guix system: error: build failed: build of 
`/gnu/store/jz6mlhlz7f5sp4g93spac69bxfjpjbqg-run-vm.sh.drv' failed
g1@e3b:~/dev/vms$

tia, - George



c01glc.scm
Description: Binary data

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

[myglc2]

l...@gnu.org (Ludovic Courtès) writes:

> Hello,
>
> myglc2 <myg...@gmail.com> 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:173
>> source:
>> + (test-equal
>> +   "query narinfo without signature"
>> +   ""
>> +   (with-narinfo
>> + %narinfo
>> + (string-trim-both
>> +   (with-output-to-string
>> + (lambda ()
>> +   (with-input-from-string
>> + (string-append
>> +   "have "
>> +   (%store-prefix)
>> +   "/-foo")
>> + (lambda () (guix-substitute "--query"
>> expected-value: 
>> actual-value: #f
>> actual-error:
>> + (system-error
>> +   "lstat"
>> +   "~A: ~S"
>> +   ("No such file or directory"
>> +"/home/g1/dev/guix/test-tmp/var/24621/cache-24621/guix/substitute/")
>> +   (2))
>> result: FAIL
>
> This is fishy.  Could it be that files in this directory were being
> accessed or removed concurrently?

Maybe because I ran make with 5 jobs ...

[guix env] g1@e3b:~/dev/guix$ make -j5

Was that a bad idea?

>
> Could you retry these tests with:
>
>   make check TESTS=tests/substitute.scm

please see below :-)

g1@e3b:~/dev/guix$ guix environment guix
;;; note: source file /home/g1/.config/guix/latest/gnu/packages/screen.scm
;;;   newer than compiled 
/home/g1/.config/guix/latest/gnu/packages/screen.go
;;; found fresh local cache at 
/home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/dev/guix/gnu/packages/screen.scm.go
substitute: warning: failed to install locale: Invalid argument
[guix env] g1@e3b:~/dev/guix$ make check TESTS=tests/substitute.scm
make  check-recursive
make[1]: Entering directory '/home/g1/dev/guix'
Making check in po/guix
make[2]: Entering directory '/home/g1/dev/guix/po/guix'
make[2]: Leaving directory '/home/g1/dev/guix/po/guix'
Making check in po/packages
make[2]: Entering directory '/home/g1/dev/guix/po/packages'
make[2]: Leaving directory '/home/g1/dev/guix/po/packages'
make[2]: Entering directory '/home/g1/dev/guix'
Compiling Scheme modules...
  LOAD (gnu packages screen)
;;; note: source file ./gnu/packages/screen.scm
;;;   newer than compiled /home/g1/dev/guix/gnu/packages/screen.go
;;; found fresh local cache at 
/home/g1/.cache/guile/ccache/2.0-LE-8-2.0/home/g1/dev/guix/gnu/packages/screen.scm.go
  GUILEC   gnu/packages/screen.go
make  check-TESTS check-local
make[3]: Entering directory '/home/g1/dev/guix'
make[4]: Entering directory '/home/g1/dev/guix'
FAIL: tests/substitute.scm

Testsuite summary for GNU Guix 0.10.0

# TOTAL: 11
# PASS:  3
# SKIP:  0
# XFAIL: 0
# FAIL:  8
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to bug-guix@gnu.org

Makefile:4097: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
make[4]: Leaving directory '/home/g1/dev/guix'
Makefile:4203: recipe for target 'check-TESTS' failed
make[3]: *** [check-TESTS] Error 2
make[3]: Leaving directory '/home/g1/dev/guix'
Makefile:4446: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/home/g1/dev/guix'
Makefile:3983: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/home/g1/dev/guix'
Makefile:4448: recipe for target 'check' failed
make: *** [check] Error 2
[guix env] g1@e3b:~/dev/guix$



test-suite.log
Description: Binary data

Thanks! - George

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

[myglc2]

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:  15
# XFAIL: 0
# FAIL:  9
# XPASS: 0
# ERROR: 0




test-suite.log
Description: Binary data


160623.make.check.log
Description: Binary data

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

[myglc2]

Alex Kost <alez...@gmail.com> writes:

> myglc2 (2016-02-08 21:29 +0300) wrote:
>
>> Alex Kost <alez...@gmail.com> 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 that of Vim."
>>>>
>>>> TYPO:
>>>>
>>>> "edit" (last line above) should be replaced with "view", "inspect", or
>>>> "examine".
>>>
>>> Just to mention - I like "edit" name :-)
>
> I changed my mind, I don't like it anymore :-(

Good to hear.

>>>> RENAME:
>>>>
>>>> Calling these functions 'guix edit' and 'M-x guix-edit' implies that the
>>>> user will be able to modify the recipe, but this is not actually the
>>>> case. The functions should be given a more informative and accurate
>>>> name, such as: 'guix view', 'guix inspect', or 'guix examine'.
>>>
>>> Along with the package recipes that come with Guix, a user can also have
>>> his/her own packages (specified using GUIX_PACKAGE_PATH env var), and
>>> "guix edit my-super-package" opens a user's file with this package.  It
>>> is highly likely that this file is editable, so "guix edit" is a perfect
>>> name in this case I think.  IMO it's a user responsibility to understand
>>> what files can be edited and what cannot.
>>
>> Sorry this is so long, but I think this is a useability issue that is
>> worth discussing more.
>>
>> I understand your point-of-view, but I think it is much more
>> packager-centric than you should plan on your ultimate user base being.
>>
>> If we think about the mix of guix users when it is more widely
>> successful, as I strongly believe it will be, a majority (80-90%) will
>> be "simply" managing and configuring their computer and/or user
>> account. They will NOT make packages.
>>
>> If this is the case, the majority of people clicking on "guix edit" will
>> not understand "what files can be edited and what cannot." The very idea
>> that a recipe on their computer can make something they need will be a
>> radical leap. For these people, taking the fist look at a guix recipe
>> will be a step deeper into guix.
>>
>> Such a user's first interaction might run along the lines of mine ...
>>
>> - Hmm, I want to see an actual recipe.
>>
>> - Oh wow, it says I can edit a recipe right here!
>>
>> - Hmm, maybe I shouldn't because I don't want to break something.
>>
>> - But they wouldn't call it "guix edit" if it wasn't OK to change stuff,
>>   right?
>>
>> - OK, I'll give it a shot. I'll look at something I am familiar with ...
>>
>> - 'guix edit screen'
>>
>> - WOW look at that. Finds the recipe, opens an editor, COOL!
> [...]
>
> Now I agree with this.  There was another person¹ who was confused by
> "edit" name, and I think there will be more.  OTOH if it will be renamed
> to anything else, I'm afraid some people will still think they can just
> modify the package definition in place.  But "guix edit" is…, well, not
> the best name we can have.
>
> Moreover, I think there are inconsistencies in guix commands.  For
> example, we have "guix system build" to build a system, but "guix build"
> to build a package.  IMO "guix package build" would be a better choice.
>
> In general, I think it would be good to move package commands inside
> "guix package" (which is probably a different direction to Andy's
> suggestion²), e.g, to make "guix package lint", "guix package size",
> etc.

For overall Guix usability, the overloading of a single guix command for
everything is not so good. When you eventually create a man page, it
will be intimidating for someone just trying to do per-user package
management, which the majority of, and least sophisticated users, will
be trying to do.

On the other hand there are several "classes" of commands and this is
reflected by the guix CLI being described in several logically different
parts of the doc, but not, as you point out, by being differentiated in
the CLI.

A possibly better approach would be to explicitly split the guix
command-verse into command classes to better match the structure of the
doc. For example, per-user ('guix ...'), global-system ('guix

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

[myglc2]

Alex Kost <alez...@gmail.com> 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 much the same configurations to
> set up Guix (and emacs stuff) from git.

Thank you Alex. I promise not to post any more on this bug ;)

Best, George

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

[myglc2]

Alex Kost <alez...@gmail.com> 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" package.  Currently it is
>> "guix-devel" package at commit c3f29bc², which is older then commit
>> 004ea62 (that fixed this issue).
>>
>> After we update "guix" package (either via updating "guix-devel"
>> snapshot or via pointing "guix" to "guix-0.9.1" after the new release),
>> this will be finally fixed.
>>
>> ¹ http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22550#38
>> ² 
>> http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/package-management.scm#n198
>
> This issue should be completely fixed now (after commit 092dd65¹).
> (Just to remind) the original issue is a request for auto-finding emacs
> packages installed globally (in a system profile).
>
> So, if you update your Emacs, it should automatically find emacs
> packages (magit, etc.) installed both in user and system profiles.
>
> To update Emacs, one need to:
>
> 1. If emacs is installed in a user profile:
>
>   $ guix pull
>   $ guix package --upgrade=emacs
>
> 2. If emacs is installed in a system profile:
>
>   # guix pull
>   # guix system reconfigure
>
> ¹ 
> http://git.savannah.gnu.org/cgit/guix.git/commit/?id=092dd6541fc75ed19ebbb1f9d8e6f32a88cb3445

Hi Alex, Thank you for the followup.

I can't test on GuixSD right now, but '2.' looks good here.

If you have a moment, Is there a way to set up my git checkout guix
environment to use changes like this as they are made in the development
version?

My current 'Guix checkout' config (on a Guix/Debian install) looks like
this ...

  /home/g1/.config/guix:
  lrwxrwxrwx 1 g1 g1   14 Mar 24 13:49 latest -> ../../src/guix

... in ~/.profile I have ...

# guix
export GUIX_LOCPATH=$HOME/.guix-profile/lib/locale
GUIX_PROFILE="$HOME/.guix-profile"
source "$HOME/.guix-profile/etc/profile"

... and in ~/.emacs.d/init.el I have ...

;; start: guix emacs setup

;; to run emacs interface from git checkout and have guix-edit operate
;; on git checkout files
(let ((dir "/home/g1/src/guix/emacs"))
  (add-to-list 'load-path dir)
  (setq guix-load-path dir))
(require 'guix-init nil t)

 ;; to read the guix manual from git checkout
(with-eval-after-load 'info
  (info-initialize)
  (add-to-list 'Info-directory-list
   "/home/g1/src/guix/doc"))

;; from #guix for guix compatible diffs
(setq ediff-patch-options "-b -f")

;; end: guix emacs setup

Many thanks, - George

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

[myglc2]

l...@gnu.org (Ludovic Courtès) writes:

> Alex Kost <alez...@gmail.com> skribis:
>
>> Ludovic Courtès (2016-03-14 01:01 +0300) wrote:
>>
>>> myglc2 <myg...@gmail.com> skribis:
>>>
>>>> Guix is "stateful" because, to use a git checkout, I have to set "state"
>>>> variables like ...
>>>>
>>>> (setq guix-directory "/home/glc/src/guix")
>>>>
>>>> (let ((dir "~/dev/guix/emacs"))
>>>>   (add-to-list 'load-path dir)
>>>>   (setq guix-load-path dir)
>>>>   (require 'guix-init nil t))
>>>>
>>>> '(safe-local-variable-values
>>>>(quote
>>>> ((bug-reference-bug-regexp . 
>>>> "<https?://\\(debbugs\\|bugs\\)\\.gnu\\.org/\\([0-9]+\\)>")
>>>> (custom-set-faces
>>>>
>>>> /home/glc/.config/guix/latest’ -> ‘../../src/guix'
>>>> /root/.config/guix/latest’ -> ‘/home/glc/src/GUI’
>>>>
>>>>
>>>> Guix would be less stateful (AKA more "stateless") if instead I could
>>>> put something like ...
>>>>
>>>> (guix
>>>>   (#:use-git #t)
>>>>   (#:git-directory:"~/src/guix"))
>>>
>>> It seems to me that it’s not a question of “statefulness”, but rather a
>>> question of how much configuration is needed to have guix.el use the
>>> Guix that you want.
>>
>> I agree.  If someone want to use a "non-installed" software, (s)he has
>> to do some additional configuration.  I don't see how to reduce such
>> a configuration to set up emacs code from a guix git checkout.
>
> Should this issue be closed?
>
> Ludo’.
Sure! Thanks! - George

bug#23072: GuixSD SSD install hangs at clocksource

[myglc2]

Florian Paul Schmidt <mista.ta...@gmx.net> 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 & mouse drivers, then hangs
>>   showing:
>> 
>>   "clocksource: Switched to clocksource tsc"
>
> This is just a shot in the dark, but I use SSD systems, too, and I
> noticed that the first boot of a guixsd installation hangs for a while
> collecting entropy before displaying a corresponding message IIRC and I
> faintly remember the "switching to clocksource" message. Did you try
> banging the keyboard? Maybe that's not possible on a headless server
> though. Did you let it sit for a while?
>
> Flo
Thanks Flo. Can't test that theory at the moment.  But I do have a
display attached (which is how I saw the "clocksource..." message).

FWIW, in the HD install there is a prompt for keyboard input. It seems
like the SSD install hung before it reached that.  - George

bug#23072: GuixSD SSD install hangs at clocksource

[myglc2]

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 switched to a 2nd server running
Guix/Debian and ...

- reinstalled GuixSD to the 1st server's HD, see
  "c06system.scm.log". This runs fine back in the 1st server.

- 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 & mouse drivers, then hangs
  showing:

  "clocksource: Switched to clocksource tsc"

So to summarize, ~identical install on HD runs fine, install on SSD
hangs.

Please see attached logs. - George



c06system-ssd.scm.log
Description: Binary data


c06system-sdd.scm.log
Description: Binary data

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

[myglc2]

Alex Kost <alez...@gmail.com> 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 English language is not enough to understand this
> question.  Could you explain what "state-full" means?

NP. I may have caused a problem by miss-spelling "stateful", which I
meant this way ...

"The output of a digital circuit or computer program at any time is
completely determined by its current inputs and its state."

  Ref: https://en.wikipedia.org/wiki/State_(computer_science)


Guix is "stateful" because, to use a git checkout, I have to set "state"
variables like ...

(setq guix-directory "/home/glc/src/guix")

(let ((dir "~/dev/guix/emacs"))
  (add-to-list 'load-path dir)
  (setq guix-load-path dir)
  (require 'guix-init nil t))

'(safe-local-variable-values
   (quote
((bug-reference-bug-regexp . 
"<https?://\\(debbugs\\|bugs\\)\\.gnu\\.org/\\([0-9]+\\)>")
(custom-set-faces

/home/glc/.config/guix/latest’ -> ‘../../src/guix'
/root/.config/guix/latest’ -> ‘/home/glc/src/GUI’


Guix would be less stateful (AKA more "stateless") if instead I could
put something like ...

(guix
  (#:use-git #t)
  (#:git-directory:"~/src/guix"))

... in user.scm and do 'guix package -m user.scm' ;)

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

[myglc2]

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
icons? But it is messy and  on #guix reported the same thing:

VV
 I was expecting if I do -i emacs -- to get binary emacs, not the
ony that was compiled without gdk-pixbuf incorrectly
 JeanLouis: what do you mean by "that was compiled without
  gdk-pixbuf incorrectly" ?
 https://rcdrun.com/images/upload/tmp/2016-03-12-23:41:52.jpg
 that is what I mean
 (emacs-24-5:28561): Gdk-CRITICAL **:
gdk_cairo_surface_create_from_pixbuf: assertion 'GDK_IS_PIXBUF
(pixbuf)' failed[18:06]
 I get many such when running it.
 buttons missing
^^

Here is my setup:

M-x version:
GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.18.2) of
2016-02-27 on localhost

Guix commit:
* master 81a9653 gnu: webkitgtk: Update to 2.10.8 [fixes CVE-2016-1726].

Example of the messages in the tty session:
V
** (emacs-24-5:18164): WARNING **: Couldn't connect to accessibility bus: 
Failed to connect to socket /tmp/dbus-JHb3wYZmX7: Connection refused

(emacs-24-5:18164): Gtk-WARNING **: Could not find the icon 'document-new'. The 
'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
http://icon-theme.freedesktop.org/releases

(emacs-24-5:18164): Gtk-WARNING **: Error loading theme icon 'document-new' for 
stock: Icon 'document-new' not present in theme Adwaita

(emacs-24-5:18164): Gtk-WARNING **: Error loading theme icon 'image-missing' 
for stock: Icon 'image-missing' not present in theme Adwaita

(emacs-24-5:18164): GLib-GObject-CRITICAL **: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed

(emacs-24-5:18164): Gdk-CRITICAL **: gdk_cairo_surface_create_from_pixbuf: 
assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(emacs-24-5:18164): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed

(emacs-24-5:18164): Gtk-WARNING **: Error loading theme icon 'document-new' for 
stock: Icon 'document-new' not present in theme Adwaita

(emacs-24-5:18164): Gtk-WARNING **: Error loading theme icon 'image-missing' 
for stock: Icon 'image-missing' not present in theme Adwaita
^



c05glc.scm
Description: Binary data


c05system.scm
Description: Binary data

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

[myglc2]

Alex Kost <alez...@gmail.com> 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 checkout in /home/glc5/src/guix, guix-edit does not find
>> the checkout source.
>>
>> Note: I followed comments from the #guix irc channel to set links in glc
>> and root that point to the glc checkout:
>>
>> glc@g1 ~/src/guix [env]$ stat ~/.config/guix/latest
>>   File: ‘/home/glc/.config/guix/latest’ -> ‘../../src/guix’
>>
>> glc@g1 ~/src/guix [env]$ stat /root/.config/guix/latest
>>   File: ‘/root/.config/guix/latest’ -> ‘/home/glc/src/guix’
>>
>>
>> CREATE USER glc5
> [...]
>> glc5@g1 ~/src$ stat ~/.config/guix/latest
>> stat: cannot stat ‘/home/glc5/.config/guix/latest’: No such file or directory
>
> I don't understand, so you made the links for user 'glc', but then you
> check another user 'glc5'.  If you run emacs under glc, and try "M-x
> guix-edit" there, you should be pointed to "~/.config/guix/latest".

Yes, but it only it works for me (glc) because I studied guix for 6
weeks and learned an unpublished trick on #guix IRC channel.

> Since you didn't make such a link for 'glc5', you are pointed to the
> store.

Yes because I am trying to help you improve the user experience. So glc5
is a simulated new user following the manual literally ;)

> Anyway, you can configure any directory for "M-x guix-edit" by setting
> 'guix-directory' variable.  See (info "(guix) Emacs Commands").  It is
> not in the hmtl manual yet.

But what is the _recommended_ way to do this?

A) set 'guix-directory' variable in emacs init file?

B) make symbolic link to ~/src/guix from ~/.config/guix/latest?

C) something else?

And if a _new_ user starts reading in "8.1 Building from Git", how do
they find this information?

FWIW, I vote for method B.

bug#22974: make check FAIL: tests/store

[myglc2]

l...@gnu.org (Ludovic Courtès) writes:

> myglc2 <myg...@gmail.com> 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
>   make check TESTS=tests/store.scm
[...]

git branch -v
* (HEAD detached at ce6027b) ce6027b gnu: nautilus: Don't propagate gtk+.
  master 9720651 gnu: libass: Update to 0.13.2.
make recheck
[...]

Testsuite summary for GNU Guix 0.9.1

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0
[...]

sudo rm -rf test-tmp

make check TESTS=tests/store.scm
[...]

Testsuite summary for GNU Guix 0.9.1

# TOTAL: 1
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0


hth - George

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

[myglc2]

Alex Kost <alez...@gmail.com> writes:

> myglc2 (2016-03-08 16:49 +0300) wrote:
>
>> Alex Kost <alez...@gmail.com> 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 features from 'git checkout master' one must add to emacs init:
>>>>
>>>> (let ((dir "~/src/guix/emacs"))
>>>>   (add-to-list 'load-path dir)
>>>>   (setq guix-load-path dir)
>>>>   (require 'guix-init nil t))
>>>
>>> Yes, this is the recommended way of setting it up.  It is described in
>>> (info "(guix) Emacs Initial Setup").
>>>
>>>> Do you think we should we add that to (info "(guix) Building from Git") ? 
>>>
>>> Since it is already described in the other section, it shouldn't be
>>> duplicated, but we can add a cross reference, not into "Building from
>>> Git" though, maybe to (info "(guix) The Perfect Setup")
>>
>> Then you need to also fix the intro paragraph which says (emphasis
>> added):
>
> I don't agree, this intro paragraph is (should be in theory) correct.
>
>> "On the Guix System Distribution (*note GNU Distribution::), “guix.el”
>> is ready to use [...] So [...] you can happily SKIP THIS SECTION [...]"
>>
>> Since I am using GuixSD I have always skipped this section.  That is why
>> you have had to explain this twice to me.
>
> It's just that no one tried to use system profile for adding emacs
> packages before you, but this case will be handled in the next release,
> so I think this part of the manual shouldn't be changed.

You are are assuming that I am running emacs in the system
profile. Meanwhile "tricky george" stopped trying to swim upstream and
installed emacs in the user profile :O. Based on running both ways I
still believe this needs attention.  But I am badly off the topic of the
original bug so I will put it in a new post.

I do apologize for the run-around. Many thanks! - George

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

[myglc2]

Alex Kost <alez...@gmail.com> writes:

> myglc2 (2016-03-07 23:03 +0300) wrote:
>
>> Alex Kost <alez...@gmail.com> 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 "guix" package (either via updating "guix-devel"
>>> snapshot or via pointing "guix" to "guix-0.9.1" after the new release),
>>> this will be finally fixed.
>>>
>>> ¹ http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22550#38
>>> ²
>>> http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/package-management.scm#n198
>>
>> Thank you. Sorry you had to explain this twice :(
>>
>> I re-read your earlier posts. AIUI now, in order to use the latest guix
>> emacs features from 'git checkout master' one must add to emacs init:
>>
>> (let ((dir "~/src/guix/emacs"))
>>   (add-to-list 'load-path dir)
>>   (setq guix-load-path dir)
>>   (require 'guix-init nil t))
>
> Yes, this is the recommended way of setting it up.  It is described in
> (info "(guix) Emacs Initial Setup").
>
>> Do you think we should we add that to (info "(guix) Building from Git") ? 
>
> Since it is already described in the other section, it shouldn't be
> duplicated, but we can add a cross reference, not into "Building from
> Git" though, maybe to (info "(guix) The Perfect Setup")

Then you need to also fix the intro paragraph which says (emphasis
added):

"On the Guix System Distribution (*note GNU Distribution::), “guix.el”
is ready to use [...] So [...] you can happily SKIP THIS SECTION [...]"

Since I am using GuixSD I have always skipped this section.  That is why
you have had to explain this twice to me.

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

[myglc2]

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 "guix" package (either via updating "guix-devel"
> snapshot or via pointing "guix" to "guix-0.9.1" after the new release),
> this will be finally fixed.
>
> ¹ http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22550#38
> ² 
> http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/package-management.scm#n198

Thank you. Sorry you had to explain this twice :(

I re-read your earlier posts. AIUI now, in order to use the latest guix
emacs features from 'git checkout master' one must add to emacs init:

(let ((dir "~/src/guix/emacs"))
  (add-to-list 'load-path dir)
  (setq guix-load-path dir)
  (require 'guix-init nil t))

Do you think we should we add that to (info "(guix) Building from Git") ? 

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

[myglc2]

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 localhost lshd[372]: lshd: Failed to cd to `/tmp/.X11-unix' 
(errno = 2): No such file or directory 
Mar  6 19:23:35 localhost lshd[372]: lshd: Updating utmp for login failed 
(errno = 2): No such file or directory 

If we do ...

mkdir /tmp/.X11-unix

... logout and login, forwarding works, emacs runs in X, and
/var/log/messages is clean. If we reboot, X11 forwarding again fails.



c02glc.scm
Description: Binary data


c02system.scm
Description: Binary data

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

[myglc2]

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 counter-intuitive that emacs 'M-x list-fontsets' gives ...

Fontset: -*-*-*-*-*-*-*-*-*-*-*-*-fontset-default
Fontset: -*-fixed-medium-r-normal-*-16-*-*-*-*-*-fontset-standard
Fontset: -urw-Nimbus Mono L-normal-normal-normal-*-13-*-*-*-m-0-fontset-startup

... when the system package list is ...

  % *Guix Package L...  5437 Guix-Output-List
  
  [...]
  emacs24.5   out   Yes  The extensible, 
customizable, self-documenting text editor
  [...]
  font-dejavu  2.34   out   Yes  Vera font  family 
derivate with additional characters
  [...]

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

[myglc2]

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 inspected for emacs packages), so
> it will not be necessary in the closest future.

Hi Alex. Tried removing this and got 'command-execute: Symbol's function
definition is void: magit-status'  Shouldn't it be fixed by now?

TIA - george

glc@g1 ~/dev/guix$ git branch -av | head -n 1
* master  59a4dd5 doc: Explain how to check 
whether security updates are used.

glc@g1 ~/dev/guix$ env | grep EMACSLOADPATH
EMACSLOADPATH=/etc/emacs:

glc@g1 ~/dev/guix$ cat ~/.emacs.d/init.el | grep autoloads
;; (guix-emacs-load-autoloads "/run/current-system/profile")

glc@g1 ~/dev/guix$ guix package --list-installed
glc@g1 ~/dev/guix$

system config.q.scm (attached)



config.q.scm
Description: Binary data

bug#22872: make check fails on commit caeadfd

[myglc2]

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#22650: guixSD default umask is 0000

[myglc2]

l...@gnu.org (Ludovic Courtès) writes:

> myglc2 <myg...@gmail.com> 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
> src/daemon.c:daemon_init) but never changes it again.
>
> Perhaps we should be using pam_umask and login.defs (although I’m unsure
> if lshd would honor it), or alternately add explicitly set the umask in
> /etc/profile.
>
> Thoughts?

Thanks for looking into this. Sorry, but I'm not qualified to comment. 

bug#22650: guixSD default umask is 0000

[myglc2]

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 umask?

I don't think so. I have attached a log of dot files for a sample user
(glc4) and the most current (feb 12) system config.

'system-generations-package-list' file was generated by 'emacs' 'M-x
guix-system-generations' '"select" (current) generation'

HTH, George


umask.bug.log
Description: Binary data


config.n.scm
Description: Binary data