guix import go: How to work around https://issues.guix.gnu.org/54097 ?

[wolf]

Hello,

I'm trying to use go-importer to build terraform using Guix.  However, along the
way I did encounter https://issues.guix.gnu.org/54097, leading to following
error:

    $ guix import go -r --pin-versions github.com/hashicorp/terraform
    following redirection to `https://github.com/google/gnostic?go-get=1'...
    following redirection to 
`https://github.com/hashicorp/go-metrics?go-get=1'...
    following redirection to 
`https://pkg.go.dev/github.com/apparentlymart/go-textseg/v13'...
    Backtrace:
    In srfi/srfi-1.scm:
       586:29 19 (map1 _)
       586:29 18 (map1 _)
       586:29 17 (map1 _)
       586:29 16 (map1 _)
       586:29 15 (map1 _)
       586:29 14 (map1 _)
       586:17 13 (map1 (("github.com/Azure/go-autorest/tracing" "v0…") …))
    In guix/import/utils.scm:
       630:33 12 (lookup-node "github.com/Azure/go-autorest/tracing" "v0…")
    In guix/memoization.scm:
         98:0 11 (mproc "github.com/Azure/go-autorest/tracing" # #<proc…> …)
    In unknown file:
              10 (_ #<procedure 7f20a94304e0 at guix/memoization.scm:17…> …)
    In guix/import/go.scm:
       685:10  9 (_ _ #:version _ #:repo _)
    In ice-9/exceptions.scm:
       406:15  8 (go-module->guix-package* . _)
    In ice-9/boot-9.scm:
      1752:10  7 (with-exception-handler _ _ #:unwind? _ # _)
    In guix/import/go.scm:
       511:19  6 (go-module->guix-package "github.com/Azure/go-autorest…" …)
    In guix/git.scm:
        291:4  5 (update-cached-checkout _ #:ref _ #:recursive? _ # _ # _ …)
       277:19  4 (resolve _)
    In git/reference.scm:
         60:8  3 (_ _ _)
    In git/bindings.scm:
         77:2  2 (raise-git-error _)
    In ice-9/boot-9.scm:
      1685:16  1 (raise-exception _ #:continuable? _)
      1683:16  0 (raise-exception _ #:continuable? _)
    
    ice-9/boot-9.scm:1683:16: In procedure raise-exception:
    Git error: reference 'refs/tags/v0.6.0' not found

I am not sure how to work around that.  The description for the -r does say:

> generate package expressions for all Go modules that are not yet in Guix

Would it be possible to work around this bug by manually providing the failing
package, so that the import would just skip it?  If yes, how would I do so?  I
am not sure what the precise definition of "not yet in Guix" is.  Any other
ideas how to get this working?



Thank you and have nice day,
W.

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

signature.asc
Description: PGP signature