bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities

2018-10-24 Thread Maxim Cournoyer
l...@gnu.org (Ludovic Courtès) writes: > Leo Famulari skribis: > >> On Wed, Oct 24, 2018 at 09:01:07AM -0400, Maxim Cournoyer wrote: >>> From 06ba66d1949ba59573518f471ad3cbacefea6ea2 Mon Sep 17 00:00:00 2001 >>> From: Maxim Cournoyer >>> Date: Wed, 24 Oct 2018 08:49:50 -0400 >>> Subject: [PATCH]

bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities

2018-10-24 Thread Leo Famulari
On Wed, Oct 24, 2018 at 11:33:03PM +0200, Ludovic Courtès wrote: > If might be that current-output-port is fully buffered. What if you > add: > > (setvbuf (current-output-port) 'line) > > before the ‘format’ call? Yeah, this lets' the message through.

bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities

2018-10-24 Thread Ludovic Courtès
Leo Famulari skribis: > On Wed, Oct 24, 2018 at 09:01:07AM -0400, Maxim Cournoyer wrote: >> From 06ba66d1949ba59573518f471ad3cbacefea6ea2 Mon Sep 17 00:00:00 2001 >> From: Maxim Cournoyer >> Date: Wed, 24 Oct 2018 08:49:50 -0400 >> Subject: [PATCH] build: git-fetch: Print message when falling ba

bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities

2018-10-24 Thread Ludovic Courtès
Hi, Maxim Cournoyer skribis: > Upon further inspection, we can do better on our side, specifically by > printing a message of the fallback occurring when calling git-fetch. The > patch below implements this simple change. > > What do you think? > > From 06ba66d1949ba59573518f471ad3cbacefea6ea2 M

bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities

2018-10-24 Thread Leo Famulari
On Wed, Oct 24, 2018 at 09:01:07AM -0400, Maxim Cournoyer wrote: > From 06ba66d1949ba59573518f471ad3cbacefea6ea2 Mon Sep 17 00:00:00 2001 > From: Maxim Cournoyer > Date: Wed, 24 Oct 2018 08:49:50 -0400 > Subject: [PATCH] build: git-fetch: Print message when falling back to a full > checkout. > >

bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities

2018-10-24 Thread Maxim Cournoyer
Hi Ludovic, l...@gnu.org (Ludovic Courtès) writes: [...] >> Perhaps just clearer messages would have helped here also ('Failed to do >> a shallow git clone due to ~error message~, falling back to a full clone'). > > I agree, and that’s something to suggest to the Git folks. :-) Upon further in

bug#33105: cups Can't create temporary file or stopped "Filter failed"

2018-10-24 Thread Ludovic Courtès
Hi Oleg, Oleg Pykhalov skribis: > I read gnu/services/cups.scm and found that the /var/spool/cups/ > directory should be owned by ‘lp’ user: > > (define %cups-activation > ;; Activation gexp. > (with-imported-modules '((guix build utils)) > #~(begin > (use-modules (guix build uti

bug#33137: [Wishlist] recursive guix lint

2018-10-24 Thread Efraim Flashner
We have the linter check for CVEs and updates to packages in a list, but what about those packages they depend on? It would be great to be able to 'guix lint --recursive foo' and get foo and also all the packages in the different types of inputs. -- Efraim Flashner אפרים פלשנר GPG key = A28B

bug#33106: "make check-system TESTS=basic" fails on master

2018-10-24 Thread Ludovic Courtès
Chris Marusich skribis: > Chris Marusich writes: > >> I just did a Git pull; the master branch head currently points to >> a89f731b1506b3b560f4a179da2889408dfa881d. I'm rebuilding Guix from a >> fresh checkout of this commit. Once it's done, I'll let you know >> whether the system test passes.