Your message dated Fri, 12 Jul 2024 23:18:06 +0000
with message-id <e1sspwg-009uwv...@fasolo.debian.org>
and subject line Bug#1070492: fixed in mixxx 2.4.0+dfsg-3
has caused the Debian Bug report #1070492,
regarding mixxx: Tries to use the network during build
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 ow...@bugs.debian.org
immediately.)


-- 
1070492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mixxx
Version: 2.4.0+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
          --- LOG END ---
          error: downloading 
'https://github.com/xsco/libdjinterop/archive/refs/tags/0.20.1.tar.gz' failed
          status_code: 6
          status_string: "Couldn't resolve host name"
          log:
          --- LOG BEGIN ---
          Could not resolve host: github.com

  Closing connection



          --- LOG END ---
          error: downloading 
'https://launchpad.net/~xsco/+archive/ubuntu/djinterop/+sourcefiles/libdjinterop/0.20.1-0ubuntu1/libdjinterop_0.20.1.orig.tar.gz'
 failed
          status_code: 6
          status_string: "Couldn't resolve host name"
          log:
          --- LOG BEGIN ---
          Could not resolve host: launchpad.net

  Closing connection



          --- LOG END ---

make[4]: *** [CMakeFiles/libdjinterop.dir/build.make:102: 
libdjinterop-prefix/src/libdjinterop-stamp/libdjinterop-download] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:317: CMakeFiles/libdjinterop.dir/all] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[2]: *** [Makefile:169: all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j2 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:15: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

The build was made using the unshare backend of sbuild, which
does not allow network access.

If you need a full build log, it also fails here for the same reason:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mixxx.html

(X-Debian-Cc: Jochen, as we are tracking all packages which ftbfs with unshare)

Thanks.

--- End Message ---
--- Begin Message ---
Source: mixxx
Source-Version: 2.4.0+dfsg-3
Done: Boyuan Yang <by...@debian.org>

We believe that the bug you reported is fixed in the latest version of
mixxx, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang <by...@debian.org> (supplier of updated mixxx 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 12 Jul 2024 17:10:10 -0400
Source: mixxx
Architecture: source
Version: 2.4.0+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Boyuan Yang <by...@debian.org>
Closes: 1070492
Changes:
 mixxx (2.4.0+dfsg-3) unstable; urgency=high
 .
   * Team upload.
   * debian/patches/0005-Allow-libdjinterop-0.21.0.patch: Add patch to allow
     libdjinterop 0.21.0.
   * debian/control:
     + Add missing build-dependency on libdjinterop-dev. (Closes: #1070492)
     + Remove hardcoded build-dependency on libvamp-*. Use the development
       package vamp-plugin-sdk instead to implicitly pull them in and to
       avoid the t64 library suffix problem.
Checksums-Sha1:
 6459d444795b89ae85c514a7cc0dc61f6ee6e451 3018 mixxx_2.4.0+dfsg-3.dsc
 a136b9cb1c432a3854a3f4c8756ce006a2e378f4 22070072 mixxx_2.4.0+dfsg.orig.tar.xz
 be9297b67ec2135c4a6fdc220f98b11a376be7bd 28244 mixxx_2.4.0+dfsg-3.debian.tar.xz
 7388d37742eeb1c4a963075885fed6053183eae0 18855 
mixxx_2.4.0+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 5592e9161f9f9713b0658f0f0f121177d067857de60285c71e2d2dbd8cd2d390 3018 
mixxx_2.4.0+dfsg-3.dsc
 bd801c824256150ef9c126c2ac95b07ba7f8511261aed5717dabe64922f17759 22070072 
mixxx_2.4.0+dfsg.orig.tar.xz
 b47f228ece9bf737e122bfd51fd03b43363ce1660efb67406128772e2b32fe35 28244 
mixxx_2.4.0+dfsg-3.debian.tar.xz
 784981fb206c0bfaa996ebae6871d968e0309d6ae493e3680bdde5840e4b857c 18855 
mixxx_2.4.0+dfsg-3_amd64.buildinfo
Files:
 b0a9fd4280d8cd4bc107b8702e66e446 3018 sound optional mixxx_2.4.0+dfsg-3.dsc
 735b0e8938e8f307b52d8a65e5340781 22070072 sound optional 
mixxx_2.4.0+dfsg.orig.tar.xz
 d2737332b5aa60f22d8e23df716fed2b 28244 sound optional 
mixxx_2.4.0+dfsg-3.debian.tar.xz
 0ba028639534fddc5eb00ecd329b2127 18855 sound optional 
mixxx_2.4.0+dfsg-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmaRqfEACgkQwpPntGGC
Ws7vfBAAsIguD9BLbn/ax5PWER/1Q/9lWS84KB7ehMZfC3IBzfXzp78VPELA27H2
yUOpdfiJh+JS/SVRfD5wfAUPD+5P6E+Fv+kmCBQ0H8FgjtZqik4IcQzUuozPMKxa
Vb23yjmKQlMPozeJerMXjfLzXutk2ljBzfElS6yDf8ZYaGosUv+WqYHXVpRdbo9B
Me2sMj92up28judth2GHf1o8erBNzWCJilAbriJlSQzhhJ75+2D5653bo2QRVkjs
O/Oevah+ee9YsrHCPtWiYdPTiCSk/OB207N7vnVgOcNOF0PzA6PJHdssaoFpwkbf
MBrDuGh8+sc0VLYFM+E+ny+wETAU5OwOdvOm0KcB1EpePpF/s1IgOwdJTDmqzB72
7kDvXIfyWu8jUIAoUrR/zUVGgYFsyaH9gi1TRiLfu9Y6UaO8YwkuxMR30yysIVVX
sinhKzZenm/t8vNxkhJ9w0IKmrp2FzJxmIJC+BNMnEguOprWrJfK4zjAxXRHviWX
kV82jM/Foe0XBOm8zexUQ5sZAA17F8elzqr0emYBr5TfwkBdIYpJmcogCVMokUk0
Smdb7qZDueddrkutZ1unIPkZLzy8TZLuPFINAmY/sJ6sfvlEHDvF9L23eVEgWgJx
jvXJVLi3Dfc6Jp46onPdEea9dbeB0AWrLG3NLiaVyEMSZ1TlA3A=
=OACP
-----END PGP SIGNATURE-----

Attachment: pgp5pziTlI72g.pgp
Description: PGP signature


--- End Message ---

Reply via email to