[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#941710: marked as done (lilv FTCBFS: Build-Depends: python not installable)

Your message dated Sun, 24 Jan 2021 20:24:11 +0000
with message-id <E1l3lvf-000CLm-Sh@fasolo.debian.org>
and subject line Bug#941710: fixed in lilv 0.24.12-2
has caused the Debian Bug report #941710,
regarding lilv FTCBFS: Build-Depends: python not installable
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.)


-- 
941710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941710
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: lilv
Version: 0.24.4~dfsg0-1
Tags: patch
User: debian-cross@lists.debian.org
Usertags: cross-satisfiability ftcbfs

lilv fails to cross build from source, because its build dependency on
(the host architecture) python is not installable. Indeed, it wants
python for the build architecture to run. Beyond that, one should export
CC and PKGCONFIG to tell waf what we are compiling for. Please consider
applying the attached patch.

Helmut

diff --minimal -Nru lilv-0.24.4~dfsg0/debian/changelog lilv-0.24.4~dfsg0/debian/changelog
--- lilv-0.24.4~dfsg0/debian/changelog	2019-08-22 12:00:49.000000000 +0200
+++ lilv-0.24.4~dfsg0/debian/changelog	2019-10-04 04:55:13.000000000 +0200
@@ -1,3 +1,12 @@
+lilv (0.24.4~dfsg0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
+    + Annotate Build-Depends: python with :native.
+    + Export suitable cross environment from dpkg's buildtools.mk.
+
+ -- Helmut Grohne <helmut@subdivi.de>  Fri, 04 Oct 2019 04:55:13 +0200
+
 lilv (0.24.4~dfsg0-1) unstable; urgency=medium
 
   * Team upload.
diff --minimal -Nru lilv-0.24.4~dfsg0/debian/control lilv-0.24.4~dfsg0/debian/control
--- lilv-0.24.4~dfsg0/debian/control	2019-08-22 12:00:49.000000000 +0200
+++ lilv-0.24.4~dfsg0/debian/control	2019-10-04 04:55:12.000000000 +0200
@@ -14,7 +14,7 @@
  libsratom-dev (>= 0.4.0~),
  lv2-dev (>= 1.14.0~),
  pkg-config,
- python
+ python:native
 Standards-Version: 4.4.0
 Homepage: https://drobilla.net/software/lilv/
 Vcs-Git: https://salsa.debian.org/multimedia-team/lilv.git
diff --minimal -Nru lilv-0.24.4~dfsg0/debian/rules lilv-0.24.4~dfsg0/debian/rules
--- lilv-0.24.4~dfsg0/debian/rules	2019-08-22 12:00:49.000000000 +0200
+++ lilv-0.24.4~dfsg0/debian/rules	2019-10-04 04:55:13.000000000 +0200
@@ -1,9 +1,12 @@
 #!/usr/bin/make -f
 
 include /usr/share/dpkg/architecture.mk
+include /usr/share/dpkg/buildtools.mk
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
+export CC
+export PKGCONFIG = $(PKG_CONFIG)
 export LINKFLAGS += $(LDFLAGS)
 
 WAF = ./waf

--- End Message ---
--- Begin Message --- 
Source: lilv
Source-Version: 0.24.12-2
Done: Dennis Braun <d_braun@kabelmail.de>

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

Debian distribution maintenance software
pp.
Dennis Braun <d_braun@kabelmail.de> (supplier of updated lilv 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: Sun, 24 Jan 2021 20:44:49 +0100
Source: lilv
Architecture: source
Version: 0.24.12-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Dennis Braun <d_braun@kabelmail.de>
Closes: 941710
Changes:
 lilv (0.24.12-2) unstable; urgency=medium
 .
   * d/control: Fix really FTCBFS, with python3:native as B-D (Closes: #941710)
   * Add d/lilv-utils.lintian-overrides
Checksums-Sha1:
 9659293b7b088f7553555754471a314cf9eca59a 2530 lilv_0.24.12-2.dsc
 0c231784205539124967b6af79d882e824308302 13128 lilv_0.24.12-2.debian.tar.xz
 20388d2f83bd96172b74a1778b4414942ff41817 5978 lilv_0.24.12-2_source.buildinfo
Checksums-Sha256:
 7fbca30f650a070269c90b97a6b3a896f9b598fa236809ee0f67d055f17f232f 2530 lilv_0.24.12-2.dsc
 5e1f3a3c292c9c7c7e19ac243ca57beab88323b9b9befd6b671665f0d479d211 13128 lilv_0.24.12-2.debian.tar.xz
 4b4b37c6c03f8ad14bb0a7f3216e15b7104129eebbe6cb784097c94ddcc007a0 5978 lilv_0.24.12-2_source.buildinfo
Files:
 f81d9cc8618fbe3166ef37ea0c905ce5 2530 libs optional lilv_0.24.12-2.dsc
 f3d17583b26821083867513a19886879 13128 libs optional lilv_0.24.12-2.debian.tar.xz
 60f40595b9001e667820a807f9738eef 5978 libs optional lilv_0.24.12-2_source.buildinfo

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

iQJJBAEBCgAzFiEEPLfDAq+1fmGoxhfdY06lXZArmDYFAmANz34VHGRfYnJhdW5A
a2FiZWxtYWlsLmRlAAoJEGNOpV2QK5g2mNgP/3iWDtbgq6vScOzORLMR5qRr1+Cu
2LFCxSaVUT1HAms19/Zul+VlQ2v4OYpHYXYCbgebojrdD06gmsHFHIzRUOTBXWD4
fA6HnurvSfR7jzyp4rJVzUlmOyjNi9j2SSFRjU1J/o/9HcMpSyym1ozjPxm9cEwu
SAGGPpbeeouCAGUiy8NnY6C7IFqxFYOxPSuSIdTgxpJKvH52hw3PbLSnE6rj7iy4
FUol0n7R3yOO4TwZ7sfhMtPGZJezEsGezwos1I6FTtC0NoWkMxaVP5ISNxWlfHNp
zj9wSP4fs675CDMJC6roryLabzseZa3iXI4/BKUyw4GVpyDHwKi6mLrlHNX5slUk
JfY2RVEruSMVM8n1VXwlq2Qlp/cLCGNT1X3f7ov6RO7s5pQsXTNbXIIF9f6YYFND
sLLoaGXt0lknThR3aM0hPL/olOq8MZL5mT+ZOKkBzfH6E5Rx1cqVOepsXqxUTJkU
fo/MMNOK9DKt0MGE2mhZAFIFJ/nCK9sm7y2Yq9KADIkldzYh7wcRBcErFOLM6eB7
5ySs9DL8/oQlYwdc1o82y/F0VMkbHbFLg0W4gjjnD9587azYVH0kxh+PHNHG+wiM
EM2gmcJgjaUrPr/dp0sdMqpYmGhZHXAWhr1WV0f4trD92Od5GH9+0n2Q9LtPquDp
O0dgy0g+6PT2y5ON
=gGeW
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: