Bug#1043240: transition: pandas 1.5 -> 2.1

On Fri, Jan 26, 2024 at 08:43:03AM +0200, Graham Inggs wrote: > Hi > > On Tue, 23 Jan 2024 at 14:38, Julian Gilbey wrote: > > We're nearly there (the transition page says it's 99% done), and when > > this transition is complete, then python3-defaults 3.11.6+ will be > > able to migrate to

Bug#1043240: transition: pandas 1.5 -> 2.1

Hi On Tue, 23 Jan 2024 at 14:38, Julian Gilbey wrote: > We're nearly there (the transition page says it's 99% done), and when > this transition is complete, then python3-defaults 3.11.6+ will be > able to migrate to testing. python3-defaults/3.11.6-1 with Python 3.12 as a supported version is

guiqwt 4.4.4-1 MIGRATED to testing

FYI: The status of the guiqwt source package in Debian's testing distribution has changed. Previous version: 4.4.1-1 Current version: 4.4.4-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

ros-rosinstall REMOVED from testing

FYI: The status of the ros-rosinstall source package in Debian's testing distribution has changed. Previous version: 0.7.8-6 Current version: (not in testing) Hint: # 1058268 in ros-wstool # 1058224 The script that generates

xtensor 0.24.7-5 MIGRATED to testing

FYI: The status of the xtensor source package in Debian's testing distribution has changed. Previous version: 0.24.7-4 Current version: 0.24.7-5 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

ros-wstool REMOVED from testing

FYI: The status of the ros-wstool source package in Debian's testing distribution has changed. Previous version: 0.1.18-3 Current version: (not in testing) Hint: # 1058268 The script that generates this mail tries to extract

dolfin 2019.2.0~legacy20240118.982f376-1 MIGRATED to testing

FYI: The status of the dolfin source package in Debian's testing distribution has changed. Previous version: 2019.2.0~legacy20230609.8b85e9d.ar-8 Current version: 2019.2.0~legacy20240118.982f376-1 -- This email is automatically generated once a day. As the installation of new packages

gle-graphics 4.3.4-1 MIGRATED to testing

FYI: The status of the gle-graphics source package in Debian's testing distribution has changed. Previous version: 4.3.3-3 Current version: 4.3.4-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

mrcal_2.4-1_amd64.changes is NEW

binary:libmrcal4 is NEW. binary:libmrcal4 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely

mrcal_2.4-1_source.changes REJECTED

mrcal_2.4-1_source.changes: Refers to non-existing file 'mrcal_2.4-1.dsc' Perhaps you need to include the file in your upload? If the orig tarball is missing, the -sa flag for dpkg-buildpackage will be your friend. === Please feel free to respond to this email if you don't understand why

Bug#1060026: yade: please move away from python3-future

Hi, I've pushed my changes incorporating Alexandre's patch plus further changes to Salsa. The build went on my not very recent desktop machine more then 6 hours but finally failed: ... plot (yade.plot) Doctest: yade.plot.plot ... ok saveDataTxt (yade.plot) Doctest: yade.plot.saveDataTxt ... ok

Processed: adding fixes, package still doesn't build

Processing control commands: > tags -1 + patch Bug #1061316 [src:gringo] gringo ftbfs with Python 3.12 as the default Added tag(s) patch. -- 1061316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --

Bug#1061316: adding fixes, package still doesn't build

Control: tags -1 + patch adding patches, however the package still ftbfs with: [...] /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/Scrt1.o: in function `_start': (.text+0x1b): undefined reference to `main' /usr/bin/ld: CMakeFiles/test_reify.dir/program.cc.o: in

Processed: adding fixes, package still doesn't build

Processing control commands: > tags -1 + patch Bug #1054688 [src:gringo] gringo: FTBFS: main.cc:2:10: fatal error: catch2/catch.hpp: No such file or directory Added tag(s) patch. -- 1054688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054688 Debian Bug Tracking System Contact

suitesparse_7.6.0+dfsg-1_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 25 Jan 2024 11:19:14 +0100 Source: suitesparse Architecture: source Version: 1:7.6.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Processing of suitesparse_7.6.0+dfsg-1_source.changes

suitesparse_7.6.0+dfsg-1_source.changes uploaded successfully to localhost along with the files: suitesparse_7.6.0+dfsg-1.dsc suitesparse_7.6.0+dfsg.orig.tar.xz suitesparse_7.6.0+dfsg-1.debian.tar.xz suitesparse_7.6.0+dfsg-1_amd64.buildinfo Greetings, Your Debian queue daemon

Bug#1060998: marked as done (cthreadpool: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Thu, 25 Jan 2024 08:34:35 + with message-id and subject line Bug#1060998: fixed in cthreadpool 0.0+git20231218.4eb5a69-1 has caused the Debian Bug report #1060998, regarding cthreadpool: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked

cthreadpool_0.0+git20231218.4eb5a69-1_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 25 Jan 2024 08:41:52 +0100 Source: cthreadpool Architecture: source Version: 0.0+git20231218.4eb5a69-1 Distribution: unstable Urgency: medium Maintainer: Debian Science