> > I was able to build this package in the past: > > > > Status: successful > > debian-ports-archive-keyring_2016.02.01_amd64-20161101T035130Z > > Status: successful > > debian-ports-archive-keyring_2016.02.01_amd64-20161106T230827Z > > Status: successful > > debian-ports-archive-keyring_2016.02.01_amd64-20161111T100904Z > > Status: successful > > debian-ports-archive-keyring_2016.02.01_amd64-20161117T090450Z > > Status: failed > > debian-ports-archive-keyring_2016.02.01_amd64-20161122T013538Z > > Status: failed > > debian-ports-archive-keyring_2016.02.01_amd64-20161122T155001Z > > Status: failed > > debian-ports-archive-keyring_2016.02.01_amd64-20161122T154957Z > > Status: failed > > debian-ports-archive-keyring_2016.02.01_amd64-20161122T155025Z > > > > so maybe some build-dependency has changed behaviour and package has to > > adapt accordingly. > > The problem is that gpg now insists in using an agent, and creates a UNIX > socket to exchange messages. The UNIX socket path is limited to 108 > characters, and depending on the used build path, this size can be > exceeded.
Well, I'm using sbuild, so I guess this would fail in buildd.debian.org too (last upload was made 301 days ago). Does this package absolutely require gpg version 2 to build, or maybe the build-depends could be changed to gpg1 as a temporary workaround? Thanks.
