Your message dated Tue, 20 Feb 2024 10:34:29 +0000
with message-id <e1rcnsh-0000hq...@fasolo.debian.org>
and subject line Bug#1044054: fixed in dyda 1.41.1-2
has caused the Debian Bug report #1044054,
regarding dyda: test failure with pandas 2.0
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.)
--
1044054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dyda
Version: 1.41.1-1.1
Control: block 1043240 by -1
dyda fails its autopkgtest with pandas 2.0, currently in experimental.
Log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dyda/36575804/log.gz
A common source of failures is that pandas.util.testing has been renamed
to pandas.testing. Both names were available in all 1.x versions (and
hence in Debian stable and oldstable), so Debian packages that were
using this can immediately switch unconditionally.
--- End Message ---
--- Begin Message ---
Source: dyda
Source-Version: 1.41.1-2
Done: Andreas Tille <ti...@debian.org>
We believe that the bug you reported is fixed in the latest version of
dyda, 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 1044...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille <ti...@debian.org> (supplier of updated dyda 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: Tue, 20 Feb 2024 11:14:50 +0100
Source: dyda
Architecture: source
Version: 1.41.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Andreas Tille <ti...@debian.org>
Closes: 1044054
Changes:
dyda (1.41.1-2) unstable; urgency=medium
.
* Team upload.
* Team maintenance in Debian Science team
* Standards-Version: 4.6.2 (routine-update)
* debhelper-compat 13 (routine-update)
* Secure URI in copyright format (routine-update)
* Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
* Rules-Requires-Root: no (routine-update)
* Use secure URI in Homepage field.
* Add upstream/metadata
* Port to Pandas 2.0 by passing numeric_only=True to mean()
Closes: #1044054
* Drop debian/gbp.conf which is in contrast with real repository layout
Checksums-Sha1:
f504c88065056005bca8911f6ff10b5b9e1b22aa 2145 dyda_1.41.1-2.dsc
d3bcbe48e1cedf0d9a5666644ee42406b24c607a 5628 dyda_1.41.1-2.debian.tar.xz
0cf810947db36fece64e1e80ee2a801fd166def2 7342 dyda_1.41.1-2_amd64.buildinfo
Checksums-Sha256:
bd072d6b811b45521aeb8abccd69adb1315ba040c7cd2066431d22857580cf81 2145
dyda_1.41.1-2.dsc
58813b8fa8b1f46d2843f2bcd551e8c149c1e827a74baeda4186a7dc06594e5c 5628
dyda_1.41.1-2.debian.tar.xz
6ba1cbcd30b898ecfa7f81aa90c912b605e4d0ff992f98c3eb5b83d6f01d9a9e 7342
dyda_1.41.1-2_amd64.buildinfo
Files:
bd6a13126b4987c76673f4d7c7c485a8 2145 python optional dyda_1.41.1-2.dsc
5fa432264acf8e9dd812775e9e0c863c 5628 python optional
dyda_1.41.1-2.debian.tar.xz
266d44ac4883da60c62dc5e48ef31fbc 7342 python optional
dyda_1.41.1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmXUfKoRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGcXg/+NgxZy9BNc6wabcxOZ5D59RFg1r7/zli2
pYrzorAkXGK95NxxhUPDrHU43z+PjkqJufMR7fGbv3z8oqBZM7Ilfdz8/DITS2U6
DJzw1E+R3FxFFmCerKIV05KXga2Psmnhuh0V/g0f6cD3VCSI3WPCeobM4cMPlWOc
achasqJdAyQAUBTeWGYIEU8jtij5PCnid6q/hwExClxayFoP/5N2bYbFCSCRdLzC
3QeKD6BqNrN5qqnwRxhK72QMUU0vGHjHUBmLlj/ea1YvR0jwK4+tp0juuylZIRRp
jmIT7f7T3D0ZrO+ZeZfOOg0zhqOa7aHyA4ZlZnikMNHLeCun6S/AX3kt0lEoEVxc
Gpa/Se8RhQ3uS/RPcqHHWDIR0rsOi8TVYDTkskFuiotFsCAXfDk9GtmyCYZMZctM
WOeL5VUeTN2ud+Pc+52dDrgRFHAZyv1h8hedMb1ft2L2aTKOASYAuDxIDLcqwMyR
HJHvfv9DQWiK8akJT64FcV1bCDqQnCl+fdHubxPV9R+u+OO82An9Lu10HquEgrNt
ZHae11x0liK1MrsmIZj7Olgkbr2IjOuZwKHtRKtE9UJDKRPWtHkGwHj8ZgPaf//F
assrItiydwj6TlwRBgXPHl8Yb26qswJs+/9V7WQWvUyONyyKDYB87bek2lO6vkIy
8Q8HYoNEN1Y=
=g9IJ
-----END PGP SIGNATURE-----
pgpRQ1LyGTyJt.pgp
Description: PGP signature
--- End Message ---
