On Sun, Nov 13, 2022 at 02:44:42PM +0000, Rebecca N. Palmer wrote: > Control: block 1021984 by -1 > Control: tags -1 fixed-upstream fixed-in-experimental > > There's more than just those 2[0]. > Some are tests that expect an error and check the message (not just the > type), and fail because the message has been reworded - these should be > trivial to fix. > The 2 in test_null_quote_char/test_null_byte_char don't look like this, but > also don't look like major problems. > > The ones that may need someone else's attention (because DMs can't upload > arbitrary packages) are that Debian's parso is too old to support 3.11 - > I've filed a new bug about this. > > I'm in the process of moving to pandas 1.5 (#1017809), which probably fixes > these[1], but also breaks a few reverse dependencies[2]. Do I take the > 'serious' tag to mean this is urgent enough to fix in 1.3?
Graham did an upload ignoring test failures,[1] if the problems are only in tests this might be good enough as a short-term fix? > [0] > https://launchpadlibrarian.net/631797785/buildlog_ubuntu-lunar-amd64.pandas_1.3.5+dfsg-5build1_BUILDING.txt.gz > [1] > https://buildd.debian.org/status/fetch.php?pkg=pandas&arch=ppc64el&ver=1.5.1%2Bdfsg-3&stamp=1668226153&raw=0 > (the lxml-not-found errors are probably because it hadn't been built in 3.11 > yet) > [2] https://qa.debian.org/excuses.php?experimental=1&package=pandas and > maybe more because I haven't done a build test yet cu Adrian [1] https://tracker.debian.org/news/1384166/accepted-pandas-135dfsg-6-source-into-unstable/
