On 2021-05-05, Ludovic Courtès wrote:
> Pushed to ‘master’ with followup commits to address the ‘guile2.2-guix’
> issues you mentioned:
>
>   dd3e4fe6e7 gnu: guile2.2-guix: Add missing dependencies.
>   2238bd8ddc gnu: guile-lzlib: Add Guile 2.2 variant.
>   2a9af22540 gnu: guile-zlib: Add Guile 2.2 variant.
>   c3f20a6678 gnu: guix: Phases refer to #:system, #:target, and #:native-inputs.
>   e42bfd236e gnu: guix: Avoid Bash wrapper.
>   55f7cd701c gnu: guix: Add run-time dependency on Guile-Lib.
>
> I’ll cherry-pick to ‘version-1.3.0’.
>
> ‘guile2.2-guix’ fails tests/swh.scm though, because (guix swh) relies on
> #:verify-certificate?, which Guile 2.2 didn’t have.  I wonder how
> Vagrant addressed that for Debian?

Heavy handedly sprinkling (test-skip 1):

  https://salsa.debian.org/debian/guix/-/blob/debian/devel/debian/patches/0029-tests-swh.scm-Disable-tests-the-fail-with-guile-2.2.patch
  https://salsa.debian.org/debian/guix/-/blob/debian/devel/debian/patches/0032-Disable-origin-visit-no-snapshots-test.patch

It would be nice to be able to automatically skip tests using known
guile 3 features when building with guile 2.2; maybe that will require
flagging each test individually or maybe there is a clever way to do
that dynamically?


live well,
  vagrant