Your message dated Sun, 06 Aug 2017 09:03:59 +0000
with message-id <e1dehtb-000go0...@fasolo.debian.org>
and subject line Bug#870887: fixed in python-udatetime 0.0.12-2
has caused the Debian Bug report #870887,
regarding python-udatetime: FTBFS: Invalid RFC3339 date-time string
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.)


-- 
870887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-udatetime
Version: 0.0.12-1
Severity: important
Tags: upstream
Justification: fails to build from source

Builds of python-udatetime for a number of architectures failed, as
excerpted below (modulo some varation in elapsed time) and detailed at
https://buildd.debian.org/status/logs.php?pkg=python-udatetime&ver=0.0.12-1.
Specifically, these failures occurred on armel, armhf, mips, mipsel,
and the non-release architectures hppa, powerpc, ppc64, and sparc64.
I'm not sure offhand why those specific architectures encountered
these errors; I doubt the buildd's native timezone is relevant, since
I see a successful mips64el build at mipsel-manda01 and a failed
mipsel build at mipsel-manda03, which is presumably at the same data
center.

Could you please take a look?

Thanks!

======================================================================
ERROR: test_from_and_to_string (test_udatetime.Test)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/test/test_udatetime.py", 
line 36, in test_from_and_to_string
    dt = udatetime.from_string(rfc3339)
ValueError: Invalid RFC3339 date-time string. Time invalid.

======================================================================
ERROR: test_ok_from_string (test_udatetime.Test)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/test/test_udatetime.py", 
line 156, in test_ok_from_string
    udatetime.from_string(r),
ValueError: Invalid RFC3339 date-time string. Time invalid.

======================================================================
ERROR: test_tzone (test_udatetime.Test)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/test/test_udatetime.py", 
line 162, in test_tzone
    dt = udatetime.from_string(rfc3339)
ValueError: Invalid RFC3339 date-time string. Time invalid.

----------------------------------------------------------------------
Ran 10 tests in 0.022s

FAILED (errors=3)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

--- End Message ---
--- Begin Message ---
Source: python-udatetime
Source-Version: 0.0.12-2

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis <ilias...@debian.org> (supplier of updated python-udatetime 
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: Sun, 06 Aug 2017 11:38:03 +0300
Source: python-udatetime
Binary: python-udatetime python3-udatetime
Architecture: source
Version: 0.0.12-2
Distribution: unstable
Urgency: low
Maintainer: Ilias Tsitsimpis <ilias...@debian.org>
Changed-By: Ilias Tsitsimpis <ilias...@debian.org>
Description:
 python-udatetime - fast RFC3339 compliant date-time library (Python 2)
 python3-udatetime - fast RFC3339 compliant date-time library (Python 3)
Closes: 870887
Changes:
 python-udatetime (0.0.12-2) unstable; urgency=low
 .
   * Patch udatetime to fix an out-of-bounds read.
     This caused random FTBFS on some architectures (Closes: #870887).
Checksums-Sha1:
 b73a0e30ba4f2c34c9d9fe3624340a47d24cc68e 2292 python-udatetime_0.0.12-2.dsc
 e4b37a08e27bf768f9647a239820a7fa7c96db1f 3600 
python-udatetime_0.0.12-2.debian.tar.xz
 4581d70b83421b784fc41d5b98693f04e4092e47 7823 
python-udatetime_0.0.12-2_amd64.buildinfo
Checksums-Sha256:
 8017601cc08ccc54c2a5a339ff173bd3be201db1d51ca06ba189de8f7c227854 2292 
python-udatetime_0.0.12-2.dsc
 c42050d898b89871d0053c37c6f9fb09169c9c11e1a42adde99e9fb019a81a5b 3600 
python-udatetime_0.0.12-2.debian.tar.xz
 2ad08910d3b96d804cf13e825c81ec6d95d492ceeb2ae2851a30d35aad6c2984 7823 
python-udatetime_0.0.12-2_amd64.buildinfo
Files:
 369d304d7873c3856a6f4b433e427258 2292 python optional 
python-udatetime_0.0.12-2.dsc
 637ce1f040597e44cb2039789c529264 3600 python optional 
python-udatetime_0.0.12-2.debian.tar.xz
 a4d46782b15c9076e870d68235a82474 7823 python optional 
python-udatetime_0.0.12-2_amd64.buildinfo

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

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlmG2OUUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDzk9BAAuetFFqccjW2YfJNxTWEkWxDsV+5z
bIdkBjzjl6JOxFbFp6XhiakCDSewKsHoBdfNaGAW2DBYw9bY8MYZdGk9e9ML4TVd
yTZFF8iyiyXQ7nExqpYNJif+hLYSnsNgA8qIP16knxrocjGU9h7sm5JGqzpLS7B7
hM8G0YzBjF/k09bH23sdYPfU37QU7wKsXlgCzIod7c7vkuju8oSKXmA0RTrYktms
Dm8j/suyifRpi9/U5BQMAauo0bI+xU31km3IDreZ7Ci5yABoyLAFMCmRvbA0OdJ+
vE8GFUPl89HdzZ5siRVxOmTN8LHlcT7DhJjjWX4s4mV5BeGWXHJez0cKbVL1WLtK
NL3NaAl/rusEvethEzjv/MtltLGg/iHm9NPT3MedVBjavDPJyf79g4h9n/QezsWj
reNsS9zh4OOs3l6sJftyAqmGljW/W24RBfyYD4lXopuxE8zXjoTsVRxMgXVpUTTp
ByJmSw3GreDU4hJ0djwC2zDEszj6j8FGN1RCm9V3A8Do4Ds8vaaNmCIvRFczP0Sh
HsXdQOYUY8LkjKP4PuhGi649wsBAR6u8LdsYUe7CzFa7tnI7+N6orHkw1RcToWQ6
Z+sSStLuO4xQvpgRtPwrJJrvDwp0Y3rWTyRXT5PSzwkRtprs2l+/LvWDcZo0sUBn
D+aNKfZ8u5xJ+PQ=
=QHzM
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to