Your message dated Wed, 09 Aug 2023 15:53:29 +0000
with message-id <[email protected]>
and subject line Bug#930343: fixed in libgcr410 2.4.0-10
has caused the Debian Bug report #930343,
regarding libgcr410 FTCBFS: uses the wrong compiler
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.)


-- 
930343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930343
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libgcr410
Version: 2.4.0-9.2
Tags: patch
User: [email protected]
Usertags: ftcbfs

libgcr410 fails to cross build from source, because it does not pass
cross tools to make. The easiest way of doing so - using dh_auto_build -
makes libgcr410 cross buildable. Please consider applying the attached
patch.

Helmut
diff -u libgcr410-2.4.0/debian/changelog libgcr410-2.4.0/debian/changelog
--- libgcr410-2.4.0/debian/changelog
+++ libgcr410-2.4.0/debian/changelog
@@ -1,3 +1,10 @@
+libgcr410 (2.4.0-9.3) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne <[email protected]>  Tue, 11 Jun 2019 06:10:48 +0200
+
 libgcr410 (2.4.0-9.2) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u libgcr410-2.4.0/debian/rules libgcr410-2.4.0/debian/rules
--- libgcr410-2.4.0/debian/rules
+++ libgcr410-2.4.0/debian/rules
@@ -3,7 +3,7 @@
 build: build-stamp
 build-stamp: 
        dh_testdir
-       $(MAKE)
+       dh_auto_build
        touch build-stamp
 
 clean:

--- End Message ---
--- Begin Message ---
Source: libgcr410
Source-Version: 2.4.0-10
Done: Bastian Germann <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libgcr410, 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 libgcr410 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: Wed, 09 Aug 2023 17:31:04 +0200
Source: libgcr410
Architecture: source
Version: 2.4.0-10
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 930343
Changes:
 libgcr410 (2.4.0-10) unstable; urgency=medium
 .
   * QA upload.
   * Convert to source format 3.0.
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Let dh_auto_build pass cross tools to make.  Closes: #930343
Checksums-Sha1:
 53320b731fd28dea24635afae4f06abf25c4a67e 1571 libgcr410_2.4.0-10.dsc
 17c30c642170be61fbe6624e678f7ccc8678c79d 10660 libgcr410_2.4.0-10.debian.tar.xz
 3e286fbe89ddb082120e8091737eaa9908ef1232 5474 
libgcr410_2.4.0-10_source.buildinfo
Checksums-Sha256:
 9321310eca12ef852e6cb1d6bb5298b49742a5fc95f4d7d1fac9c4cbc42d9ab1 1571 
libgcr410_2.4.0-10.dsc
 06f7514af1db6d13e4f9cdd24040e10378479913335e4850fa8ec75a0a84fc6f 10660 
libgcr410_2.4.0-10.debian.tar.xz
 d48aa7ba607d4b31e96dc53895befd37e38ceb2bfc5b3fe9df53c05b83376d82 5474 
libgcr410_2.4.0-10_source.buildinfo
Files:
 00b19c1b9d014fd71f5beb0ce766285e 1571 misc optional libgcr410_2.4.0-10.dsc
 6c2f499668c79c327071ed92ceb7854f 10660 misc optional 
libgcr410_2.4.0-10.debian.tar.xz
 4e4761daaec62b78b2f83067cbfeb5ce 5474 misc optional 
libgcr410_2.4.0-10_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTTsjUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFHprDACsiWiRdz5DKtaKWd9N4F83sdrBXoK8Z0Yp
Oi7qivPZ9paqwM5rNV1pMit7gLLRqlcAdGKvk1XAzqEIe+pvgxdWe66BE/GWcWGd
ch18jUAtHFN4e8ItDhZetbTs9vhIjK1hERG0MU+LjRuMmlcicbGtJIpR0R6ChqTt
92JKIZjSUC6z4TQ1YuXnzbuESJ3S69lKsoq7vlUzRnV3OOrhDat8oStZMTkM/Leh
lz/gF00Ppu0/wICjPQ9XNnoJqyvPscPF+jF+6MnHgaNa+jHJ17X0Y+K7P+Fqqvbr
qDBZvWbjZdcoZi9D57XLixyi9Zum20LywZygDsHhK2j/OGSbZA7I3tZyxguqIuE9
UfYtlYhy/KM35zQOs9Cl4H9QiUMfNcM2Zwin2UkkQ50nWSmCDMjCUaR3EJwT4doa
RWVnQ4EeALMzboPTXJGK7NhU22PtAQfr34AL8zySPgKmxFEs3Txoqj+HE6ARlYPo
X67CbocFbsnziFnaHhJObFkCPNKtUVM=
=Npwp
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to