Package Details: guix 1.3.0-1

Git Clone URL: https://aur.archlinux.org/guix.git (read-only, click to copy)
Package Base: guix
Description: A purely functional package manager for the GNU system
Upstream URL: https://guix.gnu.org
Keywords: guile nix package system
Licenses: GPL3
Submitter: lantw44
Maintainer: lantw44
Last Packager: lantw44
Votes: 31
Popularity: 0.058804
First Submitted: 2013-04-22 11:06 (UTC)
Last Updated: 2022-03-14 10:08 (UTC)

Latest Comments

lantw44 commented on 2022-04-17 15:46 (UTC) (edited on 2022-04-17 15:47 (UTC) by lantw44)

@Ferk This looks like a bug of the gnutls package. Binding files installed by gnutls are empty. I have reported the bug as https://bugs.archlinux.org/task/74486.

Ferk commented on 2022-04-15 08:11 (UTC)

I'm getting this error:

checking for guile-2.2... yes
checking if (gnutls) is available... no
configure: error: The Guile bindings of GnuTLS are missing; please install them.

Both guile and gnutls are installed, but it seems the bindings are missing.

valandil commented on 2022-03-17 01:01 (UTC)

This should be temporary: AUR had some trouble earlier this week.

simona commented on 2022-03-16 10:06 (UTC)

errore: command failed: /home/simona/.cache/paru/clone: git clone --no-progress -- https://aur.archlinux.org/guile-semver:
Clone in 'guile-semver' in corso...
error: RPC non riuscita; HTTP 429 curl 22 The requested URL returned error: 429 fatal: atteso flush dopo elenco ref

valandil commented on 2022-03-16 01:44 (UTC)

I've seen this issue in a couple guile packages. It seems that having multiple versions of guile installed is not something that some guile packages can deal with. The easiest way I found to resolve that was to build all packages in a chroot using paru:

paru -S --nocheck --chroot guix

I added --nocheck because some guix checks were failing and I didn't feel like troubleshooting it :)

You have to setup a local AUR repo, but I think paru gives you the procedure when you first try it.

simona commented on 2022-03-15 09:32 (UTC)

configure: error: in /home/simona/.cache/yay/guile-avahi/src/guile-avahi-0.4': configure: error: searching for guile development files for versions 2.0 1.8, but previously found /bin/guile version 2.2<br> Seeconfig.log' for more details

valandil commented on 2022-03-15 01:35 (UTC)

Yeah ok. I just removed tidy_strip locally to make it work :)

lantw44 commented on 2022-03-14 10:10 (UTC)

@valandil I fixed it by ignoring the return value of tidy_strip.

valandil commented on 2022-02-15 02:41 (UTC)

I get the following errow when trying to build guix-1.3.0-1. It seems that calling tidy_strip fails at the end. Have you seen this erro before?

/build/guix/pkg/guix/usr/lib/systemd/system/guix-daemon.service /build/guix/pkg/guix/usr/lib/systemd/system/guix-daemon-latest.service differ: byte 223, line 6
/build/guix/pkg/guix/usr/lib/systemd/system/guix-publish.service /build/guix/pkg/guix/usr/lib/systemd/system/guix-publish-latest.service differ: byte 226, line 6
  -> Stripping unneeded symbols from binaries and libraries...
==> ERROR: A failure occurred in package().
    Aborting...
==> ERROR: Build failed, check /var/lib/aurbuild/x86_64/valandil/build
error: failed to build 'guix-1.3.0-1': failed to run: makechrootpkg -r /var/lib/aurbuild/x86_64 -D /var/lib/repo/aur -d /var/cache/pacman/pkg/ -- -feA --noconfirm --noprepare --holdver --nocheck: 
error: packages failed to build: guix-1.3.0-1

lantw44 commented on 2021-10-09 16:47 (UTC)

@vv111y Yes, you can build it in /tmp. For the guile-lib issue, you can patch the PKGBUILD of guile-lib like this:

diff --git a/PKGBUILD b/PKGBUILD
index 2b1f839..82b9f27 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -14,11 +14,11 @@ md5sums=('e52648afc567f202352e07e0ab732d79')
 build(){
   cd ${pkgname}-${pkgver}
   ./configure --prefix=/usr
-  make
+  make moddir=/usr/share/guile/site/2.2 godir=/usr/lib/guile/2.2/site-ccache
 }

 package() {
   cd ${pkgname}-${pkgver}
-  make DESTDIR="${pkgdir}" install
+  make moddir=/usr/share/guile/site/2.2 godir=/usr/lib/guile/2.2/site-ccache DESTDIR="${pkgdir}" install
   rm -f "${pkgdir}/usr/share/info/dir"
 }

Unfortunately, the maintainer of guile-lib doesn't respond to my comment: https://aur.archlinux.org/packages/guile-lib/#comment-812838.

vv111y commented on 2021-10-04 19:37 (UTC) (edited on 2021-10-05 15:38 (UTC) by vv111y)

I got this:

make[2]: Leaving directory '/home/will/.cache/yay/guix/src/guix-1.3.0'
make[1]: Leaving directory '/home/will/.cache/yay/guix/src/guix-1.3.0'
==> Starting check()...
==> ERROR: /home/will/.cache/yay/guix/src/guix-1.3.0 is too long.
==> ERROR: The working directory cannot be longer than 36 bytes.
==> ERROR: A failure occurred in check().

update: okay I see the comment in pkg-build. so what am I supposed to do? do a manual build in /tmp?

update II: Now I ran into the latest issue for guile-lib. I just used the alternative guix-installer package instead.

lantw44 commented on 2021-09-02 16:04 (UTC)

@cxor It is used to get the fish completion directory.

cxor commented on 2021-09-01 23:47 (UTC)

why is fish a dependency for this build? did someone watch too many distrotube videos?

lantw44 commented on 2021-07-18 10:29 (UTC)

@twilk I can't reproduce the error. For tests/go.scm, you probably have to patch guile-lib PKGBUILD because it doesn't install into the standard location.

diff --git a/PKGBUILD b/PKGBUILD
index 2b1f839..82b9f27 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -14,11 +14,11 @@ md5sums=('e52648afc567f202352e07e0ab732d79')
 build(){
   cd ${pkgname}-${pkgver}
   ./configure --prefix=/usr
-  make
+  make moddir=/usr/share/guile/site/2.2 godir=/usr/lib/guile/2.2/site-ccache
 }

 package() {
   cd ${pkgname}-${pkgver}
-  make DESTDIR="${pkgdir}" install
+  make moddir=/usr/share/guile/site/2.2 godir=/usr/lib/guile/2.2/site-ccache DESTDIR="${pkgdir}" install
   rm -f "${pkgdir}/usr/share/info/dir"
 }

twilk commented on 2021-07-16 19:39 (UTC) (edited on 2021-07-16 19:42 (UTC) by twilk)

Hi, I get unit test errors after building:

FAIL: tests/go.scm
FAIL: tests/git-authenticate.scm
FAIL: tests/channels.scm
FAIL: tests/git.scm

The full log of tests is here.

Errors include GPG errors from git:

error: gpg failed to sign the data
fatal: failed to write commit object

And even some errors from guile:

