Re: Files not .gitignored when contributing to Guix
On Fri, Jan 17, 2020 at 02:19:35PM -0500, Julien Lepiller wrote: > Le 17 janvier 2020 13:57:56 GMT-05:00, EuAndreh via a > écrit : > >Hi Guix! > > > >When running the setup steps to prepare a patch, I find myself with a > >dirty repository of changed files. Is this expected behaviour? > > > >I couldn't find guidance regarding that on the manual or the mailing > >list archives (only a similar issue[0]), and I wonder if is there a way > >to avoid it, or should I just get used to it? Is there something > >missing > >for things being this way that I didn't get yet? > > > >The output of make spits some warning regarding outdated .po files. If > >the dirty files are generated, should they even be commited in the > >repository if they are derived data? Looking at the diff, it confirms > >this hypothesis: the diff of the .po files contain mostly generated > >translation strings and timestamps. > > > >The setup steps I use are: > >--8<---cut here---start->8--- > >cd $GUIX_REPO > >git clean -ffdx > >guix environment guix --ad-hoc help2man git strace > >./bootstrap > >./configure --localstatedir=/var > >make > >--8<---cut here---end--->8--- > > > >At the end the dirty files are: > >--8<---cut here---start->8--- > >$ git status > >Sur la branche master > >Modifications qui ne seront pas validées : > >(utilisez "git add ..." pour mettre à jour ce qui sera validé) > >(utilisez "git restore ..." pour annuler les modifications > >dans le répertoire de travail) > >modifié : po/guix/cs.po > >modifié : po/guix/da.po > >modifié : po/guix/de.po > >modifié : po/guix/eo.po > >modifié : po/guix/es.po > >modifié : po/guix/fr.po > >modifié : po/guix/hu.po > >modifié : po/guix/pl.po > >modifié : po/guix/pt_BR.po > >modifié : po/guix/sr.po > >modifié : po/guix/sv.po > >modifié : po/guix/vi.po > >modifié : po/guix/zh_CN.po > >modifié : po/packages/da.po > >modifié : po/packages/de.po > >modifié : po/packages/eo.po > >modifié : po/packages/es.po > >modifié : po/packages/fr.po > >modifié : po/packages/hu.po > >modifié : po/packages/pl.po > >modifié : po/packages/pt_BR.po > >modifié : po/packages/sr.po > >modifié : po/packages/vi.po > >modifié : po/packages/zh_CN.po > > > >aucune modification n'a été ajoutée à la validation (utilisez "git add" > >ou "git commit -a") > >--8<---cut here---end--->8--- > > > >I'm looking to a better way to handle this situation (that I find a bit > >of a nuisance right now) or maybe just an explanation behind the way > >things currently are. > > > >Thanks :) > >EuAndreh > > > >[0]: > >https://lists.gnu.org/archive/html/guix-devel/2018-12/msg00387.html > > You should do "git checkout po" after your first make. You won't be annoyed > by that anymore afterwards. > IIRC the reason for having it this way is if the .po files are added to .gitignore then it messes with the guix snapshots and releases. Unfortunately I don't remember more than that. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
guix pull: error: symlink: File exists
Hi, I'm working on an Alpine Docker image with the Guix package manager [1]. The container is building and can run Guix without the ``--privileged`` option. The installation process is based on the documentation and the installation script [2]. Everything is working fine however, when I run ``guix pull`` in the generated image, I got the following error: Migrating profile generations to '/var/guix/profiles/per-user/root'... guix pull: error: symlink: File exists: " /var/guix/profiles/per-user/root/current-guix" This issue has already been discussed at [3] but the workaround to delete all the links in the directory ``/var/guix/profiles/per-user/root`` is causing some troubles: 1. If I want to ship a ready to use image and delete the links upfront, ``guix daemon`` will fail to start since ``/root/.config/guix/current`` is broken. 2. Users of the image can delete the links themselves but this is not really friendly. So what is exactly causing this error and what would be a good option to fix it? [1] https://hub.docker.com/repository/docker/x237net/alpine-guix [2] https://git.savannah.gnu.org/cgit/guix.git/plain/etc/guix-install.sh [3] https://lists.gnu.org/archive/html/help-guix/2018-12/msg00098.html
Re: TeX Live issues
Je 18 jan 16:12 skribis Ricardo: > Can you show us what “guix package -I | grep texlive” says? Also please > remove ~/.texlive* if it exists and show us the output of “env”. marco@graviton ~$ guix package -I | grep texlive guile: warning: failed to install locale texlive-fonts-latex 49435 out /gnu/store/5m5nqvjvykw9xgfsv4azs4iv2dw03kf0-texlive-fonts-latex-49435 texlive 20180414out /gnu/store/wlba9v03ypi0z5qz7p89sa0w12lh37zb-texlive-20180414 texlive-latex-base 51265 out /gnu/store/s9qr333cj87mc1gpns1xcid763mfgfz3-texlive-latex-base-51265 marco@graviton ~/temp$ rm -rf .texlive* marco@graviton ~/temp$ latex test.tex This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=latex) restricted \write18 enabled. ---! /home/marco/.guix-profile/share/texmf-dist/web2c/latex.fmt made by different executable version (Fatal format file error; I'm stymied) marco@graviton ~/temp$ env SHELL=/gnu/store/n1c9jiv2njnvdfz58v71fvzq0hkgivz1-bash-5.0.7/bin/bash WINDOWID=41943043 FER_DATA=/scratch/fer_dsets/data COLORTERM=truecolor XDG_CONFIG_DIRS=/home/marco/.guix-profile/etc/xdg:/run/current-system/profile/etc/xdg FER_PALETTE=/home/marco/ferret/palettes /lokale-data/scratch/ferret/ppl BASH_LOADABLES_PATH=/run/current-system/profile/lib/bash LINUX_MODULE_DIRECTORY=/run/booted-system/kernel/lib/modules XCURSOR_PATH=/home/marco/.icons:/home/marco/.guix-profile/share/icons:/run/current-system/profile/share/icons FER_GO=/lokale-data/scratch/ferret/go /home/marco/ferret/scripts NM_VPN_PLUGIN_DIR=/gnu/store/70sm39p9sxrjjlg66r5fgxs9aik1fvnj-network-manager-vpn-plugins/lib/NetworkManager/VPN SWM_STARTED=YES GPG_TTY=/dev/pts/4 GTK_DATA_PREFIX=/run/current-system/profile XDG_SEAT=seat0 PWD=/home/marco/temp LOGNAME=marco XDG_SESSION_TYPE=x11 MANPATH=/run/current-system/profile/share/man:/home/marco/.guix-profile/share/man:/run/current-system/profile/share/man GUILE_LOAD_PATH=/home/marco/.guix-profile/share/guile/site/2.2:/run/current-system/profile/share/guile/site/2.2 XAUTHORITY=/home/marco/.Xauthority FER_FONTS=/lokale-data/scratch/ferret/ppl/fonts X_XFCE4_LIB_DIRS=/run/current-system/profile/lib/xfce4 LD_PRELOAD=/gnu/store/dh3243hav0ldyy42sd0b0p7f52s1ns7f-spectrwm-3.2.0/lib/libswmhack.so.0.0 GIT_EXEC_PATH=/home/marco/.guix-profile/libexec/git-core HOME=/home/marco _SWM_PID=22164 GIT_SSL_CAINFO=/etc/ssl/certs/ca-certificates.crt LANG=en_US.utf8 FER_GRIDS=/scratch/fer_dsets/grids VTE_VERSION=5802 TEXMF=/home/marco/.guix-profile/share/texmf-dist SSL_CERT_DIR=/etc/ssl/certs _SWM_WS=3 GIO_EXTRA_MODULES=/home/marco/.guix-profile/lib/gio/modules:/home/marco/.guix-profile/lib/gio/modules PULSE_CLIENTCONFIG=/etc/pulse/client.conf GUILE_LOAD_COMPILED_PATH=/home/marco/.guix-profile/lib/guile/2.2/site-ccache:/run/current-system/profile/lib/guile/2.2/site-ccache INFOPATH=/home/marco/.config/guix/current/share/info:/home/marco/.guix-profile/share/info:/run/current-system/profile/share/info:/home/marco/.guix-profile/share/info:/run/current-system/profile/share/info DICPATH=/home/marco/.guix-profile/share/hunspell:/run/current-system/profile/share/hunspell XDG_SESSION_CLASS=user DBUS_FATAL_WARNINGS=0 PYTHONPATH=/home/marco/.guix-profile/lib/python3.7/site-packages:/home/marco/.guix-profile/lib/python3.7/site-packages TERM=xterm-termite TEXMFCNF=/home/marco/.guix-profile/share/texmf-dist/web2c ACLOCAL_PATH=/home/marco/.guix-profile/share/aclocal USER=marco LIBRARY_PATH=/home/marco/.guix-profile/lib:/home/marco/.guix-profile/lib FER_DIR=/lokale-data/scratch/ferret TZDIR=/gnu/store/9mmsilz9avdl49i6a6nj5mzfyim8ihv2-tzdata-2019c/share/zoneinfo VISUAL=vim DISPLAY=:0 SHLVL=1 PLOTFONTS=/lokale-data/scratch/ferret/ppl/fonts GUIX_LOCPATH=/home/marco/.guix-profile/lib/locale XDG_VTNR=7 XDG_SESSION_ID=c5 GST_PLUGIN_PATH=/home/marco/.guix-profile/lib/gstreamer-1.0 TERMINFO_DIRS=/home/marco/.guix-profile/share/terminfo XDG_RUNTIME_DIR=/run/user/1000 SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt PULSE_CONFIG=/etc/pulse/daemon.conf XDG_DATA_DIRS=/home/marco/.guix-profile/share:/run/current-system/profile/share:/home/marco/.guix-profile/share:/run/current-system/profile/share PATH=/run/setuid-programs:/home/marco/.config/guix/current/bin:/home/marco/.guix-profile/bin:/home/marco/.guix-profile/sbin:/run/current-system/profile/bin:/run/current-system/profile/sbin FER_DESCR=/scratch/fer_dsets/descr FER_DSETS=/scratch/fer_dsets MAIL=/var/mail/marco CPATH=/home/marco/.guix-profile/include:/home/marco/.guix-profile/include GUIX_GTK3_PATH=/run/current-system/profile/lib/gtk-3.0 _=/run/current-system/profile/bin/env OLDPWD=/home/marco —Marco
Re: TeX Live issues
Marco van Hulten writes: > $ lualatex test > This is LuaTeX, Version 1.07.0 (TeX Live 2018) > restricted system commands enabled. > > (Fatal format file error; I'm stymied) > $ latex test > This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded > format=latex) > restricted \write18 enabled. > ---! /home/marco/.guix-profile/share/texmf-dist/web2c/latex.fmt made by > different executable version > (Fatal format file error; I'm stymied) Can you show us what “guix package -I | grep texlive” says? Also please remove ~/.texlive* if it exists and show us the output of “env”. -- Ricardo
Re: TeX Live issues
Je 17 jan 13:05 skribis Ricardo: > Marco van Hulten writes: > > > Ricardo— > > > > On 17 Jan 10:03 Ricardo Wurmus wrote: > >> > I am unable to use LaTeX and friends. I get this error: > >> > >> Hmm, something broke here. I also cannot compile my older documents any > >> more. I’ll investigate. > > > > That's great, thanks! > > This is now fixed on the core-updates branch. Note that it should not > be a problem that pdftex.map cannot be found. The PDF file gets > generated just fine. Thank you for fixing this bug! I switched to the core-updates branch, but I am not sure if I did it correctly. First I did guix pull --branch=core-updates which seemed to work fine as there is a new current-guix link. Then I tried guix package -i texlive-latex-base -u which did not succeed: ... readline 8.0 → 8.0.1 /gnu/store/hjh0n0f734q1mx9dnjlwisjl32nn43yl-readline-8.0.1 pinentry-gtk21.1.0 → 1.1.0 /gnu/store/g7ymwwc10gzzqkzbvnqxg07lvls369my-pinentry-gtk2-1.1.0 claws-mail 3.17.4 → 3.17.4 /gnu/store/6gzi2jhj5v1j3scrmfmcrckcph9vpjmz-claws-mail-3.17.4 The following package will be installed: texlive-latex-base 51265 /gnu/store/s9qr333cj87mc1gpns1xcid763mfgfz3-texlive-latex-base-51265 substitute: updating substitutes from 'https://ci.guix.gnu.org'... 162.2% guix package: error: got unexpected path `/gnu/store/dwynpdsqpw24q1rkia7j4ifscc1ph2wg-libfontenc-1.1.4.tar.bz2' from substituter (sorry for mangling of the lines; pasted text should never be touched, it's really Claws Mail's fault). Whereas that did not work, I was able to only install texlive-latex-base, but compilation of a document gives: $ lualatex test This is LuaTeX, Version 1.07.0 (TeX Live 2018) restricted system commands enabled. (Fatal format file error; I'm stymied) $ latex test This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=latex) restricted \write18 enabled. ---! /home/marco/.guix-profile/share/texmf-dist/web2c/latex.fmt made by different executable version (Fatal format file error; I'm stymied) So what my actual question here probably is: How do I make sure things are consistent when switching branch? —Marco
Re: Redshift and Geoclue
Hi Guix! Pierre Neidhardt writes: > Anyone using redshift on Guix? I am, but I hadn't got round to investigating geoclue yet so I'm just using -l and a hardcoded lat/long pair. -- Josh Holland
Avoiding the garbage collector for the Guix Data Service
Hey, The Guix Data Service has Guix compute lots of derivations, and then it loads the data in to a database. I'm having some issues with the garbage collector though, as sometimes it removes data from the disk before I've had a chance to read it (at least I think this is what's happening, I think this job failed for this reason [1]). 1: http://data.guix.gnu.org/job/10638 I'm not quite sure what the best strategy is to combat this? I had a look, and I couldn't see how to acquire a lock to prevent the garbage collector from running. I thought about registering thousands of gc roots, but that seems to just move the race a bit, as there's still a period between generating the derivation and registering the root where it can be deleted. Any ideas? Thanks, Chris signature.asc Description: PGP signature
