Hi, and thanks for the report, and sorry for delay in noticing this. The golang-gitlab-gitlab-org-api-client-go-dev package is a rename/reupload of golang-github-xanzy-go-gitlab-dev so it is not surprising these conflict. I've asked for advice on next steps here:
https://lists.debian.org/debian-go/2025/04/msg00000.html The rename process is briefly described here, but I'm not able to fill in the blanks on what to do: https://go-team.pages.debian.net/packaging.html#_upstream_package_moves The interaction with the ongoing freeze also complicate things. If anyone has ideas on either short-term fixes or long-term best solutions, feel free to suggest patches or do uploads. I really don't know what the best way forward is, but I'm happy to make uploads of cosign and glab to fix anything if there are concrete suggestions. They are the only two reverse dependencies of these two library packages. Meanwhile, it seems fine for golang-gitlab-gitlab-org-api-client-go-dev to stay out of testing until we have resolved this. /Simon Helmut Grohne <hel...@subdivi.de> writes: > Package: golang-gitlab-gitlab-org-api-client-go-dev > Version: 0.123.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: fileconflict > Control: affects -1 + golang-github-xanzy-go-gitlab-dev > > golang-gitlab-gitlab-org-api-client-go-dev installs > /usr/share/gocode/src/github.com/xanzy/go-gitlab as a symbolic link > whereas golang-github-xanzy-go-gitlab-dev installs it as a directory. > This poses the typical challenges that we see with /usr-merge and causes > unpredictable behaviour from dpkg depending on the unpack order. Please > stop installing a symlink where other packages install a directory. > > Helmut > >
signature.asc
Description: PGP signature