actual-error:
+ (unbound-variable
+   "module-lookup"
+   "Unbound variable: ~S"
+   (html->sxml)
+   #f)

[...]

Syntax error: unexpected token : (ghc-options (-Wall)) (at line 11, column 2)
Syntax error: unexpected end of input

[...]

Syntax error: unexpected token : (buildable (False)) (at line 12, column 4)
Syntax error: unexpected end of input

I have the following guile-* packages installed, which include all of this package's regular, build and optional guile-* dependencies:

  • guile 2.2.7-1
  • guile-avahi 0.4-1
  • guile-bytestructures 1.0.7-1
  • guile-gcrypt 0.3.0-1
  • guile-git-lib 0.5.1-1
  • guile-json 4.5.2-1
  • guile-lib 0.2.7-2
  • guile-lzlib 0.0.2-1
  • guile-semver 0.1.1-1
  • guile-sqlite3 0.1.3-1
  • guile-ssh 0.13.1-1
  • guile-zlib 0.1.0-1
  • guile-zstd 0.1.1-1

simona commented on 2020-11-30 15:11 (UTC)

new 1.2?

lantw44 commented on 2020-07-27 12:44 (UTC)

@simona The failed test came from https://aur.archlinux.org/packages/guile-git-lib, not guix.

simona commented on 2020-07-26 18:54 (UTC)

==> Avvio di check() in corso...
make check-TESTS
make[1]: ingresso nella directory «/home/simona/.cache/yay/guile-git-lib/src/guile-git-0.3.0»
make[2]: ingresso nella directory «/home/simona/.cache/yay/guile-git-lib/src/guile-git-0.3.0»
PASS: tests/blob.scm
PASS: tests/branch.scm
FAIL: tests/clone.scm
PASS: tests/commit.scm
PASS: tests/describe.scm
PASS: tests/oid.scm
PASS: tests/reference.scm
SKIP: tests/repository.scm
PASS: tests/reset.scm
PASS: tests/remote.scm
PASS: tests/rev-parse.scm
PASS: tests/status.scm
PASS: tests/submodule.scm
PASS: tests/tag.scm
PASS: tests/tree.scm
============================================================================
Testsuite summary for Guile-Git 0.3.0
============================================================================

TOTAL: 86
PASS: 82
SKIP: 1
XFAIL: 0
FAIL: 3
XPASS: 0
ERROR: 0

============================================================================
See ./test-suite.log
============================================================================

lantw44 commented on 2020-07-26 14:33 (UTC)

@simona I can't find tests/clone.scm in guix. Where does this test come from?

simona commented on 2020-07-07 16:57 (UTC)

FAIL: tests/clone.scm

lantw44 commented on 2020-06-13 09:28 (UTC)

@SArchB Please don't remove the length check. There are many tests assuming the path isn't too long, and tests/gexp.scm is just an example. I just got a successful build under the directory /home/lantw44/g.

SArchB commented on 2020-05-10 10:11 (UTC) (edited on 2020-05-10 10:12 (UTC) by SArchB)

Ok, so first this kept failing for me on the 'no longer then 36 bytes' issue, which for me seemed unsolvable since my '/home/username/.cache/yay/guix/src/' was already over 36 characters in length. So, I changed this limit in the PKGBUILD to skip the issue. The PKGBUILD stated the lenght check to be there to prevent tests/gexp.scm from failing, but later during the testfase the gexp file was automatically skipped.

Next though, the build still failed. Looking into the logs it failed multiple times for 2 specific reasons:

  1. It was unable to define my email address:

    fatal: unable to auto-detect email address (got 'username@computername. (none)')

  2. Many times it said:

    failed to download "/tmp/guix-file.7yoWNT" from https://hackage.haskell.org/package/foo/foo-1.0.0.tar.gz

The 2nd seems logical since https://hackage.haskell.org/package/foo/foo-1.0.0.tar.gz isn't a valid address, it should be https://hackage.haskell.org/package/foo-1.0/foo-1.0.tar.gz

So, in my experience, at this moment, this package won't build properly on the latest version or Arch.

lantw44 commented on 2020-03-21 15:22 (UTC)

@exaos Is it a networking issue? I just tested it in a clean VM and there are no failed tests. Do you have logs for debugging?

exaos commented on 2020-03-10 03:52 (UTC) (edited on 2020-03-10 06:21 (UTC) by exaos)

Building failed at the end of process:

==> 正在开始 check()...
==> 错误: /home/vivodo/.cache/yay/guix/src/guix is too long.
==> 错误: The working directory cannot be longer than 36 bytes.
==> 错误: 在 check() 中发生一个错误。
    正在放弃...
Error making: guix

It seems related to the long path name. So I moved the full building path into /tmp, and tried again. make check failed on:

- FAIL: tests/containers.scm
- FAIL: tests/guix-environment-container.sh

lantw44 commented on 2020-02-27 15:39 (UTC)

@azmeuk I don't know why guile-json was deleted, and I just typed 'ssh aur@aur4.archlinux.org restore guile-json' to restore guile-json package. Does it work for you now?

azmeuk commented on 2020-02-14 10:05 (UTC)

It seems the package has a dependency problem with guile-json (even with guile-json1 installed):

% yay -S guix --noconfirm            
:: There are 2 providers available for guix:
:: Repository AUR
    1) guix 2) guix-git 

Enter a number (default=1): 1
==> Error: Could not find all required packages:
    guile-json>=3 (Wanted by: guix)

yay -Ss guile-json     
aur/guile-json1 1.3.2-1 (+1 0.00%) (Installed)
    JSON module for Guile (Version 1)

lantw44 commented on 2019-09-18 06:29 (UTC)

I updated the package to a newer commit on the master branch. It should pass all tests and 'guix pull' should works now.

theYinYeti commented on 2019-08-08 11:00 (UTC)

If that’s any help, here’s a part of the process tree:

└─test-env,6734 ./test-env --quiet-stderr /usr/bin/guile --no-auto-compile -e main ./build-aux/test-driver.scm --test-name tests/processes.scm --log-file tests/processes.log --trs-file tests/processes.trs --color-tests yes --enable-hard-errors yes --expect-failure no --brief=yes -- ./tests/processes.scm
    ├─guile,6753 --no-auto-compile -e main ./build-aux/test-driver.scm --test-name tests/processes.scm --log-file tests/processes.log --trs-file tests/processes.trs --color-tests yes --enable-hard-errors yes --expect-failure no --brief=yes -- ./tests/processes.scm
    │   ├─{guile},6756
    │   ├─{guile},6757
    │   ├─{guile},6758
    │   └─{guile},6759
    └─guix-daemon,6742 --disable-chroot --substitute-urls=file:///home/yves/guix/src/guix-1.0.1/t/var/6734/substituter-data
        └─guix-daemon,6761 6753             --substitute-urls=file:///home/yves/guix/src/guix-1.0.1/t/var/6734/substituter-data
            └─guix substitute,6763 \\ /home/yves/guix/src/guix-1.0.1/scripts/guix substitute --query
                ├─{guix substitute},6764
                ├─{guix substitute},6765
                ├─{guix substitute},6766
                ├─{guix substitute},6767
                └─{guix substitute},6768

and here’s gdb’s stacktrace for process 6763:

