bug#37865: guix pull: error: You found a bug:
On Thu, 24 Oct 2019 13:49:56 -0700
Bengt Richter wrote:
> >
> > When invoking guix package -I for example, I encountered an error
> > like guile: failed to install locale
> >
>
> I have encountered the same error. It seems to recur for me after
> major updates. So there seems to be something lurking to reawaken the
> real error message source. I collected some symptoms and posted them
> as bug#37900.
>
Hello Bengt,
as I see, issue #37900 is closed, but I don't understand the solution,
unfortunately.
This issue #37865 is closed as well, so I don't know whether this reply
reaches you well and is placed correctly.
I for myself use a different way to get around the warning messages,
which re-occurred after a while:
$ guix package -I
guile: warning: failed to install locale
warning: failed to install locale: Invalid argument
I have the impression, that
cat<> ~/.bash_profile
GUIX_PROFILE="$HOME/.guix-profile"
source "\$GUIX_PROFILE/etc/profile"
EOF
is not enough to provide full information regarding search paths.
As a complement, I put the output of
guix package --search-paths -p "$HOME/.guix-profile"
into my ‘~/.bashrc’, but append the
${:+:}$
pattern to each line in order to keep existing variable content.
However, it seems as if the output of that command is incomplete as
well, as it often (not always) misses information regarding
GUIX_LOCPATH and PATH (~/.config/guix/current).
I append these definitions as well, just to make sure they are not
missing. (In a helper script, I use a ‘sort -u’ to avoid redundant
occurences of lines.)
cat<> ~/.bashrc
export PATH="$HOME/.config/guix/current/bin\${PATH:+:}\$PATH"
export
GUIX_LOCPATH="$HOME/.guix-profile/lib/locale\${GUIX_LOCPATH:+:}\$GUIX_LOCPATH"
EOF
Placing these complementary lines altogether in ~/.bash_profile won't
help me, I use ~/.bashrc instead.
Then I perform a logout, login sequence and the error messages
disappear and everything seems to run smoothly.
I update my ~/.bashrc after each new package generation.
As a conclusion, I would like to word three assumptions:
1. sourcing GUIX_PROFILE is not enough
2. output of ‘guix package --search-paths’ is incomplete
3. ~/.bash_profile and ~/.bashrc are not equally weighted in respect to
guix environment settings
@all
What do you think? Could this be regarded as useful information?
Or does it address my specific use case only?
best regards
Kai
--
Kai Mertens
OpenPGP Key-ID: 0x40B15AB4B05B5BF1 on keys.gnupg.net
Key fingerprint = 7C83 0A80 01FF 679C 6E8E AFD3 40B1 5AB4 B05B 5BF1
What is that? Please check: https://emailselfdefense.fsf.org/en/
pgp0ntrTApOZ2.pgp
Description: OpenPGP digital signature
bug#37882: [PATCH] build-system/linux-module: Accept a #:make-flags keyword.
On Fri, Oct 25, 2019 at 09:37:31PM +0200, Tobias Geerinckx-Rice via Bug reports for GNU Guix wrote: > * guix/build-system/linux-module.scm (linux-module-build): Accept a > MAKE-FLAGS argument. > : Pass it on. > --- > > Efraim, > > Is this in any way related to the topic coming up on IRC last week, or just a > coincidence? > > In any case, I'd written the following simple fix but never merged it because > I have yet to meet a module with a legitimate need for it. It works, though. > I thought I had a use-case for it but it turns out I'm pretty sure I didn't need it in the end. It was more of surprise that it was in one place and not another. -- 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
bug#37939: guix-install.sh: Fails to detect signing key on Debian10.
Dear GNU Guix developers, I just tried to install guix on top of a fresh debian10 system, which has been installed from debian-live-10.0.0-amd64-gnome.iso and updated. The guix install script fails in function chk_gpg_keyring(), although the key is present. If I remove the discard redirection >/dev/null 2>&1 from the gpg command, the following message occurs: gpg: keyblock resource '/root/.gnupg/pubring.kbx': No such file or directory gpg: Fatal: /root/.gnupg: directory does not exist! Of course these files do not exist, as I imported the key to the user account, not to the root account. Then I executed the script as user, using sudo. This procedure works fine on trisquel7 or 8, but it fails on debian10. I wonder why ‘sudo gpg’ does not make a difference between being called via sudo versus being called as root. Do I use debian the wrong way? best regards Kai -- Kai Mertens OpenPGP Key-ID: 0x40B15AB4B05B5BF1 on keys.gnupg.net Key fingerprint = 7C83 0A80 01FF 679C 6E8E AFD3 40B1 5AB4 B05B 5BF1 What is that? Please check: https://emailselfdefense.fsf.org/en/ pgpZWV9Tmm3r9.pgp Description: OpenPGP digital signature
bug#36634: Virtual Machine Manager (virt-manager)
Hello again,
The two patches attached create the cgroup directory needed and remove
the warning for the ip binary missing. Still the following errors
are emitted to the log.
8<---
error : virConnectGetCPUModelNames:1109 : this function is not supported by the
connection driver: virConnectGetCPUModelNames
error : virConnectGetAllDomainStats:11705 : this function is not supported by
the connection driver: virConnectGetAllDomainStats
error : virCgroupSetValueRaw:473 : Unable to write to
'/sys/fs/cgroup/unified/machine/qemu-1-Guix.libvirt-qemu/tasks': No such file
or directory
error : virCgroupRemoveRecursively:2383 : Unable to remove
/sys/fs/cgroup/unified/machine/qemu-1-Guix.libvirt-qemu/ (16)
>8---
The last two may indicate there may be lurking another bug in the
cgroups configuration, but at least the machines can be created and
started/stopped seamlessly. What do you think?
Happy hacking!
Miguel
>From a5dd055ea0fc20420cca6df2d38302596d397c49 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Miguel=20=C3=81ngel=20Arruga=20Vivas?=
Date: Sun, 27 Oct 2019 03:56:17 +0100
Subject: [PATCH 1/2] services: libvirtd: Create required control groups.
* gnu/services/virtualization.scm (libvirt-shepherd-service)
[libvirtd-activation]: New shepherd service.
[libvirtd]: Add a requirement of the new service.
---
gnu/services/virtualization.scm | 11 +++
1 file changed, 11 insertions(+)
diff --git a/gnu/services/virtualization.scm b/gnu/services/virtualization.scm
index bc8ac9b40a..2f26945efd 100644
--- a/gnu/services/virtualization.scm
+++ b/gnu/services/virtualization.scm
@@ -428,8 +428,19 @@ potential infinite waits blocking libvirt."))
(let* ((config-file (libvirt-conf-file config))
(libvirt (libvirt-configuration-libvirt config)))
(list (shepherd-service
+ ;; See https://libvirt.org/cgroups.html#currentLayoutGeneric
+ (documentation "Create the cgroup hierarchy required by libvirt.")
+ (provision '(libvirtd-activation))
+ (requirement '(file-system-/sys/fs/cgroup))
+ (one-shot? #t)
+ (start #~(lambda args
+ (let ((path "/sys/fs/cgroup/unified/machine"))
+(or (access? path F_OK) (mkdir path)
+ (stop #~(lambda args #t)))
+ (shepherd-service
(documentation "Run the libvirt daemon.")
(provision '(libvirtd))
+ (requirement '(libvirtd-activation))
(start #~(make-forkexec-constructor
(list (string-append #$libvirt "/sbin/libvirtd")
"-f" #$config-file)
--
2.23.0
>From 24f7c06a47562f410ceb982a3b2a0d44980de392 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Miguel=20=C3=81ngel=20Arruga=20Vivas?=
Date: Sun, 27 Oct 2019 03:59:23 +0100
Subject: [PATCH 2/2] services: libvirtd: Provide ip binary at runtime.
* gnu/services/virtualization.scm (libvirt-shepherd-service): Add sbin to
the PATH variable, as ip binary is installed there.
---
gnu/services/virtualization.scm | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/gnu/services/virtualization.scm b/gnu/services/virtualization.scm
index 2f26945efd..488cd63041 100644
--- a/gnu/services/virtualization.scm
+++ b/gnu/services/virtualization.scm
@@ -444,9 +444,11 @@ potential infinite waits blocking libvirt."))
(start #~(make-forkexec-constructor
(list (string-append #$libvirt "/sbin/libvirtd")
"-f" #$config-file)
+ ;; For finding qemu and ip binaries.
#:environment-variables
- ;; For finding qemu binaries.
- '("PATH=/run/current-system/profile/bin")))
+ (list (string-append
+"PATH=/run/current-system/profile/bin:"
+"/run/current-system/profile/sbin"
(stop #~(make-kill-destructor))
(define libvirt-service-type
--
2.23.0
bug#37940: endless "try upgrading both" cycles
Hi, When installing a package while some packages are not up to date, guix can require adding more and more packages to guix install: $ LANG=C guix install gtk+ dbus dbus-c++ dbus-glib glib libsoup rest libnotify poppler pcre libffi The following packages will be upgraded: dbus 1.12.12 -> 1.12.16 /gnu/store/nlb24nrrrkn2h9vflnqigcf2hx58rvyx-dbus-1.12.16 dbus-c++ 0.9.0 -> 0.9.0 /gnu/store/f67vzh5hp4jd2y34hiz8jdd9wymv1j8x-dbus-c++-0.9.0 dbus-glib0.108 -> 0.108 /gnu/store/0riy07j7njqf2avcr9n5asrdxapd2np4-dbus-glib-0.108 glib 2.56.3 -> 2.60.6 /gnu/store/fbnpd7vjifm6ijyij4hi18mnsnf76983-glib-2.60.6 libsoup 2.66.2 -> 2.68.2 /gnu/store/pabg3nkgmxg5cglimz7fklnk4n4dypb1-libsoup-2.68.2 rest 0.8.1 -> 0.8.1 /gnu/store/xpvpfhf93rz4jkvi9pp2p5cvh4jcbv1h-rest-0.8.1 libnotify0.7.7 -> 0.7.7 /gnu/store/djpm5rvn35aaasfsgh7y3kqis71av5fy-libnotify-0.7.7 poppler 0.72.0 -> 0.79.0 /gnu/store/8xysjsr4nh72m4334vff987x52pxyfmn-poppler-0.79.0 pcre 8.42 -> 8.43/gnu/store/5j6w0x3aq0i5r9565w92lrh016vlmv2d-pcre-8.43 libffi 3.2.1 -> 3.2.1 /gnu/store/ain96mrdwqd4s9shdd3s7m4syp5icdx5-libffi-3.2.1 The following package will be installed: gtk+ 3.24.10 /gnu/store/6x13nr57i1qml20kjl30l7b767cw0d0b-gtk+-3.24.10 guix install: error: profile contains conflicting entries for util-linux guix install: error: first entry: util-linux@2.34 /gnu/store/xymkwf57x988q8cny2is1dgzrbr9xdfi-util-linux-2.34 guix install: error:... propagated from glib@2.60.6 guix install: error:... propagated from poppler@0.79.0 guix install: error: second entry: util-linux@2.32.1 /gnu/store/8k4pnixpz73kxvxbjqajgbprjjmmgpxy-util-linux-2.32.1 hint: Try upgrading both `poppler' and `util-linux', or remove one of them from the profile. Since Guix already knows about these requirements, it would be great if I could tell it to just pull in all additional updates to be able to install the package. Or at least tell me about all the required upgrades in one step. Something like guix install: error: profile contains conflicting entries guix install: error: conflict N: util-linux guix install: error: first entry: util-linux@2.34 /gnu/store/xymkwf57x988q8cny2is1dgzrbr9xdfi-util-linux-2.34 guix install: error:... propagated from glib@2.60.6 guix install: error:... propagated from poppler@0.79.0 guix install: error: second entry: util-linux@2.32.1 /gnu/store/8k4pnixpz73kxvxbjqajgbprjjmmgpxy-util-linux-2.32.1 guix install: error: conflict N+1: util-linux guix install: error: first entry: util-linux@2.34 /gnu/store/xymkwf57x988q8cny2is1dgzrbr9xdfi-util-linux-2.34 guix install: error: second entry: util-linux@2.32.1 /gnu/store/8k4pnixpz73kxvxbjqajgbprjjmmgpxy-util-linux-2.32.1 guix install: error:... propagated from fontconfig@2.13.1 hint: Try upgrading removing dbus from the profile or upgrading all dependent packages with hint: guix install gtk+ dbus dbus-c++ dbus-glib glib libsoup rest libnotify poppler pcre libffi util-linux ... Best wishes, Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken signature.asc Description: PGP signature
bug#37942: Insufficient environment wrappers
Some packages -- such as meld after the startup fix -- fail to use important resources when simply called from their build directory. For instance, meld aborts inside a call to `g_log` by `g_settings_set_property`. In the case of meld, it is sufficient to run the program inside an ad-hoc environment -- other packages may require to be installed in the user profile. Regards, Leo
bug#37865: guix pull: error: You found a bug:
Hi Kai,
On +2019-10-27 08:54:19 +0100, Kai Mertens wrote:
> On Thu, 24 Oct 2019 13:49:56 -0700
> Bengt Richter wrote:
>
> > >
> > > When invoking guix package -I for example, I encountered an error
> > > like guile: failed to install locale
> > >
> >
> > I have encountered the same error. It seems to recur for me after
> > major updates. So there seems to be something lurking to reawaken the
> > real error message source. I collected some symptoms and posted them
> > as bug#37900.
> >
>
> Hello Bengt,
>
> as I see, issue #37900 is closed, but I don't understand the solution,
> unfortunately.
>
> This issue #37865 is closed as well, so I don't know whether this reply
> reaches you well and is placed correctly.
>
> I for myself use a different way to get around the warning messages,
> which re-occurred after a while:
>
> $ guix package -I
> guile: warning: failed to install locale
> warning: failed to install locale: Invalid argument
>
> I have the impression, that
>
> cat<> ~/.bash_profile
> GUIX_PROFILE="$HOME/.guix-profile"
> source "\$GUIX_PROFILE/etc/profile"
> EOF
>
> is not enough to provide full information regarding search paths.
>
> As a complement, I put the output of
>
> guix package --search-paths -p "$HOME/.guix-profile"
>
> into my ‘~/.bashrc’, but append the
>
> ${:+:}$
>
> pattern to each line in order to keep existing variable content.
>
> However, it seems as if the output of that command is incomplete as
> well, as it often (not always) misses information regarding
> GUIX_LOCPATH and PATH (~/.config/guix/current).
>
> I append these definitions as well, just to make sure they are not
> missing. (In a helper script, I use a ‘sort -u’ to avoid redundant
> occurences of lines.)
>
> cat<> ~/.bashrc
> export PATH="$HOME/.config/guix/current/bin\${PATH:+:}\$PATH"
> export
> GUIX_LOCPATH="$HOME/.guix-profile/lib/locale\${GUIX_LOCPATH:+:}\$GUIX_LOCPATH"
> EOF
>
> Placing these complementary lines altogether in ~/.bash_profile won't
> help me, I use ~/.bashrc instead.
>
> Then I perform a logout, login sequence and the error messages
> disappear and everything seems to run smoothly.
>
> I update my ~/.bashrc after each new package generation.
>
> As a conclusion, I would like to word three assumptions:
>
> 1. sourcing GUIX_PROFILE is not enough
> 2. output of ‘guix package --search-paths’ is incomplete
> 3. ~/.bash_profile and ~/.bashrc are not equally weighted in respect to
>guix environment settings
>
1. I think what produces GUIX_PROFILE is not designed to do what you are doing
manually,
nor IMO should it be, as there is (or should be) a proper solution ;-)
2. I don't know if it's incomplete, but I suspect you are saying so because it
does not
serve your current approach to solving the problem :)
3. True. Normally ~/.bash_profile is sourced only at login, whereas I think
~/.bashrc is
sourced by any new subshell being entered (normally, though AIUI options can
make a difference).
To diagnose your situation would you post the ouputs of:
1. strace guix -v |& grep locale
2. which guix|xargs readlink -f|xargs cat -n
3. guix package -I glibc
#1 should show where locale is being looked for and failing to be found
#2 will show that guix on the command line invokes a hash-bang guile script,
setting some things up and calling the real machinery of guix.
My current version for #2 lists 3 script lines:
1 #!/gnu/store/sc7z07gim1iq5zvfz1amdwf2irxrzifg-guile-2.2.6/bin/guile
--no-auto-compile
2 !#
3 (begin (set! %load-path (cons (string-append
"/gnu/store/053vb2vkbrv6mjddhkyhb6ddkj85d9ia-guix-module-union"
"/share/guile/site/" (effective-version)) %load-path)) (set!
%load-compiled-path (cons (string-append
"/gnu/store/053vb2vkbrv6mjddhkyhb6ddkj85d9ia-guix-module-union" "/lib/guile/"
(effective-version) "/site-ccache") %load-compiled-path)) (let ((locpath
(getenv "GUIX_LOCPATH"))) (setenv "GUIX_LOCPATH" (string-append (if locpath
(string-append locpath ":") "")
"/gnu/store/n79cf8bvy3k96gjk1rf18d36w40lkwlr-glibc-utf8-locales-2.29/lib/locale")))
(let ((guix-main (module-ref (resolve-interface (quote (guix ui))) (quote
guix-main (begin (bindtextdomain "guix"
"/gnu/store/0m73px55qzbx70v2k346igajrszzz8kb-guix-locale-guix") (bindtextdomain
"guix-packages"
"/gnu/store/c01aal3wvwlhi5h81rz14yasf70w04j2-guix-locale-guix-packages"))
(apply guix-main (command-line
Notice the -2.29 version of
"/gnu/store/n79cf8bvy3k96gjk1rf18d36w40lkwlr-glibc-utf8-locales-2.29/lib/locale"
My problem was that I had version 2.28 installed, but not 2.29 -- at least not
where it could be seen
What version is referenced in your #2 output?
My current output for #3 is
glibc 2.28out /gnu/store/c43rbmzv1laxgbnkvf76hx4305n4206a-glibc-2.28
glibc-locales 2.28out
/gnu/store/bb9alx1ap57pz0vmx7p1r8qk0lxxfg3x-glibc-locales-2.28
glibc-utf8-locales 2.29out
/gnu/store/n79cf8bvy3k96gjk1rf18d36w40lkwlr-glibc-utf8-locale
bug#37939: guix-install.sh: Fails to detect signing key on Debian10.
Hi again Kai, On +2019-10-27 09:59:39 +0100, Kai Mertens wrote: > Dear GNU Guix developers, > > I just tried to install guix on top of a fresh debian10 system, which > has been installed from debian-live-10.0.0-amd64-gnome.iso and updated. > > The guix install script fails in function chk_gpg_keyring(), although > the key is present. > > If I remove the discard redirection >/dev/null 2>&1 from the gpg > command, the following message occurs: > > gpg: keyblock resource '/root/.gnupg/pubring.kbx': No such file or directory > gpg: Fatal: /root/.gnupg: directory does not exist! > > Of course these files do not exist, as I imported the key to the user > account, not to the root account. Then I executed the script as user, > using sudo. > > This procedure works fine on trisquel7 or 8, but it fails on debian10. > > I wonder why ‘sudo gpg’ does not make a difference between being called > via sudo versus being called as root. > man sudo ;-) specifically the -i option I think if you are a "sudoer" plain sudo switches you to root, but keeps the environment you were in, with PATH etc, but sudo -i will set the environment as if you logged in as root. try "sudo set" and compare with "sudo -i set" (or env in place of set) HTH -- Regards, Bengt Richter
bug#37917: Kernel Panic
On Fri, Oct 25, 2019 at 10:23:54AM +0200, pelzflorian (Florian Pelz) wrote: > I > have to use > > (kernel linux-libre-4.9) > > I suppose it is a Shepherd bug then, maybe? > […] > My Macbook has none of these except the CPU is similar. > > Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz > > Maybe something is too slow? > I got one now (attached, kernel 4.9), intermixed with output that GDM is restarting… Regards, Florian
bug#37917: Kernel Panic
On Sun, Oct 27, 2019 at 01:24:49PM +0100, pelzflorian (Florian Pelz) wrote: > I got one now (attached, kernel 4.9), intermixed with output that GDM is > restarting… > P.S. Note that this is upon telling GNOME to shut down.
bug#37940: endless "try upgrading both" cycles
Hi Arne, Arne Babenhauserheide writes: > When installing a package while some packages are not up to date, guix > can require adding more and more packages to guix install: [...] > guix install: error: profile contains conflicting entries for util-linux > guix install: error: first entry: util-linux@2.34 > /gnu/store/xymkwf57x988q8cny2is1dgzrbr9xdfi-util-linux-2.34 > guix install: error:... propagated from glib@2.60.6 > guix install: error:... propagated from poppler@0.79.0 > guix install: error: second entry: util-linux@2.32.1 > /gnu/store/8k4pnixpz73kxvxbjqajgbprjjmmgpxy-util-linux-2.32.1 > hint: Try upgrading both `poppler' and `util-linux', or remove one of them > from the profile. I just wanted to briefly mention that if you use the "declarative approach" to specifying user profiles, via the --manifest option to "guix package", you will avoid this problem entirely. I've been happily using that approach for years, and I literally cannot remember the last time I saw a "conflicting entries" message. I heartily recommend it. Mark
bug#37469: meld doesn't start up successfully
Danny, I can't reproduce this failure so I'm closing the bug. Kind regards, T G-R signature.asc Description: PGP signature
bug#37942: Insufficient environment wrappers
Leo, Leo Prikler 写道： Some packages -- such as meld after the startup fix -- fail to use important resources when simply called from their build directory. This is… true, and has been a source of personal annoyance for years :-) As it is, this bug report is a bit vague, almost a meta-bug (‘many packages have bugs’). Because *many* packages have this problem, for different reasons. Most instances are pretty easy to fix once you find out the exact problem, but there's no one-size-fits-all solution. Do you have any ideas to make it more actionable? For instance, meld aborts inside a call to `g_log` by `g_settings_set_property`. In the case of meld, it is sufficient to run the program inside an ad-hoc environment -- other packages may require to be installed in the user profile. I fixed this specific example in 3a428dd63af0bec23861a8ed1c76665e8f424265. Thanks for the report! T G-R signature.asc Description: PGP signature
bug#37949: build failures for fetchmail-6.3.26
Hi,
I get build failures with fetchmail:
/gnu/store/vvsmdkxzml90m0ny6jr8w8zfnjyj5lrh-fetchmail-6.3.26.drv
Derive([("out","/gnu/store/miybrj479aasihqbkpmxyi558ccdl5lm-fetchmail-6.3.26","","")],[("/gnu/store/08ygwyq8zaa7ar8zanrivi9dixzkgcx5-grep-3.3.drv",["out"]),("/gnu/store/1919am1cqx1qbc0y68c499wkffmdal9g-gcc-7.4.0.drv",["out"]),("/gnu/store/1fyicgpjsgi0hzi9d3rxwjnncd8mklr7-openssl-1.1.1c.drv",["out"]),("/gnu/store/2mm6winnig97d9325hrggwc7hbm0-glibc-utf8-locales-2.29.drv",["out"]),("/gnu/store/4fqc5dydkc4svkl1zjyz5ymnyycfakx8-module-import.drv",["out"]),("/gnu/store/4kwwfs95x1i8lph8ya1ryh9pras7x2pz-gzip-1.10.drv",["out"]),("/gnu/store/81z4phfx8wbb9kl42x623s7rb41mvg67-bzip2-1.0.6.drv",["out"]),("/gnu/store/8yqmsdiqyzbcbpirk0frlsl58ivdkdlc-make-4.2.1.drv",["out"]),("/gnu/store/92dy7sxgw56nvnr9dpz6mivvclz1kql5-xz-5.2.4.drv",["out"]),("/gnu/store/bwrhlqh6ga34830bwag62n2r6x2c71yd-file-5.33.drv",["out"]),("/gnu/store/d2yx1bxbaqqrjsa3aszywbxpc0i90zvb-binutils-2.32.drv",["out"]),("/gnu/store/djxlq3ilag624v2zr8ya3zivwcrpiji7-linux-libre-headers-4.19.56.drv",["out"]),("/gnu/store/drsw7wpx93qkdffz9cjgpzlq7xgr8yxn-tar-1.32.drv",["out"]),("/gnu/store/gchaky6fdf7n2dy4bxkkxy5qw20hmhbc-guile-2.2.6.drv",["out"]),("/gnu/store/h11jxyh0n8ynzkig24gkrbwmny683ykx-diffutils-3.7.drv",["out"]),("/gnu/store/i7zzkyz0d9fa34w682lfjqby940chcb5-patch-2.7.6.drv",["out"]),("/gnu/store/m2c49751nx48i9msg8786yxqy2yfgrx0-coreutils-8.31.drv",["out"]),("/gnu/store/mgrixjmxy2507sivq773nb5n4vxbz24j-sed-4.7.drv",["out"]),("/gnu/store/ncs92k43ahgcf7kvpiym9shvkndbp7ym-findutils-4.6.0.drv",["out"]),("/gnu/store/phsimniilqah0vjxvbyp18yj7vwi1qaz-ld-wrapper-0.drv",["out"]),("/gnu/store/rmfsg2dsb88b136arb40z3kgd57kcnzs-glibc-2.29.drv",["out","static"]),("/gnu/store/sq3828hx2160fynwcv0hpknpqjznvxw0-fetchmail-6.3.26.tar.xz.drv",["out"]),("/gnu/store/wys7xrlqvhaakxlgsna8dnbnnd12j65p-bash-minimal-5.0.7.drv",["out"]),("/gnu/store/z02a27xlpzaciv5ihidgx1lr79pzj54s-gawk-5.0.1.drv",["out"]),("/gnu/store/zyzmvfn8spp7d159bashiwsw5lllnbap-module-import-compiled.drv",["out"])],["/gnu/store/w63j6cb313g3n0wp4jiw1wqmw3r4krvf-fetchmail-6.3.26-guile-builder"],"x86_64-linux","/gnu/store/sc7z07gim1iq5zvfz1amdwf2irxrzifg-guile-2.2.6/bin/guile",["--no-auto-compile","-L","/gnu/store/w3jlc8pk8416m7h677r5vq92b66h8cqd-module-import","/gnu/store/w63j6cb313g3n0wp4jiw1wqmw3r4krvf-fetchmail-6.3.26-guile-builder"],[("GUILE_LOAD_COMPILED_PATH","/gnu/store/jl8jj8d1s2ldvazylyfgmz7ga7rvcgxx-module-import-compiled"),("out","/gnu/store/miybrj479aasihqbkpmxyi558ccdl5lm-fetchmail-6.3.26")])
/var/log/guix/drvs/vv/smdkxzml90m0ny6jr8w8zfnjyj5lrh-fetchmail-6.3.26.drv.bz2
starting phase `set-SOURCE-DATE-EPOCH'
phase `set-SOURCE-DATE-EPOCH' succeeded after 0.0 seconds
starting phase `set-paths'
environment variable `PATH' set to
`/gnu/store/cnqpra8vr2l5fz00rr4yj4bp3hr00cfw-tar-1.32/bin:/gnu/store/py3k9zla9fj3z7430v4crqj5pyrsd3qj-gzip-1.10/bin:/gnu/store/l86azr7r3p5631wj3kk329jl1y1mpjgy-bzip2-1.0.6/bin:/gnu/store/lbip9isk25isymvnb159l115xnacb5j8-xz-5.2.4/bin:/gnu/store/6jdshxwdrad9mlhcqc9k0g24yw45rqf1-file-5.33/bin:/gnu/store/58sq8iabw3jkv0fvf95hd7sq2g4xcsnz-diffutils-3.7/bin:/gnu/store/v76scv4n63ip08g119rczh2mrw31zwpd-patch-2.7.6/bin:/gnu/store/g9d3wv1d68iflx57yp3mcp3k3sv8spsl-findutils-4.6.0/bin:/gnu/store/2z9hsww76aag37p40671l9niq5pvvasx-gawk-5.0.1/bin:/gnu/store/afmvfw1yhfal48n1kjq6bk6kcw8sc3db-sed-4.7/bin:/gnu/store/7iyvxhp2g3v3655zqwr6biz2h0lqv7pr-grep-3.3/bin:/gnu/store/9kzrrccpzl6i1sfwb0drb00gi2gwk0x0-coreutils-8.31/bin:/gnu/store/b5vpfzkr59bpgcsg1k9vvad9h5rwvpgk-make-4.2.1/bin:/gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin:/gnu/store/nc5vlidpxbvngalng30nif8nb3j7gfy2-ld-wrapper-0/bin:/gnu/store/3hkdiscs4910r75njbrql10znxxn7chk-binutils-2.32/bin:/gnu/store/x3jx25cd3q363mr7nbgzrhrv1vza6cf7-gcc-7.4.0/bin:/gnu/store/ahqgl4h89xqj695lgqvsaf6zh2nhy4pj-glibc-2.29/bin:/gnu/store/ahqgl4h89xqj695lgqvsaf6zh2nhy4pj-glibc-2.29/sbin:/gnu/store/k2m4q2av9hw73hw2jx6qrxqdyh855398-openssl-1.1.1c/bin'
environment variable `BASH_LOADABLES_PATH' unset
environment variable `CPATH' set to
`/gnu/store/l86azr7r3p5631wj3kk329jl1y1mpjgy-bzip2-1.0.6/include:/gnu/store/lbip9isk25isymvnb159l115xnacb5j8-xz-5.2.4/include:/gnu/store/6jdshxwdrad9mlhcqc9k0g24yw45rqf1-file-5.33/include:/gnu/store/2z9hsww76aag37p40671l9niq5pvvasx-gawk-5.0.1/include:/gnu/store/b5vpfzkr59bpgcsg1k9vvad9h5rwvpgk-make-4.2.1/include:/gnu/store/3hkdiscs4910r75njbrql10znxxn7chk-binutils-2.32/include:/gnu/store/x3jx25cd3q363mr7nbgzrhrv1vza6cf7-gcc-7.4.0/include:/gnu/store/ahqgl4h89xqj695lgqvsaf6zh2nhy4pj-glibc-2.29/include:/gnu/store/k2m4q2av9hw73hw2jx6qrxqdyh855398-openssl-1.1.1c/include:/gnu/store/7czrqpi0kwazras6pgyx0bhdn89pg0jl-linux-libre-headers-4.19.56/include'
environment variable `LIBRARY_PATH' set to
`/gnu/store/l86azr7r3p5631wj3kk329jl1y1mpjgy-bzip2-1.0.6/lib:/gnu/store/lbip9isk25isymvnb159l115xnacb5j8-xz-5.2.4/lib:/gnu/store/6jdshxwdrad9mlhcqc9k0g24yw45rqf1-file-5.33/lib:/gnu/store/2z9hsww76aag37p40671l9niq5pvvasx
bug#29686: gnu: aspell: Do not ignore GuixOS system profile.
Hi, Pierre Neidhardt skribis: > I just noticed that Nix has a different, possibly better approach to > this in the attached patch. > > What do you think? I think that honoring an ‘ASPELL_DICT_DIR’ variable is more generic than browsing a set of profiles (which ones?), especially with support for search paths as available in Guix. :-) Ludo’.
bug#37940: endless "try upgrading both" cycles
Hi Arne & Mark, Mark H Weaver skribis: > Arne Babenhauserheide writes: >> When installing a package while some packages are not up to date, guix >> can require adding more and more packages to guix install: > [...] >> guix install: error: profile contains conflicting entries for util-linux >> guix install: error: first entry: util-linux@2.34 >> /gnu/store/xymkwf57x988q8cny2is1dgzrbr9xdfi-util-linux-2.34 >> guix install: error:... propagated from glib@2.60.6 >> guix install: error:... propagated from poppler@0.79.0 >> guix install: error: second entry: util-linux@2.32.1 >> /gnu/store/8k4pnixpz73kxvxbjqajgbprjjmmgpxy-util-linux-2.32.1 >> hint: Try upgrading both `poppler' and `util-linux', or remove one of them >> from the profile. > > I just wanted to briefly mention that if you use the "declarative > approach" to specifying user profiles, via the --manifest option to > "guix package", you will avoid this problem entirely. I've been happily > using that approach for years, and I literally cannot remember the last > time I saw a "conflicting entries" message. I heartily recommend it. Indeed. Even if you don’t use the declarative approach, usually just upgrade everything (“guix upgrade”) and you won’t have any problems either. Problems arise when you try to upgrade only part of the packages. Now, it doesn’t sound right that ‘util-linux’ is propagated from glib and from poppler…? Ludo’.
bug#37949: fixed by updating fetchmail, thanks to nckx
Version: 6.4.1 -- Unpolitisch sein heißt politisch sein ohne es zu merken signature.asc Description: PGP signature
bug#37940: endless "try upgrading both" cycles
Hi Mark and Ludovic, Ludovic Courtès writes: > Hi Arne & Mark, > > Mark H Weaver skribis: >> Arne Babenhauserheide writes: >>> When installing a package while some packages are not up to date, guix >>> can require adding more and more packages to guix install: >> [...] >>> guix install: error: profile contains conflicting entries for util-linux >>> guix install: error: first entry: util-linux@2.34 >>> /gnu/store/xymkwf57x988q8cny2is1dgzrbr9xdfi-util-linux-2.34 >>> guix install: error:... propagated from glib@2.60.6 >>> guix install: error:... propagated from poppler@0.79.0 >>> guix install: error: second entry: util-linux@2.32.1 >>> /gnu/store/8k4pnixpz73kxvxbjqajgbprjjmmgpxy-util-linux-2.32.1 >>> hint: Try upgrading both `poppler' and `util-linux', or remove one of them >>> from the profile. >> >> I just wanted to briefly mention that if you use the "declarative >> approach" to specifying user profiles, via the --manifest option to >> "guix package", you will avoid this problem entirely. I've been happily >> using that approach for years, and I literally cannot remember the last >> time I saw a "conflicting entries" message. I heartily recommend it. I’m just using guix install when I need a new package and guix remove to clean up. Shouldn’t that be equivalent? > Indeed. Even if you don’t use the declarative approach, usually just > upgrade everything (“guix upgrade”) and you won’t have any problems > either. > > Problems arise when you try to upgrade only part of the packages. This problem cuts in when the system is not fully up to date and I use guix install. > Now, it doesn’t sound right that ‘util-linux’ is propagated from glib > and from poppler…? Poppler needs glib at runtime and glib needs tools from util-linux at runtime? Best wishes, Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken signature.asc Description: PGP signature
