bug#32020: [PATCH 1/2] bash completion: Complete files names after 'guix build -L'.

Hello Ludovic, Thank you for review. l...@gnu.org (Ludovic Courtès) writes: > Oleg Pykhalov skribis: > >> * etc/completion/bash/guix (_guix_complete): Complete files names after 'guix >> build -L'. > > [...] > >> * etc/completion/bash/guix (_guix_complete): Complete files names after 'guix >> w

bug#30921: Jupyter uses the wrong Python.

Konrad Hinsen skribis: > l...@gnu.org (Ludovic Courtès) writes: > >>> Yes. Installed kernels are normally under $prefix/share/jupyter/kernels. >>> A standard installation of Jupyter via PyPI also installs a kernel for >>> the same Python interpreter that is used for Jupyter. Additional kernels >>

bug#31390: java-hamcrest-all fails to build

This should be fixed now with commit 2cc63e6fc. -- Ricardo

bug#32022: (new feature) Change guix pull to choose commits for which substitutes is already built by default

Hello swedebugia, swedebugia skribis: > I would like it to be easy for newcomers to do the right thing when pulling. > > I suggest we by default give guix pullers a bit more information and > interaction. > Something like this: > "Checking for newly built derivations of guix at hydra.gnu.org...

bug#30921: Jupyter uses the wrong Python.

l...@gnu.org (Ludovic Courtès) writes: >> Yes. Installed kernels are normally under $prefix/share/jupyter/kernels. >> A standard installation of Jupyter via PyPI also installs a kernel for >> the same Python interpreter that is used for Jupyter. Additional kernels >> can then be installed afterwar

bug#30921: Jupyter uses the wrong Python.

Hello, Konrad Hinsen skribis: > Ricardo Wurmus writes: > >> I wonder if that’s by design. As far as I understand Jupyter can be >> used with many different kernels, including different versions of >> Python. This means that we may not limit it to just a single version of >> Python at build ti

bug#31319: ghc-case-insensitive: Duplicate 'inputs' field.

Hello Mark, Mark H Weaver skribis: > It's true that it wouldn't change anything to simply remove those > ignored duplicate field initializers. However, I thought it would be > better to give people familiar with these packages an opportunity to > investigate. Someone may have had a good reason

bug#28211: Grafting code triggers GC/thread-safety issue on Guile 2.2.2

Hi, l...@gnu.org (Ludovic Courtès) skribis: > On current ‘core-updates’, the code in (guix build graft) triggers > random Guile crashes (GC issue? thread-safety issue?) when running on > Guile 2.2.2, as initially reported by Marius at >

bug#32020: [PATCH 1/2] bash completion: Complete files names after 'guix build -L'.

Oleg Pykhalov skribis: > * etc/completion/bash/guix (_guix_complete): Complete files names after 'guix > build -L'. [...] > * etc/completion/bash/guix (_guix_complete): Complete files names after 'guix > weather -m'. OK for both, thank you Oleg! Ludo’.

bug#32018: Guixsd pull error on very old install

Hello, swedebugia skribis: > Trying to get an updated an old GuixSD installation via guix pull on a pre > 0.10 GuixSD returned an error message about gexp-modules not found. (details > can be provided if asked). Could you post the full backtrace? > I suggest we either test pulling from old