bug#52073: remove Google support from GVFS?

Earlier, I wrote: > In fact, if you look at the commit log over the last few years, you'll > see that 8 out of the last 10 non-micro updates of WebKitGTK have > required additional changes to the build recipe. Correction: it's actually 9 out of the last 10. At first glance, the following commit

bug#52073: remove Google support from GVFS?

Hi Leo, Leo Famulari writes: > My experience with WebKitGTK is that the build is quite reliable. That's > why I pushed the broken update to begin with: it always worked in the > past. That might be true of _micro_ version updates of WebKitGTK, but it's certainly false for non-micro updates. I

bug#52906: python-biopython conflicts with python-numpy

zimoun writes: > Hi, > > On Fri, 31 Dec 2021 at 13:44, Ricardo Wurmus wrote: > >> I just realized that switching over to the new numpy is going to cause >> more than a 1000 rebuilds. So I’ll apply your patch on the master >> branch and build out the numpy upgrade on a separate branch. > >

bug#52904: nmtui - user authorisation

Hello, raingloom writes: > On Wed, 29 Dec 2021 11:04:39 + > Paul Jewell wrote: > >> On 29/12/2021 00:50, raingloom wrote: >> > On Tue, 28 Dec 2021 18:39:52 + >> > Paul Jewell wrote: >> > >> >> On 27/12/2021 23:20, Leo Famulari wrote: >> >>> On Mon, Dec 27, 2021 at 10:07:17PM +,

bug#52919: Hidden "disk-image-rw" files aren't deleted after use, filling $tmpdir

I noticed that files such as ".gk8hqaqb6z4q1gmk678sixjbc9r7kd9g-disk-image-rw" are filling up my $TMPDIR when building ISO images with Guix. This is new. I think the issue was introduced with recent work on (gnu system image), perhaps from this commit:

bug#52073: remove Google support from GVFS?

On Fri, Dec 31, 2021 at 01:24:55PM +0100, Liliana Marie Prikler wrote: > Given that we have GNOME 40/41 on master right now with GVFS supporting > Google as it did before, is this still relevant? Since the bug report was a reaction to WebKitGTK being broken, and it's no longer broken, I'm closing

bug#48064: [Dev-luatex] bug#48064: texlive-* packages fail to build non-deterministically

On Fri, Jul 2, 2021 at 5:11 PM Thiago Jung Bauermann wrote: > Em quarta-feira, 30 de junho de 2021, às 08:53:41 -03, luigi scarso > escreveu: > > On Wed, Jun 30, 2021 at 8:20 AM Ludovic Courtès wrote: > > > Hi, > > > > > > Ludovic Courtès skribis: > > > > While investigating luatex crashes in

bug#52539: Fwd: Comments in /etc/passwd don't get updated

Hi Jacob, Jacob First skribis: > Thanks for the explanation. This rationale sounds reasonable to me. If > someone with proper permission has modified a user account's comment, > it could be important to preserve that customization. > > As I pointed out in an earlier message, I believe this

bug#52652: FreeCAD requires write access to store for parsetab.py

I started building it after the patch was merged, it finished now and the presented issue is no longer present. On 12/31/21 11:44, Guillaume Le Vaillant wrote: Hi, With Guix at b7078d5d49d72cb5e5356d698b99540612b4d6c4, I tried to reproduce the issue, but I didn't get any error. I started

bug#52652: FreeCAD requires write access to store for parsetab.py

Jacob Hrbek skribis: > I started building it after the patch was merged, it finished now and > the presented issue is no longer present. Ok, thanks for confirming. Closing. signature.asc Description: PGP signature

bug#52906: python-biopython conflicts with python-numpy

Hi, On Fri, 31 Dec 2021 at 13:44, Ricardo Wurmus wrote: > I just realized that switching over to the new numpy is going to cause > more than a 1000 rebuilds. So I’ll apply your patch on the master > branch and build out the numpy upgrade on a separate branch. Thanks! A separate wip-* branch?

bug#52906: python-biopython conflicts with python-numpy

zimoun writes: > Attached a proposed patch. I applied it with a small change: I also had to override the name as “python-numpy” in the derived packages. Thanks! -- Ricardo

bug#52906: python-biopython conflicts with python-numpy

