* Understanding a Golang importer error
@ 2023-05-22 3:13 Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-22 6:38 ` Csepp
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: Felix Lechner via Development of GNU Guix and the GNU System distribution. @ 2023-05-22 3:13 UTC (permalink / raw)
To: Guix Devel
Hi,
The command
guix import go -r github.com/google/certificate-transparency-go
produces the output below. Which repo is missing the v0.41.1 tag,
please? Thanks!
Kind regards
Felix
* * *
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 (("go.opentelemetry.io/contrib/instrumentat…" …) …))
In guix/import/utils.scm:
630:33 12 (lookup-node "go.opentelemetry.io/contrib/instrumentat…" …)
In guix/memoization.scm:
98:0 11 (mproc "go.opentelemetry.io/contrib/instrumentation/go…" …)
In unknown file:
10 (_ #<procedure 7f95afe55540 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 "go.opentelemetry.io/contrib/…" …)
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.41.1' not found
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Understanding a Golang importer error
2023-05-22 3:13 Understanding a Golang importer error Felix Lechner via Development of GNU Guix and the GNU System distribution.
@ 2023-05-22 6:38 ` Csepp
2023-05-22 14:44 ` Attila Lendvai
2023-05-22 16:27 ` Simon Tournier
2 siblings, 0 replies; 7+ messages in thread
From: Csepp @ 2023-05-22 6:38 UTC (permalink / raw)
To: Felix Lechner; +Cc: guix-devel
Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> writes:
> Hi,
>
> The command
>
> guix import go -r github.com/google/certificate-transparency-go
>
> produces the output below. Which repo is missing the v0.41.1 tag,
> please? Thanks!
>
> Kind regards
> Felix
>
> * * *
>
> 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 (("go.opentelemetry.io/contrib/instrumentat…" …) …))
> In guix/import/utils.scm:
> 630:33 12 (lookup-node "go.opentelemetry.io/contrib/instrumentat…" …)
> In guix/memoization.scm:
> 98:0 11 (mproc "go.opentelemetry.io/contrib/instrumentation/go…" …)
> In unknown file:
> 10 (_ #<procedure 7f95afe55540 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 "go.opentelemetry.io/contrib/…" …)
> 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.41.1' not found
Try re-running the commands with COLUMNS=0, I thiiink that's the magic
incantation to un-break the logs.
And for the record this is why I think truncating lines in Guile traces
is a very terrible idea. It usually hides a lot of important info and
makes it necessary to re-run expensive computations for no reason.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Understanding a Golang importer error
2023-05-22 3:13 Understanding a Golang importer error Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-22 6:38 ` Csepp
@ 2023-05-22 14:44 ` Attila Lendvai
2023-05-22 16:27 ` Simon Tournier
2 siblings, 0 replies; 7+ messages in thread
From: Attila Lendvai @ 2023-05-22 14:44 UTC (permalink / raw)
To: Felix Lechner; +Cc: Guix Devel
> The command
>
> guix import go -r github.com/google/certificate-transparency-go
>
> produces the output below. Which repo is missing the v0.41.1 tag,
> please? Thanks!
i have a series of go importer fixes that is long overdue for a cleanup and filing a v2.0 of them:
https://issues.guix.gnu.org/55242
but until then i've run the following import:
RUN=1
clear && ./pre-inst-env guix import go -r --pin-versions github.com/google/certificate-transparency-go > >(tee -a ~/workspace/guix/importing/certificate-transparency-go-${RUN}.scm) 2> >(tee -a ~/workspace/guix/importing/certificate-transparency-go-${RUN}.log >&2) && beep
and without --pin-versions:
RUN=2
clear && ./pre-inst-env guix import go -r github.com/google/certificate-transparency-go > >(tee -a ~/workspace/guix/importing/certificate-transparency-go-${RUN}.scm) 2> >(tee -a ~/workspace/guix/importing/certificate-transparency-go-${RUN}.log >&2) && beep
whose output i'll send you in a private mail due to their size.
HTH,
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“I would rather have questions that can't be answered than answers that can't be questioned.”
— Richard Feynman (1918–1988)
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Understanding a Golang importer error
2023-05-22 3:13 Understanding a Golang importer error Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-22 6:38 ` Csepp
2023-05-22 14:44 ` Attila Lendvai
@ 2023-05-22 16:27 ` Simon Tournier
2023-05-25 2:29 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2 siblings, 1 reply; 7+ messages in thread
From: Simon Tournier @ 2023-05-22 16:27 UTC (permalink / raw)
To: Felix Lechner, Guix Devel
Hi,
On dim., 21 mai 2023 at 20:13, Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> wrote:
> produces the output below. Which repo is missing the v0.41.1 tag,
> please? Thanks!
Using submission #63647 [1], now it raises:
--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix import go -r github.com/google/certificate-transparency-go
guix import: warning: Git error: reference 'refs/tags/v0.41.1' not found in https://github.com/open-telemetry/opentelemetry-go-contrib
guix import: warning: Git error: reference 'refs/tags/v2.305.9' not found in https://github.com/etcd-io/etcd
following redirection to `https://github.com/bufbuild/protoc-gen-validate?go-get=1'...
guix import: warning: Git error: reference 'refs/tags/v1.9.1' not found in https://github.com/googleapis/google-cloud-go
guix import: warning: Git error: reference 'refs/tags/v1.14.0' not found in https://github.com/googleapis/google-cloud-go
guix import: warning: Git error: reference 'refs/tags/v1.19.3' not found in https://github.com/googleapis/google-cloud-go
--8<---------------cut here---------------end--------------->8---
Note that these warnings are non-blocking and thus a list of Guix
packages can be generated, although some are partial.
Well, I do not know if we can do better. I mean, the issue seems about
a wrong packaging upstream. I mean, the tag v0.41.1 is reported as
metadata from goproxy (https://proxy.golang.org) but then the real Git
repository of the package does not contain it.
Other said, the importer first queries goproxy and get metadata. This
lists available versions; v0.41.1 is part of this list as reported by
the hint:
--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix import go go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc@0.41
hint: Pick one of the following available versions: 0.42.0-rc.1 0.41.1 0.41.0-rc.2 0.41.0-rc.1 0.41.0 0.40.0 0.39.0 0.38.0 0.37.0 0.36.4 0.36.3 0.36.2 0.36.1
0.36.0 0.35.0 0.34.0 0.33.0 0.32.0 0.31.0 0.30.0 0.29.0 0.28.0 0.27.0 0.26.1 0.26.0 0.25.0 0.24.0 0.23.0 0.22.0 0.21.0 0.20.0 0.19.0 0.18.0 0.17.0
0.16.0 0.15.1 0.15.0 0.14.0 0.13.0 0.12.0.
--8<---------------cut here---------------end--------------->8---
Second, the importer Git clone the repository. You can access to the
cache (replace ’simon’ by your username on your machine :-))
--8<---------------cut here---------------start------------->8---
$ git -C /tmp/guix-import-go-simon/bpi2cmvczo24ns3r74zzxe3upjamzlo5t7c5cv4gwgcpld7jiw4a tag | grep v0.41.1
detectors/aws/lambda/v0.41.1
instrumentation/github.com/Shopify/sarama/otelsarama/example/v0.41.1
instrumentation/github.com/Shopify/sarama/otelsarama/test/v0.41.1
instrumentation/github.com/Shopify/sarama/otelsarama/v0.41.1
instrumentation/github.com/astaxie/beego/otelbeego/example/v0.41.1
instrumentation/github.com/astaxie/beego/otelbeego/test/v0.41.1
instrumentation/github.com/astaxie/beego/otelbeego/v0.41.1
instrumentation/github.com/aws/aws-lambda-go/otellambda/example/v0.41.1
instrumentation/github.com/aws/aws-lambda-go/otellambda/test/v0.41.1
instrumentation/github.com/aws/aws-lambda-go/otellambda/v0.41.1
instrumentation/github.com/aws/aws-lambda-go/otellambda/xrayconfig/v0.41.1
instrumentation/github.com/aws/aws-sdk-go-v2/otelaws/example/v0.41.1
instrumentation/github.com/aws/aws-sdk-go-v2/otelaws/test/v0.41.1
instrumentation/github.com/aws/aws-sdk-go-v2/otelaws/v0.41.1
instrumentation/github.com/bradfitz/gomemcache/memcache/otelmemcache/example/v0.41.1
instrumentation/github.com/bradfitz/gomemcache/memcache/otelmemcache/test/v0.41.1
instrumentation/github.com/bradfitz/gomemcache/memcache/otelmemcache/v0.41.1
instrumentation/github.com/emicklei/go-restful/otelrestful/example/v0.41.1
instrumentation/github.com/emicklei/go-restful/otelrestful/test/v0.41.1
instrumentation/github.com/emicklei/go-restful/otelrestful/v0.41.1
instrumentation/github.com/gin-gonic/gin/otelgin/example/v0.41.1
instrumentation/github.com/gin-gonic/gin/otelgin/test/v0.41.1
instrumentation/github.com/gin-gonic/gin/otelgin/v0.41.1
instrumentation/github.com/go-kit/kit/otelkit/example/v0.41.1
instrumentation/github.com/go-kit/kit/otelkit/test/v0.41.1
instrumentation/github.com/go-kit/kit/otelkit/v0.41.1
instrumentation/github.com/gocql/gocql/otelgocql/example/v0.41.1
instrumentation/github.com/gocql/gocql/otelgocql/test/v0.41.1
instrumentation/github.com/gocql/gocql/otelgocql/v0.41.1
instrumentation/github.com/gorilla/mux/otelmux/example/v0.41.1
instrumentation/github.com/gorilla/mux/otelmux/test/v0.41.1
instrumentation/github.com/gorilla/mux/otelmux/v0.41.1
instrumentation/github.com/labstack/echo/otelecho/example/v0.41.1
instrumentation/github.com/labstack/echo/otelecho/test/v0.41.1
instrumentation/github.com/labstack/echo/otelecho/v0.41.1
instrumentation/go.mongodb.org/mongo-driver/mongo/otelmongo/test/v0.41.1
instrumentation/go.mongodb.org/mongo-driver/mongo/otelmongo/v0.41.1
instrumentation/google.golang.org/grpc/otelgrpc/example/v0.41.1
instrumentation/google.golang.org/grpc/otelgrpc/test/v0.41.1
instrumentation/google.golang.org/grpc/otelgrpc/v0.41.1
instrumentation/gopkg.in/macaron.v1/otelmacaron/example/v0.41.1
instrumentation/gopkg.in/macaron.v1/otelmacaron/test/v0.41.1
instrumentation/gopkg.in/macaron.v1/otelmacaron/v0.41.1
instrumentation/host/example/v0.41.1
instrumentation/host/v0.41.1
instrumentation/net/http/httptrace/otelhttptrace/example/v0.41.1
instrumentation/net/http/httptrace/otelhttptrace/test/v0.41.1
instrumentation/net/http/httptrace/otelhttptrace/v0.41.1
instrumentation/net/http/otelhttp/example/v0.41.1
instrumentation/net/http/otelhttp/test/v0.41.1
instrumentation/net/http/otelhttp/v0.41.1
instrumentation/runtime/example/v0.41.1
instrumentation/runtime/v0.41.1
propagators/autoprop/v0.41.1
propagators/opencensus/examples/v0.41.1
propagators/opencensus/v0.41.1
zpages/v0.41.1
--8<---------------cut here---------------end--------------->8---
Well, I do not know if there are conventions in the Go ecosystem that
points to other tags. For sure, some tags are there as expected and
then after v0.24, no.
--8<---------------cut here---------------start------------->8---
$ git -C /tmp/guix-import-go-simon/bpi2cmvczo24ns3r74zzxe3upjamzlo5t7c5cv4gwgcpld7jiw4a tag | grep ^v
v0.10.0
v0.10.1
v0.11.0
v0.12.0
v0.13.0
v0.14.0
v0.15.0
v0.15.1
v0.16.0
v0.17.0
v0.18.0
v0.19.0
v0.20.0
v0.21.0
v0.22.0
v0.23.0
v0.24.0
v0.6.0
v0.6.1
v0.7.0
v0.8.0
v0.9.0
v1.0.0
v1.1.0
v1.1.1
v1.10.0
v1.11.0
v1.11.1
v1.12.0
v1.13.0
v1.14.0
v1.15.0
v1.16.0
v1.16.0-rc.1
v1.16.0-rc.2
v1.16.1
v1.17.0-rc.1
v1.2.0
v1.3.0
v1.4.0
v1.5.0
v1.6.0
v1.7.0
v1.8.0
v1.9.0
--8<---------------cut here---------------end--------------->8---
1: <https://issues.guix.gnu.org/issue/63647>
Cheers,
simon
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Understanding a Golang importer error
2023-05-22 16:27 ` Simon Tournier
@ 2023-05-25 2:29 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-25 14:09 ` Simon Tournier
0 siblings, 1 reply; 7+ messages in thread
From: Felix Lechner via Development of GNU Guix and the GNU System distribution. @ 2023-05-25 2:29 UTC (permalink / raw)
To: Simon Tournier; +Cc: Guix Devel
Hi Simon,
On Mon, May 22, 2023 at 10:02 AM Simon Tournier
<zimon.toutoune@gmail.com> wrote:
>
> Using submission #63647 [1], now it raises:
>
> --8<---------------cut here---------------start------------->8---
> $ ./pre-inst-env guix import go -r github.com/google/certificate-transparency-go
> guix import: warning: Git error: reference 'refs/tags/v0.41.1' not found in https://github.com/open-telemetry/opentelemetry-go-contrib
> guix import: warning: Git error: reference 'refs/tags/v2.305.9' not found in https://github.com/etcd-io/etcd
> following redirection to `https://github.com/bufbuild/protoc-gen-validate?go-get=1'...
> guix import: warning: Git error: reference 'refs/tags/v1.9.1' not found in https://github.com/googleapis/google-cloud-go
> guix import: warning: Git error: reference 'refs/tags/v1.14.0' not found in https://github.com/googleapis/google-cloud-go
> guix import: warning: Git error: reference 'refs/tags/v1.19.3' not found in https://github.com/googleapis/google-cloud-go
> --8<---------------cut here---------------end--------------->8---
>
> Note that these warnings are non-blocking and thus a list of Guix
> packages can be generated, although some are partial.
Thank you so much! That patch takes the cake and probably deserves to
become the accepted answer.
I would find it more consistent, however, to pick a nearby version (or
the newest version) and emit that package definition, instead.
After all, Guix package variables do not care about versions, and
neither do we. Guix and its contributors assume more or less
throughout that nearby versions work fine. Why not here, too?
We could also prompt the user of 'guix import' to select a tag.
> Well, I do not know if we can do better. I mean, the issue seems about
> a wrong packaging upstream. I mean, the tag v0.41.1 is reported as
> metadata from goproxy (https://proxy.golang.org) but then the real Git
> repository of the package does not contain it.
There must be a convention that were are missing. The repositories
contain hundreds and sometimes thousands of Git tags that look like
file paths. The version number we recognize are at the very end. At
the other end of the weirdness spectrum is the speculation by folks on
#go-nuts that the missing tags were subsequently deleted.
Do the versions perhaps come from the consuming go.mod files that
spell out the version requirements?
Kind regards,
Felix
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Understanding a Golang importer error
2023-05-25 2:29 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
@ 2023-05-25 14:09 ` Simon Tournier
2023-05-25 16:02 ` Simon Tournier
0 siblings, 1 reply; 7+ messages in thread
From: Simon Tournier @ 2023-05-25 14:09 UTC (permalink / raw)
To: Felix Lechner; +Cc: Guix Devel
Hi,
On mer., 24 mai 2023 at 19:29, Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> wrote:
> I would find it more consistent, however, to pick a nearby version (or
> the newest version) and emit that package definition, instead.
Well, what does it mean “nearby“? From my understanding, it seems
better to display a warning, to be non-blocking and provide a recipe
where the integrity checksum is missing. For an example, see:
https://issues.guix.gnu.org/issue/63647#0-lineno61
> After all, Guix package variables do not care about versions, and
> neither do we. Guix and its contributors assume more or less
> throughout that nearby versions work fine. Why not here, too?
I do not understand what it means. Guix package cares a lot about
fixed-output, i.e. about the integrity checksum. :-) Quoting the manual:
Operations such as file downloads and version-control checkouts
for which the expected content hash is known in advance are
modeled as fixed-output derivations. Unlike regular derivations,
the outputs of a fixed-output derivation are independent of its
inputs—e.g., a source code download produces the same result
regardless of the download method and tools being used.
https://guix.gnu.org/manual/devel/en/guix.html#Derivations
Therefore, you need a mean to express the map between the Guix
content-addressed and the outside world working with URIs and often with
version label.
> We could also prompt the user of 'guix import' to select a tag.
Well, I know nothing about Go. Neither about how Go packaging is
working. Currently, these tags does not seems appearing in the goproxy
(https://proxy.golang.org) which is the information used to construct
the recipe, IIUC.
> Do the versions perhaps come from the consuming go.mod files that
> spell out the version requirements?
Please note that, as Attila pointed, some improvements [1,2] for the Go
importer are waiting for review in the patch tracker. Help is
welcome. ;-)
1: https://issues.guix.gnu.org/issue/55242
2: https://issues.guix.gnu.org/issue/63631
Cheers,
simon
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Understanding a Golang importer error
2023-05-25 14:09 ` Simon Tournier
@ 2023-05-25 16:02 ` Simon Tournier
0 siblings, 0 replies; 7+ messages in thread
From: Simon Tournier @ 2023-05-25 16:02 UTC (permalink / raw)
To: Felix Lechner; +Cc: Guix Devel
Hi,
On jeu., 25 mai 2023 at 16:09, Simon Tournier <zimon.toutoune@gmail.com> wrote:
>> We could also prompt the user of 'guix import' to select a tag.
>
> Well, I know nothing about Go. Neither about how Go packaging is
> working. Currently, these tags does not seems appearing in the goproxy
> (https://proxy.golang.org) which is the information used to construct
> the recipe, IIUC.
I correct myself. :-)
See v3 of #63647 which rebases #52362 implementing support of tags.
--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix import go go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
(define-public go-go-opentelemetry-io-contrib-instrumentation-google-golang-org-grpc-otelgrpc
(package
(name
"go-go-opentelemetry-io-contrib-instrumentation-google-golang-org-grpc-otelgrpc")
(version "0.42.0")
(source (origin
(method git-fetch)
(uri (git-reference
(url
"https://github.com/open-telemetry/opentelemetry-go-contrib")
(commit (string-append
"instrumentation/google.golang.org/grpc/otelgrpc/v"
version))))
(file-name (git-file-name name version))
(sha256
(base32
"0ny4v9jcv5x6y78dwazsif93r0bcfc17h7rb7q2c9hgnfxx6lap3"))))
(build-system go-build-system)
(arguments
'(#:import-path
"go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc"))
(propagated-inputs `(("go-gopkg-in-yaml-v3" ,go-gopkg-in-yaml-v3)
("go-google-golang-org-genproto" ,go-google-golang-org-genproto)
("go-google-golang-org-appengine" ,go-google-golang-org-appengine)
("go-golang-org-x-text" ,go-golang-org-x-text)
("go-golang-org-x-sys" ,go-golang-org-x-sys)
("go-golang-org-x-oauth2" ,go-golang-org-x-oauth2)
("go-golang-org-x-net" ,go-golang-org-x-net)
("go-github-com-pmezard-go-difflib" ,go-github-com-pmezard-go-difflib)
("go-github-com-golang-protobuf" ,go-github-com-golang-protobuf)
("go-github-com-go-logr-stdr" ,go-github-com-go-logr-stdr)
("go-github-com-go-logr-logr" ,go-github-com-go-logr-logr)
("go-github-com-davecgh-go-spew" ,go-github-com-davecgh-go-spew)
("go-cloud-google-com-go-compute-metadata" ,go-cloud-google-com-go-compute-metadata)
("go-cloud-google-com-go-compute" ,go-cloud-google-com-go-compute)
("go-google-golang-org-protobuf" ,go-google-golang-org-protobuf)
("go-google-golang-org-grpc" ,go-google-golang-org-grpc)
("go-go-opentelemetry-io-otel-trace" ,go-go-opentelemetry-io-otel-trace)
("go-go-opentelemetry-io-otel-metric" ,go-go-opentelemetry-io-otel-metric)
("go-go-opentelemetry-io-otel" ,go-go-opentelemetry-io-otel)
("go-github-com-stretchr-testify" ,go-github-com-stretchr-testify)))
(home-page
"https://go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc")
(synopsis #f)
(description #f)
(license license:asl2.0)))
--8<---------------cut here---------------end--------------->8---
Cheers,
simon
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2023-05-25 18:34 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-05-22 3:13 Understanding a Golang importer error Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-22 6:38 ` Csepp
2023-05-22 14:44 ` Attila Lendvai
2023-05-22 16:27 ` Simon Tournier
2023-05-25 2:29 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-25 14:09 ` Simon Tournier
2023-05-25 16:02 ` Simon Tournier
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).