bug#45187: git download defaults to origin/master

Ricardo Wurmus writes: > Importing https://github.com/immunogenomics/scpost with the CRAN > importer fails, because the git repository does not have an > origin/master branch. This repository only has a “main” branch. > > Arguably, this shouldn’t matter, but (guix git) has the “master” name >

bug#45172: fiano-fmap test failure

Hello, I confirm the test failure. I tried fixing it with the patch below, but there's still something up with it. I don't know the go build system enough to be able to tell what's up--can someone else help? diff --git a/gnu/packages/admin.scm b/gnu/packages/admin.scm index

bug#45187: git download defaults to origin/master

Importing https://github.com/immunogenomics/scpost with the CRAN importer fails, because the git repository does not have an origin/master branch. This repository only has a “main” branch. Arguably, this shouldn’t matter, but (guix git) has the “master” name set up as the default. When cloning

bug#45051: Guix pull fails: `In procedure put-string: Wrong type argument in position 1 (expecting open output port): #`

Hi Ludovic, > Could it be that your substitute URL is ? > > If so, could you try: > > guix build inkscape --substitute-urls=https://ci.guix.gnu.org This works, thanks.

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

Hi, Mark H Weaver skribis: > gnu/services/ssh.scm:570:31, here: > > > https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/services/ssh.scm?id=ec2eccbf3d1a6378c5ebf1e3d17ec72b4b2a4cd0#n570 > > Here's what I see when I build a system: > > mhw@jojen ~/guix$ ./pre-inst-env guix system build

bug#45051: Guix pull fails: `In procedure put-string: Wrong type argument in position 1 (expecting open output port): #`

Hi pkill9, pkill9 skribis: > Computing Guix derivation for 'x86_64-linux'... /@ substituter-started > /gnu/store/9ph7spq3b72fv4scqqzwxalb8n0wc6xn-graphviz-2.42.3-doc > substitute -following redirection to Could it be that your substitute URL is ? If so, could you try:

bug#45173: ‘guix search’ traverses all the modules when extra channels are used

