Your message dated Mon, 21 Oct 2024 10:19:23 +0000
with message-id <e1t2pvt-003oh4...@fasolo.debian.org>
and subject line Bug#1085611: fixed in m2crypto 0.42.0-2
has caused the Debian Bug report #1085611,
regarding m2crypto: FTBFS on armel and armhf (and hppa, hurd-i386, powerpc and 
x32)
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.)


-- 
1085611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: m2crypto
Version: 0.42.0-1
Severity: serious
Tags: ftbfs patch pending
Justification: ftbfs

Hi,

As hinted at in bug 1082422, m2crypto fails to build on armel and armhf. I've hunted it down to a refreshed patch that dropped a 64-bit time_t part for non-i386 [1].

I'll upload the attached NMU to DELAYED/10 shortly (adding the bug number).

Paul

https://salsa.debian.org/python-team/packages/m2crypto/-/commit/7f86ac049121f798d9ecc2a6df1b0f498e831c9c#caa888e864d322d64f070a08057f61b5626c2e13
diff -Nru m2crypto-0.42.0/debian/changelog m2crypto-0.42.0/debian/changelog
--- m2crypto-0.42.0/debian/changelog    2024-08-20 18:06:43.000000000 +0200
+++ m2crypto-0.42.0/debian/changelog    2024-10-20 22:02:01.000000000 +0200
@@ -1,3 +1,10 @@
+m2crypto (0.42.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * fix-ssl-timeout-for-t64.patch: reinstate qq in pack()
+
+ -- Paul Gevers <elb...@debian.org>  Sun, 20 Oct 2024 22:02:01 +0200
+
 m2crypto (0.42.0-1) unstable; urgency=medium
 
   * Team upload
diff -Nru m2crypto-0.42.0/debian/patches/fix-ssl-timeout-for-t64.patch 
m2crypto-0.42.0/debian/patches/fix-ssl-timeout-for-t64.patch
--- m2crypto-0.42.0/debian/patches/fix-ssl-timeout-for-t64.patch        
2024-08-20 18:06:43.000000000 +0200
+++ m2crypto-0.42.0/debian/patches/fix-ssl-timeout-for-t64.patch        
2024-10-20 22:02:01.000000000 +0200
@@ -14,7 +14,22 @@
  
  from M2Crypto.util import is_32bit, is_libc_musl
  
-@@ -43,7 +44,10 @@
+@@ -27,10 +28,12 @@
+             millisec = int(self.sec * 1000 + round(float(self.microsec) / 
1000))
+             binstr = struct.pack('l', millisec)
+         else:
+-            if is_32bit() and not is_libc_musl():
++            if platform.machine() in ["i386", "i686"] and not is_libc_musl():
+                 binstr = struct.pack('ii', self.sec, self.microsec)
+-            else:
++            elif platform.machine() in ["i386", "i686"]:
+                 binstr = struct.pack('ll', self.sec, self.microsec)
++            else:
++                binstr = struct.pack('qq', self.sec, self.microsec)
+         return binstr
+ 
+ 
+@@ -43,7 +46,10 @@
          sec = int(millisec / 1000)
          microsec = (millisec % 1000) * 1000
      else:
@@ -26,7 +41,7 @@
      return timeout(sec, microsec)
  
  
-@@ -52,4 +56,7 @@
+@@ -52,4 +58,7 @@
      if sys.platform == 'win32':
          return struct.calcsize('l')
      else:

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: m2crypto
Source-Version: 0.42.0-2
Done: Santiago Vila <sanv...@debian.org>

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

Debian distribution maintenance software
pp.
Santiago Vila <sanv...@debian.org> (supplier of updated m2crypto 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: Mon, 21 Oct 2024 11:42:00 +0200
Source: m2crypto
Architecture: source
Version: 0.42.0-2
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>,
Changed-By: Santiago Vila <sanv...@debian.org>
Closes: 1085589 1085611
Changes:
 m2crypto (0.42.0-2) unstable; urgency=high
 .
   * Team upload.
   [ Paul Gevers ]
   * fix-ssl-timeout-for-t64.patch: reinstate qq in pack().
     Fixes FTBFS on several archs. Closes: #1085611, #1085589.
Checksums-Sha1:
 ef36360d32d2162f8dfef2225f3593159f3ff884 2025 m2crypto_0.42.0-2.dsc
 8e71764373f6af70d05e19db9da3d3ff9893c5e9 59992 m2crypto_0.42.0-2.debian.tar.xz
 eafc179d3f50505af87517459dd0263ef4247dd4 7746 
m2crypto_0.42.0-2_source.buildinfo
Checksums-Sha256:
 c2401ad5804b08131ffb4d4e91d8f39223229ce0f11995e74e66a1f35f533443 2025 
m2crypto_0.42.0-2.dsc
 b8e48db90ad6ae5d78e61e9f8e0ef7aede7e0d5b0eb1586d296d06fb5ea973ce 59992 
m2crypto_0.42.0-2.debian.tar.xz
 bdf47eb5467b8dc2bc9e4b66b27aa70fff948297e68e52e0183612716b40e953 7746 
m2crypto_0.42.0-2_source.buildinfo
Files:
 978716dfae655722249c9ef670ecd160 2025 python optional m2crypto_0.42.0-2.dsc
 bb12ccf596ce4a6db4d54c34e55d02db 59992 python optional 
m2crypto_0.42.0-2.debian.tar.xz
 5657a0f3db3c414f00d723fd9dfd5db8 7746 python optional 
m2crypto_0.42.0-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmcWJqEACgkQQc5/C58b
izL48gf+JxhCIPZ56pVCLCB4V7VgNT1P9lmFC3QFIBGoj11kA5r+a/snU2X6F7XM
unLKpwEjKyK8bUp5wkVfJGyzJhOQ7p+Ok1J3VBgUqK+q1p2eRE3Y6XIaz+iPGI0E
ZrE1gd17GtFvLhKfvnpA7hmrYbAuUHn5/79kUWyMtOpw5MsZbXObw7Qqr3QRIa4S
FoL+k1vp+VsVN5PVOVmAX5w1OF3fEpH9qsG44HrU2DOowt1U/8IIzH83S4EfxL7t
LfkUFnpgVUEeyrn2QyNEgjfveGCRbazzL9xzzsVqXK1obaHbtx2I1lQI7E5Sk3Pb
Ug0OG2a/Jvh7qHOpjx08qrEBd5r9Qw==
=1sYk
-----END PGP SIGNATURE-----

Attachment: pgppny2iMQ7wD.pgp
Description: PGP signature


--- End Message ---

Reply via email to