#0  0x00007f191586ae5b in select () from /usr/lib/libc.so.6
#1  0x00007f19159f0c9c in ?? () from /usr/lib/libguile-2.2.so.1
#2  0x00007f1915725baf in ?? () from /usr/lib/libgc.so.1
#3  0x00007f19157196d5 in ?? () from /usr/lib/libgc.so.1
#4  0x00007f191571f7cc in GC_do_blocking () from /usr/lib/libgc.so.1
#5  0x00007f19159f194b in scm_without_guile () from /usr/lib/libguile-2.2.so.1
#6  0x00007f19159f1bcc in scm_std_select () from /usr/lib/libguile-2.2.so.1
#7  0x00007f19159f26ac in scm_std_usleep () from /usr/lib/libguile-2.2.so.1
#8  0x00007f19159d0293 in scm_usleep () from /usr/lib/libguile-2.2.so.1
#9  0x00007f19159fed2c in ?? () from /usr/lib/libguile-2.2.so.1
#10 0x00007f1915a04701 in scm_call_n () from /usr/lib/libguile-2.2.so.1
#11 0x00007f1915981119 in scm_primitive_eval () from /usr/lib/libguile-2.2.so.1
#12 0x00007f191599f38b in scm_primitive_load () from /usr/lib/libguile-2.2.so.1
#13 0x00007f191599fd09 in scm_primitive_load_path () from /usr/lib/libguile-2.2.so.1
#14 0x00007f19159fed2c in ?? () from /usr/lib/libguile-2.2.so.1
#15 0x00007f1915a04701 in scm_call_n () from /usr/lib/libguile-2.2.so.1
#16 0x00007f1915981119 in scm_primitive_eval () from /usr/lib/libguile-2.2.so.1
#17 0x00007f191598117a in scm_eval () from /usr/lib/libguile-2.2.so.1
#18 0x00007f19159d0f6b in scm_shell () from /usr/lib/libguile-2.2.so.1
#19 0x00007f19159991be in ?? () from /usr/lib/libguile-2.2.so.1
#20 0x00007f1915979b0a in ?? () from /usr/lib/libguile-2.2.so.1
#21 0x00007f19159fed2c in ?? () from /usr/lib/libguile-2.2.so.1
#22 0x00007f1915a04701 in scm_call_n () from /usr/lib/libguile-2.2.so.1
#23 0x00007f19159f2ad4 in ?? () from /usr/lib/libguile-2.2.so.1
#24 0x00007f191597a147 in ?? () from /usr/lib/libguile-2.2.so.1
#25 0x00007f191597a226 in scm_c_with_continuation_barrier () from /usr/lib/libguile-2.2.so.1
#26 0x00007f19159f14df in ?? () from /usr/lib/libguile-2.2.so.1
#27 0x00007f191571f765 in GC_call_with_stack_base () from /usr/lib/libgc.so.1
#28 0x00007f19159f18d9 in scm_with_guile () from /usr/lib/libguile-2.2.so.1
#29 0x00007f19159993b4 in scm_boot_guile () from /usr/lib/libguile-2.2.so.1
#30 0x0000563f692f1093 in ?? ()
#31 0x00007f191579dee3 in __libc_start_main () from /usr/lib/libc.so.6
#32 0x0000563f692f114e in ?? ()

joemaro commented on 2019-07-27 19:22 (UTC) (edited on 2019-07-27 19:26 (UTC) by joemaro)

guile-ssh fails, here's the output of guile-ssh/src/guile-ssh-0.11.3/tests/test-suite.log https://pastebin.com/tWbX48Xw

i also get failed tests:

PASS: log.scm
PASS: server.scm
PASS: session.scm
PASS: client-server.scm
PASS: popen.scm
PASS: shell.scm
PASS: server-client.scm
PASS: sssh-ssshd.scm
FAIL: key.scm
PASS: tunnel.scm
PASS: dist.scm

but the script doesn't hang, just notifies of the failing and exits.

theYinYeti commented on 2019-07-13 11:28 (UTC)

Hi! During the build, I get failed tests:

…
PASS: tests/substitute.scm
FAIL: tests/builders.scm
FAIL: tests/derivations.scm
PASS: tests/glob.scm
FAIL: tests/grafts.scm  
PASS: tests/ui.scm
PASS: tests/status.scm  
PASS: tests/records.scm 

and then the build just freezes at this last “PASS” line: nothing more happens, the CPU does not seem to do anything…

lantw44 commented on 2019-07-11 09:28 (UTC)

@Ovsyanka Yes, I will do it once gnutls 3.6.8-3 enters core repository. It is still in testing.

Ovsyanka commented on 2019-07-10 15:38 (UTC) (edited on 2019-07-10 15:38 (UTC) by Ovsyanka)

Loolks like now it should depend on the gnutls package instead of gnutls-guile. According to this change https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/gnutls&id=28128ef0d8c273c6876c885c96a25d649a6d9876 gnutls now made with the guile support.

lantw44 commented on 2019-07-10 15:28 (UTC)

I can reproduce the issue, but I haven't spent time figuring out how to resolve it. As a workaround, you can install guix with guix, switch from guix-daemon.service to guix-daemon-latest.service, and use ~/.guix-profile/bin/guix to pull.

sikmir commented on 2019-07-03 11:31 (UTC)

After uninstall/install guix:

