On 2016-11-26 11:08, Santiago Vila wrote:
> Package: src:debian-ports-archive-keyring
> Version: 2016.02.01
> Severity: serious
> 
> Dear maintainer:
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
> 
> --------------------------------------------------------------------------------
> [...]
>  debian/rules build-indep
> dh build-indep
> dh: Compatibility levels before 9 are deprecated (level 7 in use)
>    dh_testdir -i
>    dh_update_autotools_config -i
>    dh_auto_configure -i
> dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in 
> use)
>    debian/rules override_dh_auto_build
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> mkdir -p /<<PKGBUILDDIR>>/build       
> # Build keyrings
> mkdir -p /<<PKGBUILDDIR>>/build/keyrings
> gpg --no-options --no-default-keyring --no-auto-check-trustdb --homedir 
> /<<PKGBUILDDIR>>/build --keyring 
> /<<PKGBUILDDIR>>/build/keyrings/debian-ports-archive-keyring.gpg --import 
> /<<PKGBUILDDIR>>/active-keys/*
> gpg: WARNING: unsafe permissions on homedir '/<<PKGBUILDDIR>>/build'
> gpg: keybox 
> '/<<PKGBUILDDIR>>/build/keyrings/debian-ports-archive-keyring.gpg' created
> gpg: /<<PKGBUILDDIR>>/build/trustdb.gpg: trustdb created
> gpg: key B4C86482705A2CE1: public key "Debian Ports Archive Automatic Signing 
> Key (2016) <ftpmas...@debian-ports.org>" imported
> gpg: can't connect to the agent: IPC connect call failed
> gpg: Total number processed: 1
> gpg:               imported: 1
> debian/rules:9: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 2
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> debian/rules:6: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> --------------------------------------------------------------------------------
> 
> The relevant part of the build log is included above.
> 
> This is not a random bug, it happens every time I try. I'm building on a 
> QEMU/KVM virtual
> machine with sbuild and a stretch chroot with minimal packages installed.
> 
> 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.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                 http://www.aurel32.net

Reply via email to