python-coverage-test-runner_1.13.1-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 29 Nov 2019 22:44:36 -0500 Source: python-coverage-test-runner Architecture: source Version: 1.13.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sandro Tosi Closes: 937666

Bug#937666: marked as done (python-coverage-test-runner: Python2 removal in sid/bullseye)

Your message dated Sat, 30 Nov 2019 04:04:21 + with message-id and subject line Bug#937666: fixed in python-coverage-test-runner 1.13.1-3 has caused the Debian Bug report #937666, regarding python-coverage-test-runner: Python2 removal in sid/bullseye to be marked as done. This means that you

python-cliapp_1.20180812.1-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 29 Nov 2019 22:01:47 -0300 Source: python-cliapp Architecture: source Version: 1.20180812.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Antonio Terceiro Closes: 937647

Bug#937647: marked as done (python-cliapp: Python2 removal in sid/bullseye)

>* QA upload >* Drop python2 support (Closes: #937647) >* Run tests during build and under autopkgtest there are still 2 rdeps http://sandrotosi.me/debian/py2removal/python-cliapp_1.svg ! -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian:

Bug#937647: marked as done (python-cliapp: Python2 removal in sid/bullseye)

Your message dated Sat, 30 Nov 2019 01:35:06 + with message-id and subject line Bug#937647: fixed in python-cliapp 1.20180812.1-3 has caused the Debian Bug report #937647, regarding python-cliapp: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Processed: py2removal blocks updates - 2019-11-29 17:49:14.973133+00:00

Processing commands for cont...@bugs.debian.org: > # Part of the effort for the removal of python from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # python2.7 > block 937569 by 942941 Bug #937569 [src:python2.7] python2.7:

Processed: Re: Bug#945842: grdesktop: Debian patch for gsettings broken: wrong settings-name used

Processing control commands: > tags -1 + pending Bug #945842 [grdesktop] grdesktop: Debian patch for gsettings broken: wrong settings-name used Added tag(s) pending. -- 945842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945842 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#945842: grdesktop: Debian patch for gsettings broken: wrong settings-name used

Control: tags -1 + pending Thomas Hooge wrote: > The current debian patch for gsettings uses different settings > names: rdp-protocol and rdp_protocol. So the setting ist never > applied to the gui. The selection stays at protocol "Windows 2000". Yes, GSettings does not allow keys with

Bug#943298: marked as done (xlsx2csv: Python2 removal in sid/bullseye)

Your message dated Fri, 29 Nov 2019 17:04:39 + with message-id and subject line Bug#943298: fixed in xlsx2csv 1:0.7.6-1 has caused the Debian Bug report #943298, regarding xlsx2csv: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#945842: grdesktop: Debian patch for gsettings broken: wrong settings-name used

Package: grdesktop Version: 0.23+d040330-3+b1 Severity: normal The current debian patch for gsettings uses different settings names: rdp-protocol and rdp_protocol. So the setting ist never applied to the gui. The selection stays at protocol "Windows 2000". -- System Information: Debian

Bug#945797: Some ingredients to a solution

I will need help with this. I’m not familiar with Debian packaging, nor with the technologies used to build the libmilter package. I think a simple milter.pc file would look something like the following: prefix=/usr