Re: Bug#1111127: ITP: golang-go.yaml-yaml-v3 -- YAML Support for the Go Language

[Arthur Diniz <arthurbdiniz@gmail.com>]

Hi Mathias,

Maybe this is a sbuild backend specific behaviour?

I'm using sbuild with unshare and I had no issues building distrobuilder here.

Before uploading the package I ran ratt to check the reverse dependencies and make sure the links would work.

The filelist links look ok to me.

https://packages.debian.org/trixie/all/golang-gopkg-yaml.v2-dev/filelist
https://packages.debian.org/testing/all/golang-gopkg-yaml.v2-dev/filelist

Might be something in the sbuild directory backend.

Do you have any easy way to reproduce on my local without having to wipe my current build configuration?

On Sun, 24 Aug 2025 at 17:06, Mathias Gibbens <gibmat@debian.org> wrote:

Arthur,

  I've noticed a weird build issue after the yaml packages were
updated. In my normal gbp workflow with pbuilder backend, everything
builds fine. But if I try to build a package with a sbuild schroot
(directory backend, not the newer unshare), I get errors like the
following:

> package github.com/gcla/termshark
>         imports github.com/gcla/termshark/v2/configs/profiles
>         imports github.com/spf13/viper
>         imports github.com/spf13/viper/internal/encoding/yaml
>         imports gopkg.in/yaml.v3: no Go files in /build/reproducible-path/termshark-2.4.0/_build/src/gopkg.in/yaml.v3
>
> package github.com/lxc/distrobuilder/distrobuilder
>         imports gopkg.in/yaml.v2: no Go files in /build/reproducible-path/distrobuilder-3.2/_build/src/gopkg.in/yaml.v2

  I haven't investigated this, but maybe something's not quite right
with the symlinks?

Mathias