Hey, On Fri, 11 Dec 2020 at 16:56, Ludovic Courtès wrote: > The point :-) is to show that things that should definitely not be > loaded, such as gnu/services/*, are getting loaded when multiple > channels are in use. What I have tried to show is that even with the default, «things that should

bug#45165: binutils-mesboot0 fails at configure, cannot find lex

Hi Janneke! Oh, that’s a very good find! I have no idea why config.cache is not writable… This is most strange! I checked that my mountpoints have enough free space… Not sure what else to check? Looking at `guix describe`, I’m on bf8dfe3df025e4ac80cccb87497b4f072ba10e2a Cheers, Carl Dong >

bug#45173: ‘guix search’ traverses all the modules when extra channels are used

Hi! zimoun skribis: > On Fri, 11 Dec 2020 at 10:29, Ludovic Courtès > wrote: > >> --8<---cut here---start->8--- >> $ strace -o /tmp/,,s guix search sdfsdf >> $ grep gnu/services /tmp/,,s >> $ echo $? >> 1 >> --8<---cut

bug#44760: [PATCH 09/15] database: Remove #:deduplicate? from 'register-items'.

It is now up to the caller to deduplicate store contents. * guix/store/database.scm (register-items): Remove #:deduplicate? parameter and call to 'deduplicate'. (register-path): Call 'deduplicate' when #:deduplicate? is true. * gnu/build/image.scm (register-closure): Adjust call accordingly. *

bug#44760: [PATCH 04/15] store-copy: 'populate-store' resets timestamps.

Until now, 'populate-store' would reset permissions but not timestamps, so callers would resort to going through an extra directory traversal to reset timestamps. * guix/build/store-copy.scm (reset-permissions): Remove. (copy-recursively): New procedure. (populate-store): Pass #:keep-permissions?

bug#44760: [PATCH 02/15] serialization: 'restore-file' sets canonical timestamp and permissions.

* guix/serialization.scm (restore-file): Set the permissions and mtime of FILE. * guix/nar.scm (finalize-store-file): Pass #:reset-timestamps? #f to 'register-items'. * tests/nar.scm (rm-rf): Add 'chmod' calls to ensure files are writable. ("write-file + restore-file with symlinks"): Ensure every

bug#44760: [PATCH 12/15] system: 'init' does not recompute the hash of each store item.

Fixes . Previously, the 'register-path' call would re-traverse ITEM to compute its nar hash, even though that hash is already known in the initial store. This patch also avoids repeated opening/closing of the database. * guix/store/database.scm (call-with-database):

bug#44760: [PATCH 00/15] Speed up 'guix system init' & co.

Hi there! Here’s a long and rather boring patch series to address and a bit more. To avoid traversing store items repeatedly as described in the issue above, the strategy here is to gradually move the reset-timestamps and deduplicate phases as part of the file

bug#44760: [PATCH 15/15] deduplicate: Create the '.links' directory lazily.

This avoids repeated (mkdir-p "/gnu/store/.links") calls when deduplicating lots of files. * guix/store/deduplication.scm (deduplicate): Remove initial call to 'mkdir-p'. Add ENOENT case in 'link' exception handler. Reindent. * tests/store-deduplication.scm ("deduplicate, ENOSPC"): Check for

bug#44760: [PATCH 14/15] database: Honor 'SOURCE_DATE_EPOCH'.

* guix/store/database.scm (timestamp): New procedure. (sqlite-register): Use it as the default for #:time. (register-items): Likewise for #:registeration-time. --- guix/store/database.scm | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git

bug#44760: [PATCH 10/15] guix system: 'init' copies, resets timestamps, and deduplicates at once.

Partly fixes . * guix/build/store-copy.scm (copy-store-item): New procedure. (populate-store): Use it instead of the inline 'copy-recursively' call. * guix/scripts/system.scm (copy-item): Likewise. Pass #:reset-timestamps? and #:deduplicate? to 'register-path'. ---

bug#44760: [PATCH 13/15] database: Remove 'register-path'.

* guix/store/database.scm (register-path): Remove. * tests/store-database.scm ("register-path"): Rename to... ("register-items"): ... this, and use 'register-items' instead of 'register-path'. ("register-path, directory"): Rename to... ("register-items, directory"): ... this, and use

bug#44760: [PATCH 11/15] database: Remove #:deduplicate? and #:reset-timestamps? from 'register-path'.

* guix/store/database.scm (register-path): Remove #:deduplicate? and #:reset-timestamps?. * guix/scripts/system.scm (copy-item): Adjust accordingly. * tests/store-database.scm ("register-path") ("register-path, directory"): Call 'reset-timestamps'. --- guix/scripts/system.scm | 6 +-

bug#44760: [PATCH 08/15] image: 'register-closure' leaves it up to the caller to deduplicate.

* gnu/build/image.scm (register-closure): Remove #:deduplicate? parameter and pass #:deduplicate? #f to 'register-items'. (initialize-root-partition): Adjust accordingly. * gnu/build/vm.scm (register-closure, root-partition-initializer): Likewise. --- gnu/build/image.scm | 8 ++--

bug#44760: [PATCH 06/15] database: Remove #:reset-timestamps? from 'register-items'.

The assumption now is that the caller took care of resetting timestamps and permissions. * guix/store/database.scm (register-items): Remove #:reset-timestamps? parameter and the call to 'reset-timestamps'. (register-path): Adjust accordingly and add call to 'reset-timestamps'. *

bug#44760: [PATCH 07/15] store-copy: 'populate-store' can optionally deduplicate files.

Until now deduplication was performed as an additional pass after copying files, which involve re-traversing all the files that had just been copied. * guix/store/deduplication.scm (copy-file/deduplicate): New procedure. * tests/store-deduplication.scm ("copy-file/deduplicate"): New test. *

bug#44760: [PATCH 03/15] nar: Deduplicate files right as they are restored.

This avoids having to traverse and re-read the files that we have just restored, thereby reducing I/O. * guix/serialization.scm (dump-file): New procedure. (restore-file): Add #:dump-file parameter and honor it. * guix/store/deduplication.scm (tee, dump-file/deduplicate): New procedures. *

bug#44760: [PATCH 05/15] image: 'register-closure' assumes already-reset timestamps.

* gnu/build/image.scm (register-closure): Remove #:reset-timestamps? parameter. Pass #:reset-timestamps? #f to 'register-items'. (initialize-root-partition): Adjust accordingly. * gnu/build/vm.scm (register-closure, root-partition-initializer): Likewise. --- gnu/build/image.scm | 8 +++-

bug#44760: [PATCH 01/15] serialization: 'fold-archive' notifies about directory processing completion.

* guix/serialization.scm (fold-archive): Call PROC with a 'directory-complete tag when done with a directory. (restore-file): Handle it. * guix/scripts/archive.scm (list-contents): Likewise. * guix/scripts/challenge.scm (archive-contents): Likewise. * tests/nar.scm ("write-file-tree +

bug#45179: qutebrowser stuck on browser checks forever

guix (GNU Guix) 91e35e32a4938e0e37499c64fa8ed3e7cf51dce3 some example sites with browser checks: https://gitlab.com/users/sign_in http://livechart.me/ I already contacted the people in the qutebrowser IRC. The bug persists when I launch with no config (`qutebrowser --temp-basedir'), and they

bug#26247: Gettext introduces timestamps in .mo files

Hi! Ludovic Courtès writes: > Julien Lepiller skribis: > >> So it's not gettext itself, but our build system that generates the >> en@quote and en@boldquote files. Do we really need them? If so, we >> should find a way to generate them reproducibly. > > They’re generated automatically by the

bug#45173: ‘guix search’ traverses all the modules when extra channels are used

Hi Ludo, On Fri, 11 Dec 2020 at 10:29, Ludovic Courtès wrote: > --8<---cut here---start->8--- > $ strace -o /tmp/,,s guix search sdfsdf > $ grep gnu/services /tmp/,,s > $ echo $? > 1 > --8<---cut here---end--->8--- I do

bug#45174: ‘guix substitute’ doesn’t handle HTTP redirects

Hi! As reported by mange on #guix, it seems that ‘guix substitute’ does not follow redirects: --8<---cut here---start->8--- $ guix weather icecat emacs --substitute-urls=https://ci.guix.gnu.org computing 2 package derivations for x86_64-linux... looking for 2

bug#45173: ‘guix search’ traverses all the modules when extra channels are used

When a single channel is in use, ‘guix search’ understandable traverses nothing but gnu/packages/*.scm: --8<---cut here---start->8--- $ strace -o /tmp/,,s guix search sdfsdf $ grep gnu/services /tmp/,,s $ echo $? 1 --8<---cut