From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thompson, David" Subject: bug#22695: Binary Installation bugs and suggestions Date: Tue, 16 Feb 2016 09:00:41 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52761) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVgBg-0001ME-VS for bug-guix@gnu.org; Tue, 16 Feb 2016 09:01:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aVgBa-00072H-P3 for bug-guix@gnu.org; Tue, 16 Feb 2016 09:01:08 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:50160) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVgBa-00072A-Hi for bug-guix@gnu.org; Tue, 16 Feb 2016 09:01:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aVgBa-0005CM-Bz for bug-guix@gnu.org; Tue, 16 Feb 2016 09:01:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: myglc2 Cc: 22695@debbugs.gnu.org On Tue, Feb 16, 2016 at 8:41 AM, myglc2 wrote: > I attempted to perform 'Binary Installation' on Debian 8 following ... > > https://www.gnu.org/software/guix/manual/html_node/Binary-Installation.ht= ml#Binary-Installation > > last updated November 04, 2015 > > > Bugs: > > A) The 4 occurrences of '~root' should be replaced with '/root' Not a bug. '~root' expands to '/root' or whatever the root user's home directory is. > B) What does 'On hosts using the systemd init system, drop > /root/.guix-profile/lib/systemd/system/guix-daemon.service in > /etc/systemd/system.' mean. > > FWIW, I tried ... > > cp /root/.guix-profile/lib/systemd/system/guix-daemon.service \ > /etc/systemd/system/guix-daemon.service > > ... which did not work. What didn't work, exactly? I've personally done this on systemd setups and it works fine. > Suggestions: > > 1)'guix archive --authorize < /root/.guix-profile/share/guix/hydra.gnu.o= rg.pub' > > ... produced ... > > 'warning: failed to install locale: Invalid argument' > > It is not good that the first guix operation that root attempts > throws a warning. Apparently this is to be expected, as careful > study of '2.6 Application Setup' might suggest. As a minimum, we > should advise root that the warning is expected. This warning is unavoidable when the glibc on the host distro has locales that our incompatible with the glibc that Guix uses. It's unfortunate, but *much time* was spent dealing with this headache already, including time spent talking to glibc developers. > 2) 'And that=E2=80=99s it! For additional tips and tricks, see Applicatio= n > Setup.' should be changed to say something like, 'This completes > root-level install of Guix, However each of your users will need to > first set their Locales and, if they intend to use X Window system, > X11 fonts, as described in '2.6 Application Setup' before Guix will > be fully functional. That sounds mostly fine, but I don't understand the X11 fonts part. I use Guix on foreign distros and have no such issues regarding fonts. > 3) Is it possible for root to pre-configure locales and X11 fonts for > users? They would have to modify that user's package profile and .bash_profile, which I don't think we would want to recommend. > 4) What do we mean by, 'The guix package must remain available in root=E2= =80=99s > profile, or it would become subject to garbage collection=E2=80=94in w= hich > case you would find yourself badly handicapped by the lack of the > guix command.' > > What does root have to do to assure that 'The guix package remains > available'? Don't run 'guix package -r guix'. > 5) We should tell root how to verify that the installation was > successful. If 'make guix-binary.system.tar.xz' is intended to do > this, we need to explain where to run it and how to verify the > result. 'make guix-binary.system.tar.xz' is how you reproduce the binary tarball, not how you verify the build was successful. If the installation is successful, then running 'guix build hello' or anything else like that should work. > 6) Should a root 'guix pull' be recommended? I don't think so. It only affects the root user, and most people use Guix as their regular user. So, if anything, we should recommend 'guix pull' be run for their regular unprivileged user. > 7) Given the "invasive" nature of this install, an uninstall script, or, > as a minimum, explicit instructions of how to remove Guix, really > must be provided. The install is absolutely not invasive. Guix is entirely self-contained and does not affect the host distro at all. Remove /gnu and /var/guix and it is uninstalled. > 8) It seems unlikely that a typical sysadmin will be willing to install > Guix following the instructions as they now stand. This might be > addressed by providing a Guix package for popular distributions. This has been mentioned many times, but does anyone actually want to step up and do the work? Getting such packages into upstream distros is unlikely because Guix does not conform to the FHS, but we can provide the packages on our own website. Personally, I feel that the instructions are so few that it's easy to do by myself and it also informs me about what exactly is going on with my system. > 9) We leave the root user with no locales or X11 fonts. Do we recommend > this? Again, I don't understand the X11 fonts part, but this problem only happens when the host distro uses a glibc with incompatible locales. - Dave