zimoun writes: > Hi Ricardo, > > On Fri, 31 Dec 2021 at 11:18, Ricardo Wurmus wrote: >> zimoun writes: > >> Back then we reverted to numpy 1.20.x as the default because of numba, >> which did not work with 1.21. I’m now upgrading numba (and llvmlite) to >> a more recent release candidate,

bug#52073: remove Google support from GVFS?

Hi, Given that we have GNOME 40/41 on master right now with GVFS supporting Google as it did before, is this still relevant? Cheers

bug#50299: [PATCH v4 07/25] gnu: swi-prolog: Don't use 'cc'.

* gnu/packages/prolog.scm (swi-prolog)[arguments]<#:configure-flags>: Set CMAKE_HOST_CC to gcc when cross-compiling. --- gnu/packages/prolog.scm | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/gnu/packages/prolog.scm b/gnu/packages/prolog.scm index

bug#50299: [PATCH v4 06/25] gnu: swi-prolog: Make configuration wok when cross-compiling.

* gnu/packages/prolog.scm (swi-prolog)[arguments]<#:configure-flags>: Set BSD_SIGNALS and QSORT_R_GNU when cross-compiling. --- gnu/packages/prolog.scm | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/gnu/packages/prolog.scm b/gnu/packages/prolog.scm index

bug#50299: [PATCH v4 02/25] gnu: lean: Don't run tests when cross-compiling.

It still fails to cross-compile though. * gnu/packages/lean.scm (lean)[arguments]<#:tests?>: Set to #false when cross-compiling. --- gnu/packages/lean.scm | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/gnu/packages/lean.scm b/gnu/packages/lean.scm index

bug#50299: [PATCH v4 10/25] gnu: swi-prolog: Correct reference to 'bin/swi-prolog'.

* gnu/packages/prolog.scm (swi-prolog)[arguments]<#:phases>{fix-cross-references}: New phase. --- gnu/packages/prolog.scm | 37 - 1 file changed, 24 insertions(+), 13 deletions(-) diff --git a/gnu/packages/prolog.scm b/gnu/packages/prolog.scm index

bug#50299: [PATCH v4 22/25] gnu: pjproject: Run tests conditionally.

* gnu/packages/telephony.scm (pjproject)[arguments]: Remove #:tests? instead of unconditionally setting it to #t. --- gnu/packages/telephony.scm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/gnu/packages/telephony.scm b/gnu/packages/telephony.scm index

bug#50299: [PATCH v4 15/25] gnu: ecl: Run tests conditionally.

* gnu/packages/lisp.scm (ecl)[arguments]<#:tests?>: Move comment about failing tests to ... (ecl)[arguments]<#:phases>{check}: ... this deleted phase. (ecl)[arguments]: Remove #:tests? instead of unconditionally setting it to #t. --- gnu/packages/lisp.scm | 5 ++--- 1 file changed, 2

bug#50299: [PATCH v4 11/25] gnu: ruby-yard-with-tests: Run tests conditionally.

* gnu/packages/ruby.scm (ruby-yard-with-tests)[arguments]: Remove #:tests? instead of setting unconditionally setting it to #t. --- gnu/packages/ruby.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/ruby.scm b/gnu/packages/ruby.scm index

bug#50299: [PATCH v4 12/25] gnu: ruby-ffi-rzmq: Run tests conditionally.

* gnu/packages/ruby.scm (ruby-ffi-rzmq)[arguments]: Remove #:tests? instead of setting unconditionally setting it to #t. --- gnu/packages/ruby.scm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/gnu/packages/ruby.scm b/gnu/packages/ruby.scm index e04302a5e3..be773c7a61

bug#50299: [PATCH v4 03/25] gnu: lean: Add bash-minimal.

Explicitely adding this input is required for cross-compilation. * gnu/packages/lean.scm (lean)[inputs]: Add 'bash-minimal'. --- gnu/packages/lean.scm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gnu/packages/lean.scm b/gnu/packages/lean.scm index fa36d282d7..7f4cd507f8

bug#50299: [PATCH v4 14/25] gnu: go-1.16: Don't run tests when cross-compiling.

* gnu/packages/golang.scm (go-1.16)[arguments]: Remove #:tests? instead of unconditionally setting it to #t. --- gnu/packages/golang.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/golang.scm b/gnu/packages/golang.scm index de0f5a695e..e139ba6f36 100644

