bug#23286: Unable to unlock xscreensaver in Xfce

2016-04-20 Thread Ludovic Courtès
Andreas Enge skribis: > On Thu, Apr 14, 2016 at 06:50:32PM +0200, Ludovic Courtès wrote: >> (operating-system >> ;; … >> (services (cons (screen-locker-service "xscreensaver") >> %desktop-services))) >> Could you try and report back? >> I guess we’ll enable it by def

bug#23311: TLS handshake error

2016-04-20 Thread Ludovic Courtès
Mathieu Lirzin skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Indeed, as soon as we add %COMPAT, ‘gnutls-cli’ et al. send a 253-byte >> client hello (instead of 261) and the problem vanishes. >> >> Commit 967ee481e893fd77ff8ca896188e20e425331bf2 does that. > > \o/ > > Thanks for taking th

bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change

2016-04-20 Thread Ludovic Courtès
Alex Kost skribis: > Ludovic Courtès (2016-04-19 13:50 +0300) wrote: > >> Alex Kost skribis: >> >>> Ludovic Courtès (2016-04-18 20:41 +0300) wrote: >>> It seems to me that this bug has no clear purpose, or too broad a purpose, or something. Could you retitle it, or close it,

bug#23311: TLS handshake error

2016-04-20 Thread Mathieu Lirzin
l...@gnu.org (Ludovic Courtès) writes: > Indeed, as soon as we add %COMPAT, ‘gnutls-cli’ et al. send a 253-byte > client hello (instead of 261) and the problem vanishes. > > Commit 967ee481e893fd77ff8ca896188e20e425331bf2 does that. \o/ Thanks for taking the time to debug this! -- Mathieu Lirz

bug#23311: TLS handshake error

2016-04-20 Thread Ludovic Courtès
l...@gnu.org (Ludovic Courtès) skribis: > $ while ./pre-inst-env guix download https://mirror.hydra.gnu.org/index.html > ; do : ; done Interestingly, the same loop with wget (which uses the very same GnuTLS) goes on forever. It turns out that instead of the default TLS cipher suite priority str

bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change

2016-04-20 Thread Alex Kost
Ludovic Courtès (2016-04-19 13:50 +0300) wrote: > Alex Kost skribis: > >> Ludovic Courtès (2016-04-18 20:41 +0300) wrote: >> >>> It seems to me that this bug has no clear purpose, or too broad a >>> purpose, or something. >>> >>> Could you retitle it, or close it, or fix it, whichever is appropri