Notice: Undefined variable: name in /srv/http/vhosts/ on line 248

Package Details: guix 0.12.0-2

Git Clone URL: (read-only)
Package Base: guix
Description: A purely functional package manager for the GNU system
Upstream URL:
Keywords: guix nix package system
Licenses: GPL3
Submitter: lantw44
Maintainer: lantw44
Last Packager: lantw44
Votes: 16
Popularity: 0.274422
First Submitted: 2013-04-22 11:06
Last Updated: 2016-12-31 19:07

Dependencies (17)

Required by (0)

Sources (2)

Latest Comments

1 2 3 4 Next › Last »

Pelzflorian commented on 2016-12-26 18:16

Thank you. I changed the article as per your suggestions. I did not know about systemctl edit. :)

lantw44 commented on 2016-12-26 17:17

Two simple comments for the article:

1. You don't have to copy the systemd unit file. To override options in guix-daemon.service, type 'systemctl edit guix-daemon.service' and put options you want to change in it.
2. You may want to mention '/var/log/guix' in 'Uninstalling Guix'.

Pelzflorian commented on 2016-12-26 10:53

I’ve created a Guix article on the Arch wiki. If that was too soon, feel free to delete it again.

lantw44 commented on 2016-12-17 14:28

You can find error messages of failing tests in test-suite.log.

Reded commented on 2016-12-17 13:44

Getting a build failure that doesn't seem to be the same as rafaelff's -

I did check the DNS servers, and turned off my usual dnsmasq/crypt combo to see if that was affecting it, but couldn't see anything immediate.

Anything I can do? Thanks!

rafaelff commented on 2016-11-08 12:45

You're right. My *nice* ISP's DNS servers redirects HTTP error messages to their search website, which masks the failure. This problem is solved by setting another DNS server in my computer and check() works just fine now. Sorry for the noise.

lantw44 commented on 2016-11-08 10:33

I think this is still caused by networking problems. It seems that when the test program tried to download http://does-not-exist, you got a web page that asked a browser to redirect to instead of failing.

rafaelff commented on 2016-11-06 13:30

I was behind a proxy, so probably the networking errors are related to it. However I'm having errors even without a proxy. See new logs:

Build & Check log:

fusion809 commented on 2016-11-06 13:04

I get the same error as rafaelff. If the default is to allow the tests internet access then that is what's happening on my system. I haven't deliberately turned internet access on or off.

lantw44 commented on 2016-11-05 07:39

Do you enable networking when running tests? I think there are many tests that need Internet access.