GNU Guix 1.1.0 released
We are pleased to announce the release of GNU Guix 1.1.0.
This release corresponds to 14,078 commits over 11 months by 201 people.
It includes many new features, user interface and performance
improvements, as well as many bug fixes—see below for a list of changes.
Read more about today’s announcement at:
https://guix.gnu.org/blog/2020/gnu-guix-1.1.0-released
• About
GNU Guix is a transactional package manager and an advanced
distribution of the GNU system that respects user freedom. Guix can
be used on top of any system running the kernel Linux, or it can be
used as a standalone operating system distribution for i686, x86_64,
ARMv7, and AArch64 machines.
In addition to standard package management features, Guix supports
transactional upgrades and roll-backs, unprivileged package
management, per-user profiles, and garbage collection. When used as a
standalone GNU/Linux distribution, Guix offers a declarative,
stateless approach to operating system configuration management. Guix
is highly customizable and hackable through Guile programming
interfaces and extensions to the Scheme language.
https://guix.gnu.org
• Download
Here are the compressed sources and a GPG detached signature[*]:
https://ftp.gnu.org/gnu/guix/guix-1.1.0.tar.gz
https://ftp.gnu.org/gnu/guix/guix-1.1.0.tar.gz.sig
Here are the bootable USB installation images and their signatures[*]:
https://ftp.gnu.org/gnu/guix/guix-system-install-1.1.0.i686-linux.iso.xz
https://ftp.gnu.org/gnu/guix/guix-system-install-1.1.0.i686-linux.iso.xz.sig
https://ftp.gnu.org/gnu/guix/guix-system-install-1.1.0.x86_64-linux.iso.xz
https://ftp.gnu.org/gnu/guix/guix-system-install-1.1.0.x86_64-linux.iso.xz.sig
Here is the QCOW2 virtual machine (VM) image and its signature[*]:
https://ftp.gnu.org/gnu/guix/guix-system-vm-image-1.1.0.x86_64-linux.xz
https://ftp.gnu.org/gnu/guix/guix-system-vm-image-1.1.0.x86_64-linux.xz.sig
Here are the binary tarballs and their signatures[*]:
https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.i686-linux.tar.xz
https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.i686-linux.tar.xz.sig
https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.x86_64-linux.tar.xz
https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.x86_64-linux.tar.xz.sig
https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.armhf-linux.tar.xz
https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.armhf-linux.tar.xz.sig
https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.aarch64-linux.tar.xz
https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.aarch64-linux.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA256 checksums:
5c59106ff4ac497c6097686834b0c914109cf5e44eb6b94ebce818923043640f
guix-1.1.0.tar.gz
f81b529c4a94d0ab2cfc6df9819af3d7e2ccfcf17ef7f901e1d2df0a63516ab6
guix-binary-1.1.0.aarch64-linux.tar.xz
4d08782979383c2848ca1c0ca9478cbfb4f9181d94370f4226398fbb51fd1d24
guix-binary-1.1.0.armhf-linux.tar.xz
33472a26cdf515ba496f770602ead6369ee6dc3dc6b679c279e1f5c4d8cd63fa
guix-binary-1.1.0.i686-linux.tar.xz
eae0b8b4ee8ba97e7505dbb85d61ab2ce7f0195b824d3a660076248d96cdaece
guix-binary-1.1.0.x86_64-linux.tar.xz
848c9a6a73cf4cf6fe4e7d5815342a9c40ec01fd93c23b5d4e12d41b18b16bb5
guix-system-install-1.1.0.i686-linux.iso.xz
ff2d74f64d8e1545271ab0f46ee0e11ae96fbb09cb105c3d929c9e123ad00ce2
guix-system-install-1.1.0.x86_64-linux.iso.xz
519d93fb27d33a97db568225bfa4e84f0cfc95bd173f5bf8277cb4098ae46b43
guix-system-vm-image-1.1.0.x86_64-linux.xz
[*] Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact. First, be sure to download both the .sig file
and the corresponding tarball. Then, run a command like this:
gpg --verify guix-1.1.0.tar.gz.sig
If that command fails because you don't have the required public key,
then run this command to import it:
gpg --keyserver keys.openpgp.org \
--recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
and rerun the 'gpg --verify' command.
To install the standalone Guix system, please see “System
Installation” in the manual. To install Guix on a running system, see
“Installation” in the manual.
• Changes since version 1.0.1 (excerpt from the NEWS file)
** Package management
*** New ‘guix deploy’ command to deploy several machines at once
*** Channels can now provide news, viewed with ‘guix pull --news’
*** ‘guix system reconfigure’ saves provenance data
*** New ‘guix system describe’ command to view system provenance info
*** New /run/current-system/{channels,configuration}.scm files
*** New ‘guix time-machine’ command
*** ‘guix pack’ has a new ‘--entry-point’ option
*** ‘guix pack’ saves environment variables for ‘docker’ and ‘singularity’
*** ‘guix pack’ provides a meaningful repository name for ‘docker’
*** New ‘--target’ option for ‘guix system’
*** ‘--no-build-hook’ was renamed to ‘--no-o
Re: about basic operation of guix sd
hi, thank you for your reply. On Wed, Apr 8, 2020 at 1:30 AM Julien Lepiller wrote: > I think this is a bad idea, because it might break assumptions of the > mathematical model guix relies on. Not sure how to sync two stores > automatically. The "guix copy" command can be used to do that manually. Note > that guix publish will publish your whole /gnu/store, independently of how > items were obtained. > > If you use guix publish for things that were not built on the official build > farm, you need to have a look at guix --archive to generate key pairs and > authorize your personal substitute server. For items that were built on the > official build farm, it is enough to authorize the build farm, because these > items will be detected as identical, even if they come from a different > source. Thanks, lazy evaluating "Invoking guix copy", it seems to be handy for each target package! > The manual has a section "the perfect setup" that should explain everything > if you want to contribute. > > Guix pull is indeed more or less a wrapper around git pull. The repository is > available in the store, but because of the mathematical model, it is > read-only and must not be modified. You can still use "guix edit foo" to open > the package definition of foo in your favorite editor. OK, I wil read that section throughly when time come. For now I have to used to its daily administration... >> If this is not for a contribution, the next best thing you can do is create >> a channel that allows you to share your modifications (or you can keep them >> private, but share them between your computers). > > Note that the guix-daemon is only there to build and download packages, it > doesn't know anything about available packages, etc. Your guix command does. > That allows each user on your system to customize the set of available > packages. Anyway, I use GUIX_PACKAGE_PATH and have managed to build small font package recipe. With some more, I will try it migrating to channel. regards, -- KURASHIKI Satoru
Re: about basic operation of guix sd
hi, thank you for your reply. On Wed, Apr 8, 2020 at 1:27 AM Marius Bakke wrote: > > Hi Satoru, and welcome to Guix! I hope you will enjoy your stay. :-) > > Satoru KURASHIKI writes: > > > hi, > > > > I happen to know Guix SD recently, and trying to tinkering it. > > FYI the 'SD' name has been deprecated in favor of 'Guix System'. Ah, I see, so there are several bindings...:) > Syncing /gnu/store will not work without also syncing /var/guix/db. I > think what you want to do is on host1 run 'guix publish' as you already > found, and on host2 you can then use 'guix install foo > --substitute-urls="https://host1 https://ci.guix.gnu.org";' to get > substitutes from both host1 and the Guix CI infrastructure. > > See https://guix.gnu.org/manual/en/guix.html#Invoking-guix-publish for a > more complete explanation. > hmm...OK, so it's dificult to have a partial mirror on my tiny VPS. # I thought of pushing to VPS from my desktop, and fetch them from # old laptop when I'm away from home. (to demonstrate guix to friends) ## mainly for iwlwifi things and so on. kernel demands me one night. > To do this through the configuration system, you need > 'guix-publish-service-type' and adjusting the 'substitute-urls' field of > 'guix-service-type'. > > > - The right way of treating guix code (or guile code structure?) > > - I have to clone guix repo into my home directory? > > - Though "guix pull" should have source tree anywhere (in > > /gnu/store?), so are there any interfaces > > to access them through guix-daemon? > > - I want to tweak existing code (package definition) > > - I should copy target file to somewhere working directory to edit > > or edit target file in the project tree？ > > After cloning the Guix repository, you can run Guix directly from the > checkout using the "./pre-inst-env" script: see the Contributing > section of the manual for how to configure a development environment: > > https://guix.gnu.org/manual/en/guix.html#Contributing > > Another alternative is to use 'guix pull --url=/your/cloned/repository'. Hacking guix itself is... difficult for me, so I expect guix command to work out of the box: - invoke "current" guix - it refers current store (readonly), cloned checkout of guix tree (overriding current one), and my local package module would be desirable. > You can get completion and jumping through Geiser, but I don't have > instructions at hand. Hopefully some of the Emacs gurus can chime in > here. :-) I've found setting "geiser-guile-load-path" and Autodoc seems to work. I will try to build environment on this. regards, -- KURASHIKI Satoru
Re: GNU Guix 1.1.0 released
Hi Ludovic, Thanks! And JFYI: ... gpg: Note: signature key 090B11993D9AEBB5 expired Mon Feb 18 16:18:37 2019 MSK gpg: Note: This key has expired! -- Vladimir (λ)επτόν EDA — https://github.com/lepton-eda
Re: GNU Guix 1.1.0 released
Vladimir, Vladimir Zhbanov 写道： And JFYI: ... gpg: Note: signature key 090B11993D9AEBB5 expired Mon Feb 18 16:18:37 2019 MSK gpg: Note: This key has expired! Only your local copy of that key is out of date. You can refresh your entire keyring with $ gpg --refresh-keys or fetch only Ludo's key directly from Savannah: $ curl -L 'https://savannah.gnu.org/people/viewgpg.php?user_id=15145' | gpg --import HTH, T G-R signature.asc Description: PGP signature
Re: about basic operation of guix sd
Le 15 avril 2020 10:23:40 GMT-04:00, Satoru KURASHIKI a écrit : >hi, thank you for your reply. > >On Wed, Apr 8, 2020 at 1:30 AM Julien Lepiller >wrote: >> I think this is a bad idea, because it might break assumptions of the >mathematical model guix relies on. Not sure how to sync two stores >automatically. The "guix copy" command can be used to do that manually. >Note that guix publish will publish your whole /gnu/store, >independently of how items were obtained. >> >> If you use guix publish for things that were not built on the >official build farm, you need to have a look at guix --archive to >generate key pairs and authorize your personal substitute server. For >items that were built on the official build farm, it is enough to >authorize the build farm, because these items will be detected as >identical, even if they come from a different source. > >Thanks, lazy evaluating "Invoking guix copy", it seems to be handy for >each target package! > >> The manual has a section "the perfect setup" that should explain >everything if you want to contribute. >> >> Guix pull is indeed more or less a wrapper around git pull. The >repository is available in the store, but because of the mathematical >model, it is read-only and must not be modified. You can still use >"guix edit foo" to open the package definition of foo in your favorite >editor. > >OK, I wil read that section throughly when time come. >For now I have to used to its daily administration... > >>> If this is not for a contribution, the next best thing you can do is >create a channel that allows you to share your modifications (or you >can keep them private, but share them between your computers). >> >> Note that the guix-daemon is only there to build and download >packages, it doesn't know anything about available packages, etc. Your >guix command does. That allows each user on your system to customize >the set of available packages. > >Anyway, I use GUIX_PACKAGE_PATH and have managed to build small font >package recipe. >With some more, I will try it migrating to channel. GUIX_PACKAGE_PATH is the deprecated way to use a channel (introduced before tge notion of channels). If you have a working dehinition with it, you can simply do "git init" and push it as a new repo somewhere. Then, set up your ~/.config/guix/channels.scm to use it. To test changes in your channel you can use "-L path/to/channel/root" (same as what you pass to GUIX_PACKAGE_PATH) with any guix command. > >regards, >-- >KURASHIKI Satoru
Re: GNU Guix 1.1.0 released
Thank you very much for the new release! GNU Guix is one of the most
important project in free software today
On Wed, Apr 15, 2020 at 6:19 AM Ludovic Courtès wrote:
> We are pleased to announce the release of GNU Guix 1.1.0.
>
> This release corresponds to 14,078 commits over 11 months by 201 people.
> It includes many new features, user interface and performance
> improvements, as well as many bug fixes—see below for a list of changes.
>
> Read more about today’s announcement at:
>
> https://guix.gnu.org/blog/2020/gnu-guix-1.1.0-released
>
> • About
>
> GNU Guix is a transactional package manager and an advanced
> distribution of the GNU system that respects user freedom. Guix can
> be used on top of any system running the kernel Linux, or it can be
> used as a standalone operating system distribution for i686, x86_64,
> ARMv7, and AArch64 machines.
>
> In addition to standard package management features, Guix supports
> transactional upgrades and roll-backs, unprivileged package
> management, per-user profiles, and garbage collection. When used as a
> standalone GNU/Linux distribution, Guix offers a declarative,
> stateless approach to operating system configuration management. Guix
> is highly customizable and hackable through Guile programming
> interfaces and extensions to the Scheme language.
>
> https://guix.gnu.org
>
> • Download
>
> Here are the compressed sources and a GPG detached signature[*]:
> https://ftp.gnu.org/gnu/guix/guix-1.1.0.tar.gz
> https://ftp.gnu.org/gnu/guix/guix-1.1.0.tar.gz.sig
>
> Here are the bootable USB installation images and their signatures[*]:
>
> https://ftp.gnu.org/gnu/guix/guix-system-install-1.1.0.i686-linux.iso.xz
>
> https://ftp.gnu.org/gnu/guix/guix-system-install-1.1.0.i686-linux.iso.xz.sig
>
> https://ftp.gnu.org/gnu/guix/guix-system-install-1.1.0.x86_64-linux.iso.xz
>
> https://ftp.gnu.org/gnu/guix/guix-system-install-1.1.0.x86_64-linux.iso.xz.sig
>
> Here is the QCOW2 virtual machine (VM) image and its signature[*]:
>
> https://ftp.gnu.org/gnu/guix/guix-system-vm-image-1.1.0.x86_64-linux.xz
>
> https://ftp.gnu.org/gnu/guix/guix-system-vm-image-1.1.0.x86_64-linux.xz.sig
>
> Here are the binary tarballs and their signatures[*]:
> https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.i686-linux.tar.xz
> https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.i686-linux.tar.xz.sig
> https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.x86_64-linux.tar.xz
> https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.x86_64-linux.tar.xz.sig
> https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.armhf-linux.tar.xz
> https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.armhf-linux.tar.xz.sig
> https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.aarch64-linux.tar.xz
>
> https://ftp.gnu.org/gnu/guix/guix-binary-1.1.0.aarch64-linux.tar.xz.sig
>
> Use a mirror for higher download bandwidth:
> https://www.gnu.org/order/ftp.html
>
> Here are the SHA256 checksums:
>
> 5c59106ff4ac497c6097686834b0c914109cf5e44eb6b94ebce818923043640f
> guix-1.1.0.tar.gz
> f81b529c4a94d0ab2cfc6df9819af3d7e2ccfcf17ef7f901e1d2df0a63516ab6
> guix-binary-1.1.0.aarch64-linux.tar.xz
> 4d08782979383c2848ca1c0ca9478cbfb4f9181d94370f4226398fbb51fd1d24
> guix-binary-1.1.0.armhf-linux.tar.xz
> 33472a26cdf515ba496f770602ead6369ee6dc3dc6b679c279e1f5c4d8cd63fa
> guix-binary-1.1.0.i686-linux.tar.xz
> eae0b8b4ee8ba97e7505dbb85d61ab2ce7f0195b824d3a660076248d96cdaece
> guix-binary-1.1.0.x86_64-linux.tar.xz
> 848c9a6a73cf4cf6fe4e7d5815342a9c40ec01fd93c23b5d4e12d41b18b16bb5
> guix-system-install-1.1.0.i686-linux.iso.xz
> ff2d74f64d8e1545271ab0f46ee0e11ae96fbb09cb105c3d929c9e123ad00ce2
> guix-system-install-1.1.0.x86_64-linux.iso.xz
> 519d93fb27d33a97db568225bfa4e84f0cfc95bd173f5bf8277cb4098ae46b43
> guix-system-vm-image-1.1.0.x86_64-linux.xz
>
> [*] Use a .sig file to verify that the corresponding file (without the
> .sig suffix) is intact. First, be sure to download both the .sig file
> and the corresponding tarball. Then, run a command like this:
>
> gpg --verify guix-1.1.0.tar.gz.sig
>
> If that command fails because you don't have the required public key,
> then run this command to import it:
>
> gpg --keyserver keys.openpgp.org \
> --recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
>
> and rerun the 'gpg --verify' command.
>
> To install the standalone Guix system, please see “System
> Installation” in the manual. To install Guix on a running system, see
> “Installation” in the manual.
>
> • Changes since version 1.0.1 (excerpt from the NEWS file)
>
> ** Package management
> *** New ‘guix deploy’ command to deploy several machines at once
> *** Channels can now provide news, viewed with ‘guix pull --news’
> *** ‘guix system reconfigure’ saves provenance data
> *** New ‘guix system describe’ command to view system provenance info
> *** New /run/current-system/{channels,configuration}.scm files
> *** New ‘gu
Re: GNU Guix 1.1.0 released
Everyone, Ludovic Courtès 写道： 14,078 commits over 11 months by 201 people. Thank you, thank you, thank you. All 200 of you. Andy Tai 写道： GNU Guix is one of the most important project in free software today This is absolute truth. Kind regards, T G-R signature.asc Description: PGP signature