$ guix pull
...
srfi/srfi-19.scm:420:2: In procedure time-difference!:
In procedure time-difference!: TIME-ERROR type incompatible-time-types: (#<time type: time-tai nanosecond: 514001000 second: 1562153361> . #<time type: time-monotonic nanosecond: 511605000 second: 1562153361>)

lantw44 commented on 2019-05-31 08:56 (UTC)

@sikmir If you already have an old version of guix package installed on the system, you have to remove it before building the new version.

sikmir commented on 2019-05-31 07:28 (UTC)

ERROR: In procedure %resolve-variable:
error: glibc-supported-locales: unbound variable
make[2]: *** [Makefile:5731: make-go] Error 1

lantw44 commented on 2019-05-21 17:15 (UTC)

@joz If you want to run tests, please build the package in a directory with a shorter path. For example, It is OK to build and test the package in /home/lantw44/guix, but you won't be able to run the test if you build it in /home/lantw44/aur/guix because the length of /home/lantw44/aur/guix/src/guix-1.0.0 is 37 bytes. The reason of having the check is that lengths of UNIX domain sockets and shebangs are limited.

joz commented on 2019-05-21 10:22 (UTC)

Hi, this fails for me with "The working directory cannot be longer than 36 bytes."

However, if I make the check() function a dummy one (return 0), the package gets built.

lantw44 commented on 2019-05-16 12:59 (UTC)

@doronbehar Thanks for your gnutls-guile package. I will switch this package to use gnutls-guile on the next update.

I am still working on the patch to update guix to 1.0.0. There are still a few failed tests, and I am trying to resolve them. I cannot apply your patch because you removed a lot of necessary things.

commented on 2019-05-12 11:42 (UTC)

If anyone is interested, here is my patch for the 1.0.0 release:

diff --git i/PKGBUILD w/PKGBUILD
index 33280c1..f18bac3 100644
--- i/PKGBUILD
+++ w/PKGBUILD
@@ -6,7 +6,7 @@
 #   gpg --recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5

 pkgname=guix
-pkgver=0.16.0
+pkgver=1.0.0
 pkgrel=1
 pkgdesc="A purely functional package manager for the GNU system"
 arch=('x86_64' 'i686' 'armv7h')
@@ -14,8 +14,6 @@ url="https://www.gnu.org/software/guix/"
 license=('GPL3')
 options=('!strip')
 makedepends=(
-  'bash-completion'
-  'fish'
   'guile-json'
   'guile-ssh>=0.10.2'
   'help2man')
@@ -26,103 +24,31 @@ depends=(
   'guile-sqlite3'
   'sqlite>=3.6.19'
   'bzip2'
-  'gnutls'
+  'gnutls-guile' # AUR
   'libgcrypt'
   'zlib')
 optdepends=(
-  'bash-completion: to enable bash programmable completion'
   'guile-json: to import packages from cpan, gem, pypi'
   'guile-ssh: to offload builds to other machines')
 source=(
-  "https://alpha.gnu.org/gnu/${pkgname}/${pkgname}-${pkgver}.tar.gz"{,.sig}
-  "aarch64-linux-20170217-guile-2.0.14.tar.xz::https://alpha.gnu.org/gnu/${pkgname}/bootstrap/aarch64-linux/20170217/guile-2.0.14.tar.xz"
-  "aarch64-linux-20170217-guile-2.0.14.tar.xz.sig::https://alpha.gnu.org/gnu/${pkgname}/bootstrap/aarch64-linux/20170217/guile-2.0.14.tar.xz.sig"
-  "armhf-linux-20150101-guile-2.0.11.tar.xz::https://alpha.gnu.org/gnu/${pkgname}/bootstrap/armhf-linux/20150101/guile-2.0.11.tar.xz"
-  "armhf-linux-20150101-guile-2.0.11.tar.xz.sig::https://alpha.gnu.org/gnu/${pkgname}/bootstrap/armhf-linux/20150101/guile-2.0.11.tar.xz.sig"
-  "i686-linux-20131110-guile-2.0.9.tar.xz::https://alpha.gnu.org/gnu/${pkgname}/bootstrap/i686-linux/20131110/guile-2.0.9.tar.xz"
-# "i686-linux-20131110-guile-2.0.9.tar.xz.sig::https://alpha.gnu.org/gnu/${pkgname}/bootstrap/i686-linux/20131110/guile-2.0.9.tar.xz.sig"
-  "mips64el-linux-20131110-guile-2.0.9.tar.xz::https://alpha.gnu.org/gnu/${pkgname}/bootstrap/mips64el-linux/20131110/guile-2.0.9.tar.xz"
-# "mips64el-linux-20131110-guile-2.0.9.tar.xz.sig::https://alpha.gnu.org/gnu/${pkgname}/bootstrap/mips64el-linux/20131110/guile-2.0.9.tar.xz.sig"
-  "x86_64-linux-20131110-guile-2.0.9.tar.xz::https://alpha.gnu.org/gnu/${pkgname}/bootstrap/x86_64-linux/20131110/guile-2.0.9.tar.xz"
-# "x86_64-linux-20131110-guile-2.0.9.tar.xz.sig::https://alpha.gnu.org/gnu/${pkgname}/bootstrap/x86_64-linux/20131110/guile-2.0.9.tar.xz.sig"
+  "https://ftp.gnu.org/gnu/${pkgname}/${pkgname}-${pkgver}.tar.gz"{,.sig}
 )
 install="${pkgname}.install"
-sha1sums=(
-  '62f665dc02ea4c575f75b6728d6ec62875206846'
-  'ae4ded76633ff0d37c5297f457542cee2e6ee205'
-  'SKIP'
-  'SKIP'
-  'SKIP'
-  'SKIP'
-  'SKIP'
-# 'SKIP'
-  'SKIP'
-# 'SKIP'
-  'SKIP'
-# 'SKIP'
-)
-sha256sums=(
-  'SKIP'
-  'SKIP'
-  '3939909f24dcb955621aa7f81ecde6844bea8a083969c2d275c55699af123ebe'
-  'bfceb1a0cb92c9182e5bc2bfe9e728078df0f5f86e6580820ead845d7f11f3c5'
-  'e551d05d4d385d6706ab8d574856a087758294dc90ab4c06e70a157a685e23d6'
-  '4ceb3b490e2eed1631ec204d68ebf2a91806f6d1c438fc3a8d744b3f0351633d'
-  'b757cd46bf13ecac83fb8e955fb50096ac2d17bb610ca8eb816f29302a00a846'
-# '5c710ad8efa927711347cb585ceec25d99c3b3065955060275076be55f46f228'
-  '994680f0001346864aa2c2cc5110f380ee7518dcd701c614291682b8e948f73b'
-# 'd22c325e7d64b805679cc449b8865f7ac7629b83c71a6ae9812541408bac1952'
-  '037b103522a2d0d7d69c7ffd8de683dfe5bb4b59c1fafd70b4ffd397fd2f57f0'
-# '50ec32f47dd659583d7ee633b8d6d4180b413c3680b1628ab6346241ac2c2b46'
-)
-validpgpkeys=('3CE464558A84FDC69DB40CFB090B11993D9AEBB5')
-noextract=(
-  'aarch64-linux-20170217-guile-2.0.14.tar.xz'
-  'armhf-linux-20150101-guile-2.0.11.tar.xz'
-  'i686-linux-20131110-guile-2.0.9.tar.xz'
-  'mips64el-linux-20131110-guile-2.0.9.tar.xz'
-  'x86_64-linux-20131110-guile-2.0.9.tar.xz')
-_noextract_dest_map=(
-  'gnu/packages/bootstrap/aarch64-linux/guile-2.0.14.tar.xz'
-  'gnu/packages/bootstrap/armhf-linux/guile-2.0.11.tar.xz'
-  'gnu/packages/bootstrap/i686-linux/guile-2.0.9.tar.xz'
-  'gnu/packages/bootstrap/mips64el-linux/guile-2.0.9.tar.xz'
-  'gnu/packages/bootstrap/x86_64-linux/guile-2.0.9.tar.xz')

-prepare() {
-   cd "${srcdir}/${pkgname}-${pkgver}"
-   for index in $(seq 0 $((${#noextract[@]} - 1))); do
-       cp "${srcdir}/${noextract[${index}]}" "${_noextract_dest_map[${index}]}"
-   done
-}
+sha256sums=('fbe519dabc4cff8c2cd9ceb57609290518bca6536626dec837817a0261352598'
+            'SKIP')
+validpgpkeys=('3CE464558A84FDC69DB40CFB090B11993D9AEBB5')

 build() {
-   local bash_completion_dir="$(pkg-config --variable=completionsdir bash-completion)"
-   local fish_completion_dir="$(pkg-config --variable=completionsdir fish)"
    cd "${srcdir}/${pkgname}-${pkgver}"
    ./configure --prefix=/usr --sbindir=/usr/bin --sysconfdir=/etc \
        --libexecdir="/usr/lib/${pkgname}" --localstatedir=/var \
-       --with-bash-completion-dir="${bash_completion_dir}" \
-       --with-fish-completion-dir="${fish_completion_dir}" \
-       --disable-rpath
+       --with-bash-completion-dir=/usr/share/bash-completion/completions \
+       --disable-rpath 
    make
 }

 check() {
-   # FIXME: There are too many failed tests and upstream developers haven't
-   # made any response. All tests are temporarily skipped for now.
-   # https://debbugs.gnu.org/32098
-   return 0
-
-   cd "${srcdir}/${pkgname}-${pkgver}"
-   # Check whether the current working directory is too long
-   local cwd_str="$(pwd)"
-   local cwd_len="${#cwd_str}"
-   if [ "${cwd_len}" -gt 46 ]; then
-       error "${cwd_str} is too long."
-       error "The working directory cannot be longer than 46 bytes."
-       false
-   fi
    # Make sure we have a valid shell accepting -c option
    SHELL=/bin/sh make check
 }
@@ -132,67 +58,10 @@ package() {
    make DESTDIR="${pkgdir}" install
    # Remove unused upstart service files
    rm -r "${pkgdir}/usr/lib/upstart"
-   # Rename systemd service files provided by upstream because they are not
-   # usable without previous guix installation
-   local system_unit_dir="${pkgdir}/usr/lib/systemd/system"
-   local guix_daemon_default="${system_unit_dir}/guix-daemon.service"
-   local guix_daemon_upstream="${system_unit_dir}/guix-daemon-latest.service"
-   local guix_publish_default="${system_unit_dir}/guix-publish.service"
-   local guix_publish_upstream="${system_unit_dir}/guix-publish-latest.service"
-   mv "${guix_daemon_default}" "${guix_daemon_upstream}"
-   mv "${guix_publish_default}" "${guix_publish_upstream}"
-   # Generate default systemd service files from upstream ones by fixing paths
-   local guix_profile_root="/var/guix/profiles/per-user/root/current-guix"
-   sed -e "s|^ExecStart=${guix_profile_root}/bin|ExecStart=/usr/bin|" \
-       -e "s|^Description=\(.*\)|Description=\1 (default)|" \
-       -e "/^Environment=/d" "${guix_daemon_upstream}" \
-       > "${guix_daemon_default}"
-   sed -e "s|^ExecStart=${guix_profile_root}/bin|ExecStart=/usr/bin|" \
-       -e "s|^Description=\(.*\)|Description=\1 (default)|" \
-       -e "/^Environment=/d" "${guix_publish_upstream}" \
-       > "${guix_publish_default}"
-   # Make sure the above sed commands really work
-   ! cmp "${guix_daemon_default}" "${guix_daemon_upstream}"
-   ! cmp "${guix_publish_default}" "${guix_publish_upstream}"
-   # Edit the description of upstream systemd service files
-   sed -i "s|^Description=\(.*\)|Description=\1 (upstream)|" \
-       "${guix_daemon_upstream}" "${guix_publish_upstream}"
-   # The default makepkg strip option cannot be used here because binaries
-   # installed in /usr/share must not be stripped.
-   # To keep user-defined 'strip' and 'debug' options useful, we still
-   # depend on 'tidy_strip' function provided by makepkg to do the stripping
-   # work. To make the function useful, we have to temporarily remove the
-   # '!strip' option from 'options' array. However, assignments to 'options'
-   # cause mksrcinfo to insert wrong lines to .SRCINFO, so they have to be
-   # put in eval.
    eval 'options=()'
    cd "${pkgdir}/usr/bin"
    tidy_strip
    cd "${pkgdir}/usr/lib/guix"
    tidy_strip
    eval 'options=("!strip")'
-   # Make sure bootstrap binaries are not modified
-   cd "${pkgdir}/usr/share/guile/site/2.2/gnu/packages/bootstrap"
-   cat << EOF | sha256sum -c
-e3bf6ffe357eebcc28221ffdbb5b00b4ed1237cb101aba4b1b8119b08c732387  aarch64-linux/bash
-444c2af9fefd11d4fc20ee9281fa2c46cbe3cfb3df89cc30bcd50d20cdb6d6c0  aarch64-linux/mkdir
-05273f978a072269193e3a09371c23d6d149f6d807f8e413a4f79aa5a1bb6f25  aarch64-linux/tar
-48e9baa8a6c2527a5b4ecb8f0ac87767e2b055979256acab2a3dbff4f6171637  aarch64-linux/xz
-2ad82bb9ee6e77eaff284222e1d43a2829b5a1e2bcf158b08564a26da48e0045  armhf-linux/bash
-a19e386b31ebc8a46b5f934c11bca86e28f8aa997272a5fcd052b52d5019f790  armhf-linux/mkdir
-da56be0b332fac3880b151abe60c1eeb2649cd192379b18658b1d872f7aa53e8  armhf-linux/tar
-6507d04d55210e3a8cdc2e5758d79a4b0da3cb53bb142f60a78788af7b915ab1  armhf-linux/xz
-ed059a9ae964d538605c923c4e73128bd5ca912994709b3fe2d71d061751e8c5  i686-linux/bash
-b369264bda7bbb98d1acf0bf53ebc9077e82f48b190f3956fa23cb73d6e99f92  i686-linux/mkdir
-9f7e79e52aa369fc9ed69359e503d4f8179117842df8261fc0cae5629cc896cb  i686-linux/tar
-d23173dfe66c41e1c8d8eef905d14d1f39aaa52c9d70621f366c275e9139b415  i686-linux/xz
-213cfb8794ffdf4a71cb321a89987ee61704edcec5d1203912575f0a626a239c  mips64el-linux/bash
-d436070fde044366d72d7e59d8d12b1ba72b32d7b0f13e409b61118bdc8254c8  mips64el-linux/mkdir
-d27fcb52f9b4a42fafdae3164fffd200f52e04d142574dcf06212dbf7701cbb8  mips64el-linux/tar
-107eac7523b0148d18f461d81bec9d0db6154d6c61e4caf3a4cdb43a9a6afb3c  mips64el-linux/xz
-265d2f633a5ab35747fc4836b5e3ca32bf56ad44cc24f3bd358f1ff6cf0779a5  x86_64-linux/bash
-50689abdf2d5374e17ea8c51801f04f7590ad604af33a12a940cc11d137a4a2f  x86_64-linux/mkdir
-16440b4495a2ff9c6aa50c05a8c9066e1004a5990b75aa891f08cdf8753c8689  x86_64-linux/tar
-930ad7e88ca0b2275dc459b24aea912fadd5b7c9e95be06788d4b61efc7ef470  x86_64-linux/xz
-EOF
 }

lantw44 commented on 2019-03-28 14:09 (UTC)

@kapcom01 This is not a packaging problem. Please read https://wiki.archlinux.org/index.php/Makepkg#ERROR:_One_or_more_PGP_signatures_could_not_be_verified!.

kapcom01 commented on 2019-03-26 22:10 (UTC) (edited on 2019-03-26 22:12 (UTC) by kapcom01)

I get this error:

==> Verifying source file signatures with gpg...
    guix-0.16.0.tar.gz ... FAILED (unknown public key 090B11993D9AEBB5)
    aarch64-linux-20170217-guile-2.0.14.tar.xz ... FAILED (unknown public key 090B11993D9AEBB5)
    armhf-linux-20150101-guile-2.0.11.tar.xz ... FAILED (unknown public key 090B11993D9AEBB5)
==> ERROR: One or more PGP signatures could not be verified!
Error downloading sources: guix

sngn commented on 2019-03-10 18:08 (UTC)

@lantw44 you are probably right, I was looking through this a few weeks ago and do not remember my findings clearly.

Anyways, it is more hassle to maintain a custom gnutls package (though there might be one on the AUR, or someone could put it up), than to install directly, and not be dependent on arch packages.

lantw44 commented on 2019-03-10 13:39 (UTC)

@sngn GnuTLS enables Guile binding automatically when Guile is found on the system. Since 'make' package on Arch Linux is built with Guile enabled, GnuTLS should be able to find Guile because 'make' is a part of 'base-devel'. It is the Arch Linux maintainer of 'gnutls' package that disables Guile binding explicitly. In fact, 'gnutls' package had been built with Guile enabled for a few years. It got disabled when 'gnutls' was updated to 3.6.

sngn commented on 2019-03-10 08:07 (UTC)

For anyone who wants to install guix right now..

I successfully built gnutls with guile bindings and installed this guix package.

Though I uninstalled again and followed guix manual for binary installation.. which is the way I would recommend if you want to install guix on arch right now.

I don't think that arch gnutls is gonna build against guile in the near future, because upstream doesn't and that's kind of the whole point of arch, that you get 'pure' packages, meaning as close to upstream as possible.

lantw44 commented on 2018-12-16 11:05 (UTC)

I reported the problem to Arch Linux bug tracker: https://bugs.archlinux.org/task/61095.

sikmir commented on 2018-12-12 12:41 (UTC)

@lantw44 It's already in core repository:

upgpkg: gnutls 3.6.5-1
upstream update 3.6.5 - move to new stable branch, drop guile bindings as they don't build currently with recent guile 2.2.x branch

lantw44 commented on 2018-12-10 13:10 (UTC)

Did you use gnutls from testing? It seems that gnutls in testing is built with guile disabled.

sikmir commented on 2018-12-07 17:30 (UTC)

ERROR: Makepkg was unable to build guix:

checking if (gnutls) is available... no
configure: error: The Guile bindings of GnuTLS are missing; please install them.

lantw44 commented on 2018-11-02 15:39 (UTC)

The file /gnu/store/gz3agxnnlgkafw2c8jnvk2hqmlh85pkc-guile-bootstrap-2.0.drv exists on my system. Is it a clean installation? If it isn't, you can try to rename or remove /gnu/store and /var/guix. I remember that guix-daemon automatically creates and copies files to /gnu/store when it is started the first time.

guix-daemon.service is the one you should use if you install guix with AUR. guix-daemon-latest.service is the one shipped by the upstream and it can only be used when you have guix installed by guix using root account. This means you have to run 'guix package -i guix' as root before you can use guix-daemon-latest.service.

dpriskorn commented on 2018-10-29 21:30 (UTC) (edited on 2018-10-29 21:31 (UTC) by dpriskorn)

The installation went fine but neither guix-daemon or guix-daemon-latest seem to work.

guix-daemon throws this error when a any guix command (e.g. guix environment --pure guix) is run:

guix environment: error: build failed: opening file `/gnu/store/gz3agxnnlgkafw2c8jnvk2hqmlh85pkc-guile-bootstrap-2.0.drv': Filen eller katalogen finns inte

guix-daemon-latest does not start:

okt 29 22:29:31 parabola systemd[30059]: guix-daemon-latest.service: Failed to execute command: No such file or directory

okt 29 22:29:31 parabola systemd[30059]: guix-daemon-latest.service: Failed at step EXEC spawning /var/guix/profiles/per-user/root/guix-prof>

okt 29 22:29:31 parabola systemd[1]: guix-daemon-latest.service: Main process exited, code=exited, status=203/EXEC

okt 29 22:29:31 parabola systemd[1]: guix-daemon-latest.service: Failed with result 'exit-code'.

urbanslug commented on 2018-08-02 19:56 (UTC) (edited on 2018-08-02 19:57 (UTC) by urbanslug)

@zeronineseven did your problem have to do with guile-ssh? why do we need guile-ssh again? guile-ssh fails for me on btrfs with https://lpaste.net/3282218839441408000

zeronineseven commented on 2018-05-10 17:27 (UTC)

I've successfully built guix on btrfs partition. Will report upstream. Thx!

lantw44 commented on 2018-05-10 15:07 (UTC)

I haven't spent time debugging this issue. If you can reproduce it on upstream git master, please report this tmpfs-related problem to the upstream bug tracker. Does guix tests pass if you build it on a filesystem which is not tmpfs?

zeronineseven commented on 2018-05-08 20:35 (UTC)

In fact my /tmp is actually mounted as tmpfs =/

lantw44 commented on 2018-05-08 14:22 (UTC)

It looks like it is an issue related to tmpfs, again ...

zeronineseven commented on 2018-05-08 09:18 (UTC)

lantw44, I ran the build on my host machine without manual chroot/container - no virtualization was involved except the one used by makepkg itself (fakeroot?). I'm not sure how can I test unprivileged user namespace functionality directly but I believe that it's working fine - I have unprivileged lxcs running on this machine and "unshare" command has spawned new bash session without any errors.

lantw44 commented on 2018-05-07 15:58 (UTC)

Did you run the test inside a chroot or a container? Can you use 'unshare' to successfully create an unprivileged user namespace in the environment you ran the test?

zeronineseven commented on 2018-05-06 21:58 (UTC)

Hi, It seems that I can't build guix due to failing tests/guix-environment-container. AFAIK this is related to userns but "cat /proc/sys/kernel/unprivileged_userns_clone" returns 1 and in fact I have unprivileged lxcs running on the very same host. test-suite.log content is here: http://paste.debian.net/1023605/

lantw44 commented on 2018-05-05 11:21 (UTC)

Hello, you can find the information on Arch wiki: https://wiki.archlinux.org/index.php/Guix.

dpriskorn commented on 2018-05-05 07:25 (UTC)

Hi. Installed this recently.

I missed an explanation post-install that explains to me that I have to enable and start the daemon and add the buildusers to be able to run/use guix at all. Alternatively that the package sets it all up and remains quiet.

T-recks commented on 2018-03-18 20:42 (UTC)

Ah, you're right. Thanks for the response and for maintaining this package. Everything went smoothly for me once I followed the below example and changed DNS servers to pass some of the check() tests.

lantw44 commented on 2018-03-18 12:41 (UTC)

/gnu and /var/guix will be created by guix-daemon when you start the service the first time.

T-recks commented on 2018-03-18 10:53 (UTC)

Installing with this package build produced no /gnu directory and no /var/guix directory for me. Is this supposed to be the case or did I do something wrong?

stefanc_diff commented on 2017-11-19 11:15 (UTC) (edited on 2017-11-19 11:21 (UTC) by stefanc_diff)

This AUR package will build with pacaur only if the user edits the PKGBUILD file and removes/comments the check() function. Otherwise the check() function gives this error: ==> ERROR: The working directory cannot be longer than 46 bytes I was able to build the guix package and test it in a clean VM, it doesn't build on my archlinux host and it can't be built easily with the devtools since the guix AUR package requires other 2 AUR packages as build dependencies. You still have to follow the guix manual to run the additional steps after install manually for now.

g99 commented on 2017-10-08 17:07 (UTC)

builds well with yaourt (apacman), but not pacaur (key missing). guix root service startable, but addgroup and all other setup must be done manually still.

fusion809 commented on 2017-10-05 04:08 (UTC)

For me I get the build error: GUILEC gnu/build/linux-container.go GUILEC gnu/build/linux-initrd.go GUILEC gnu/build/linux-modules.go GUILEC gnu/build/marionette.go GUILEC gnu/build/shepherd.go ;;; Failed to autoload read-pid-file in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload read-pid-file in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload exec-command in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload read-pid-file in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload read-pid-file in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload exec-command in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload read-pid-file in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) gnu/build/shepherd.scm:98:13: warning: possibly unbound variable `read-pid-file' gnu/build/shepherd.scm:159:32: warning: possibly unbound variable `exec-command' gnu/build/shepherd.scm:170:14: warning: possibly unbound variable `read-pid-file' ;;; Failed to autoload read-pid-file in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload exec-command in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload read-pid-file in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload read-pid-file in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload exec-command in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) ;;; Failed to autoload read-pid-file in (shepherd service): ;;; ERROR: missing interface for module (shepherd service) GUILEC gnu/build/vm.go GUILEC gnu/tests.go GUILEC gnu/tests/base.go GUILEC gnu/tests/dict.go GUILEC gnu/tests/nfs.go GUILEC gnu/tests/install.go GUILEC gnu/tests/mail.go GUILEC gnu/tests/messaging.go GUILEC gnu/tests/networking.go GUILEC gnu/tests/ssh.go GUILEC gnu/tests/web.go GUILEC guix/docker.go GUILEC guix/import/cpan.go GUILEC guix/import/crate.go GUILEC guix/import/gem.go GUILEC guix/import/github.go GUILEC guix/import/json.go GUILEC guix/import/pypi.go GUILEC guix/import/stackage.go GUILEC guix/scripts/import/crate.go GUILEC guix/scripts/import/gem.go GUILEC guix/scripts/import/pypi.go GUILEC guix/scripts/import/stackage.go GUILEC guix/ssh.go GUILEC guix/scripts/copy.go GUILEC guix/store/ssh.go GUILEC guix/scripts/offload.go GUILEC guix/config.go GUILEC guix/tests.go GUILEC guix/tests/http.go Some deprecated features have been used. Set the environment variable GUILE_WARN_DEPRECATED to "detailed" and rerun the program to get more information. Set it to "no" to suppress this message. GEN etc/guix-daemon.service GEN etc/guix-publish.service GEN etc/guix-daemon.conf GEN etc/guix-publish.conf make[2]: Leaving directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.13.0' make[1]: Leaving directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.13.0'

plattfot commented on 2017-09-13 05:11 (UTC)

Had some issues running guix build, got these errors: guix: offload: command not found Try `guix --help' for more information. guix build: error: build failed: unexpected EOF reading a line Turns out that the guile path isn't properly set up. After some help from the mailing list, I managed to fix it by running: systemctl edit guix-daemon And added: [Service] Environment=GUILE_LOAD_PATH=/root/.guix-profile/share/guile/site/2.2 Environment=GUILE_LOAD_COMPILED_PATH=/root/.guix-profile/lib/guile/2.2 Note that I've run guix pull and it's now using guile 2.2 and not 2.0. Not sure if this should be added to the package or mentioned in the wiki.

lantw44 commented on 2017-07-25 12:59 (UTC) (edited on 2017-07-25 13:00 (UTC) by lantw44)

If you want to run the check, you cannot build it in a directory with long path name because there are limits on the length of shebang and unix socket path.

Plexcon commented on 2017-07-25 11:59 (UTC) (edited on 2017-07-25 12:23 (UTC) by Plexcon)

==> Verificando las firmas de las fuentes con gpg... guix-0.13.0.tar.gz ... HA FALLADO (clave pública desconocida 090B11993D9AEBB5) aarch64-linux-20170217-guile-2.0.14.tar.xz ... HA FALLADO (clave pública desconocida 090B11993D9AEBB5) armhf-linux-20150101-guile-2.0.11.tar.xz ... HA FALLADO (clave pública desconocida 090B11993D9AEBB5) ==> ERROR: ¡No se ha podido verificar alguna de las firmas PGP! $ gpg --recv-keys 090B11993D9AEBB5 ==> Iniciando check()... ==> ERROR: /tmp/pamac-build-kantergos/guix/src/guix-0.13.0 is too long. ==> ERROR: The working directory cannot be longer than 46 bytes. ==> ERROR: Se produjo un fallo en check(). Cancelando...

lantw44 commented on 2017-03-25 13:52 (UTC)

You have to download the public key to verify the signature. Please see the comment at the top of PKGBUILD.

shillshocked commented on 2017-03-24 04:18 (UTC)

==> Verifying source file signatures with gpg... guix-0.12.0.tar.gz ... FAILED (error during signature verification) ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build .

Pelzflorian commented on 2016-12-26 18:16 (UTC)

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 (UTC) (edited on 2016-12-26 17:17 (UTC) by lantw44)

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 (UTC)

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 (UTC)

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

Reded commented on 2016-12-17 13:44 (UTC)

Getting a build failure that doesn't seem to be the same as rafaelff's - http://termbin.com/r60f 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 (UTC)

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 (UTC)

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 http://dnserros.oi.com.br instead of failing.

rafaelff commented on 2016-11-06 13:30 (UTC)

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: https://ptpb.pw/Wfae test-suite.log: https://ptpb.pw/RthO

fusion809 commented on 2016-11-06 13:04 (UTC) (edited on 2016-11-06 13:20 (UTC) by fusion809)

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 (UTC)

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

rafaelff commented on 2016-11-04 18:34 (UTC)

Compilation looks good, but check() reports 9 errors. With check() disabled (commented), no problems are displayed and package() finishes without issue. Build & Check log: https://ptpb.pw/UY2w test-suite.log: https://ptpb.pw/CxnE

lantw44 commented on 2016-11-04 12:38 (UTC)

It should be fixed in 0.11.0-3 now. I pulled two patches from upstream git repo to fix it.

lantw44 commented on 2016-11-03 17:31 (UTC)

It seems it is caused by the update to guile 2.0.13. guile 2.0.12 doesn't have this problem. I am still finding ways to fix it. Thanks for your reporting.

rafaelff commented on 2016-11-01 15:36 (UTC)

I'm unable to build this package. Full build log can be seen here: http://pastie.org/10953882 . What could be wrong?

wilfred commented on 2016-09-04 03:14 (UTC)

Note that you will need to create a guixbuild group and some users before you can install any packages. From the official docs: https://www.gnu.org/software/guix/manual/html_node/Build-Environment-Setup.html $ sudo groupadd --system guixbuild $ sudo for i in `seq -w 1 10`; do useradd -g guixbuild -G guixbuild \ -d /var/empty -s `which nologin` \ -c "Guix build user $i" --system \ guixbuilder$i; done Next, ensure the daemon is running ($ sudo systemctl start guix-daemon) and you can use guix.

mhw commented on 2016-08-13 07:32 (UTC)

The test failure reported by fusion809 will happen whenever the absolute file name of the build directory $(abs_top_builddir) is too long, and is ultimately due to the fact that shebangs (the first line with #!) of executable scripts in Linux (the kernel) are limited to 127 characters. Some of the tests involve building packages inside the build directory, with the store inside the build directory instead of in /gnu/store (so the tests can be done without root access), so you end up with shebangs like: #!$(abs_top_builddir)/test-tmp/store/lr35ppi5q3r3bazhx4nzvjf12vfdf08v-bash-static-4.3.42/bin/sh In fusion809's case, this becomes something like: #!/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0/test-tmp/store/lr35ppi5q3r3bazhx4nzvjf12vfdf08v-bash-static-4.3.42/bin/sh The example above is 126 characters which just barely fits, but for packages with longer names, or if there is an argument after the script name on the shebang line, the length limitation will be exceeded. If you cannot arrange to do the builds in a directory with a shorter absolute file name, then you won't be able to run tests. I'm sorry about that, but until Linux (the kernel) increases this length limit, I don't see another solution.

fusion809 commented on 2016-08-12 20:11 (UTC)

For me the new revision is giving the check() failure: CXXLD guix-register Compiling Scheme modules... LOAD (guix config) ;;; note: source file ./guix/config.scm ;;; newer than compiled /home/fusion809/.cache/pacaur/guix/src/guix-0.11.0/guix/config.go GUILEC guix/config.go GEN etc/guix-daemon.service GEN etc/guix-daemon.conf make[2]: Leaving directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0' make[1]: Leaving directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0' ==> Starting check()... unshare: unshare failed: Invalid argument make check-recursive make[1]: Entering directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0' Making check in po/guix make[2]: Entering directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0/po/guix' make[2]: Leaving directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0/po/guix' Making check in po/packages make[2]: Entering directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0/po/packages' make[2]: Leaving directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0/po/packages' make[2]: Entering directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0' Compiling Scheme modules... make check-TESTS check-local make[3]: Entering directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0' make[4]: Entering directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0' ============================================================================ Testsuite summary for GNU Guix 0.11.0 ============================================================================ # TOTAL: 0 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 ============================================================================ make[4]: Leaving directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0' Cannot run tests because file name limits would be exceeded. Look for 'length' in the 'config.log' file for details. make[3]: *** [Makefile:4816: check-local] Error 1 make[3]: Leaving directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0' make[2]: *** [Makefile:4441: check-am] Error 2 make[2]: Leaving directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0' make[1]: *** [Makefile:3978: check-recursive] Error 1 make[1]: Leaving directory '/home/fusion809/.cache/pacaur/guix/src/guix-0.11.0' make: *** [Makefile:4443: check] Error 2 ==> ERROR: A failure occurred in check(). Aborting... :: failed to build guix package(s)

lantw44 commented on 2016-08-10 18:38 (UTC)

Thanks for noticing the problem of stripping. I uploaded a new version of PKGBUILD and I think it should resolve the issue.

mhw commented on 2016-08-09 23:47 (UTC)

As a lead developer of GNU Guix, I wanted to follow up on balduin's comment. It's important for the bootstrap binaries installed in gnu/packages/bootstrap/* to be copied precisely, without modification. These bootstrap binaries are the foundation upon which everything else in Guix is built, and thus they affect the hashes of every derivation. I've learned that by default, 'makepkg' automatically strips all executables, including these bootstrap binaries. As a result, users of this AUR package generate different derivations than all other Guix users, and thus they cannot make use of our binary substitutes, nor can they compare their build outputs with build outputs from other users to gain confidence that results are genuine and uncorrupted. balduin has verified that adding "options=(!strip)" to this PKGBUILD fixes the problem. I would be grateful if you could make this change ASAP. Feel free to stop by #guix if you have questions about this. Thanks!

balduin commented on 2016-08-09 20:53 (UTC)

The package works fine so far. The only problem is that you have to build each and every package from source, because the bash binary of the guix-0.11.0.tar.gz get's modified by makepkg. The negative effect is none of substitutes (pre-build packages) from hydra.gnu.org can be used since all produce a different output. The solution is to add to the PKGBUILD file: options=(!strip) for example: ~~~ ... url="https://www.gnu.org/software/guix/" license=('GPL') options=(!strip) makedepends=( 'bash-completion' ... ~~~ after adding the options line none of the binaries in guix-0.11.0.tar.gz will be modified and using substitutes from hydra.gnu.org works.

lantw44 commented on 2016-07-15 13:10 (UTC)

You have to obtain the required public key before you can verify the signature. You can find the required command at the beginning of PKGBUILD file.

mcmuntjac commented on 2016-07-15 05:42 (UTC) (edited on 2016-07-15 20:14 (UTC) by mcmuntjac)

after download: Validating source files with sha1sums... guix-0.10.0.tar.gz ... Passed guix-0.10.0.tar.gz.sig ... Passed ==> Verifying source file signatures with gpg... guix-0.10.0.tar.gz ... FAILED (unknown public key... ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build guix. e: thanks, I used gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys [PUBLIC KEY] and was able to finish building

lantw44 commented on 2016-01-31 18:18 (UTC)

I cannot reproduce the test failure. It is possible that it is just a temporary failure because some tests depend on remote servers. If it still fails, you can use the output in tests/build-utils.log to debug and report the issue.

divansantana commented on 2016-01-29 12:05 (UTC)

Failing PASS: tests/base64.scm PASS: tests/base32.scm PASS: tests/hash.scm PASS: tests/cpio.scm PASS: tests/pk-crypto.scm PASS: tests/sets.scm PASS: tests/pki.scm PASS: tests/substitute.scm PASS: tests/ui.scm PASS: tests/records.scm PASS: tests/utils.scm FAIL: tests/build-utils.scm

Gonzih commented on 2015-10-19 08:03 (UTC)

And today this test passed :/

lantw44 commented on 2015-10-16 19:10 (UTC)

Does your system run out of memory? Is there any network problem found in the log file? It is also possible that this is a problem of a remote server because this test needs Internet access.

Gonzih commented on 2015-10-16 09:13 (UTC)

with 0.8.3 i have 1 failing test: FAIL: tests/guix-package-net.sh Any tips on how can I look closer in to that?

techno-geek commented on 2015-05-14 15:22 (UTC)

0.8.2 is out

lantw44 commented on 2015-03-10 08:14 (UTC)

An install file is added now. It is copied and modified from grep.install.

holos commented on 2015-03-09 22:22 (UTC)

This ought to include an install file for the info manual.

lantw44 commented on 2015-02-18 18:58 (UTC)

I added the gpg command to PKGBUILD as a comment.

archthail commented on 2015-02-13 16:54 (UTC)

I have no problem doing it, thanks for pointing me in right direction. However, if the step is indentical for every user it makes sense for it to be included.

lantw44 commented on 2015-02-13 16:41 (UTC)

Do we really need to add the gpg command to PKGBUILD? I think it should be done by users ...

muchweb commented on 2015-02-13 16:13 (UTC)

==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build guix. Following needs adding to PKGBUILD: gpg --recv-keys 090B11993D9AEBB5

lantw44 commented on 2015-02-13 15:55 (UTC)

Please import the needed key when you see the error. Documentation: https://wiki.archlinux.org/index.php/makepkg

archthail commented on 2015-02-13 03:07 (UTC)

==> ERROR: One or more PGP signatures could not be verified!

tantalum commented on 2013-06-28 19:47 (UTC)

i just saw we now have guile 2.0.9 in extra. the package guile2 doesn't exist anymore.

lantw44 commented on 2013-05-13 16:20 (UTC)

3 tests of guix-0.2 cannot not pass because of some strange problems. configure: WARNING: unrecognized options: --enable-fast-install ./configure: ./config.status: /var/tmp/yaourt-tmp-lantw44/aur-guix/src/guix-0.2/test-tmp/store/bipvm5958i36: bad interpreter: No such file or directory chmod: cannot access 'build.sh': No such file or directory phase `configure' failed after 9 seconds