Your message dated Wed, 22 Jan 2025 08:46:04 +0000
with message-id <[email protected]>
and subject line Bug#1068223: fixed in cyrus-imapd 3.10.1-1
has caused the Debian Bug report #1068223,
regarding cyrus-imapd - FTBFS on 32-bit non-i386 architectures
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.)


-- 
1068223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068223
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cyrus-imapd
Version: 3.8.2-1
Severity: serious
User: [email protected]
Usertag: time-t

cyrus-imapd is failing to build on the architectures affected by the
time_t transition (armel, armhf, several debian-ports architectures)
with the following error.

unit: fatal(Internal error: assertion failed: cunit/timeofday.c: 113: 
tv.tv_usec != 0xffffffff)
A quick look at the code, suggests that the testsuite is trying to
intercept gettimeofday, and this interception is broken by the
time64 changes.

The specific error appears to be cause by calling
the non-time64 gettimeofday function from glibc with the time64
definition of struct timeval, but I suspect there are other issues
with the interception code that will rear their ugly head if that one
is fixed.



--- End Message ---
--- Begin Message ---
Source: cyrus-imapd
Source-Version: 3.10.1-1
Done: Xavier Guimard <[email protected]>

We believe that the bug you reported is fixed in the latest version of
cyrus-imapd, 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.
Xavier Guimard <[email protected]> (supplier of updated cyrus-imapd 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, 22 Jan 2025 07:38:54 +0100
Source: cyrus-imapd
Architecture: source
Version: 3.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cyrus Team <[email protected]>
Changed-By: Xavier Guimard <[email protected]>
Closes: 1068223
Changes:
 cyrus-imapd (3.10.1-1) unstable; urgency=medium
 .
   * New upstream version 3.10.1
   * Restrict architecture list to supported platforms (Closes: #1068223)
   * Update copyright
Checksums-Sha1: 
 e65211546f647d8096a2a46a937f7cc38037b085 5881 cyrus-imapd_3.10.1-1.dsc
 3b1c154151c6328bfdb3861770516645ed55f1b6 7733856 cyrus-imapd_3.10.1.orig.tar.xz
 d21403e19df8d12d5de6e8267a49a7e4783a179e 87112 
cyrus-imapd_3.10.1-1.debian.tar.xz
Checksums-Sha256: 
 1ba33f6db6343e5ed150b6c7ee17b06b71c3967dc1d3f6ac534f0e8953dbac71 5881 
cyrus-imapd_3.10.1-1.dsc
 02706a7ad09537e0dff8dfdda0eb6c6e6007b82e8264eddd1bcc43b0014ee492 7733856 
cyrus-imapd_3.10.1.orig.tar.xz
 351c90231bb0766ec4fe6d0b82dfb89b326fbb2e58c183b98aa09ce74f927ae9 87112 
cyrus-imapd_3.10.1-1.debian.tar.xz
Files: 
 8cdfc5749af8d81416bf0ac84e6e5b5b 5881 mail optional cyrus-imapd_3.10.1-1.dsc
 1d0d90c376d9302f4419e14a2c89c809 7733856 mail optional 
cyrus-imapd_3.10.1.orig.tar.xz
 378a4e1d19e4c4e627ece9664fddf9cc 87112 mail optional 
cyrus-imapd_3.10.1-1.debian.tar.xz

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

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmeQk74ACgkQ9tdMp8mZ
7ukIwA//dqbuwlpOqA+UpwEPr09ff9rz3EAXOgPMuBoQUIWMd1aIqfc0egzSZUKc
GFWR5m25i1eqxHBxxUGrK4iHbcnmDYFzbemX3emylyFrrL5tGCDCLCe6nGBOF/9L
bB/nUYsOk5DvDtgmsWadrqg43f82OJHq/RI6cl/QaPFMqi8oS42h/+CmR61kqoYz
v+KwLv23XNKw5Nyof8ZK7wT7PkPE+ctqD62kXVIsR8IHvoNXTXsxyZEWamBHbZEQ
vEs6mZO7brSTclRjMYWdgcZeLM4kWyikhE1bywGx3+hm7fEulPhIn8Y3TFTSJvC4
lbOYZzEQ4LcANupXaGwwo2M/igzzPZ5bZI0MzPMHsFCkdNg+6odgQUEU/gQ4oRlT
fj+fMlBGDJspTgWEQkpKQqhHCgc+6Rg4j2E7nqOPtaktMOyFz702JjMXQuhVBxd9
q5sM6SVVYTmMacSAzn37190rbWfZUGQMsKqrQK9OYGkX5+nQ/E3j3Fd25nPY2siY
VFUh0AeS8n0TTUgvYzKGkztxHV8dVpAOfEa7u9QsZFkX/gLwe1RZbtp8CrWjqM6E
8nL0zDgllknJDviPBbNbjJDyNTKBXb5O6EDpIlFsKqoFKeYQjuVAzAbJHiPjmG+x
3dQo4hOzy54m2suXeRaWyKgkdmo2bVMqoe9QDpbmEM6/hx1Fu8c=
=dGTm
-----END PGP SIGNATURE-----

Attachment: pgpC_0vCnTwPR.pgp
Description: PGP signature


--- End Message ---

Reply via email to