python-sparkpost is marked for autoremoval from testing

python-sparkpost 1.3.10-3 is marked for autoremoval from testing on 2024-07-19 It is affected by these RC bugs: 1065937: python-sparkpost: Please drop dependencies on python3-distutils https://bugs.debian.org/1065937 This mail is generated by: https://salsa.debian.org/release-team/release-tool

Bug#1074175: netkit-rwho: remove for trixie?

rwho(d) is a design from a different time, when networks were trusted, and so on. It seems to me, we should and could stop shipping it for trixie. I'm raising this bug now, to: 1) establish awareness I was long aware of this, as I was using rwhod/ruptime when networks were not split into thousa

[bts-link] source package src:python-sparkpost

# # bts-link upstream status pull for source package src:python-sparkpost # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #1065937 (http://bugs.debia

Bug#1075755: marked as done (leave: ftbfs due to 'don't have (pseudo-)root!')

Your message dated Thu, 04 Jul 2024 12:50:38 + with message-id and subject line Bug#1075755: fixed in leave 1.12-6 has caused the Debian Bug report #1075755, regarding leave: ftbfs due to 'don't have (pseudo-)root!' to be marked as done. This means that you claim that the problem has been dea

Bug#355121: marked as done (please show which commands are run)

Your message dated Thu, 4 Jul 2024 14:48:46 +0200 with message-id <94c466cc-384a-43e3-8116-323659530...@debian.org> and subject line Re: please show which commands are run has caused the Debian Bug report #355121, regarding please show which commands are run to be marked as done. This means that y

leave_1.12-6_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 04 Jul 2024 14:15:00 +0200 Source: leave Architecture: source Version: 1.12-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Santiago Vil

Processing of leave_1.12-6_source.changes

leave_1.12-6_source.changes uploaded successfully to localhost along with the files: leave_1.12-6.dsc leave_1.12-6.debian.tar.xz leave_1.12-6_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1075755: leave: ftbfs due to 'don't have (pseudo-)root!'

El 4/7/24 a las 13:25, Bo YU escribió: I think the issue was raised by adding `Rules-Requires-Root: no` in previous upload but checking the root env during build. I am not sure why to check it so please double check it. Yes, that was the thing that triggered this problem. In this case, this pa

log4c_1.2.4-4_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 04 Jul 2024 08:48:53 +0200 Source: log4c Architecture: source Version: 1.2.4-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Rein

Processing of log4c_1.2.4-4_source.changes

log4c_1.2.4-4_source.changes uploaded successfully to localhost along with the files: log4c_1.2.4-4.dsc log4c_1.2.4-4.debian.tar.xz log4c_1.2.4-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1075741: elpa-jedi-core: deprecated warning on jedi server

Package: elpa-jedi-core Version: 0.2.8+git20220410.81c5a42-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Edit a python file in emacs with jedi enabled. archec@tagol:~$ grep jedi .emacs