bug#48077: assword superseded by impass

Efraim Flashner writes: > https://finestructure.net/assword/ > > The assword password management system project as been renamed "impass", > and has moved to https://salsa.debian.org/debian/impass. > > Someone™ who uses this package should update it and deprecate the > current package. That

bug#47260: Package GNU MediaGoblin as a Guix service

Ben Sturmfels via Bug reports for GNU Guix writes: > On Fri, 19 Mar 2021, jgart wrote: > >> This sounds like a great project. I would love MediaGoblin to be in Guix >> also. >> >>> 6. Rewrite MediaGoblin's JavaScript code not to use jQuery. Maybe >>> improve the no-bundled-JavaScript video/audio

bug#44808: Default to allowing password authentication on leaves users vulnerable

Mark H Weaver writes: > Hi, > > "Dr. Arne Babenhauserheide" writes: >> To nudge them to secure their system, guix system reconfigure could emit >> a warning that this is a potential security risk that requires setting >> an explicit value (password yes or no) to silence. > > I think this is a

bug#44808: Default to allowing password authentication on leaves users vulnerable

Leo Famulari writes: > On Sat, Dec 05, 2020 at 01:22:23PM -0500, Christopher Lemmer Webber wrote: >> > 2. Change the default value of the relevant field in >> > . >> > >> > #2 is more thorough but also more risky: people could find themselve

bug#44808: Default to allowing password authentication on leaves users vulnerable

Dr. Arne Babenhauserheide writes: > Ludovic Courtès writes: > #2 is more thorough but also more risky: people could find themselves locked out of their server after reconfiguration, though this could be mitigated by a news entry. Thoughts? > > My thoughts are that there

bug#44808: Default to allowing password authentication on leaves users vulnerable

Ludovic Courtès writes: > Hi! > > Maxim Cournoyer skribis: > I'm on board with what you're proposing, and I think Guix should default to the more secure option, but I'm not sure that an "average user" (whatever that means for Guix's demographic) would expect that password

bug#37309: ‘ssh-daemon’ service fails to start at boot

Leo Famulari writes: > On Sat, Nov 28, 2020 at 02:08:34AM +0100, Marius Bakke wrote: >> Christopher Lemmer Webber skriver: >> > I'm assuming others must be experiencing this still too... right? >> >> FWIW I have never encountered this. :-/ > > I reenabled IP

bug#37309: ‘ssh-daemon’ service fails to start at boot

Giovanni Biscuolo writes: > Hi, > > following a recent discussion on guix-sysadmin I have to confirm the > ssh-daemon issue since it is still happening on some of the machines I > administer > > Previous possibly related bug reports are > https://issues.guix.gnu.org/issue/30993 and >

bug#44825: Error in reporting guix deploy error

default-authorized-guix-keys) So basically I referenced a file that doesn't exist with local-file. But why would that cause the string formatting to fail? Dunno... Christopher Lemmer Webber writes: > Seems strange... the message I get: > > guix deploy: error: failed to depl

bug#44825: Error in reporting guix deploy error

