setlocale: LC_ALL: cannot change locale (en_US.utf8)
Hi Guix,
I recently reinstalled Arch Linux with the Guix binary distribution on
my desktop, and since then I've had some strange error messages whenever
a Guix command is running:
/gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash:
warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
/gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash:
warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
I have LANG set to en_GB.UTF-8, and glibc-locales is installed with
GUIX_LOCPATH set properly:
$ ls $GUIX_LOCPATH/2.28/{en_GB.UTF-8,en_US.UTF-8}
/home/josh/.guix-profile/lib/locale/2.28/en_GB.UTF-8:
LC_ADDRESS LC_CTYPE LC_MEASUREMENT LC_MONETARY LC_NUMERIC
LC_TELEPHONE
LC_COLLATE LC_IDENTIFICATION LC_MESSAGES LC_NAME LC_PAPERLC_TIME
/home/josh/.guix-profile/lib/locale/2.28/en_US.UTF-8:
LC_ADDRESS LC_CTYPE LC_MEASUREMENT LC_MONETARY LC_NUMERIC
LC_TELEPHONE
LC_COLLATE LC_IDENTIFICATION LC_MESSAGES LC_NAME LC_PAPERLC_TIME
I asked in the IRC channel, and the only suggestion was to check whether that
copy
of bash was indeed using glibc 2.28, which it is:
/gnu/store/q19l04vd2za80mk1845pz7r8cz29qk43-bash-minimal-4.4.23/bin/bash: ELF
64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked,
interpreter
/gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib/ld-linux-x86-64.so.2,
for GNU/Linux 2.6.32, not stripped
I've not seen this problem on either of the two other machines I've
installed Guix on, and not before I reinstalled. Does anybody have
any ideas?
--
Josh Holland
Re: warning: setlocale: LC_ALL: cannot change locale on foreign distro
Hi Guix, It's only now I reply to this that I notice that it wasn't my thread I was responding to, since I was having exactly the same problem. On Mon, Jun 03, 2019 at 02:01:50PM -0400, Jack Hill wrote: > 1) The default locale in the provided systemd unit, en_US.utf8, is not > provided by the glibc-locales package but rather only by the > glibc-utf8-locales package. Installing glibc-utf8-locales has made the errors go away. > > 2) The quoting in systemd unit is wrong. Changing > > ``` > Environment=GUIX_LOCPATH='/var/guix/profiles/per-user/root/guix-profile/lib/locale' > LC_ALL=en_US.utf8 > ``` > > to > > > ``` > Environment='GUIX_LOCPATH=/var/guix/profiles/per-user/root/guix-profile/lib/locale' > LC_ALL=en_US.utf8 > ``` > > fixed the problem. I've made this change too, though it appeared to be fixed just by installing glibc-utf8-profiles. > > I'll open bugs for each of these issues. Glad that these won't be a problem any more; thanks a lot! -- Josh Holland
guix upgrade: packages to upgrade, but nothing to be done
Hi Guix, This is not a super-major issue, but I'm a little confused as to what's going on. If I run `guix upgrade` (on a freshly-pulled guix), I get the following output: $ guix upgrade The following packages will be upgraded: transmission:gui 2.94 → 2.94 /gnu/store/4q11i2maw5rim3sv5fglpn1pc8nmk6bd-transmission-2.94-gui zathura 0.4.3 → 0.4.3 /gnu/store/pvl4hys5i37a6b321rnml21wkm9xx296-zathura-0.4.3 streamlink 0.14.2 → 0.14.2 /gnu/store/04kjbcsypn12wvjplvais7ync7c2d1d2-streamlink-0.14.2 guile2.2.6 → 2.2.6 /gnu/store/zp53jz14ql8syglh4nyrwmq2awvfirb8-guile-2.2.6 glibc-locales2.28 → 2.28 /gnu/store/bb9alx1ap57pz0vmx7p1r8qk0lxxfg3x-glibc-locales-2.28 git:send-email 2.22.0 → 2.22.0 /gnu/store/0h88j29z674whbwvq0klwwv6p7nqapxx-git-2.22.0-send-email git:credential-netrc 2.22.0 → 2.22.0 /gnu/store/4x9x7blnfd20r1kypr93472f3mlsh6xh-git-2.22.0-credential-netrc emacs-use-package2.4 → 2.4 /gnu/store/2lsz1bb9w06y35jsz6q940jhqjva9i5x-emacs-use-package-2.4 emacs-request0.3.0 → 0.3.0 /gnu/store/1wgmfcigry8k2yxzg3mcwjl6ix7rqlwv-emacs-request-0.3.0 emacs-org-caldav 20180403 → 20180403 /gnu/store/77yvd57qbjyxl32nqd8l2bs9w5zphcd9-emacs-org-caldav-20180403 emacs-magit 2.90.1-1.b4aec01 → 2.90.1-1.b4aec01 /gnu/store/8zh9k3ykp5d5a2ssp2mqwrnacdbdvhfg-emacs-magit-2.90.1-1.b4aec01 emacs-haskell-mode 16.1 → 16.1 /gnu/store/5jhjnq8198jqrdzrjh5qs8l5gq7gry64-emacs-haskell-mode-16.1 emacs-guix 0.5.1.1 → 0.5.1.1 /gnu/store/flids6v745dm800hqcs6q8icqykm7vjl-emacs-guix-0.5.1.1 emacs-flycheck 31 → 31 /gnu/store/65dsxk1rinn513cycg99awd1gq6sy6vc-emacs-flycheck-31 emacs-company-auctex 0-1.48c42c5 → 0-1.48c42c5 /gnu/store/p36y0kbza7g36kijy99dkwxgvgx90ddh-emacs-company-auctex-0-1.48c42c5 nothing to be done I've seen packages being "upgraded" to the same version that they already are before, and I am led to understand that this is typically due to some input being upgraded. But why are no changes actually being performed in the end? Thanks, Josh -- Josh Holland
Re: A 'guix pull' option for 'manifest.scm' to be used in the next update
Hi Hubert, hub.lomb...@free.fr writes: > In order for 'manifest.scm' to be used in the next update, should I do > something like this: > > $ guix pull -p, --profile=PROFILE > > (using PROFILE instead of ~/.config/guix/current) `guix pull` is not the command that you should be passing your manifest file to. If you are familiar with Debian-based distros, then `guix pull` is (somewhat) analogous to `apt update`: it gets updated package definitions (and also updates the guix program itself) but doesn't make any changes to packages you have installed. Also, I think you have misunderstood what the PROFILE option is referring to. A "profile" in Guix is a collection of packages. Usually you'll have a single profile for each user, and perhaps some ad-hoc profiles created behind the scenes by running `guix environment`. In several months of running Guix, I've never needed to use the --profile option. To actually use the manifest, you want to pass it to `guix package`. For example, here's the command I normally run to upgrade everything: $ guix pull && guix package -m ~/guix-packages.scm -u . Thanks, Josh
Re: A 'guix pull' option for 'manifest.scm' to be used in the next update
Hi Hubert, hub.lomb...@free.fr writes: > So maybe (I'm not sure) I can try, considering the path of my manifest.scm: > > $ guix pull && guix package -m ~/.config/guix/manifest.scm -u Yep, if that's the right path to where you saved your manifest file. (Note that the -u option, upgrade, takes an optional argument, a regexp matching which packages to act on. I prefer to explicitly pass in `-u.` to match anything since I normally run this command from my shell history, and I can then just add any other options I want without them being interpreted as an argument to -u.) > Otherwise, unless I have to move my file to another place? You can save the manifest file wherever you want, since you pass the path into `guix package` with the -m option it'll always be able to find it. Thanks, Josh
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
