bug#37865: guix pull: error: You found a bug:

2019-10-25 Thread Bengt Richter
On +2019-10-24 13:49:56 -0700, Bengt Richter wrote:
> On +2019-10-24 13:34:29 +0200, Kai Mertens 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.
> 
A recently committed fix enabled me to fix my problem with "guile: failed to 
install locale"
that was triggered by any invocation of guix:

guix pull  ## make sure the fix is in! ;-)

guix install avahi ## likely you won't need this first, but it stood in my way 
per bug#37900
   ## (after the fix, I might not have needed it either for the 
locale upgrade, idk).

guix install glibc-utf8-locales ## if your locale is within '("de_DE" "el_GR" 
"en_US" "fr_FR" "tr_TR")

If you have an exotic locale outside of those, you may have to install the big 
one:

guix install glibc-locales

A snip from  guix edit glibc-utf8-locales:
---
   ;; tests---e.g., in Guile's i18n tests.
   '("de_DE" "el_GR" "en_US" "fr_FR" "tr_TR"))
 #t
(native-inputs `(("glibc" ,glibc)
 ("gzip" ,gzip)))
(synopsis "Small sample of UTF-8 locales")
(description
 "This package provides a small sample of UTF-8 locales mostly useful in
test environments.")
---
HTH, in case your "guile: failed to install locale" hasn't gone away yet :)
--
Regards,
Bengt Richter





bug#37913: Aisleriot pt-br portuguese

2019-10-25 Thread ison
On Thu, Oct 24, 2019, Pablo Ferreira wrote:
> Olá equipe!
> 
> Eu instalei o Aisleriot em um Guix System usando o "guix install" mas ele
> não inicia. Quando uso o terminal ele retorna à mensagem "Non UTF-8 locale
> (ANSI_X3.4-1968) is not supported!".
> 
> Observação: Sempre que eu uso o comando "guix" ele avisa para instalar o
> glibc-utf8-locales e criar a variavel de ambiente GUIX_LOCPATH.

I get the same error with en_US.utf8 (set for all values listed by "locale")
I also have both glibc-locales and glibc-locales-2.28 installed.
However I do not see the error about installing glibc-utf8-locales, nor
the one about setting GUIX_LOCPATH when using guix commands, so that may be
unrelated.





bug#37917: Kernel Panic

2019-10-25 Thread Raghav Gururajan
Hello Guix!

Whenever I shutdown my system, 50% of the time, I end up with kernel
panic. Then I had to do cold restart.

Kernel Panic: 
https://upload.disroot.org/r/B5Z3ofx_#/XTJVfcPxwYaDqzEGiQdv0Y6wQal34Oik77HlA7K7BE=

System Config: 
https://bin.disroot.org/?a1ab3e3f7c3d38a5#SF5FHGGDC2+OYKbCrTCT+szeNvLFQbvN13OoimpDxng=

Device: FSF's RYF-Certified TET-X200T (https://tehnoetic.com/tet-x200t)
a.k.a Lenovo ThinkPad X200 Tablet

Hardware Specs (Mods/Variants):
Intel® Core™2 Duo Processor SL9600 (2.13 GHz), Added Ericsson F3507g
Wireless WAN card,
Added Gemalto Compact Smart Card Reader Writer (ExpressCard),
Upgraded to Display with Wacom Pen+Finger Touch and Web Camera,
Upgraded to 8GB RAM,
and Upgraded to Atheros AR5BHB116 300Mbps Dual-Band WWAN.

Regards,
RG.


signature.asc
Description: This is a digitally signed message part


bug#37917: Kernel Panic

2019-10-25 Thread pelzflorian (Florian Pelz)
On Fri, Oct 25, 2019 at 03:19:10AM -0400, Raghav Gururajan wrote:
> Hello Guix!
> 
> Whenever I shutdown my system, 50% of the time, I end up with kernel
> panic. Then I had to do cold restart.
> 

I just wanted to say I have a kernel panic too sometimes (I do not
know if the backtrace is the same and cannot easily reproduce the
issue or provide a photo) on a 2010 Macbook though much less than 50%
of the time.


> Kernel Panic:
> https://upload.disroot.org/r/B5Z3ofx_#/XTJVfcPxwYaDqzEGiQdv0Y6wQal34Oik77HlA7K7BE=
> System Config:
> https://bin.disroot.org/?a1ab3e3f7c3d38a5#SF5FHGGDC2+OYKbCrTCT+szeNvLFQbvN13OoimpDxng=

I do not see any kernel field, so you are using modern linux-libre.  I
have to use

(kernel linux-libre-4.9)

I suppose it is a Shepherd bug then, maybe?



> Device: FSF's RYF-Certified TET-X200T (https://tehnoetic.com/tet-x200t)
> a.k.a Lenovo ThinkPad X200 Tablet
> 
> Hardware Specs (Mods/Variants):
> Intel® Core™2 Duo Processor SL9600 (2.13 GHz), Added Ericsson F3507g
> Wireless WAN card,
> Added Gemalto Compact Smart Card Reader Writer (ExpressCard),
> Upgraded to Display with Wacom Pen+Finger Touch and Web Camera,
> Upgraded to 8GB RAM,
> and Upgraded to Atheros AR5BHB116 300Mbps Dual-Band WWAN.
>

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?

Regards,
Florian





bug#24168: Offloading builds does not honor --keep-failed

2019-10-25 Thread Efraim Flashner
On Wed, Aug 24, 2016 at 10:04:01PM +, ng0 wrote:
> ng0  writes:
> 
> > ng0  writes:
> >

Offloading still does not honor --keep-failed, but with
b3673e9917217fc27c743092e58e4eb33d0fdd16 there is at least a warning
about it now.

> >> This bug is to keep track of and not forget to add this feature to
> >> build offloading:
> >>
> >> When I offload builds to my build machine(s), I want to keep the results
> >> of failed builds to investigate the reason for failure.
> >>
> >> Currently this does not happen with offloading, we should fix this as
> >> its a nice feature to have.
> >
> > Adding to this: offloading does not support `guix build --keep-going`
> > either.
> >
> 
> Additionally with enabled offloading, guix pull has no option to build
> on its own when the build machines are down.
> 
> Being able to pass something like
> guix pull -- --no-build-hook
> would be good.
> 

Not sure when it was added, but 'guix pull --no-build-hook' does work
(now).

-- 
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#37682: weston 6.0.1 build failure

2019-10-25 Thread Gábor Boskovits
Just some further info. This is not deterministic. Did not work on one of
my systems yesterday, today it works just fine. I did not pull in the
meantime.

-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21


bug#37900: guix invocation induces guile locale error

2019-10-25 Thread Gábor Boskovits
Submitter requested to close the bug on #37914. Closing.

-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21


bug#37917: Kernel Panic

2019-10-25 Thread Jesse Gibbons
On Fri, 2019-10-25 at 10:23 +0200, pelzflorian (Florian Pelz) wrote:
> On Fri, Oct 25, 2019 at 03:19:10AM -0400, Raghav Gururajan wrote:
> > Hello Guix!
> > 
> > Whenever I shutdown my system, 50% of the time, I end up with kernel
> > panic. Then I had to do cold restart.
> > 
> 
> I just wanted to say I have a kernel panic too sometimes (I do not
> know if the backtrace is the same and cannot easily reproduce the
> issue or provide a photo) on a 2010 Macbook though much less than 50%
> of the time.
> 
> 
> > Kernel Panic:
> > https://upload.disroot.org/r/B5Z3ofx_#/XTJVfcPxwYaDqzEGiQdv0Y6wQal34Oik77HlA7K7BE=
> > System Config:
> > https://bin.disroot.org/?a1ab3e3f7c3d38a5#SF5FHGGDC2+OYKbCrTCT+szeNvLFQbvN13OoimpDxng=
> 
> I do not see any kernel field, so you are using modern linux-libre.  I
> have to use
> 
> (kernel linux-libre-4.9)
> 
> I suppose it is a Shepherd bug then, maybe?
> 
> 
> 
> > Device: FSF's RYF-Certified TET-X200T (https://tehnoetic.com/tet-x200t)
> > a.k.a Lenovo ThinkPad X200 Tablet
> > 
> > Hardware Specs (Mods/Variants):
> > Intel® Core™2 Duo Processor SL9600 (2.13 GHz), Added Ericsson F3507g
> > Wireless WAN card,
> > Added Gemalto Compact Smart Card Reader Writer (ExpressCard),
> > Upgraded to Display with Wacom Pen+Finger Touch and Web Camera,
> > Upgraded to 8GB RAM,
> > and Upgraded to Atheros AR5BHB116 300Mbps Dual-Band WWAN.
> > 
> 
> 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?
> 
> Regards,
> Florian
> 
> 
> 
I also have a kernel panic often. The picture i took is too large for the
mailing list though :( The dump says something about trying to kill init.

I have successfully predicted one panic when some things stopped responding
and I was unable to open gnome-control-panel or gnome-system-monitor, but
that symptom might be coincidental.

My system: librem 15v3 w/o tpm, 32GB RAM
Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz






bug#36375: [PATCH] Re: ‘guix package’ should lock the profile

2019-10-25 Thread Julien Lepiller
Le Tue, 25 Jun 2019 16:10:22 +0200,
Ludovic Courtès  a écrit :

> The article at
>  mentions
> things like:
> 
>   For instance, after installing Icecat, I installed a few other
> desktop programs and then found Icecat had disappeared from my path
> again.
> 
> It’s likely that the person ran several ‘guix package’ commands in
> parallel, and that one undoed the effects of the other.
> 
> Julien suggested that ‘guix package’ could grab a lock file, and I
> guess it could simply error out when the lock is already taken.
> 
> Ludo’.

Hi!

attached is a patch for guix package to grab a lock file. Note that I'm
using flock, so it won't work on NFS shares. The other option would be
to use fcntl but guile doesn't seem to implement the locking function
from it.
>From 987e9711f1fa6bfd270e48ee5624f69696e7e5c4 Mon Sep 17 00:00:00 2001
From: Julien Lepiller 
Date: Fri, 25 Oct 2019 21:39:21 +0200
Subject: [PATCH] guix: package: lock profiles when processing them.

* guix/scripts/package.scm (process-actions): Get a per-profile lock to
prevent concurrent actions on profiles.
---
 guix/scripts/package.scm | 17 +++--
 1 file changed, 15 insertions(+), 2 deletions(-)

diff --git a/guix/scripts/package.scm b/guix/scripts/package.scm
index 1a58d43e5c..e4f0f416f5 100644
--- a/guix/scripts/package.scm
+++ b/guix/scripts/package.scm
@@ -876,7 +876,17 @@ processed, #f otherwise."
  (package-version item)
  (manifest-entry-version entry))
 
-  ;; First, process roll-backs, generation removals, etc.
+  ;; First, acquire a lock on the profile, to ensure only one guix process
+  ;; is modifying it at a time.
+  (define lock-file (open (string-append profile ".lock") O_CREAT))
+  (catch 'system-error
+(lambda _
+  (flock lock-file (logior LOCK_EX LOCK_NB)))
+(lambda (key . args)
+  (leave (G_ "profile ~a is being locked by another guix process.~%")
+ profile)))
+
+  ;; Then, process roll-backs, generation removals, etc.
   (for-each (match-lambda
   ((key . arg)
(and=> (assoc-ref %actions key)
@@ -905,7 +915,10 @@ processed, #f otherwise."
  #:allow-collisions? allow-collisions?
  #:bootstrap? bootstrap?
  #:use-substitutes? substitutes?
- #:dry-run? dry-run?
+ #:dry-run? dry-run?)))
+
+  ;; Finaly, close the lock file
+  (close lock-file))
 
 
 ;;;
-- 
2.22.0



bug#37882: [PATCH] build-system/linux-module: Accept a #:make-flags keyword.

2019-10-25 Thread Tobias Geerinckx-Rice via Bug reports for GNU Guix
* 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.

Kind regards,

T G-R

 guix/build-system/linux-module.scm | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/guix/build-system/linux-module.scm 
b/guix/build-system/linux-module.scm
index 6084d22210..dde2423434 100644
--- a/guix/build-system/linux-module.scm
+++ b/guix/build-system/linux-module.scm
@@ -1,5 +1,6 @@
 ;;; GNU Guix --- Functional package management for GNU
 ;;; Copyright © 2019 Danny Milosavljevic 
+;;; Copyright © 2019 Tobias Geerinckx-Rice 
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -120,6 +121,7 @@
 (define* (linux-module-build store name inputs
  #:key
  (search-paths '())
+ (make-flags '())
  (tests? #t)
  (phases '(@ (guix build linux-module-build-system)
  %standard-phases))
@@ -146,6 +148,7 @@
search-paths)
  #:phases ,phases
  #:system ,system
+ #:make-flags ,make-flags
  #:tests? ,tests?
  #:outputs %outputs
  #:inputs %build-inputs)))
-- 
2.23.0






bug#37900: guix invocation induces guile locale error

2019-10-25 Thread Ludovic Courtès
Gábor Boskovits  skribis:

> Submitter requested to close the bug on #37914. Closing.

You closed 37900 though, not 37914, or am I missing something?

Ludo’.





bug#37904: CPU overheating on recent laptops

2019-10-25 Thread Ludovic Courtès
Hi,

Tobias Geerinckx-Rice via Bug reports for GNU Guix 
skribis:

> Ludovic Courtès 写道:
>> Also, there used to be an “ondemand” governor, which is no longer
>> listed
>> in /sys/devices/system/cpu/cpu?/cpufreq/scaling_available_governors.
>
> For laptops and other battery-powered devices, ‘conservative’ is
> preferred over ‘ondemand’.  It's probably a sane default choice for
> all.

Oh, didn’t know that one.

>> Was it removed or are we just missing a kconfig option?
>
> Strange:
>
>  ~ λ grep CPU_FREQ_GOV …/aux-files/linux-libre/5.3-x86_64.conf
> CONFIG_CPU_FREQ_GOV_ATTR_SET=y
>  CONFIG_CPU_FREQ_GOV_COMMON=y
>  CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
>  CONFIG_CPU_FREQ_GOV_POWERSAVE=y
>  CONFIG_CPU_FREQ_GOV_USERSPACE=y
>  CONFIG_CPU_FREQ_GOV_ONDEMAND=y
>  CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
>  CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y

Weird, I see:

--8<---cut here---start->8---
$ cat /sys/devices/system/cpu/cpu?/cpufreq/scaling_available_governors
performance powersave
performance powersave
performance powersave
performance powersave
$ uname -a
Linux ribbon 5.3.7-gnu #1 SMP 1 x86_64 GNU/Linux
--8<---cut here---end--->8---

Do you see more governors on your side?  How could that be?

> What does cpufreq-info say?

On my laptop (plugged in) I have this:

--8<---cut here---start->8---
$ guix environment --ad-hoc cpufrequtils -- cpufreq-info
cpufrequtils 0.3: cpufreq-info (C) Dominik Brodowski 2004
Report errors and bugs to li...@brodo.de, please.
analyzing CPU 0:
  driver: intel_pstate
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 400 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 400 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 3.37 GHz.
analyzing CPU 1:
  driver: intel_pstate
  CPUs which need to switch frequency at the same time: 1
  hardware limits: 400 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 400 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 3.25 GHz.
analyzing CPU 2:
  driver: intel_pstate
  CPUs which need to switch frequency at the same time: 2
  hardware limits: 400 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 400 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 3.28 GHz.
analyzing CPU 3:
  driver: intel_pstate
  CPUs which need to switch frequency at the same time: 3
  hardware limits: 400 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 400 MHz and 3.40 GHz.
  The governor "performance" may decide which speed to use
  within this range.
  current CPU frequency is 3.31 GHz.
--8<---cut here---end--->8---

Thanks,
Ludo’.





bug#37929: clojure is not usable out of the box

2019-10-25 Thread Bradley Haggerty
You cannot get a repl by running `clojure`, and it's lacking java as a
dependency even though java seems to be needed to use it. Other
languages are usable out of the box, so I think it would be good to
change these things.





bug#37799: dbus-system

2019-10-25 Thread Ludovic Courtès
Bonjour,

Gnu Röoty  skribis:

> Je savais que si j'enlever le udisk-service ça fonctionner mais le problème
> et qu'il est impossible de monter un disque amovible sur xfce4 et je vais
> pas installer GNOME juste pour obtenir gvfs afin de monter les disques
> amovibles.

Et donc tu as rajouté « udisks-service » pour pouvoir monter un disque
amovible ?  Tu le montes avec la commande « udisksctl » ?

Merci,
Ludo’.





bug#37897: Bug: Resetting locale settings

2019-10-25 Thread Ludovic Courtès
Hello,

o.ro...@posteo.net skribis:

> I believe that a locale-related bug has slipped in somewhere in the
> last two-three weeks. During installation and in my configuration
> file, I have specified de_DE specified as locale, which should
> translate to a german keyboard layout. But since said two-three weeks,
> I startup with what I believe is the US layout (qwerty) - and before
> this occurred, I was once even unable to login because my keyboard
> layout has been changed to something so obscure it didnt even seem to
> know basic characters like the exclamation mark, while there was a
> number of characters that could not be displayed (probably non-utf
> characters I suppose).

Could you be more specific about the context in which you get an
incorrect layout (console, Xorg, Wayland, GNOME, etc.)?

Note that locale settings and keyboard layout settings are entirely
separate—choosing the “de_DE” locale gives you programs that speak
German, but it does not give you a “qwertz” layout.  See:

  https://guix.gnu.org/manual/devel/en/html_node/Keyboard-Layout.html
  https://guix.gnu.org/manual/devel/en/html_node/Locales.html

HTH,
Ludo’.





bug#37911: Cannot build a system with colord-service.

2019-10-25 Thread Ludovic Courtès
Hello,

Jack Hill  skribis:

> On Thu, 24 Oct 2019, Pierre Langlois wrote:
>
>> In gnome's settings it tells me that there are no devices that can be
>> colour managed, I had assumed that was because colord was missing from
>> the config but that's probably not it. Is it working for other people?
>> If so it's probably just my hardware (ThinkPad x220).
>
> I think it is not able to manage devices because the Argyll CMS
> dependency [0] is missing in Guix. Unfortunately, it seems to also
> depend on the discontinued Jam build tool [1], so there is a little
> bit of work to be done.
>
> [0] https://argyllcms.com/
> [1] https://www.perforce.com/documentation/jam-documentation
>
> I did spot another issue with colord since the recent core-updates
> merge: https://issues.guix.gnu.org/issue/37843 It seems like it is no
> longer being started automatically via dbus?

Indeed, stracing dbus-daemon while going to the GNOME settings panel,
“Color” tag, I see:

--8<---cut here---start->8---
459   sendmsg(48, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="l\3\1\1\213\0\0\0\3\0\0\0m\0\0\0\6\1s\0\5\0\0\0:1.95\0\0\0\4\1s\0'\0\0\0org.freedesktop.DBus.Error.AccessDenied\0\5\1u\0\2\0\0\0\10\1g\0\1s\0\0\7\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0",
 iov_len=128}, {iov_base="\206\0\0\0Connection \":1.95\" is not allowed to own 
the service \"org.freedesktop.ColorManager\" due to security policies in the 
configuration file\0", iov_len=139}], msg_iovlen=2, msg_controllen=0, 
msg_flags=0}, MSG_NOSIGNAL 
--8<---cut here---end--->8---

So something somewhere is unhappy.

I diff’d the ‘org.freedesktop.color.policy’ files of colord 1.4.3 and
1.4.4 and there are no functional differences.

Ludo’.





bug#37917: Kernel Panic

2019-10-25 Thread Ludovic Courtès
Hi,

Raghav Gururajan  skribis:

> Whenever I shutdown my system, 50% of the time, I end up with kernel
> panic. Then I had to do cold restart.
>
> Kernel Panic: 
> https://upload.disroot.org/r/B5Z3ofx_#/XTJVfcPxwYaDqzEGiQdv0Y6wQal34Oik77HlA7K7BE=

I can’t access it with IceCat over Tor (“Error: the file has not been
sent entirely.”)  Can someone share it in some other way?

Like Florian writes a panic upon halt could be a Shepherd issue but we
need to see that last screen before we can draw any conclusions.

Thanks,
Ludo’.





bug#24168: Offloading builds does not honor --keep-failed

2019-10-25 Thread Ludovic Courtès
Efraim Flashner  skribis:

> On Wed, Aug 24, 2016 at 10:04:01PM +, ng0 wrote:
>> ng0  writes:
>> 
>> > ng0  writes:
>> >
>
> Offloading still does not honor --keep-failed, but with
> b3673e9917217fc27c743092e58e4eb33d0fdd16 there is at least a warning
> about it now.

Actually no.  :-)  The warning is for when you have

  GUIX_DAEMON_SOCKET=guix://host.example.com

and not when you’re offloading.

I was thinking that we could turn off offloading when ‘-K’ is passed;
that’s usually what one expects no?

Thanks,
Ludo’.





bug#36375: [PATCH] Re: ‘guix package’ should lock the profile

2019-10-25 Thread Ludovic Courtès
Hello,

Julien Lepiller  skribis:

> attached is a patch for guix package to grab a lock file. Note that I'm
> using flock, so it won't work on NFS shares. The other option would be
> to use fcntl but guile doesn't seem to implement the locking function
> from it.

(guix build syscalls) has it though, so you should probably use it.  :-)

> From 987e9711f1fa6bfd270e48ee5624f69696e7e5c4 Mon Sep 17 00:00:00 2001
> From: Julien Lepiller 
> Date: Fri, 25 Oct 2019 21:39:21 +0200
> Subject: [PATCH] guix: package: lock profiles when processing them.
>
> * guix/scripts/package.scm (process-actions): Get a per-profile lock to
> prevent concurrent actions on profiles.

[...]

> -  ;; First, process roll-backs, generation removals, etc.
> +  ;; First, acquire a lock on the profile, to ensure only one guix process
> +  ;; is modifying it at a time.
> +  (define lock-file (open (string-append profile ".lock") O_CREAT))
> +  (catch 'system-error
> +(lambda _
> +  (flock lock-file (logior LOCK_EX LOCK_NB)))
> +(lambda (key . args)
> +  (leave (G_ "profile ~a is being locked by another guix process.~%")
> + profile)))

Nitpick: "profile ~a is locked by another process~%".

> +  ;; Then, process roll-backs, generation removals, etc.
>(for-each (match-lambda
>((key . arg)
> (and=> (assoc-ref %actions key)
> @@ -905,7 +915,10 @@ processed, #f otherwise."
>   #:allow-collisions? allow-collisions?
>   #:bootstrap? bootstrap?
>   #:use-substitutes? substitutes?
> - #:dry-run? dry-run?
> + #:dry-run? dry-run?)))
> +
> +  ;; Finaly, close the lock file
> +  (close lock-file))

I’d recommend wrapping the body in ‘with-file-lock’ (from (guix build
syscalls)), which handles non-local exits.

However you’d first need to add a #:wait? argument to ‘with-file-lock’
and perhaps an additional argument to handle the already-locked case.
Or maybe call that ‘with-file-lock/no-wait’.

How does that sound?

Thanks for working on it!

Ludo’.





bug#37850: Glib documentation is missing

2019-10-25 Thread Ludovic Courtès
Hi,

Pierre Neidhardt  skribis:

> Marius Bakke  writes:

[...]

>> 'gtk-doc' unsurprisingly depends on GLib, so I'm not sure what the best
>> approach is.
>
> What about the following:
>
> 1. Turn our current glib into glib-minimal.
>
> 2. Build gtk-doc against glib-minimal.
>
> 3. Define a new glib package that inherits from glib-minimal and adds
> gtk-doc as native-inputs so that we can restore the "doc" output.

Alternately, we could define a new “glib-doc” package that would depend
on the current “glib” package, assuming the build system allows us to
build nothing but documentation.

Ludo’.





bug#37900: guix invocation induces guile locale error

2019-10-25 Thread Gábor Boskovits
Sorry, maybe I was not clear on this. On 37914 there was a message that it
is ok to close 37900. See:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37914#13

Ludovic Courtès  ezt írta (időpont: 2019. okt. 25., P, 22:46):

> Gábor Boskovits  skribis:
>
> > Submitter requested to close the bug on #37914. Closing.
>
> You closed 37900 though, not 37914, or am I missing something?
>
> Ludo’.
>


-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21


bug#37929: clojure is not usable out of the box

2019-10-25 Thread Gábor Boskovits
Hello,
this seems to be a partial duplicate of #32709. Maybe we could merge
these...


Bradley Haggerty  ezt írta (időpont: 2019. okt. 25.,
P, 22:49):

> You cannot get a repl by running `clojure`, and it's lacking java as a
> dependency even though java seems to be needed to use it. Other
> languages are usable out of the box, so I think it would be good to
> change these things.
>
>
>
>

-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21


bug#37917: Kernel Panic

2019-10-25 Thread Gábor Boskovits
Hello,

Ludovic Courtès  ezt írta (időpont: 2019. okt. 25., P, 23:09):

> Hi,
>
> Raghav Gururajan  skribis:
>
> > Whenever I shutdown my system, 50% of the time, I end up with kernel
> > panic. Then I had to do cold restart.
> >
> > Kernel Panic:
> >
> https://upload.disroot.org/r/B5Z3ofx_#/XTJVfcPxwYaDqzEGiQdv0Y6wQal34Oik77HlA7K7BE=
>
> I can’t access it with IceCat over Tor (“Error: the file has not been
> sent entirely.”)  Can someone share it in some other way?
>

Now I see the same error. I could access it eariler though. The only thing
I remember is that it was
an attempted to kill init... I hope Raghav can share it again.

>
> Like Florian writes a panic upon halt could be a Shepherd issue but we
> need to see that last screen before we can draw any conclusions.
>
> Thanks,
> Ludo’.
>
>
>
>
g_bor
-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21


bug#37900: guix invocation induces guile locale error

2019-10-25 Thread Bengt Richter
Hi Ludo,

On +2019-10-25 22:46:16 +0200, Ludovic Courtès wrote:
> Gábor Boskovits  skribis:
> 
> > Submitter requested to close the bug on #37914. Closing.
> 
> You closed 37900 though, not 37914, or am I missing something?
> 
> Ludo’.

Sorry, 37900 was mine, but (IIRC) trying to make a helpful comment
on 37914 that my 37900 might be relevant, I also mentioned
that recent fixes to guix had made my 37900 difficulties go away,
so closing 37900 would be ok by me. Gábor apparently picked up on that :)

I'm still curious about the avahi entaglement I demonstrated in 37900 though ;-)
--
Regards,
Bengt Richter
P.S. Is there a better way to post trying-to-be-helpful comments than to
add them to bug reports? Looking at archives, I see bits that could go
in turorials mixed with lots of friendly stuff that is just noise when
you want straight technical info.





bug#36375: [PATCH] Re: ‘guix package’ should lock the profile

2019-10-25 Thread Julien Lepiller
Le Fri, 25 Oct 2019 23:21:34 +0200,
Ludovic Courtès  a écrit :
> 
> I’d recommend wrapping the body in ‘with-file-lock’ (from (guix build
> syscalls)), which handles non-local exits.
> 
> However you’d first need to add a #:wait? argument to ‘with-file-lock’
> and perhaps an additional argument to handle the already-locked case.
> Or maybe call that ‘with-file-lock/no-wait’.
> 
> How does that sound?
> 
> Thanks for working on it!
> 
> Ludo’.

Thanks! here is a new patch with your suggestions.
>From 5d86226f318a111cc1bdf5a6f044c6f540f51b45 Mon Sep 17 00:00:00 2001
From: Julien Lepiller 
Date: Fri, 25 Oct 2019 21:39:21 +0200
Subject: [PATCH] guix: package: lock profiles when processing them.

* guix/scripts/package.scm (process-actions): Get a per-profile lock to
prevent concurrent actions on profiles.
* guix/build/syscalls.scm (with-file-lock/no-wait): New procedure.
(lock-file): Take a #:wait? key.
---
 guix/build/syscalls.scm  | 33 ++--
 guix/scripts/package.scm | 65 +++-
 2 files changed, 69 insertions(+), 29 deletions(-)

diff --git a/guix/build/syscalls.scm b/guix/build/syscalls.scm
index bbf2531c79..d843194cce 100644
--- a/guix/build/syscalls.scm
+++ b/guix/build/syscalls.scm
@@ -80,6 +80,7 @@
 lock-file
 unlock-file
 with-file-lock
+with-file-lock/no-wait
 
 set-thread-name
 thread-name
@@ -1087,10 +1088,10 @@ exception if it's already taken."
   ;; Presumably we got EAGAIN or so.
   (throw 'flock-error err))
 
-(define (lock-file file)
+(define* (lock-file file #:key (wait? #t))
   "Wait and acquire an exclusive lock on FILE.  Return an open port."
   (let ((port (open-file file "w0")))
-(fcntl-flock port 'write-lock)
+(fcntl-flock port 'write-lock #:wait? wait?)
 port))
 
 (define (unlock-file port)
@@ -1119,10 +1120,38 @@ exception if it's already taken."
 (when port
   (unlock-file port))
 
+(define (call-with-file-lock/no-wait file thunk handler)
+  (let ((port (catch 'system-error
+(lambda ()
+		  (catch 'flock-error
+(lambda ()
+		  (lock-file file #:wait? #f))
+		handler))
+(lambda args
+  ;; When using the statically-linked Guile in the initrd,
+  ;; 'fcntl-flock' returns ENOSYS unconditionally.  Ignore
+  ;; that error since we're typically the only process running
+  ;; at this point.
+  (if (or (= ENOSYS (system-error-errno args)) (= 'flock-error args))
+  #f
+  (apply throw args))
+(dynamic-wind
+  (lambda ()
+#t)
+  thunk
+  (lambda ()
+(when port
+  (unlock-file port))
+
 (define-syntax-rule (with-file-lock file exp ...)
   "Wait to acquire a lock on FILE and evaluate EXP in that context."
   (call-with-file-lock file (lambda () exp ...)))
 
+(define-syntax-rule (with-file-lock/no-wait file handler exp ...)
+  "Try to acquire a lock on FILE and evaluate EXP in that context.  Execute
+handler if the lock is already held by another process."
+  (call-with-file-lock/no-wait file (lambda () exp ...) handler))
+
 
 ;;;
 ;;; Miscellaneous, aka. 'prctl'.
diff --git a/guix/scripts/package.scm b/guix/scripts/package.scm
index 1a58d43e5c..4776d61077 100644
--- a/guix/scripts/package.scm
+++ b/guix/scripts/package.scm
@@ -42,6 +42,8 @@
   #:autoload   (guix store roots) (gc-roots)
   #:use-module ((guix build utils)
 #:select (directory-exists? mkdir-p))
+  #:use-module ((guix build syscalls)
+#:select (with-file-lock/no-wait))
   #:use-module (ice-9 format)
   #:use-module (ice-9 match)
   #:use-module (ice-9 regex)
@@ -876,36 +878,45 @@ processed, #f otherwise."
  (package-version item)
  (manifest-entry-version entry))
 
-  ;; First, process roll-backs, generation removals, etc.
-  (for-each (match-lambda
-  ((key . arg)
-   (and=> (assoc-ref %actions key)
-  (lambda (proc)
-(proc store profile arg opts
-  #:dry-run? dry-run?)
-opts)
 
-  ;; Then, process normal package removal/installation/upgrade.
-  (let* ((manifest (profile-manifest profile))
- (step1(options->removable opts manifest
-   (manifest-transaction)))
- (step2(options->installable opts manifest step1))
- (step3(manifest-transaction
-(inherit step2)
-(install (map transform-entry
-  (manifest-transaction-install step2)
- (new  (manifest-perform-transaction manifest step3)))
+  ;; First, acquire a lock on the profile, to ensure only one guix process
+  ;; is modifying it at a time.
+  (with-

bug#37917: Kernel Panic

2019-10-25 Thread pelzflorian (Florian Pelz)
On Fri, Oct 25, 2019 at 09:46:26AM -0600, Jesse Gibbons wrote:
> I also have a kernel panic often. The picture i took is too large for the
> mailing list though :( The dump says something about trying to kill init.
> 

Could you compress your photo like:

guix environment --ad-hoc imagemagick
convert your-photo.jpg -quality 20% new-compressed-photo.jpg

Perhaps use less than 20%.

When I recompress the photo my Raghav, I get the attached small file.

Regards,
Florian

bug#37904: CPU overheating on recent laptops

2019-10-25 Thread Arne Babenhauserheide

Ludovic Courtès  writes:
>> For laptops and other battery-powered devices, ‘conservative’ is
>> preferred over ‘ondemand’.  It's probably a sane default choice for
>> all.

> --8<---cut here---start->8---
> $ cat /sys/devices/system/cpu/cpu?/cpufreq/scaling_available_governors
> performance powersave

> $ uname -a
> Linux ribbon 5.3.7-gnu #1 SMP 1 x86_64 GNU/Linux
> --8<---cut here---end--->8---
>
> Do you see more governors on your side?  How could that be?

Do you have a recent Intel CPU? From what I know they removed support
for conservative, because their powersave is in fact conservative.

Also they don’t necessarily stick to the frequency you set for them. To
ensure that they keep the frequency, I have a script running that sets
the speed every minute:

(define cpupower-powersave-job
  ;; Set the governor to powersave every minute.
  ;; The job's action is a shell command.
  ;; TODO: migrate to clearer syntax:   #~(job '(next-hour '(3)) (string-append 
#$btrfs-progs "/bin/btrfs scrub start -c 3 /")))
  #~(job "* * * * *";Vixie cron syntax
 "cpupower frequency-set -g powersave -u 120")) ;; use powersave 
governor with a maximum frequency of 1200MHz

(this is a problem which also hits other distributions)

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken


signature.asc
Description: PGP signature


bug#37931: Cannot guix refresh -ru util-linux to get updated lsblk

2019-10-25 Thread Bengt Richter
Hi Guix,

IpPulled and updated to guix describe:
-
Generation 19   Oct 24 2019 22:37:20(current)
  guix 6caa739
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 6caa7392d8e51f5ef26e9efaa867ca5f9e1cac91
-

but lsblk -f still looks like this:
-
NAMEFSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda  
├─sda1   
├─sda2   
├─sda3   
├─sda4   
├─sda5   
├─sda6   
└─sda7   
sdb  
└─sdb1   
nvme0n1  
├─nvme0n1p1  510M50% /boot
├─nvme0n1p2  
├─nvme0n1p3  [SWAP]
└─nvme0n1p4 12.6G71% /
-
where it should look like: (got this using foreign /usr/bin/lsblk -f)
-
NAMEFSTYPE LABEL   UUID FSAVAIL 
FSUSE% MOUNTPOINT
sda 
   
├─sda1  vfat   Phanto1EFI  98AB-229C
   
├─sda2  ext4   d8ce4206-fc92-4248-8164-3fe5397c28fb 
   
├─sda3  swap   59e8ffd8-a2df-4021-ba59-c8dda6215f83 
   
├─sda4  ext4   Phanto4ArchGx   617f2280-d34a-4dea-ac50-a1222dd18c26 
   
├─sda5  ext4   Phanto5ArchGxOn 71e61e41-81d0-48ac-b50f-a00668723c32 
   
├─sda6  ext4   Phanto6Arch e5760f87-71bc-4318-92f1-d108e5c9e332 
   
└─sda7  ext4   Phanto7GuixSD   a60eac5f-2306-49c5-8c87-7cab28ff6d37 
   
sdb 
   
└─sdb1  ext4   Cruz1GxArchivA  18fb1d34-47b0-4d62-baea-43681ec2e5a4 
   
nvme0n1 
   
├─nvme0n1p1 vfat   PhantoV1EFI 6E3C-D410   510M 
   50% /boot
├─nvme0n1p2 ext4   PhantoNv2Empty  76bc8f68-126c-4a6c-8b77-afc89bd2726a 
   
├─nvme0n1p3 swap   24151091-f47a-46e2-a6cb-e5219eddae7c 
   [SWAP]
└─nvme0n1p4 ext4   PhantoNv4ArchGx 12eec2bf-bc81-48a8-b444-26913c078302   12.6G 
   71% /
-

So I tried:

[17:59 ~/bs]$ guix refresh -r util-linux
guix/build-system/gnu.scm:143:8: findutils would be upgraded from 4.6.0 to 4.7.0
gnu/packages/commencement.scm:2183:2: binutils would be upgraded from 2.32 to 
2.33.1
gnu/packages/commencement.scm:2244:2: gcc would be upgraded from 7.4.0 to 9.2.0
gnu/packages/commencement.scm:2142:2: glibc would be upgraded from 2.29 to 2.30
[18:01 ~/bs]$ guix refresh -ru util-linux
guix/build-system/gnu.scm:143:8: error: cannot download for this method: 
#
[18:02 ~/bs]$ lsblk --version
lsblk from util-linux 2.34
[18:04 ~/bs]$ guix package -I util-linux
util-linux  2.34out 
/gnu/store/xymkwf57x988q8cny2is1dgzrbr9xdfi-util-linux-2.34
[18:04 ~/bs]$ # was -ru combination a problem?
[18:05 ~/bs]$ guix refresh -u util-linux
[18:06 ~/bs]$ guix refresh -r util-linux
guix/build-system/gnu.scm:143:8: findutils would be upgraded from 4.6.0 to 4.7.0
gnu/packages/commencement.scm:2183:2: binutils would be upgraded from 2.32 to 
2.33.1
gnu/packages/commencement.scm:2244:2: gcc would be upgraded from 7.4.0 to 9.2.0
gnu/packages/commencement.scm:2142:2: glibc would be upgraded from 2.29 to 2.30
[18:06 ~/bs]$ guix refresh -ur util-linux
guix/build-system/gnu.scm:143:8: error: cannot download for this method: 
#
[18:06 ~/bs]$ su -c 'setterm -file refresh-errors.txt -dump 1'

TIA for any help :)
--
Regards,
Bengt Richter





bug#37917: Kernel Panic

2019-10-25 Thread Raghav Gururajan

> I can’t access it with IceCat over Tor (“Error: the file has not been
> sent entirely.”)  Can someone share it in some other way?

Sure, please use this different link: 
https://share.riseup.net/#7QvUR7_1zcgr4EL52e7pFw

Regards,
RG.




signature.asc
Description: This is a digitally signed message part


bug#37917: Kernel Panic

2019-10-25 Thread Raghav Gururajan
On Sat, 2019-10-26 at 00:10 +0200, pelzflorian (Florian Pelz) wrote:
> On Fri, Oct 25, 2019 at 09:46:26AM -0600, Jesse Gibbons wrote:
> > I also have a kernel panic often. The picture i took is too large for the
> > mailing list though :( The dump says something about trying to kill init.
> > 
> 
> Could you compress your photo like:
> 
> guix environment --ad-hoc imagemagick
> convert your-photo.jpg -quality 20% new-compressed-photo.jpg
> 
> Perhaps use less than 20%.
> 
> When I recompress the photo my Raghav, I get the attached small file.

Jesse,

If compression did not work, you can try sharing the picture via 
https://share.riseup.net

Regards,
RG.



signature.asc
Description: This is a digitally signed message part


bug#37917: Kernel Panic

2019-10-25 Thread Raghav Gururajan
> Now I see the same error. I could access it eariler though. The only
> thing I remember is that it was
> an attempted to kill init... I hope Raghav can share it again.

Sure, please use this different link: 
https://share.riseup.net/#7QvUR7_1zcgr4EL52e7pFw

Regards,
RG.




signature.asc
Description: This is a digitally signed message part