bug#56900: phoronix-test-suite downloads nonfree software (+ question on collaboration with Parabola on this package)

Hi Denis, Denis 'GNUtoo' Carikli writes: > Hi, > > Thanks a lot for working on having a recent FSDG compliant versions of > phoronix-test-suite. > > I've found a minor issue with phoronix-test-suite and I've a couple of > questions to help synchronize between Parabola and Guix to prevent >

bug#56900: phoronix-test-suite downloads nonfree software (+ question on collaboration with Parabola on this package)

Hi, Thanks a lot for working on having a recent FSDG compliant versions of phoronix-test-suite. I've found a minor issue with phoronix-test-suite and I've a couple of questions to help synchronize between Parabola and Guix to prevent accidental installation of nonfree software. Nonfree software

bug#56893: rust-vergen inserts build timestamps

On 02-08-2022 20:41, Geert Stappers wrote: Date: Tue, 2 Aug 2022 19:18:46 +0200, From: Maxime Devos In Guix, I've noticed that rust-vergen embeds build timestamps. There is also a work-around available: . Thanks for reporting the FTBR. Please update

bug#56895: rust-brotli-sys bundles (insecure!) brotli

Friendly reminder to the original patch author and committer (*) to check for bundling during review. (*) https://git.savannah.gnu.org/cgit/guix.git/commit/?id=52cc16b38b1b01b2bb354ed5510120856de15d39 Greetings, Maxime. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key

bug#56895: rust-brotli-sys bundles (insecure!) brotli

I noticed rust-brotli-sys bundles brotli: . The version it bundles is apparently insecure: As mentioned at , there

bug#56893: rust-vergen inserts build timestamps, possible irreproducibility source

The following phase works around the issue for me (for antioxidant) -- this makes "guix build --check" pass (at least for antioxidant): +    ;; TODO: SOURCE_DATE_EPOCH support would be nice.  Also maybe better fit for a snippet? +    ;; +    ;; Make the rust-vergen reproducible and avoid

bug#56893: rust-vergen inserts build timestamps, possible irreproducibility source

While fixing build failures in antioxidant, I noticed that rust-vergen is a potential source of irreproducibility -- the README.md contains the following: ## Documentation [Documentation](https://docs.rs/vergen) ## Generate Compile Time Information `vergen`, when used in conjunction with

bug#56799: (gnu services configuration) usage of *unspecified* is problematic

Hi Ludovic, Ludovic Courtès writes: [...] >> Granted, few services outside of Jami probably made use of this, but it >> was nevertheless a useful property. > > I don’t know of any. I think mostly because few services make use of define-configuration. While attempting to write a new VNC

bug#56786: git-minimal fails to build (non-deterministic)

The log that was sent was for a successful build (maybe they retried the build?), seems like we will have to wait for another report. Greetings, Maxime. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature

bug#56799: (gnu services configuration) usage of *unspecified* is problematic

Hi, On +2022-08-02 09:31:14 +0200, Ludovic Courtès wrote: > Hi, > > Maxim Cournoyer skribis: > > > Ludovic Courtès writes: > > > >> Hi! > >> > >> Maxim Cournoyer skribis: > >> > >>> Since commit 8cb1a49a3998c39f315a4199b7d4a121a6d66449, the > >>> define-configuration machinery in (gnu

bug#56799: (gnu services configuration) usage of *unspecified* is problematic

Hi, Maxim Cournoyer skribis: > Ludovic Courtès writes: > >> Hi! >> >> Maxim Cournoyer skribis: >> >>> Since commit 8cb1a49a3998c39f315a4199b7d4a121a6d66449, the >>> define-configuration machinery in (gnu services configuration) uses >>> *unspecified* instead of 'disabled for an unspecified