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

Bug#1108111: marked as done (libpyzy FTCBFS: cannot install a host architecture python interpreter)

Your message dated Sat, 13 Sep 2025 16:34:33 +0000
with message-id <E1uxTCr-003TP7-2j@fasolo.debian.org>
and subject line Bug#1108111: fixed in libpyzy 1.0.1-9
has caused the Debian Bug report #1108111,
regarding libpyzy FTCBFS: cannot install a host architecture python interpreter
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.)


-- 
1108111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108111
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libpyzy
Version: 1.0.1-8
Tags: patch
User: debian-cross@lists.debian.org
Usertags: cross-satisfiability

libpyzy cannot be cross built from source, because it build depends on a
host architecture Python interpreter. It actually wants to run Python
during build rather than install a Python extension, so what it actually
needs is a native Python interpreter. I'm proposing the attached patch
for inclusion in forky.

Helmut

diff --minimal -Nru libpyzy-1.0.1/debian/changelog libpyzy-1.0.1/debian/changelog
--- libpyzy-1.0.1/debian/changelog	2022-03-13 18:33:27.000000000 +0100
+++ libpyzy-1.0.1/debian/changelog	2025-06-20 10:08:19.000000000 +0200
@@ -1,3 +1,10 @@
+libpyzy (1.0.1-8.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Build with a native python3. (Closes: #-1)
+
+ -- Helmut Grohne <helmut@subdivi.de>  Fri, 20 Jun 2025 10:08:19 +0200
+
 libpyzy (1.0.1-8) unstable; urgency=medium
 
   * Team upload.
diff --minimal -Nru libpyzy-1.0.1/debian/control libpyzy-1.0.1/debian/control
--- libpyzy-1.0.1/debian/control	2022-03-13 18:29:55.000000000 +0100
+++ libpyzy-1.0.1/debian/control	2025-06-20 10:08:17.000000000 +0200
@@ -10,7 +10,7 @@
  debhelper-compat (= 13),
  libglib2.0-dev,
  libsqlite3-dev,
- python3,
+ python3:native,
  sqlite3,
  uuid-dev,
 Standards-Version: 4.6.0

--- End Message ---
--- Begin Message --- 
Source: libpyzy
Source-Version: 1.0.1-9
Done: Boyuan Yang <byang@debian.org>

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

Debian distribution maintenance software
pp.
Boyuan Yang <byang@debian.org> (supplier of updated libpyzy 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: Sat, 13 Sep 2025 11:14:03 -0400
Source: libpyzy
Architecture: source
Version: 1.0.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Changed-By: Boyuan Yang <byang@debian.org>
Closes: 1046348 1108111
Changes:
 libpyzy (1.0.1-9) unstable; urgency=medium
 .
   * Team upload.
   * Bump Standards-Version to 4.7.2.
   * debian/control: Move package description to the source package section.
   * debian/clean: Also clean up __pycache__ directory. (Closes: #1046348)
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Build with a native python3. (Closes: #1108111)
Checksums-Sha1:
 db88548b7c1ae781544794dd50365d1b0ca4359a 2517 libpyzy_1.0.1-9.dsc
 e38a148a772e9909facda66b2d579e17b94cccbe 9977983 libpyzy_1.0.1.orig-db.tar.bz2
 b67854e02e1d83197a58a5d54b7f03d6f19d9d4d 752300 libpyzy_1.0.1.orig.tar.xz
 ca96c23204ed9c0d56d98a3bc48bf9f637e97fc3 8696 libpyzy_1.0.1-9.debian.tar.xz
 c8bd27ff8cbcd3a3b1eb081fec3fefd706f9f9b6 7483 libpyzy_1.0.1-9_amd64.buildinfo
Checksums-Sha256:
 01ebba524a8557bde1e8520da8cbf00f62e6e6159efd85bbe609b5decca24f17 2517 libpyzy_1.0.1-9.dsc
 32c7d07b9f41e1dfc0f9008f54eca8e6cb367e7f2b19ac94c49754442694c321 9977983 libpyzy_1.0.1.orig-db.tar.bz2
 9533518eceb6d757079754352e6dd25e3b8ddea3934da97d6ae9b9da82f80582 752300 libpyzy_1.0.1.orig.tar.xz
 56edb1e0785b2258695af6bb1c29cba2caf25ee8ac31d5f528fe4f8f8e1971d4 8696 libpyzy_1.0.1-9.debian.tar.xz
 e250dcd6abc0389af938d97295d3ca2f081b5d15795801a3d826cdcabdca70cf 7483 libpyzy_1.0.1-9_amd64.buildinfo
Files:
 31538cd1cceaad6b07cf0f1b1021d0b5 2517 libs optional libpyzy_1.0.1-9.dsc
 d0951b8daa7f56a2cbd3b6b4e42532e0 9977983 libs optional libpyzy_1.0.1.orig-db.tar.bz2
 17d662cc3911a8480e82749437a551db 752300 libs optional libpyzy_1.0.1.orig.tar.xz
 4ce1aceab4b3788146bb90261bf3ca98 8696 libs optional libpyzy_1.0.1-9.debian.tar.xz
 f65030b18f351ec120a19b17bbfc2d1d 7483 libs optional libpyzy_1.0.1-9_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmjFi6IACgkQwpPntGGC
Ws4dlg//atbBoV59/JE0UN63had+6R8cLKzG26x2XjE14z1VZuimU24Di+26eOCQ
TtsmOqWfLrY69FQ9Xlx2NKWNX15Qi48ye/s4KnTTGPYupJYrlUDTfT7ald8AXGLR
BJ9a4UaBZVkud8cGXca3neYYD7aiOWiO9apCJYwsPZ4zp6vNCM7O4/8x76FPuzQl
aGjE/y97Yr9vRZDpDMF7b5kCBW4DLe8aOnaSmh0h+P2t2CNC1VwEi83yoMSqTa03
RA2VUDSP5t/Px/Zw5sK7BxXBhmq9GasD0T2uZiY1gg6RKys4OHgBYCztOj7SUAun
xwARM9bMCW2syKp8j+wPDE+jucyzoZjRfcvgJWMTe2GeJdnvJT2oeWjdcHXIGjjV
a+OjbKVQ8vWoWlwN42Burw7tDZhjOPxf54Te2nUVNhmaXHYoigRgxYmFnGrsLWlA
RlDMRatkEwFkTsaiOB8DFV2E+82HoC72VmmZtUL+uCO28+4iFRkdgN5r1Jy7KjQt
ewIgLS9ZR+zkaUBRxWHrC0wPAJiaYfBU7mcz7HwET3b2GwhtgWvYedP3aurmFCyR
U27NaFFa5y8XomP2dpo8Dmerstd6tkWwGLo1tU3VFYsdNm9l89NPN2zGFDQS7DRW
U7Jk42SmfelTY1xrRbtNyYH42KO/Z4xJkJSQpOxu/gAvYHHEMTI=
=qjlF
-----END PGP SIGNATURE-----

Attachment: pgpAr5BexPISs.pgp
Description: PGP signature


--- End Message ---
Reply to: