Re: core-updates-frozen: Planning for the last world rebuild

[Mathieu Othacehe]

Hey Ricardo,

> It should be fine now.  I didn’t run the test myself, but I ran most of the
> commands and found a few more hardcoded tool file names that referenced /sbin
> or /usr/bin. 

Yes, I confirm it passes! I also fixed the childhurd test. Only 9 tests
to go :).

Thanks,

Mathieu

Re: No license in crate - guix import

[Hartmut Goebel]

Am 04.10.21 um 22:30 schrieb Michael Zappa:

guix import cratelibpulse-sys@0.0.0  -r
[…]
316:37  2 (crate->guix-package "libpulse-sys" #:version _ # _ # _)
213:14  1 (string->license _)
In unknown file:
0 (string-split null #)

ERROR: In procedure string-split:
In procedure string-split: Wrong type argument in position 1 (expecting 
string): null


I was able to reproduce this issue. Please file a bug-report.

--
Regards
Hartmut Goebel

| Hartmut Goebel  | h.goe...@crazy-compilers.com   |
| www.crazy-compilers.com | compilers which you thought are impossible |

Re: Upgrade cl-hunchentoot to version 1.3.0

[Guillaume Le Vaillant]

Tim Lee  skribis:

> In Guix, the latest version of Hunchentoot is 1.2.38 (released on
> 2017-12-03). There is a new upstream version 1.3.0 (released on
> 2021-05-07). Can someone upgrade cl-hunchentoot? I am not familiar with
> the Guix packaging process, but it appears that the following patch is
> sufficient:
>
> diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
> index 5faa69a037..c8d2a90f58 100644
> --- a/gnu/packages/lisp-xyz.scm
> +++ b/gnu/packages/lisp-xyz.scm
> @@ -4291,7 +4291,7 @@ sockets, SSL, continuable uploads, file uploads, 
> cookies, and more.")
>  (define-public sbcl-hunchentoot
>(package
>  (name "sbcl-hunchentoot")
> -(version "1.2.38")
> +(version "1.3.0")
>  (source
>   (origin
> (method git-fetch)

Hi,

When upgrading a package, you also have to update the hash of the
sources. In this case it can be computed with:

--8<---cut here---start->8---
git clone --depth 1 -b v1.3.0 https://github.com/edicl/hunchentoot
guix hash -rx hunchentoot
--8<---cut here---end--->8---

I updated the cl-hunchentoot package to 1.3.0 in commit
b5dee04c9b5d5a99f045afcaeaab615b2e468cad.

The manual has information about the packaging process
(see https://guix.gnu.org/manual/devel/en/guix.html#Contributing).


signature.asc
Description: PGP signature

Upgrade cl-hunchentoot to version 1.3.0

[Tim Lee]

In Guix, the latest version of Hunchentoot is 1.2.38 (released on
2017-12-03). There is a new upstream version 1.3.0 (released on
2021-05-07). Can someone upgrade cl-hunchentoot? I am not familiar with
the Guix packaging process, but it appears that the following patch is
sufficient:

diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
index 5faa69a037..c8d2a90f58 100644
--- a/gnu/packages/lisp-xyz.scm
+++ b/gnu/packages/lisp-xyz.scm
@@ -4291,7 +4291,7 @@ sockets, SSL, continuable uploads, file uploads, cookies, 
and more.")
 (define-public sbcl-hunchentoot
   (package
 (name "sbcl-hunchentoot")
-(version "1.2.38")
+(version "1.3.0")
 (source
  (origin
(method git-fetch)

Authenticated Boot and Disk Encryption

[Reza Housseini]

Hello Guix!

I came across this blog post

and was wondering what is the state of authenticated boot and encryption in
Guix System?
I have this vision where you define such things in your system guile script
and everything gets configured appropriately, or at least the default setup
is as secure as possible.

Thanks for any insights.

Cheers, Reza