bug#27064: after GuixSD installation

2017-05-24 Thread Quiliro
After installation (with no error mesage), I reboot. These is the output of:
guix system init /mnt/etc/bare-bone.scm /mnt --fallback
http://sprunge.us/SXgC
GrUB starts to boot the system. Then the message
waiting for "my-root" partition
appears. Finally a Guile prompt appears after the following messages:
Error: in proceedure scm-error
failed to resolve partition "my-root"
I have tryed this 8 times changing different things such as label for uefi in 
bare-bones.scm:
http://sprunge.us/AhcN
http://sprunge.us/ZFAG





bug#27007: boot-parameters are not documented

2017-05-24 Thread Danny Milosavljevic
On Tue, 23 May 2017 10:13:11 +0200
l...@gnu.org (Ludovic Courtès) wrote:
> Can we assume that all the bootloaders have a notion of “menu” and “menu
> entries”? 

I think so.

But there are bootloaders that [also can] do the traditional thing: When you 
select an entry, it can chainload the bootsector of that partition.  For 
example Grub can do that.  We don't support that use case yet.  Grub can also 
load Windows NT bootloader directly or chainload an UEFI file etcetc - there 
are actually a lot of different kinds of "menu entries" even with the same 
bootloader.

See also .

It's just a question of what of all that stuff we want to support (as in 
maintain).





bug#27034: same issue here

2017-05-24 Thread Quiliro
El Wed, 24 May 2017 12:41:17 +0200 (CEST)
some...@selfhosted.xyz escribió:

> Was trying to install with the new image but ran into failed tests.
> 
> The detailed report is in the attachment and looks similar to OP.

I think it is resolved now. I ran:

guix pull
guix system init /mnt/etc/bare-bones.scm /mnt --fallback

with a minor problem. Grub had an error. When I have enough information I will 
report it wether I can solve it or not.
-- 
Example of the problems in top posting:

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I leave quotations after my reply?

Saluton,
Quiliro
0987631031





bug#27034: mount -L will mount the first partition with the named label

2017-05-24 Thread Quiliro
El Tue, 23 May 2017 11:39:13 +0200
Ricardo Wurmus  escribió:

> 
> Quiliro  writes:
> 
> > Now that installation had failed, I decided to remove all contents of 
> > /mnt/tmp to start from 0. 
> >
> > lsblk recognized:
> > sda as the usb installer
> > sdb1 as a previous failed installation with label my-root
> > sdc1 as the current installation with label my-root
> >
> > When I restarted to begin installation from fresh, I noticed that 
> > /mnt/etc/bare-bones.scm was changed from sda to sdc. I remember having 
> > changed it. But I started doubting. Then I checked the mount and noticed 
> > that /mnt was in sdb1 instead of in sdc1. So I umounted and mounted with -L 
> > again. But it would mount sdb1 again. So I umounted and mounted with 
> > /dev/sdc1 and no -L. That worked.
> 
> I don’t understand this bug report.  Labels must be unique.  They are
> a more readable alternative to using UUIDs.

Yes. I just inserted the two disks and the old one had the same configuration 
as the old. I copied the contents of the one to the other to avoid downloading 
again the packages.


-- 
Example of the problems in top posting:

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I leave quotations after my reply?

Saluton,
Quiliro
0987631031





bug#27037: systemd service files installed by guix 0.13.0 cannot used by other distributions

2017-05-24 Thread 藍挺瑋

Leo Famulari 於 西元2017年05月24日 00:16 寫道:

On Tue, May 23, 2017 at 11:33:42PM +0800, 藍挺瑋 wrote:

Hi!


I found the systemd service files installed by guix 0.13.0
use /var/guix/profiles/per-user/root/guix-profile/bin/guix* instead of
/usr/bin/guix* in ExecStart=. The path /var/guix/profiles don't exist
on systems that don't have guix installed before


I'm a little confused: is there a situation where Guix is not installed
but '/usr/bin/guix-daemon' exists?


This can happen with source installation. 'make install' installs 
/usr/bin/guix* but not /var/guix. /var/guix doesn't exist until 
guix-daemon is started.




The path '/var/guix/profiles/per-user/root/guix-profile/bin/guix-daemon'
is guaranteed to exist if you followed the instructions in Binary
Installation [0], which is, as far as I know, the most common way to
install Guix on other distros. So, I think this path is appropriate for
the basic service file we provide.


I think you mean that the systemd service files included in Guix are 
only intended to be used with binary installation process. Do you mean 
that using them with traditional 'make install' installation is not 
supported?





Is it possible to fix systemd service files, so it can be easily used
by packages in other distributions?


I think that, if you are packaging Guix for other distros, you should
provide your own service file. My experience is that each systemd-based
distro uses systemd's advanced features (e.g. process grouping and
resource limiting) in different ways. So, making your own service file,
in accordance with your distro's standards, will help Guix work in a way
that is more idiomatic to the host distro.


Yes, I am packaging Guix for Arch and Fedora, and I use the systemd 
service files provided by Guix in my packages since version 0.8.3. If 
doing so is never supported, I can make my own service files like what I 
did for version 0.6 to 0.8.2 and I think this bug can be closed.




[0] Specifically, it happens during the initial unpacking and renaming:
`mv var/guix /var/ && mv gnu/`
https://www.gnu.org/software/guix/manual/html_node/Binary-Installation.html







bug#27051: builder for glibc-intermediate-2.25 fails and ends guix pull

2017-05-24 Thread Ludovic Courtès
Hi Calvin,

Calvin Heim  skribis:

> 'guix pull' fails with the Guix package manager on Trisquel 7.
>
> $ uname -p
> i686
>
> $ guile --version
> guile (GNU Guile) 2.2.0
>
> $ guix --version
> guix (GNU Guix) 20170430.04
>
> $ guix pull

[...]

> at 
> /gnu/store/5vvzwh41q3l0fdjyjxiz105fsxcz35rs-module-import/guix/build/gnu-build-system.scm:649:9
>  (expr)> #]
> In ice-9/eval.scm:
>  432: 1 [eval # #]
> In unknown file:
>?: 0 [system* "patch" "-p1" "--force" "--input" #f]
>
> ERROR: In procedure system*:
> ERROR: Wrong type (expecting string): #f
> builder for
> `/gnu/store/m7q6fhjy4zz8j36jvf7yihq65v6m3dnw-glibc-intermediate-2.25.drv' 
> failed with exit code 1

There was a small time window during which glibc-intermediate was broken
on i686.  This was fixed on April 30th:

  
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=c2e4f14ac8cd3e1ce7f46a192ad0c9acc084b210

One way to work around the issue might be:

  mv ~/.config/guix/latest{,.bak}
  guix pull

Could you try this?

Thanks for reporting the issue,
Ludo’.





bug#27032: make check fails for Guix 0.13.0

2017-05-24 Thread Ludovic Courtès
Hi William,

William  skribis:

> I am trying to do a fresh install of GuixSD 0.13.0 (using UEFI if it's
> important), after running "guix system init /mnt/etc/config.scm /mnt"
> the "make check" stage of guix fails.

There was one problem, which is that substitutes for the ‘guix’ package
itself were missing.  This is now fixed, meaning that if you install
GuixSD 0.13.0 now, you won’t have to build ‘guix’.

Could you try again?

> test-name: dead path can be explicitly collected
> location: /tmp/guix-build-guix-0.13.0.drv-0/source/tests/store.scm:178
> source:
> + (test-assert
> +   "dead path can be explicitly collected"
> +   (let ((p (add-text-to-store
> +  %store
> +  "random-text"
> +  (random-text)
> +  '(
> + (let-values
> +   (((paths freed) (delete-paths %store (list p
> +   (and (equal? paths (list p))
> +(> freed 0)
> +(not (file-exists? p))
> actual-value: #f
> result: FAIL

[...]

> test-name: verify-store + check-contents
> location: /tmp/guix-build-guix-0.13.0.drv-0/source/tests/store.scm:815
> source:
> + (test-assert
> +   "verify-store + check-contents"
> +   (with-store
> + s
> + (let* ((text (random-text))
> +(drv (build-expression->derivation
> +   s
> +   "corrupt"
> +   `(let ((out (assoc-ref %outputs "out")))
> +  (call-with-output-file
> +out
> +(lambda (port) (display ,text port)))
> +  #t)
> +   #:guile-for-build
> +   (package-derivation
> + s
> + %bootstrap-guile
> + (%current-system
> +(file (derivation->output-path drv)))
> +   (with-derivation-substitute
> + drv
> + text
> + (and (build-derivations s (list drv))
> +  (verify-store s #:check-contents? #t)
> +  (begin
> +(chmod file 420)
> +(call-with-output-file
> +  file
> +  (lambda (port) (display "corrupt!" port)))
> +#t)
> +  (not (verify-store s #:check-contents? #t))
> +  (delete-paths s (list file)))
> actual-value: #f
> actual-error:
> + (srfi-34
> +   # `dtmp/guix-tests/store/462z3fnl7bs44vp9s97jyg1z74nsfvly-tar' is not in the 
> Nix store" status: 1] e171e0>)
> result: FAIL

I’m surprised by the “dtmp” prefix here.   It should be
“/tmp/guix-tests”.  Was the log altered in some way?

Apart from that it’s hard to draw any conclusions.  We run these tests
very often without problems.  The difference here is that the GuixSD
installation system uses unionfs-fuse for its root file system, and I
suspect that file system could have slightly different semantics that
bite here.  We’ll have to investigate this.

Thanks for your report!

Ludo’.





bug#27051: builder for glibc-intermediate-2.25 fails and ends guix pull

2017-05-24 Thread Calvin Heim
Hi,

'guix pull' fails with the Guix package manager on Trisquel 7.

$ uname -p
i686

$ guile --version
guile (GNU Guile) 2.2.0

$ guix --version
guix (GNU Guix) 20170430.04

$ guix pull
...
...
...
starting phase `pre-configure'
Backtrace:
In ice-9/boot-9.scm:
 157: 13 [catch #t # ...]
In unknown file:
   ?: 12 [apply-smob/1 #]
In ice-9/boot-9.scm:
  63: 11 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
 432: 10 [eval # #]
In ice-9/boot-9.scm:
2320: 9 [save-module-excursion #]
3966: 8 [#]
1645: 7 [%start-stack load-stack ...]
1650: 6 [#]
In unknown file:
   ?: 5 [primitive-load
"/gnu/store/zhm1rxpqnhr8b976azyi10zkpm7i2d5q-glibc-intermediate-2.25-guile-builder"]
In ice-9/eval.scm:
 387: 4 [eval # ()]
In srfi/srfi-1.scm:
 830: 3 [every1 # ...]
In 
/gnu/store/5vvzwh41q3l0fdjyjxiz105fsxcz35rs-module-import/guix/build/gnu-build-system.scm:
 653: 2 [# #]
In ice-9/eval.scm:
 432: 1 [eval # #]
In unknown file:
   ?: 0 [system* "patch" "-p1" "--force" "--input" #f]

ERROR: In procedure system*:
ERROR: Wrong type (expecting string): #f
builder for
`/gnu/store/m7q6fhjy4zz8j36jvf7yihq65v6m3dnw-glibc-intermediate-2.25.drv' 
failed with exit code 1
cannot build derivation
`/gnu/store/kc6yxibxsk4vshl6svbwbm5wnig0d5zx-bash-static-4.4.12.drv': 1
dependencies couldn't be built
cannot build derivation
`/gnu/store/l1bp2qw2v0p0f9v9vb1z3xd6z7s5kvlc-gcc-5.4.0.drv': 1
dependencies couldn't be built
cannot build derivation
`/gnu/store/r68459m540fhs7n567pllbq827c90v9c-glibc-2.25.drv': 1
dependencies couldn't be built
cannot build derivation
`/gnu/store/0g35596mg1x4r6150pqd0jkmfyb64zyj-guile-2.0.14.drv': 1
dependencies couldn't be built
cannot build derivation
`/gnu/store/m92q2i44y1n0s1yv9h17gidvxzlg6si3-le-certs-0.drv': 1
dependencies couldn't be built
guix pull: error: build failed: build of
`/gnu/store/m92q2i44y1n0s1yv9h17gidvxzlg6si3-le-certs-0.drv' failed