bug#50299: [PATCH v4 09/25] gnu: swi-prolog: Set PROG_SWIPL when cross-compiling.

* gnu/packages/prolog.scm (swi-prolog)[arguments]<#:configure-flags>: Set PROG_SWIPL and SWIPL_NATIVE_FRIEND when cross-compiling and make this a G-expression. (swi-prolog)[native-inputs]: Add 'this-package' when cross-compiling. --- gnu/packages/prolog.scm | 35

bug#50299: [PATCH v4 23/25] gnu: tdlib: Run tests conditionally.

* gnu/packages/messaging.scm (tdlib)[arguments]: Remove #:tests? instead of unconditionally setting it to #t. --- gnu/packages/messaging.scm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/gnu/packages/messaging.scm b/gnu/packages/messaging.scm index 52b01c8f87..365dfe4090

bug#50299: [PATCH v4 20/25] gnu: lablgtk: Run tests conditionally.

* gnu/packages/ocaml.scm (lablgtk)[arguments]: Remove #:tests? instead of unconditionally setting it to #t. --- gnu/packages/ocaml.scm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/gnu/packages/ocaml.scm b/gnu/packages/ocaml.scm index e6001ca37b..01cf348e54 100644 ---

bug#50299: [PATCH v4 25/25] gnu: ghc-bsb-http-chunked: Don't run tests when cross-compiling.

* gnu/packages/haskell-web.scm (ghc-bsb-http-chunked)[arguments]<#:tests?>: Set to #false when cross-compiling. --- gnu/packages/haskell-web.scm | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/gnu/packages/haskell-web.scm b/gnu/packages/haskell-web.scm index

bug#50299: [PATCH v4 01/25] lint: check-tests-true: Allow #:tests? #t for some build systems.

emacs-build-system sets #:tests? #f by default, so the linter shouldn't warn if #:tests? #t is set for packages using emacs-build-system. Likewise for texlive-build-system * guix/lint.scm (check-tests-true): Do not warn if the build system is emacs-build-system or texlive-build-system. *

bug#50299: [PATCH v4 18/25] gnu: python2-empy: Run tests conditionally.

* gnu/packages/python-xyz.scm (python2-empy)[arguments]: Remove #:tests? instead of unconditionally setting it to #t. --- gnu/packages/python-xyz.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm index

bug#50299: [PATCH v4 00/25] Fix 'check-tests-true' linter and some packages

Hi, The following changes from v3 were made: * rebased on latest master * in the swi-prolog patch, a use of %build-host-inputs has been replaced by #$(this-package-native-input ...) * The patch 'gnu: swi-prolog: Correct reference to 'bin/swi-prolog' is new. * Commit messages are made

bug#52836: "guix import pypi" fails with "Failed to extract file from wheel" and "no requires.txt file found"

> Is it a bug on Guix side or upstream? Because it seems that upstream > does not provide metadata information, at least, as usually expected. `pip install PyPortfolioOpt`, `poetry add PyPortfolioOpt` runs for me. If other python package installer can run, I suppose the upstream is correct.

bug#50299: [PATCH v4 08/25] gnu: swi-prolog: Use cross-compiled bash in shebangs.

* gnu/packages/prolog.scm (swi-prolog)[inputs]: Add 'bash-minimal'. --- gnu/packages/prolog.scm | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/gnu/packages/prolog.scm b/gnu/packages/prolog.scm index fc3956b17b..3eaec533d7 100644 --- a/gnu/packages/prolog.scm +++

bug#50299: [PATCH v4 05/25] gnu: swi-prolog: Run tests conditionally.

Tests are enabled by default (except when cross-compiling). Running tests when cross-compiling is rarely possible. * gnu/packages/prolog.scm (swi-prolog)[arguments]<#:tests>: Remove it. --- gnu/packages/prolog.scm | 1 - 1 file changed, 1 deletion(-) diff --git a/gnu/packages/prolog.scm

bug#50299: [PATCH v4 24/25] gnu: extra-cmake-modules: Don't run tests when cross-compiling.

* gnu/packages/kde-frameworks.scm (extra-cmake-modules)[arguments]<#:tests?>: Set to #false when cross-compiling. --- gnu/packages/kde-frameworks.scm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gnu/packages/kde-frameworks.scm b/gnu/packages/kde-frameworks.scm index

bug#50299: [PATCH v4 04/25] gnu: swi-prolog: Move native-inputs to inputs where appropriate.

