mtink is marked for autoremoval from testing

mtink 1.0.16-14 is marked for autoremoval from testing on 2022-12-25 It is affected by these RC bugs: 1024824: mtink: The software outputs: "No access to printer device file". Normal user should be added to lp group to make `mtink` work and it has been added to it indeed, so it is in the

wily_0.13.42-1_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Dec 2022 14:47:55 +0100 Source: wily Architecture: source Version: 0.13.42-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian

Processing of wily_0.13.42-1_source.changes

wily_0.13.42-1_source.changes uploaded successfully to localhost along with the files: wily_0.13.42-1.dsc wily_0.13.42.orig-html.tar.gz wily_0.13.42.orig-macros.tar.gz wily_0.13.42.orig.tar.gz wily_0.13.42-1.debian.tar.xz wily_0.13.42-1_source.buildinfo Greetings, Your Debian

watchcatd_1.2.1-4_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Dec 2022 14:39:43 +0100 Source: watchcatd Architecture: source Version: 1.2.1-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By:

Processing of watchcatd_1.2.1-4_source.changes

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

ucspi-proxy_0.99-3_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Dec 2022 13:59:03 +0100 Source: ucspi-proxy Architecture: source Version: 0.99-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By:

Processing of ucspi-proxy_0.99-3_source.changes

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

Bug#1007496: marked as done (ucspi-proxy: please consider upgrading to 3.0 source format)

Your message dated Sat, 03 Dec 2022 13:21:12 + with message-id and subject line Bug#1007496: fixed in ucspi-proxy 0.99-3 has caused the Debian Bug report #1007496, regarding ucspi-proxy: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the

tcsh_6.21.00-3_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Dec 2022 12:22:56 +0100 Source: tcsh Architecture: source Version: 6.21.00-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Bastian

Processing of tcsh_6.21.00-3_source.changes

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

Bug#1007077: marked as done (tcsh: please consider upgrading to 3.0 source format)

Your message dated Sat, 03 Dec 2022 11:34:44 + with message-id and subject line Bug#1007077: fixed in tcsh 6.21.00-3 has caused the Debian Bug report #1007077, regarding tcsh: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the problem has

Bug#562702: python-pam: Debian differences not clearly separated from upstream source

Control: severity -1 serious X-Debbugs-Cc: d...@debian.org On Sun, 27 Dec 2009 17:28:04 +1100 Ben Finney wrote: However, the ‘python-pam_0.4.2.orig.tar.gz’ does not match the actual file at http://www.pangalactic.org/PyPAM/PyPAM-0.4.2.tar.gz>, with many significant changes. These changes

Processed: Re: python-pam: Debian differences not clearly separated from upstream source

Processing control commands: > severity -1 serious Bug #562702 [python-pam] python-pam: Debian differences not clearly separated from upstream source Severity set to 'serious' from 'normal' -- 562702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562702 Debian Bug Tracking System Contact

Processed: retitle

Processing commands for cont...@bugs.debian.org: > retitle 993301 prototypejs: not built from source Bug #993301 [src:prototypejs] prototypejs: FTBFS Changed Bug title to 'prototypejs: not built from source' from 'prototypejs: FTBFS'. > End of message, stopping processing here. Please contact

playmidi_2.4debian-13_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Dec 2022 10:11:08 +0100 Source: playmidi Architecture: source Version: 2.4debian-13 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By:

Bug#993301: prototypejs: FTBFS

X-Debbugs-Cc: y...@debian.org On Fri, 19 Nov 2021 08:32:52 +0100 Andreas Beckmann wrote: > Sée thé salsa tree un order to understand why i need rake Which repository are you talking about? I guess https://salsa.debian.org/js-team/prototypejs, which is a repo introduced by the JS Team to

Processing of playmidi_2.4debian-13_source.changes

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

Bug#1007442: marked as done (playmidi: please consider upgrading to 3.0 source format)

Your message dated Sat, 03 Dec 2022 09:34:56 + with message-id and subject line Bug#1007442: fixed in playmidi 2.4debian-13 has caused the Debian Bug report #1007442, regarding playmidi: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the