From: dparsons@emerall.com   
      
   On 2026-02-23 20:20, Shengjing Zhu wrote:   
   >>   
   >> It looks like there should be a compatibility link generated by   
   >> debian/links.   
   >> https://salsa.debian.org/go-team/packages/golang-yaml.v2/-/co   
   mit/15b38821bfe8587b0550f5bf185e36499455f01b   
   >>   
   >> It should have come with 2.4.2-1.   
   >> Looks like something's gone wrong with the link in 2.4.3-1   
   >   
   > The link is still in 2.4.3-1   
   >   
   > $ ls -l usr/share/gocode/src/gopkg.in/yaml.v2   
   > lrwxrwxrwx 1 zsj zsj 21 Nov  3 22:46   
   > usr/share/gocode/src/gopkg.in/yaml.v2 -> ../go.yaml.in/yaml/v2   
   >   
   > It looks valid. I'm not sure why rclone fails to build with that.   
      
   I think it's just an upgrade issue. Not a huge problem but one the   
   package should manage.   
   In the past the path was gopkg.in/yaml.v2. Now it's go.yaml.in/yaml/v2.   
   The link has been added to help the transition.   
      
   The problem is with an upgrade transition, not in a new installation.  A   
   new installation just gets gopkg.in/yaml.v2. as the symlink.   
      
   The problem is that previously gopkg.in/yaml.v2 was a directory not a   
   link.  Its contents get removed on upgrade, but the debian installations   
   scripts do not replace an existing (empty) directory with the new   
   symlink.   
      
   The same problem was reported for golang-gopkg-yaml.v3-dev in   
   Bug#1118270   
   They pointed at the solution documented at   
   https://manpages.debian.org/unstable/dpkg/dpkg-maintscript-helpe   
   .1.en.html#Switching_a_directory_to_symlink   
      
   Drew   
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118270   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)