* gnu/package/prolog.scm (swi-prolog) [native-inputs]: Keep 'texinfo', 'perl' and 'pkg-config' and move the rest to ... [inputs]: ... here. --- gnu/packages/prolog.scm | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/gnu/packages/prolog.scm

bug#50299: [PATCH v4 21/25] gnu: belcard: Run tests conditionally.

* gnu/packages/linphone.scm (belcard)[arguments]: Remove #:tests? instead of unconditionally setting it to #t. --- gnu/packages/linphone.scm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/gnu/packages/linphone.scm b/gnu/packages/linphone.scm index 285ecb58fd..1536597f1d

bug#50299: [PATCH v4 19/25] gnu: python2-promise: Run tests conditionally.

* gnu/packages/python-xyz.scm (python2-promise)[arguments]: Remove #:tests? instead of unconditionally setting it to #t. --- gnu/packages/python-xyz.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm index

bug#50299: [PATCH v4 16/25] gnu: perl-unicode-utf8: Run tests conditionally.

* gnu/packages/perl.scm (perl-unicode-utf8)[arguments]<#:tests?>: Set to #false when cross-compiling. --- gnu/packages/perl.scm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gnu/packages/perl.scm b/gnu/packages/perl.scm index c6d63ce041..2b33d2dce4 100644 ---

bug#50299: [PATCH v4 13/25] gnu: ruby-ffi-rzmq: Respect #:tests?.

* gnu/packages/ruby.scm (ruby-ffi-rzmq)[arguments]<#:phases>: Only invoke "rspec" if #:tests? is true. --- gnu/packages/ruby.scm | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/gnu/packages/ruby.scm b/gnu/packages/ruby.scm index be773c7a61..a94270ecfa 100644 ---

bug#50299: [PATCH v4 17/25] gnu: libicns: Run tests conditionally.

The #:tests? #t is actually harmless here, because there are no tests (though there is a trivial 'check' target). The ‘; No tests.’ comment might be confusing though. * gnu/packages/image.scm (libicns)[arguments]: Remove. --- gnu/packages/image.scm | 2 -- 1 file changed, 2 deletions(-) diff

bug#52836: "guix import pypi" fails with "Failed to extract file from wheel" and "no requires.txt file found"

Hi, On Fri, 31 Dec 2021 at 11:15, bbb ee wrote: > > Is it a bug on Guix side or upstream? Because it seems that upstream > > does not provide metadata information, at least, as usually expected. > > `pip install PyPortfolioOpt`, `poetry add PyPortfolioOpt` runs for me. If > other python

bug#52652: FreeCAD requires write access to store for parsetab.py

Hi, With Guix at b7078d5d49d72cb5e5356d698b99540612b4d6c4, I tried to reproduce the issue, but I didn't get any error. I started FreeCAD with: --8<---cut here---start->8--- guix shell freecad openscad -- FreeCAD --8<---cut

bug#52906: python-biopython conflicts with python-numpy

Hi Ricardo, On Fri, 31 Dec 2021 at 11:18, Ricardo Wurmus wrote: > zimoun writes: > Back then we reverted to numpy 1.20.x as the default because of numba, > which did not work with 1.21. I’m now upgrading numba (and llvmlite) to > a more recent release candidate, which should bring

bug#52606: FreeCAD - Missing dependency python-ply

Fixed in b7078d5d49d72cb5e5356d698b99540612b4d6c4. Closing. signature.asc Description: PGP signature

bug#52906: python-biopython conflicts with python-numpy

zimoun writes: > Hi, > > Using 7022eb6, the package ’python-biopython’ propagates > ’python-numpy’, i.e., python-numpy@1.20. Back then we reverted to numpy 1.20.x as the default because of numba, which did not work with 1.21. I’m now upgrading numba (and llvmlite) to a more recent release

bug#52853: Error when trying to upgrade packages

Closing. I opened bug#52913 for the failing 0ad package. signature.asc Description: PGP signature

bug#52913: 0ad only builds fine with a specific version of mozjs

The 0ad package checks the version of mozjs and throws an error if it is not exactly the version it expects. This check is done in "source/scriptinterface/ScriptTypes.h" and it currently requires version 78.6 of mozjs. As Guix has mozjs 78.15 instead, 0ad fails to build. Patching "ScriptTypes.h"