Re: Error messages and progress report

Andreas Enge skribis: > Am Donnerstag, 10. Januar 2013 schrieb Ludovic Courtès: >> I find it useful to have the server name printed (esp. in the case of >> mirror://, ftpmirror.gnu.org, etc.), so I’ve come up with a solution >> that abbreviates long URIs like this: >> I’ll commit it if there are

Re: Error messages and progress report

Am Donnerstag, 10. Januar 2013 schrieb Ludovic Courtès: > I find it useful to have the server name printed (esp. in the case of > mirror://, ftpmirror.gnu.org, etc.), so I’ve come up with a solution > that abbreviates long URIs like this: > I’ll commit it if there are no objections. This looks goo

Re: Error messages and progress report

Andreas Enge skribis: > Well, it could be slightly improved. I am just downloading > http://linux-libre.fsfla.org/pub/linux-libre/releases/3.3.8-gnu/linux-libre-3.3.8-gnu.tar.xz, > and the file name is so long that the progress counter does not fit into > the same line any more. I would suggest

Re: Error messages and progress report

Am Donnerstag, 10. Januar 2013 schrieb Andreas Enge: > Am Sonntag, 6. Januar 2013 schrieb Ludovic Courtès: > > I just pushed a progress report thingie in ‘core-updates’ (it’s not a > > progress bar, just a percentage, but I find it pleasant enough. ;-)). > It works like a charm, thanks! Well, it c

Re: Error messages and progress report

Am Sonntag, 6. Januar 2013 schrieb Ludovic Courtès: > I just pushed a progress report thingie in ‘core-updates’ (it’s not a > progress bar, just a percentage, but I find it pleasant enough. ;-)). It works like a charm, thanks! Andreas

Re: Error messages and progress report

Hi, Andreas Enge skribis: > Concerning the downloads, would it be possible to easily add a progress > bar? In particular since the first download was gcc, quite some time passed > without any hint as to whether the program was still working. I just pushed a progress report thingie in ‘core-upda

Re: Error messages and progress report

Am Mittwoch, 12. Dezember 2012 schrieb Andreas Enge: > Am Mittwoch, 12. Dezember 2012 schrieb Ludovic Courtès: > > Andreas Enge skribis: > > > However, the current behaviour is not consistent with the > > > documentation. > > It’s more that the documentation is ahead of time. :-) > I think the at

Re: Error messages and progress report

Andreas Enge skribis: > Am Mittwoch, 12. Dezember 2012 schrieb Ludovic Courtès: >> > As for the rough edges, installing the hello package twice results in >> > an error message, too. >> Commit 1c67d63 fixes that. > > Thanks! Now I can install "hello" over and over again :-) Excellent! I think t

Re: Error messages and progress report

Am Mittwoch, 12. Dezember 2012 schrieb Ludovic Courtès: > Andreas Enge skribis: > > However, the current behaviour is not consistent with the > > documentation. > It’s more that the documentation is ahead of time. :-) I think the attached patch solves the problem. Andreas diff --git a/guix-pack

Re: Error messages and progress report

Am Mittwoch, 12. Dezember 2012 schrieb Ludovic Courtès: > > As for the rough edges, installing the hello package twice results in > > an error message, too. > Commit 1c67d63 fixes that. Thanks! Now I can install "hello" over and over again :-) > > Another question: My guix source and compile dire

Re: Error messages and progress report

Andreas Enge skribis: > However, the current behaviour is not consistent with the documentation. It’s more that the documentation is ahead of time. :-) Ludo’.

Re: Error messages and progress report

Andreas Enge skribis: > Am Dienstag, 11. Dezember 2012 schrieb Ludovic Courtès: >> Anyway, what does work is something like: >> $ guix-package --profile=$HOME/.guix-profile --install=hello > > This worked, but in a rather strange way. .guix-profile did not exist > yet. It was created as a symbo

Re: Error messages and progress report

Am Dienstag, 11. Dezember 2012 schrieb Andreas Enge: > Am Dienstag, 11. Dezember 2012 schrieb Ludovic Courtès: > > Anyway, what does work is something like: > > $ guix-package --profile=$HOME/.guix-profile --install=hello > > This worked, but in a rather strange way. Well, this is actually not

Re: Error messages and progress report

Am Dienstag, 11. Dezember 2012 schrieb Ludovic Courtès: > Anyway, what does work is something like: > $ guix-package --profile=$HOME/.guix-profile --install=hello This worked, but in a rather strange way. .guix-profile did not exist yet. It was created as a symbolic link to the new file .guix-pr

Re: Error messages and progress report

Hi, Andreas Enge skribis: > The command >guix-package -i hello > still produces an error, probably related to making the symlinks > in my own environment: Yes. Currently ‘guix-package’ expects the default profile to be under /nix/var/nix/profiles/guix, which typically doesn’t exist, hence

Re: Error messages and progress report

> The command > guix-package -i hello > still produces an error, probably related to making the symlinks > in my own environment: [...] > ERROR: In procedure symlink: > ERROR: In procedure symlink: No such file or directory './pre-inst-env guix-package -i hello' returns the same backtrace on m

Re: Error messages and progress report

Hello, I am getting there! Everything compiled, and there is now a hello package. Or rather, lots of them. /nix/store contains 1 hello-2.8.tar.gz 3 hello-2.8.tar.gz.drv 3 hello-2.8.tar.gz-guile-builder 2 hello-2.8 2 hello-2.8.drv 2 hello-2.8-guile-builder Altogether 13 files or directories, with d

Re: Error messages and progress report

Am Montag, 10. Dezember 2012 schrieb Ludovic Courtès: > > Should this problem not also occur when > > compiling guile-2.0.6 by root outside of guix? Should the test maybe > > be disabled in the guile distribution? > Yes, that’s what I just did: > http://git.savannah.gnu.org/cgit/guile.git/commit/?h

Re: Error messages and progress report

Andreas Enge skribis: > Yes, I just tried creating a directory, chmod 000 and ls. root can do this. > However, when I chown the nix-build... directory to some other user, the > test succeeds. Should this problem not also occur when compiling > guile-2.0.6 by root outside of guix? Should the test

Re: Error messages and progress report

Am Montag, 10. Dezember 2012 schrieb Ludovic Courtès: > The test here creates the ‘test-EACCES’ directory, chmods it to 000, and > expects to be unable to list its contents. But in your case, it > succeeds. > > I think that’s because nix-worker is running as root and doesn’t have > build users co

Re: Error messages and progress report

Hello, Andreas Enge skribis: > ;;; (((up "/tmp/nix-build-dgk2vcwfmniiq2b5bk36whmq815abxva- > guile-2.0.6.drv-0/guile-2.0.6/test-EACCES") (leaf "/tmp/nix-build- > dgk2vcwfmniiq2b5bk36whmq815abxva-guile-2.0.6.drv-0/guile-2.0.6/test- > EACCES/a") (leaf "/tmp/nix-build-dgk2vcwfmniiq2b5bk36whmq815abx

Re: Error messages and progress report

Am Montag, 10. Dezember 2012 schrieb Ludovic Courtès: > Can you run: > guix-build -e '(@ (distro packages base) guile-final)' --keep-failed I already used ./pre-inst-env guix-build guile-2.0.6 so the build tree is there. > Once it has failed, can you please apply this patch in the build tree

Re: Error messages and progress report

Hi Andreas, Andreas Enge skribis: > Am Sonntag, 9. Dezember 2012 schrieb Ludovic Courtès: >> Note that you can get pre-built binaries for x86_64-linux from >> hydra.nixos.org: >> . > > This is a nice feature, thanks for the hint.

Re: Error messages and progress report

Hi, Andreas Enge skribis: > $ guix-package -n -i hello [...] > In guix/store.scm: > 408: 1 [add-text-to-store # "libsigsegv-2.10.tar.gz-guile-builder" ...] > In unknown file: >?: 0 [put-bytevector # #vu8(8 0 0 0 0 0 0 0) > ...] > > ERROR: In procedure put-bytevector: > ERROR: In procedur

Error messages and progress report

Hello, advancing with my first steps in guix, I have lots of questions, probably naive ones. $ guix-package -n -i hello throws lots of error messages: Backtrace: In ice-9/boot-9.scm: 63: 19 [call-with-prompt prompt0 ...] In ice-9/eval.scm: 407: 18 [eval # #] In unknown file: ?: 17 [call-