[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Correct import path of golang-github-oklog-ulid and some other packages


In debian/control file of "golang-github-oklog-ulid" package, "XS-Go-Import-Path"[1] field has "github.com/oklog/ulid" as its value. Shouldn't it be "github.com/oklog/ulid/v2"? Upstream[2] along with packages[3] which require ulid package as its dependency, uses "github.com/oklog/ulid/v2" as its import path.

[1]: https://salsa.debian.org/go-team/packages/golang-github-oklog ulid/-/blob/debian/sid/debian/control#L14
[2]: https://github.com/oklog/ulid#install
[3]: https://gitlab.com/gitlab-org/labkit/blob/v1.10.0/go.mod#L15

I noticed, similar thing with some other packages:

  - golang-android-soong (android/soong)
      No hostname present in import path.

  - json2file-go (https://salsa.debian.org/sto/json2file-go)
      Import path contains protocol information (i.e. https://).

  - obfs4proxy (gitlab.com/yawning/obfs4.git)
  - golang-goptlib (git.torproject.org/pluggable-transports/goptlib.git)
  - snowflake (git.torproject.org/pluggable-transports/snowflake.git)
Import path contains ".git" suffix, but for all these three import paths, "go get" command is working. Is it common practice to use ".git" suffix in import path? Also, note that, all these three packages are maintained under "Privacy Tools" group.


Reply to: