W dniu 27.02.2026 o 13:25, Otto Kekäläinen pisze:

In https://salsa.debian.org/go-team/packages/golang-yaml.v2/-/merge_requests/3
I see upstream had this rename:

-"gopkg.in/yaml.v2"
+"go.yaml.in/yaml/v2"

Arthur created this symlink for backwards compat:
https://salsa.debian.org/go-team/packages/golang-yaml.v2/-/blob/debian/sid/debian/links:

   usr/share/gocode/src/go.yaml.in/yaml/v2 usr/share/gocode/src/gopkg.in/yaml.v2

Is it not working?

So I was not sure what was going on. I think the moment when I purged the package (and all the related go packages) and re-created the state everything was okay.

I wonder if this is a dpkg-level problem where this was indeed wrong because the symlink was unable to replace the directory.

For clarity, I was not using a forky sbuild chroot. This was my actual system with persistent state.

Best regards
ZK

Reply via email to