On Fri, 2025-08-15 at 14:27 +0100, Arthur Diniz wrote: > The reason why I decided to create it as a new package is that the *GO_PATH* > also changed from *gopkg.in/yaml.v3 <http://gopkg.in/yaml.v3>* to > *go.yaml. in/yaml/v3 > <http://go.yaml. in/yaml/v3>* and the same for v2 meaning that by creating a > new package we would have the name following the go-team standards. I think it's possible to set multiple import paths in a package's XS- Go-Import-Path field, which should make things easier. On Fri, 2025-08-15 at 20:36 +0200, Simon Josefsson wrote: > Is this a friendly or hostile fork? What are the core differences? > Will the old one still be maintained and updated independently, or has > it slowed down into obsoleteness? The upstream for the current yaml packages is https://github.com/go-yaml/yaml/, which is unmaintained and archived as of April 1 (see bug #1103155). The continuation of that repo is https://github.com/yaml/go-yaml/, which is what Arthur's ITPs were for. It took me a couple of very confused minutes to realize those are two different github URLs. :) Mathias PS -- Apparently Debian's SMTP server is refusing to accept messages that contain the string "yaml. in" (without the space): > DATA command failed: Blacklisted URL in message. (yaml. in) in > [black]. See http://lookup.uribl.com.
Attachment:
signature.asc
Description: This is a digitally signed message part