Seems strange... the message I get: guix deploy: error: failed to deploy tulsi: ~A: ~S Errors upon errors! Formatting this time, apparently. :) Looking at the relevant code: (define (deploy-machine* store machine) "Deploy MACHINE, taking care of error handling." (info (G_ "deploying to

bug#44808: Default to allowing password authentication on leaves users vulnerable

Carlo Zancanaro writes: > Hey Chris! > > On Mon, Nov 23 2020, Christopher Lemmer Webber wrote: >> ... Plus, few distributions do what we're doing anymore, precisely >> because of wanting to be secure by default. > > Is this true? Debian defaults to passwords being

bug#44808: Default to allowing password authentication on leaves users vulnerable

raingloom writes: > On Mon, 23 Nov 2020 03:32:08 +0100 > Taylan Kammer wrote: > >> On 23.11.2020 00:20, Christopher Lemmer Webber wrote: >> > Okay, I just realized I left a friend vulnerable by guiding them >> > through a Guix graphical install and telling them

bug#44808: Default to allowing password authentication on leaves users vulnerable

Okay, I just realized I left a friend vulnerable by guiding them through a Guix graphical install and telling them it would give them a decent setup. They turned on openssh support. Then I realized their config had password-authentication? on. That's unacceptable. We need to change this

bug#38529: Make --pure the default for `guix environment'?

Taylan Kammer writes: > On 10.12.2019 18:16, Ludovic Courtès wrote: >> Hello! >> "Thompson, David" skribis: >> >>> I have long thought that --ad-hoc should be implied, as that is the >>> mode I use 99% of the time, but I disagree that --pure should be the >>> default. >> I very much agree with

bug#38529: Make --pure the default for `guix environment'?

Ludovic Courtès writes: > Hello! > > "Thompson, David" skribis: > >> I have long thought that --ad-hoc should be implied, as that is the >> mode I use 99% of the time, but I disagree that --pure should be the >> default. > > I very much agree with that. I don’t think ‘--pure’ should be the >

bug#42861: emacspeak won't shut up about TTS sync states

I was excited to try emacspeak again and opened it, but emacspeak would nonstop talk about "tts sync states" over and over and over again... I don't remember this being the case when I tried it on Debian years ago. It's saying it so much nonstop I'm not getting any other commands in. Anyone else

bug#42252: Not possible to reliably port forward with "guix system vm" anymore

[+ Cc: Marius Bakke] because I don't have enough info to respond fully myself. Bengt Richter writes: > Hi > > On +2020-07-07 16:40:21 -0400, Christopher Lemmer Webber wrote: >> In commit 5379392731b52eef22b4936637eb592b93e04318, the following change >> was introduced: &g

bug#42252: Not possible to reliably port forward with "guix system vm" anymore

Christopher Lemmer Webber writes: > Christopher Lemmer Webber writes: > >> guix system vm config.scm --hostfwd=tcp::10022-:22 --hostfwd=tcp::-:80 >> >> kind of ugly, but it could work. WDYT? > > Kind of uglier, but more versatile: > > guix system vm c

bug#42252: Not possible to reliably port forward with "guix system vm" anymore

Christopher Lemmer Webber writes: > guix system vm config.scm --hostfwd=tcp::10022-:22 --hostfwd=tcp::-:80 > > kind of ugly, but it could work. WDYT? Kind of uglier, but more versatile: guix system vm config.scm --nic=user,model=virtio-net-pci,hostfwd=tcp::10022-:22,hostfwd=

bug#42252: Not possible to reliably port forward with "guix system vm" anymore

In commit 5379392731b52eef22b4936637eb592b93e04318, the following change was introduced: modified gnu/system/vm.scm @@ -941,6 +941,7 @@ with '-virtfs' options for the host file systems listed in SHARED-FS." '()) "-no-reboot" + "-nic"

bug#42158: python-grequests broken, add zope dependencies to fix.

Efraim Flashner writes: > On Wed, Jul 01, 2020 at 04:39:05PM -0400, Christopher Lemmer Webber wrote: >> Fix attached. Ok to push? >> > > Looks good to me. I will note however that the test suite doesn't seem > to actually be run. Huh. Well at least it's no longer

bug#42158: python-grequests broken, add zope dependencies to fix.

Fix attached. Ok to push? >From 1fc31863857361e9f88d92cbea2099fd7ea03b10 Mon Sep 17 00:00:00 2001 From: Christopher Lemmer Webber Date: Wed, 1 Jul 2020 16:36:29 -0400 Subject: [PATCH] gnu: python-grequests: Fix tests by adding zope dependencies. * gnu/packages/python-web.scm (python-greque

bug#34526: Updating node.js

Marius Bakke writes: > Christopher Lemmer Webber writes: > >> Daniel Gerber writes: >> >>> Hi, >>> >>> 2019-02-20, Jelle Licht: >>>> Daniel Gerber writes: >>>> >>>>> [snip] >>>>> What

bug#38054: mumble: "QSslSocket: cannot resolve ", Certificate Expiry, segfault

Efraim Flashner writes: > On Sun, Nov 03, 2019 at 11:04:05PM -0500, Ivan Vilata i Balaguer wrote: >> Hi! I'm using Mumble 1.2.19 from Guix commit 7f81cce3 on Debian Sid. On >> start, it logs the following messages: >> >> QSslSocket: cannot resolve CRYPTO_num_locks >> QSslSocket: cannot

bug#34526: Updating node.js

Daniel Gerber writes: > Hi, > > 2019-02-20, Jelle Licht: >> Daniel Gerber writes: >> >>> [snip] >>> What about statically linking llhttp's C "sources" included in >>> node? Building v11.10.0 succeeds with this: >> >> You could do this, of course, but afaics this is not acceptable for >>

bug#38045: Video Rendering Issues on IceCat

Raghav Gururajan writes: > Hello Guix and GNUzilla! > > I am currently using IceCat (68.2.0-guix0-preview3) on Guix System. > > Starting from version 68.X.X, I started to face issues with playing > videos online. This happens on most of the websites (not all though). > > I get any of these

bug#36961: Can't use microphone in ungoogled-chromium

Ludovic Courtès writes: > Hello, > > Mathieu Lirzin skribis: > >> Brian Leung writes: >> >>> When a microphone is plugged in, ungoogled-chromium fails to detect it. >> >> I have the same issue here. > > I initially had the same problem (specifically with Jitsi on > https://riot.im) but

bug#36977: Add OpenSubdiv library, and add as Blender dependency

I was surprised to open Blender 2.80 and find that subdivision surfaces (necessary for organic modeling) were doing nothing. I couldn't figure out why this was, until I found out that Blender now uses OpenSubdiv for subdivision surfaces. Don't think I have time to package it right now, but if

bug#36964: Some importer tests failing?

A number of tests, including in cpan.scm, crate.scm, gem.scm are failing for me. Not sure if it's just me or not... Some example output: actual-value: #f actual-error: + (wrong-type-arg + "string-prefix?" + "Wrong type argument in position ~A (expecting ~A): ~S" + (2 "string" #f) +

bug#36855: guix system switch-generation doesn't

Could you look at bug #36878 and commit 1db6f137d... as of latest master, is this fixed? Robert Vollmert writes: > Could we get some input on this bug? > > Maybe I’m misunderstanding something, but it seems that a core guix > feature (atomic rollbacks) doesn’t work… > >> On 30. Jul 2019, at

bug#34176: X200 kernel panic on S3 resume (linux-libre > 4.18.9)

Mike Gerwitz writes: > On Wed, Jan 23, 2019 at 01:08:39 -0500, Mike Gerwitz wrote: >> Right after sending this message, I recalled that I used powertop to do >> "auto tuning". Sure enough, one of the lines was this: >> >>Good Autosuspend for USB device UHCI Host Controller [usb6] >>

bug#33772: StumpWM broken commands?

Pierre Langlois writes: > Alex Kost writes: > >> Pierre Langlois (2018-12-18 17:34 +) wrote: >> >>> Hello! >>> >>> Christopher Lemmer Webber writes: >>> >>>> Ludovic Courtès writes: >>>> >>>>> Hi, &

bug#33772: StumpWM broken commands?

Pierre Langlois writes: > Hello! > > Christopher Lemmer Webber writes: > >> Ludovic Courtès writes: >> >>> Hi, >>> >>> Christopher Lemmer Webber skribis: >>> >>>> It seems to me that StumpWM broke somehow, for some reason.

bug#33772: StumpWM broken commands?

Ludovic Courtès writes: > Hi, > > Christopher Lemmer Webber skribis: > >> It seems to me that StumpWM broke somehow, for some reason. I can >> confirm there was a version change: >> >> -sbcl-stumpwm@18.05:out >> /gnu/store/i0picr2xr2aq2a52ns

bug#33772: StumpWM broken commands?

It seems to me that StumpWM broke somehow, for some reason. I can confirm there was a version change: -sbcl-stumpwm@18.05:out /gnu/store/i0picr2xr2aq2a52nsaw67nvar1r3khw-sbcl-stumpwm-18.05 +sbcl-stumpwm@18.11:out /gnu/store/6h2iln76dx8pxdp1hsaqb1yncm8viczj-sbcl-stumpwm-18.11 I

bug#33119: "Bad item name" in Dungeon Crawl Stone Soup

nee writes: > As a workaround for now you can rename your ~/.crawl directory to > ~/.crawl-backup and play with a fresh saves directory for the new version. > > Here is an example: > mv ~/.crawl ~/.crawl-backup-pre-0.22.1 This worked... I was even able to keep the scores file, though I deleted

bug#33119: "Bad item name" in Dungeon Crawl Stone Soup

In crawl (and the crawl-tiles variant) I get frequent error messages when levels are being generated like "Bad item name: fruit", which appears to be for item types that were removed from the game. Worse yet, when starting some of the sprints (eg The Pits), the game freezes up, apparently with

bug#32820: Some CSS not displaying in latest Icecat

Mike Gerwitz writes: >>> When you get a chance, can you try the new version and report back? >> >> I also verified that those pages render correctly using IceCat's alpha >> binary on a Debian system. I'll build overnight and let you know >> tomorrow if the CSS issues are resolved for me. > >

bug#32820: Some CSS not displaying in latest Icecat

Oh, and thank you for your impressive work as usual Mark... we all appreciate it :)

bug#32820: Some CSS not displaying in latest Icecat

Overall very excited about the new Icecat being available! However, css is not displaying on some sites, and I'm not sure why. Disable all extensions and try the following examples: https://addons.mozilla.org/en-US/firefox/ https://github.com/ Both will show up unstyled. Not sure the

bug#30680: [racket-users] Using Racket's raco on on Guix(SD)

Good news: this seems fixed with this patch. Some more comments inline. Timothy Sample writes: >>> Also, I checked all of this from Racket without grafts, and it never >>> complained about compiling OpenSSL stuff. Running “raco setup” gives >>> some other errors, though. >> >> You're right...

bug#30680: [PATCH] Patch Racket to fix bug #30680

Timothy Sample writes: > Hi Guix, > > (Patch is attached below.) > > This patch fixes . It does so by > patching Racket to treat store files specially. I have verified that it > both fixes the bug above and still recompiles non-store files. > > As far as I can

bug#30680: [racket-users] Using Racket's raco on on Guix(SD)

Timothy Sample writes: > Christopher Lemmer Webber writes: > >> Likewise, Gregor and Raart do not install: >> >> $ mv ~/.racket ~/.racket-borked >> $ raco pkg install gregor # lots of errors during install >> $ racket >> racket@> (requir

bug#30680: [racket-users] Using Racket's raco on on Guix(SD)

Nils Gillmann writes: > Christopher Lemmer Webber transcribed 3.3K bytes: >> BTW, some examples of packages where I've had trouble, in case it helps >> with testing: >> >> - Raart >> - Gregor >> - crypto (seemed to work last time, not sure why

bug#30680: [racket-users] Using Racket's raco on on Guix(SD)

Timothy Sample writes: > Christopher Lemmer Webber writes: > >> Konrad Hinsen writes: >> >>> In my tests, all packages ended up working, but performance is indeed >>> worse than with a Racket installation outside of Guix. >>> >>> It

bug#30680: [racket-users] Using Racket's raco on on Guix(SD)

Konrad Hinsen writes: > On 22/05/2018 15:42, Christopher Lemmer Webber wrote: > >> Unfortunately when I try to install packages with "raco pkg install" >> I get errors like the following: > > I filed a bug report about this problem a while ago: > > https

bug#32283: Add chroma (a little video game)

From 3ca38f3813eb7e6473673622de04b8fbb03d256d Mon Sep 17 00:00:00 2001 From: Christopher Lemmer Webber Date: Thu, 26 Jul 2018 17:37:53 -0400 Subject: [PATCH] gnu: Add chroma. * gnu/packages/games.scm (chroma): New variable. --- gnu/packages/games.scm | 34 +- 1

bug#31069: emacs-smartparens: sp-forward-barf-sexp broken

Thorsten Wilms writes: > On 07.04.2018 17:19, Alex Kost wrote: > >> Sorry, I don't know what could cause your problem. My only idea is >> maybe you have some mixed (incompatible) packages both from Guix and >> from (M)ELPA (for example, "dash.el" from Melpa and "smartparens" from >> Guix). Look

bug#30714: Racket doesn't build any more, xform error

Fixed bugs #30714 and #30603 in 75afbd247876d62f27cb2c90098bd59040f7e614

bug#30714: Racket doesn't build any more, xform error

Related to the attempt to upgrade Racket to 6.12: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30603 Apparently the patch I proposed may break GC, so another option should be found. But more interestingly is that my thought that things broke because of a change from Racket 6.11 to 6.12

bug#28578: xorg not starting on x200 due to recent commit

Ricardo Wurmus writes: > Hi, > >> In the meanwhile, I've figured maybe I could test trying to set up xorg >> to use a specific driver to see if that fixes it: >> >> (services (cons* >> ;;; ... >> (modify-services %desktop-services >>

bug#28578: xorg not starting on x200 due to recent commit

Mark H Weaver writes: > Danny Milosavljevic writes: > >> (Does anyone mind >>> pasting their equivalent lspci output who's saying "it works for me" on >>> an x200? I wonder if we can find the soruce of the difference.) >> >> 00:00.0 Host bridge: Intel Corporation Mobile

bug#28578: xorg not starting on x200 due to recent commit

Christopher Allan Webber writes: > Chris Marusich writes: > >> Leo Famulari writes: >> >>> On Sun, Sep 24, 2017 at 05:15:02PM -0700, Chris Marusich wrote: Christopher Allan Webber writes: > The following commit to guix makes it so that