Otto Kekäläinen <otto@debian.org> writes: > Is the goal of having the version string in all go packages? > > Or should golang-github-minio-minio-go be kept in the archive and just > updated to latest? I would kinda prefer to merge all the changes in golang-github-minio-minio-go-v7-dev into golang-github-minio-minio-go-dev and do an upload of the latter, then migrate all packages that use golang-github-minio-minio-go-v7-dev to use golang-github-minio-minio-go-dev, and then RM golang-github-minio-minio-go-v7-dev instead. But that is also a lot of work for what appears to only be an easthetic goal. So I'm not sure it is worth it, especially at this time since we need to touch multiple packages... I don't think there should be any hard policy on *-vX-dev packages, sometimes it is a simple way out of a multi-version dependency mess... But I think the preference should be to not have them at all. /Simon Checking reverse dependencies... # Broken Depends: golang-github-minio-madmin-go: golang-github-minio-madmin-go-dev golang-github-minio-pkg: golang-github-minio-pkg-dev incus: golang-github-lxc-incus-dev lxd: golang-github-canonical-lxd-dev # Broken Build-Depends: gitlab-ci-multi-runner: golang-github-minio-minio-go-v7-dev golang-github-minio-madmin-go: golang-github-minio-minio-go-v7-dev (7.0.84 >=) golang-github-minio-pkg: golang-github-minio-minio-go-v7-dev (7.0.88 >=) incus: golang-github-minio-minio-go-v7-dev lxd: golang-github-minio-minio-go-v7-dev minio-client: golang-github-minio-minio-go-v7-dev restic: golang-github-minio-minio-go-v7-dev Dependency problem found.
Attachment:
signature.asc
Description: PGP signature