Your message dated Tue, 29 Nov 2022 22:06:32 +0000
with message-id <[email protected]>
and subject line Bug#915280: fixed in geki3 1.0.3-9
has caused the Debian Bug report #915280,
regarding geki3 FTCBFS: does not pass --host to ./configure
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 [email protected]
immediately.)
--
915280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915280
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: geki3
Version: 1.0.3-8.1
Tags: patch
User: [email protected]
Usertags: rebootstrap
geki3 fails to cross build from source, because it does not pass --host
to ./configure. The easiest way of fixing that is using
dh_auto_configure and that is sufficient to make geki3 cross buildable.
Please consider applying the attached patch.
Helmut
diff -u geki3-1.0.3/debian/changelog geki3-1.0.3/debian/changelog
--- geki3-1.0.3/debian/changelog
+++ geki3-1.0.3/debian/changelog
@@ -1,3 +1,10 @@
+geki3 (1.0.3-8.2) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne <[email protected]> Sun, 02 Dec 2018 12:13:58 +0100
+
geki3 (1.0.3-8.1) unstable; urgency=medium
* Non-maintainer upload
diff -u geki3-1.0.3/debian/rules geki3-1.0.3/debian/rules
--- geki3-1.0.3/debian/rules
+++ geki3-1.0.3/debian/rules
@@ -16,8 +16,7 @@
&& touch configure \
&& touch config.h.in \
&& touch `find . -name Makefile.in`
- ./configure --prefix=/usr --mandir=$${prefix}/share/man \
- --infodir=$${prefix}/share/info
+ dh_auto_configure
$(MAKE)
touch build-stamp
--- End Message ---
--- Begin Message ---
Source: geki3
Source-Version: 1.0.3-9
Done: Bastian Germann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
geki3, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann <[email protected]> (supplier of updated geki3 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 29 Nov 2022 22:33:48 +0100
Source: geki3
Architecture: source
Version: 1.0.3-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 915280 1007570
Changes:
geki3 (1.0.3-9) unstable; urgency=medium
.
* Team upload.
* Convert to 3.0 source format. Closes: #1007570
.
[ Helmut Grohne ]
* Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. Closes:
#915280
Checksums-Sha1:
421ffd2c5f68b8ddda9d02d82b691d6833d51592 1601 geki3_1.0.3-9.dsc
f4b4818e5044646433fff9024de7a1fb2236855c 71452 geki3_1.0.3-9.debian.tar.xz
3e982e5fb73cbf9265ce3bca5adc3cabf08c376f 5971 geki3_1.0.3-9_source.buildinfo
Checksums-Sha256:
60bbd724cebab0c729c1d9e04e5604e22677624202aa03e964688c985851547e 1601
geki3_1.0.3-9.dsc
2b1e788409576a707d783f539d56075863346caaa444de1336ff74b95d41dfbb 71452
geki3_1.0.3-9.debian.tar.xz
77473c2d0f1787d063cf50b77ad87f86bc485b843ecb36c33888945ea1e86889 5971
geki3_1.0.3-9_source.buildinfo
Files:
b4b3d91699e298dbf2421b26f881eef5 1601 games optional geki3_1.0.3-9.dsc
1cd5e725f91cc66ab1d10cb90991ef6b 71452 games optional
geki3_1.0.3-9.debian.tar.xz
23213eb70c2b8a712df7dfca49a15387 5971 games optional
geki3_1.0.3-9_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmOGfAgQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFK4FC/9IsWMSJLSvLaWRFvjDmWCKVA/R4FXWG6Y+
ew6Pys2ZvRD7WVup+m4w0Ybin4TRHYveOfqZ26AItxwfCtbHZRRdpAVqXYWPFJGy
1KGgcHJ1mi374SkBLx6hTRkp88uR/7MpJtojZOrpyxgOfyL4uq29d5xuGc0p0us9
CMMdiEq2SATSwiPC/JWETC4YKufNliYboh6QdrANFIdA0p31tyVD2/I8s8hjHvfQ
e8aTH6ymz7f4U8/FEFlytA3ll2Xzl6PofPgyMgqIqE2FR5wXA7EfzkdyBaM64O2c
YPXClc7eHxwvt/TV77RNqb0ptbg0pXUJqLIylBr9LpwkG09lzEZFy08RWiBMdhPF
qguNcnLD8mMHUgHhXV5EZ1kVPQbV5Kz+gf0/aah8qUsyxC0X7ld8veDhqV2lv2mH
4FfbcEzzZ+VyuimvQ3ZNAoMysFSPsqiGcTqqjdDKY+dLMDoruPE4K8TV4n5RT7oD
f8EeZxDmTN8vD9Cs37dkQk/UqCgntNI=
=cXmq
-----END PGP SIGNATURE-----
--- End Message ---
