bug#39551: Cannot declare an NFS mount using the record

2020-02-12 Thread Maxim Cournoyer
Hello,

Maxim Cournoyer  writes:

> When I try adding an NFS mount point to my Guix System, like:
>
> [...]
> (file-system
>   (device "192.168.1.10:/mnt/scratch/")
>   (mount-point "/mnt/scratch/")
>   (type "nfs")
>   (options "rw,async,soft,noexec"))
> [...]
>
> Reconfiguring fails with the message:
>
> error: device '192.168.1.10' not found: No such file or directory
> hint: If '192.168.1.10' is a file system label, write
> `(file-system-label "192.168.1.10")' in your `device' field.
>
> So it doesn't appear to be possible to declare an NFS mount currently,
> despite commit 0c85db79f7a8abc3bcdbf8931d959fe94306a5a1 that'd suggest
> it should be possible.
>
> Maxim

The attached patch fixes this issue

>From 6aad93c3a2ccef9936cadeeab92edece7afac0dd Mon Sep 17 00:00:00 2001
From: Maxim Cournoyer 
Date: Mon, 10 Feb 2020 15:06:50 -0500
Subject: [PATCH] scripts: system: Disable checks for NFS shares.

Fixes issue #39551 (https://bugs.nu.org/39551).

* guix/scripts/system.scm (check-file-system-availability): Ignore file
systems of the NFS type.
---
 guix/scripts/system.scm | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/guix/scripts/system.scm b/guix/scripts/system.scm
index b0386a1392..26a1599a93 100644
--- a/guix/scripts/system.scm
+++ b/guix/scripts/system.scm
@@ -566,6 +566,8 @@ any, are available.  Raise an error if they're not."
   (and (file-system-mount? fs)
(not (member (file-system-type fs)
 %pseudo-file-system-types))
+   ;; Fixes issue #39551 (see: https://bugs.gnu.org/39551).
+   (not (string-prefix? "nfs" (file-system-type fs)))
(not (memq 'bind-mount (file-system-flags fs)
 file-systems))
 
-- 
2.25.0



bug#38447: Fix installer restart.

2020-02-12 Thread Mathieu Othacehe


> This should allow us to close:
>
> https://issues.guix.info/issue/39217
> https://issues.guix.info/issue/38447

Fixed by 1d02052067e04d7dd8fd1ec17557ca02a30b9bcf.

Thanks,

Mathieu





bug#39575: guix time-machine fails when a tarball was modified in-place

2020-02-12 Thread Jan Nieuwenhuizen
Hi,

Trying to travel back to Sun Apr 7 22:07:14 2019 +0200 (commit
56e95d54d209c2428f970d65d9b27ae4168449ad) to re-create mcrl2-minimal by
doing

--8<---cut here---start->8---
guix time-machine --commit=56e95d54d209c2428f970d65d9b27ae4168449ad -- 
environment --ad-hoc mcrl2-minimal
--8<---cut here---end--->8---

fails with

--8<---cut here---start->8---
building 
/gnu/store/cjim33x0q1bv1ppkv3qijvr1pvsn4y0q-harfbuzz-2.4.0.tar.bz2.drv...
downloading from 
https://www.freedesktop.org/software/harfbuzz/release/harfbuzz-2.4.0.tar.bz2...
|offloading build of 
/gnu/store/6fgg1irkcvqyb4f9f8n0nzi5gknyqhfn-gcc-mesboot1-4.7.4.drv to 
'kluit.dezyne.org'
- 'build' phasesha256 hash mismatch for 
/gnu/store/b4cdp9sp44848348lrpzbfafhmjqf8nr-harfbuzz-2.4.0.tar.bz2:
  expected hash: 1mpah6kwqid1kxsj4rwqsniivqbrx231j65v51yncx6s0dch0dch
  actual hash:   0vrkvdlmihdg62a4c6h5kx27khc33xmb95l50zgnwnavvpwyyw5l
hash mismatch for store item 
'/gnu/store/b4cdp9sp44848348lrpzbfafhmjqf8nr-harfbuzz-2.4.0.tar.bz2'
build of /gnu/store/cjim33x0q1bv1ppkv3qijvr1pvsn4y0q-harfbuzz-2.4.0.tar.bz2.drv 
failed
View build log at 
'/var/log/guix/drvs/cj/im33x0q1bv1ppkv3qijvr1pvsn4y0q-harfbuzz-2.4.0.tar.bz2.drv.bz2'.
cannot build derivation 
`/gnu/store/p6gfcdacjcqf2br0zwsyzx1chfvg9gxi-harfbuzz-2.4.0.drv': 1 
dependencies couldn't be built
killing process 5083
--8<---cut here---end--->8---

The recipe for harfbuzz has a sha256 that used to be valid in April, but
hasn't been valid anymore since May, as this fix

--8<---cut here---start->8---
commit a8bb8fccd82a10a46f127b2235675b4f6cbaaf98
Author: Marius Bakke 
Date:   Sat May 4 18:01:12 2019 +0200

gnu: harfbuzz: Update source hash.

The previous tarball was modified in-place; see
.

* gnu/packages/gtk.scm (harfbuzz)[source](sha256): Update.
--8<---cut here---end--->8---

shows.  Thoughts?

Greetings,
janneke


-- 
Jan Nieuwenhuizen  | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | AvatarĀ® http://AvatarAcademy.com





bug#39575: guix time-machine fails when a tarball was modified in-place

2020-02-12 Thread zimoun
Hi,


On Wed, 12 Feb 2020 at 14:44, Jan Nieuwenhuizen  wrote:

> Trying to travel back to Sun Apr 7 22:07:14 2019 +0200 (commit
> 56e95d54d209c2428f970d65d9b27ae4168449ad) to re-create mcrl2-minimal by
> doing
>
> --8<---cut here---start->8---
> guix time-machine --commit=56e95d54d209c2428f970d65d9b27ae4168449ad -- 
> environment --ad-hoc mcrl2-minimal
> --8<---cut here---end--->8---

Even the simple:

--8<---cut here---start->8---
guix time-machine --commit=56e95d54d209c2428f970d65d9b27ae4168449ad -- help
--8<---cut here---end--->8---

> fails with
>
> --8<---cut here---start->8---
> building 
> /gnu/store/cjim33x0q1bv1ppkv3qijvr1pvsn4y0q-harfbuzz-2.4.0.tar.bz2.drv...
> downloading from 
> https://www.freedesktop.org/software/harfbuzz/release/harfbuzz-2.4.0.tar.bz2...
> |offloading build of 
> /gnu/store/6fgg1irkcvqyb4f9f8n0nzi5gknyqhfn-gcc-mesboot1-4.7.4.drv to 
> 'kluit.dezyne.org'
> - 'build' phasesha256 hash mismatch for 
> /gnu/store/b4cdp9sp44848348lrpzbfafhmjqf8nr-harfbuzz-2.4.0.tar.bz2:
>   expected hash: 1mpah6kwqid1kxsj4rwqsniivqbrx231j65v51yncx6s0dch0dch
>   actual hash:   0vrkvdlmihdg62a4c6h5kx27khc33xmb95l50zgnwnavvpwyyw5l
> hash mismatch for store item 
> '/gnu/store/b4cdp9sp44848348lrpzbfafhmjqf8nr-harfbuzz-2.4.0.tar.bz2'
> build of 
> /gnu/store/cjim33x0q1bv1ppkv3qijvr1pvsn4y0q-harfbuzz-2.4.0.tar.bz2.drv failed
> View build log at 
> '/var/log/guix/drvs/cj/im33x0q1bv1ppkv3qijvr1pvsn4y0q-harfbuzz-2.4.0.tar.bz2.drv.bz2'.
> cannot build derivation 
> `/gnu/store/p6gfcdacjcqf2br0zwsyzx1chfvg9gxi-harfbuzz-2.4.0.drv': 1 
> dependencies couldn't be built
> killing process 5083
> --8<---cut here---end--->8---

same for e.g., this commit:

--8<---cut here---start->8---
 guix time-machine --commit=ae528aaf19f3828d3d7d204b15570800e1bbf100 -- help
--8<---cut here---end--->8---


> The recipe for harfbuzz has a sha256 that used to be valid in April, but
> hasn't been valid anymore since May, as this fix
>
> --8<---cut here---start->8---
> commit a8bb8fccd82a10a46f127b2235675b4f6cbaaf98
> Author: Marius Bakke 
> Date:   Sat May 4 18:01:12 2019 +0200
>
> gnu: harfbuzz: Update source hash.
>
> The previous tarball was modified in-place; see
> .
>
> * gnu/packages/gtk.scm (harfbuzz)[source](sha256): Update.
> --8<---cut here---end--->8---
>
> shows.  Thoughts?

Therefore, all the commits between the introduction of harfbuzz with
the old sha256 (commit 2da9b81837fd1e6f08a10952784d3358be982855) and
the commit updating to the new sha256 should be broken.
Roughly speaking, all the commits between April, 7th and the May, 4th;
i.e., 1100+ commits, isn't it?


Well, this ask an interesting question: how Guix can fallback when
upstream is doing wrong?


Considering this 'harbuzz' issue, is it possible to rebuild the old
tarball and push it to SoftWare Heritage? Then when a sha mismatch
happens, fallback and try to fetch it from SWH?


WDYT?

Cheers,
simon





bug#27096: Hunting: 'guix package -i' fails when internet is disconnected

2020-02-12 Thread zimoun
Dear,

Using this version of Guix:

--8<---cut here---start->8---
  guix 403d9fa
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 403d9fae791bd22b4e2da5e90ad273755de26dc5
--8<---cut here---end--->8---

then running "guix package -i emacs" downloads all it needs.
The network wire is then unplugged and running again "guix package -i
emacs" works as expected, i.e., shows the message saying "nothing to
be done".


Considering it is an old bug, the initial reporter is not reachable
and the bug is not reproducible, I am closing it.

Please feel free to reopen it if you hit again this bug.


All the best,
simon





bug#39551: Cannot declare an NFS mount using the record

2020-02-12 Thread Giovanni Biscuolo
Hello,

Maxim Cournoyer  writes:

> The attached patch fixes this issue

[...]

> diff --git a/guix/scripts/system.scm b/guix/scripts/system.scm
> index b0386a1392..26a1599a93 100644
> --- a/guix/scripts/system.scm
> +++ b/guix/scripts/system.scm
> @@ -566,6 +566,8 @@ any, are available.  Raise an error if they're not."
>(and (file-system-mount? fs)
> (not (member (file-system-type fs)
>  %pseudo-file-system-types))
> +   ;; Fixes issue #39551 (see: https://bugs.gnu.org/39551).
> +   (not (string-prefix? "nfs" (file-system-type fs)))
> (not (memq 'bind-mount (file-system-flags fs)
>  file-systems))

Please is it possible to also add nfs4 to this fix?

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures


signature.asc
Description: PGP signature


bug#39551: Cannot declare an NFS mount using the record

2020-02-12 Thread Maxim Cournoyer
Hello Giovanni,

Giovanni Biscuolo  writes:

> Hello,
>
> Maxim Cournoyer  writes:
>
>> The attached patch fixes this issue
>
> [...]
>
>> diff --git a/guix/scripts/system.scm b/guix/scripts/system.scm
>> index b0386a1392..26a1599a93 100644
>> --- a/guix/scripts/system.scm
>> +++ b/guix/scripts/system.scm
>> @@ -566,6 +566,8 @@ any, are available.  Raise an error if they're not."
>>(and (file-system-mount? fs)
>> (not (member (file-system-type fs)
>>  %pseudo-file-system-types))
>> +   ;; Fixes issue #39551 (see: https://bugs.gnu.org/39551).
>> +   (not (string-prefix? "nfs" (file-system-type fs)))
>> (not (memq 'bind-mount (file-system-flags fs)
>>  file-systems))
>
> Please is it possible to also add nfs4 to this fix?
>
> Thanks! Gio'

It should work already, given that I'm checking for a string *prefix* of
"nfs" :-).





bug#39551: [PATCH v2] Cannot declare an NFS mount using the record

2020-02-12 Thread Maxim Cournoyer
Attached is v2 of the patch, fixing the comment in the code as reported
by Tobias.

Thank you!

>From 666ce396f2a53bec4d88ee90c1612166421f3ed8 Mon Sep 17 00:00:00 2001
From: Maxim Cournoyer 
Date: Mon, 10 Feb 2020 15:06:50 -0500
Subject: [PATCH] scripts: system: Do not validate network file systems.

Fixes issue #39551 (https://bugs.gnu.org/39551).

* guix/scripts/system.scm (check-file-system-availability): Ignore file
systems of the NFS type.
---
 guix/scripts/system.scm | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/guix/scripts/system.scm b/guix/scripts/system.scm
index b0386a1392..ac2475c551 100644
--- a/guix/scripts/system.scm
+++ b/guix/scripts/system.scm
@@ -566,6 +566,8 @@ any, are available.  Raise an error if they're not."
   (and (file-system-mount? fs)
(not (member (file-system-type fs)
 %pseudo-file-system-types))
+   ;; Don't try to validate network file systems.
+   (not (string-prefix? "nfs" (file-system-type fs)))
(not (memq 'bind-mount (file-system-flags fs)
 file-systems))
 
-- 
2.23.0



bug#39584: evolution: involid page id error when composing emails

2020-02-12 Thread Christopher Howard
Hi, I use evolution heavily, current 3.32.4 from Guix. I updated my
guix user packages and guix system about a week ago. When composing
emails, I occasionally see an error similar to this appear in a box
above the message composition area:

gdbus.error:org.freedesktop.dbus.error.invalidargs: invalid page id:
165

While the error is there, I cannot save the email to drafts or send it.
To resolve, I must copy the email contents to another program, then
restart evolution to create the email again. It seems to be very
random, but I'd guess it happens once about every five to ten emails I
send.

christopher@eowyn ~$ guix describe
Generation 9Feb 05 2020 15:44:24(current)
  guix 9d0dfd9
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 9d0dfd9a9a7c43363a4e140c20d49f119fe6f2e3

christopher@eowyn ~$ neofetch 
 .. `.   christopher@eowyn 
 `--..```..`   `..```..--`   - 
   .-:///-:::.   `-:::///:-. OS: Guix System
9d0dfd9a9a7c43363a4e140c20d49f119fe6f2e3 x86_64 
  .:::` `:::.Host: Vostro 230 00 
   -//:`-::- Kernel: 5.4.17-gnu 
://:   -::-  Uptime: 6 days, 4 hours, 5 mins 
`///- .:::`  Packages: 55 (guix-system), 80
(guix-user) 
 -+++-:::.   Shell: bash 5.0.7 
  :+/:::-DE: GNOME 3.32.2 
  `-`Theme: Adwaita [GTK2/3] 
 Icons: Adwaita [GTK2/3] 
 Terminal: .gnome-terminal 
 CPU: Intel Core 2 Duo E7500 (2) @
2.672GHz 
 GPU: Intel 4 Series Chipset 
 Memory: 2412MiB / 7929MiB 



-- 
Christopher Howard
Enterprise Solutions Manager
Alaska Satellite Internet
PO Box 70, Ester, AK 99725
3239 La Ree Way, Fairbanks, AK 99709
907.451.0088
1.888.396.5623
www.alaskasatelliteinternet.com