Bug#978348: marked as done (ipp-usb: FTBFS: src/github.com/OpenPrinting/ipp-usb/usbio_libusb.go:64:43: cannot use int32(err) (type int32) as type _Ctype_int in argument to _Cfunc_libusb_strerror)
Your message dated Mon, 28 Dec 2020 16:20:50 +0000
with message-id <E1ktvGM-000GLb-JK@fasolo.debian.org>
and subject line Bug#978348: fixed in ipp-usb 0.9.15-1
has caused the Debian Bug report #978348,
regarding ipp-usb: FTBFS: src/github.com/OpenPrinting/ipp-usb/usbio_libusb.go:64:43: cannot use int32(err) (type int32) as type _Ctype_int in argument to _Cfunc_libusb_strerror
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
978348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978348
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: ipp-usb
Version: 0.9.14-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rm -f *.8 ipp-usb
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang
> dh_clean -O--builddirectory=_build -O--buildsystem=golang
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building ipp-usb using existing ./ipp-usb_0.9.14.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of file ipp-usb.8, use --include-removal to override
> dpkg-source: info: building ipp-usb in ipp-usb_0.9.14-2.debian.tar.xz
> dpkg-source: info: building ipp-usb in ipp-usb_0.9.14-2.dsc
> debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
> dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
> dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
> dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
> dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
> cd _build && go install -trimpath -v -p 4 github.com/OpenPrinting/ipp-usb
> internal/unsafeheader
> runtime/internal/sys
> runtime/internal/atomic
> internal/cpu
> internal/race
> runtime/internal/math
> sync/atomic
> unicode
> unicode/utf8
> internal/bytealg
> math/bits
> internal/testlog
> encoding
> math
> internal/nettrace
> container/list
> runtime/cgo
> runtime
> crypto/internal/subtle
> crypto/subtle
> unicode/utf16
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/subtle
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> bytes
> strings
> reflect
> hash
> bufio
> hash/crc32
> internal/syscall/unix
> time
> internal/syscall/execenv
> crypto
> crypto/internal/randutil
> crypto/hmac
> crypto/rc4
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/text/transform
> path
> context
> internal/poll
> os
> encoding/binary
> internal/fmtsort
> crypto/sha1
> crypto/sha512
> crypto/cipher
> fmt
> path/filepath
> net
> crypto/aes
> crypto/des
> io/ioutil
> crypto/ed25519/internal/edwards25519
> compress/flate
> encoding/xml
> github.com/OpenPrinting/goipp
> compress/gzip
> log
> math/big
> crypto/md5
> crypto/sha256
> encoding/hex
> encoding/base64
> net/url
> encoding/pem
> vendor/golang.org/x/crypto/chacha20
> vendor/golang.org/x/crypto/poly1305
> vendor/golang.org/x/sys/cpu
> vendor/golang.org/x/crypto/curve25519
> vendor/golang.org/x/crypto/chacha20poly1305
> vendor/golang.org/x/text/unicode/bidi
> crypto/rand
> crypto/elliptic
> encoding/asn1
> crypto/ed25519
> crypto/rsa
> crypto/dsa
> vendor/golang.org/x/crypto/cryptobyte
> crypto/x509/pkix
> vendor/golang.org/x/text/secure/bidirule
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/net/http2/hpack
> crypto/ecdsa
> mime
> mime/quotedprintable
> net/http/internal
> os/signal
> runtime/debug
> vendor/golang.org/x/net/idna
> net/textproto
> crypto/x509
> vendor/golang.org/x/net/http/httpproxy
> vendor/golang.org/x/net/http/httpguts
> mime/multipart
> crypto/tls
> net/http/httptrace
> net/http
> github.com/OpenPrinting/ipp-usb
> # github.com/OpenPrinting/ipp-usb
> src/github.com/OpenPrinting/ipp-usb/usbio_libusb.go:64:43: cannot use int32(err) (type int32) as type _Ctype_int in argument to _Cfunc_libusb_strerror
> dh_auto_build: error: cd _build && go install -trimpath -v -p 4 github.com/OpenPrinting/ipp-usb returned exit code 2
> make: *** [debian/rules:6: binary] Error 25
The full build log is available from:
http://qa-logs.debian.net/2020/12/26/ipp-usb_0.9.14-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ipp-usb
Source-Version: 0.9.15-1
Done: Didier Raboud <odyx@debian.org>
We believe that the bug you reported is fixed in the latest version of
ipp-usb, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 978348@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Didier Raboud <odyx@debian.org> (supplier of updated ipp-usb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 28 Dec 2020 17:01:03 +0100
Source: ipp-usb
Architecture: source
Version: 0.9.15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team <debian-printing@lists.debian.org>
Changed-By: Didier Raboud <odyx@debian.org>
Closes: 978348
Changes:
ipp-usb (0.9.15-1) unstable; urgency=medium
.
* New 0.9.15 upstream release
- Add heiner99's patch to fix FTBFS (Closes: #978348)
Checksums-Sha1:
795074154c610745f8395148714f18ce2a0d9775 2225 ipp-usb_0.9.15-1.dsc
61b96006f622adfde25ce0a91fb081ff1ab69cec 58172 ipp-usb_0.9.15.orig.tar.gz
a515709befffb298cdf4187069537b4a146a0712 3468 ipp-usb_0.9.15-1.debian.tar.xz
Checksums-Sha256:
65d2d9c83e09d8861ec02b53973bb10616fa0d5ef11ee937cad07f919997138d 2225 ipp-usb_0.9.15-1.dsc
6bc11dafc3c75c5fadcb95ab1d69e9e73b54ac97ebb7ae843689f9858f97070b 58172 ipp-usb_0.9.15.orig.tar.gz
84466d0baeb2822ed6b8f3e228f7d84fb26a917a3ea4b74aa929c06cfd550e38 3468 ipp-usb_0.9.15-1.debian.tar.xz
Files:
a623840a772695c525cfd82095609c73 2225 comm optional ipp-usb_0.9.15-1.dsc
da675bfc44c46222f6c2d2b0b94bd7ca 58172 comm optional ipp-usb_0.9.15.orig.tar.gz
b665a4a9be0994a57f105c98b3f6bb1b 3468 comm optional ipp-usb_0.9.15-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEJ3k7rA0YCplkx4gZqcb6xg1jAWkFAl/qAcAACgkQqcb6xg1j
AWkp2w//fus/Y8VzayThnzXiHEFwg97iNbXrNB0Tjp6Er9kFhnD61UXgOjf/cOH0
tXXk+zhTeOvs4bBTmqB7oSkvnsvNZfefkM5xdJSCbIqfV66enMZPgiT0/BKpfKqR
VJwCBy/FlYg0C/ltPLZw+Wf5Vv0hLDx4txzbjoI8dB2K2q74JcekHIKOrxBSYww2
XkOqQoYW1605Nkzm1UFeXjmGWOnG2nrP2yaUr+7DrXpZLvMKA6z1AK5gNTcPMPVQ
1/jCx+rL8AHKIiBIKaJKrbnndvdsv0/VmQSWFo4j0Je7jX6IlqXxt55iAKyjriye
0B9jP3yeSfiR5iF6Oy9gw++otw7sWL3M3Gm8tQy9fqKzjAMYbw2/IxpGS2zYID2r
1kTN5zJuJx8zq5QCWuFP1DM5LHE1GjiuYmvid79j1NdpvEIiUHJTmwf3v01INBYq
yWwf7JbBHgW1+9McePw/Yd0VcKm/aoDqUSdZp1mtQZyF5g/7EtOSRJKWvhvuVCP5
BYz7h3G0V0R1zefY1XIyZxen03HTIjkxpf0OGekCU4yGLaeV2LU88HahycwFAmWL
fFOqKFBBd6QJ9bTaDmjtbDYHuqmJ+jNsLru2T7/He01cC17/LYsaLs3cDmMv3x3w
HADgIdxPVvdtuzm07EpLbCHirc/VBZVwWMeWlP9FYJII5/K+Eds=
=SJ1c
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: