Search Result: keyserver

Results of 1 - 1 of about 98 for keyserver (0.001 sec.)

Binary Installation (GNU Guix Reference Manual): #score: 12976; @digest: be43985467c1a051b706e6ed599d6ca6; @id: 73715; @mdate: 2019-05-19T21:18:23Z; @size: 12187; @type: text/html; content-type: text/html; charset=utf-8; description: Binary Installation (GNU Guix Reference Manual); distribution: global; generator: makeinfo; keywords: Binary Installation (GNU Guix Reference Manual); resource-type: document; #keywords: systemctl (5223), upstart (4194), guix (4171), systemd (3708), profile (2517), authorize (2176), tarball (1983), quicker (1946), profiles (1831), daemon (1639), automates (1491), root (1129), binary (1034), installation (984), mkdir (794), current (760), xz (705), config (702), substitutes (690), installing (592), warnings (549), verify (519), system (476), tar (462), share (458), requirements (447), archive (445), invoking (440), download (436), installer (413), info (383), var (346); Next: Requirements , Up: Installation [ Contents ][ Index ] 2.1 Binary Installation This section describes how to install Guix on an arbitrary system from a self-contained tarball providing binaries for Guix and for all its dependencies. This is often quicker than installing from source, which is described in the next sections. The only requirement is to have GNU tar and Xz. Note: We recommend the use of this shell installer script . The script automates the download, installation, and initial configuration steps described below. It should be run as the root user. Installing goes along these lines: Download the binary tarball from ‘ https://ftp.gnu.org/gnu/guix/guix-binary-1.0.1. system .tar.xz ', where system is x86_64-linux for an x86_64 machine already running the kernel Linux, and so on. Make sure to download the associated .sig file and to verify the authenticity of the tarball against it, along these lines: $ wget https://ftp.gnu.org/gnu/guix/guix-binary-1.0.1. system .tar.xz.sig $ gpg --verify guix-binary-1.0.1. system .tar.xz.sig If that command fails because you do not have the required public key, then run this command to import it: $ gpg --keyserver pool.sks-keyservers.net \ --recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5 and rerun the gpg --verify command. Now, you need to become the root user. Depending on your distribution, you may have to run su - or sudo -i . As root , run: # cd /tmp # tar --warning=no-timestamp -xf \ guix-binary-1.0.1. system .tar.xz # mv var/guix /var/ && mv gnu / This creates /gnu/store (see The Store ) and /var/guix . The latter contains a ready-to-use profile for root (see next step.) Do not unpack the tarball on a working Guix system since that would overwrite its own essential files. The --warning=no-timestamp option makes sure GNU tar does not emit warnings about “implausibly old time stamps” (such warnings were triggered by GNU tar 1.26 and older; recent versions are fine.) They stem from the fact that all the files in the archive have their modification time set to zero (which means January 1st, 1970.) This is done on purpose to make sure the archive content is independent of its creation time, thus making it reproducible. Make the profile available under ~root/.config/guix/current , which is where guix pull will install updates (see Invoking guix pull ): # mkdir -p ~root/.config/guix # ln -sf /var/guix/profiles/per-user/root/current-guix \ ~root/.config/guix/current Source etc/profile to augment PATH and other relevant environment variables: # GUIX_PROFILE="`echo ~root`/.config/guix/current" ; \ source $GUIX_PROFILE/etc/profile Create the group and user accounts for build users as explained below (see Build Environment Setup ). Run the daemon, and set it to automatically start on boot. If your host distro uses the systemd init system, this can be achieved with these commands: # cp ~root/.config/guix/current/lib/systemd/system/guix-daemon.service \ /etc/systemd/system/ # systemctl start guix-daemon && systemctl enable guix-daemon If your host distro uses the Upstart init system: # initctl reload-configuration # cp ~root/.config/guix/current/lib/upstart/system/guix-daemon.conf \ /etc/init/ # start guix-daemon Otherwise, you can still start the daemon manually with: # ~root/.config/guix/current/bin/guix-daemon \ --build-users-group=guixbuild Make the guix command available to other users on the machine, for instance with: # mkdir -p /usr/local/bin # cd /usr/local/bin # ln -s /var/guix/profiles/per-user/root/current-guix/bin/guix It is also a good idea to make the Info version of this manual available there: # mkdir -p /usr/local/share/info # cd /usr/local/share/info # for i in /var/guix/profiles/per-user/root/current-guix/share/info/* ; do ln -s $i ; done That way, assuming /usr/local/share/info is in the search path, running info guix will open this manual (see Other Info Directories in GNU Texinfo , for more details on changing the Info search path.) To use substitutes from ci.guix.gnu.org or one of its mirrors (see Substitutes ), authorize them: # guix archive --authorize < \ ~root/.config/guix/current/share/guix/ci.guix.gnu.org.pub Each user may need to perform a few additional steps to make their Guix environment ready for use, see Application Setup . Voilà, the installation is complete! You can confirm that Guix is working by installing a sample package into the root profile: # guix install hello The binary installation tarball can be (re)produced and verified simply by running the following command in the Guix source tree: make guix-binary. system .tar.xz ... which, in turn, runs: guix pack -s system --localstatedir \ --profile-name=current-guix guix See Invoking guix pack , for more info on this handy tool. Next: Requirements , Up: Installation [ Contents ][ Index ] ...; http://www.gnu.org/savannah-checkouts/gnu/guix/manual/en/html_node/Binary-Installation.html - [detail] - [similar]

PREV NEXT