Bug#898949: schroot: PAM config should use common-session-noninteractive

2019-09-07 Thread Simon McVittie
On Thu, 17 May 2018 at 19:36:11 +0200, Ansgar Burchardt wrote: > On systems with libpam-systemd installed using common-session will > create a logind session which schroot should not do. In particular, creating a logind session results in $XDG_RUNTIME_DIR being set inside the chroot, to a path

cronolog_1.6.2+rpk-3_source.changes ACCEPTED into unstable

2019-09-07 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 07 Sep 2019 16:09:30 +0200 Source: cronolog Binary: cronolog Architecture: source Version: 1.6.2+rpk-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Gianfranco Costamagna

Processed: Re: cronolog segfaults on [sic] cronolog --vesion

2019-09-07 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1.6.2+rpk-3 Bug #743186 [cronolog] cronolog segfaults on [sic] cronolog --vesion Bug #715757 [cronolog] [Mayhem] Bug report on cronolog: cronolog crashes with exit status 139 There is no source info for the package 'cronolog' at version '1.6.2+rpk-3' with

Bug#743186: cronolog segfaults on [sic] cronolog --vesion

2019-09-07 Thread Gianfranco Costamagna
control: fixed -1 1.6.2+rpk-3 control: close -1 A side effect of the import of the Ubuntu patch was to have the two above bugs fixed. G.

Processing of cronolog_1.6.2+rpk-3_source.changes

2019-09-07 Thread Debian FTP Masters
cronolog_1.6.2+rpk-3_source.changes uploaded successfully to localhost along with the files: cronolog_1.6.2+rpk-3.dsc cronolog_1.6.2+rpk-3.debian.tar.xz cronolog_1.6.2+rpk-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#938620: marked as done (tacacs+: Python2 removal in sid/bullseye)

2019-09-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Sep 2019 04:39:43 + with message-id and subject line Bug#838701: Removed package(s) from unstable has caused the Debian Bug report #938620, regarding tacacs+: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#936567: marked as done (fteproxy: Python2 removal in sid/bullseye)

2019-09-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Sep 2019 04:41:59 + with message-id and subject line Bug#900229: Removed package(s) from unstable has caused the Debian Bug report #936567, regarding fteproxy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#727103: marked as done (tacacs+: Please implement the patch to support PAM for PAP authentication)

2019-09-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Sep 2019 04:39:43 + with message-id and subject line Bug#838701: Removed package(s) from unstable has caused the Debian Bug report #727103, regarding tacacs+: Please implement the patch to support PAM for PAP authentication to be marked as done. This means that

Bug#852813: marked as done (rpl: Exception when locale is undefined or C)

2019-09-07 Thread Debian Bug Tracking System
Your message dated Sat, 7 Sep 2019 23:44:54 -0300 with message-id and subject line Re: rpl: Exception when locale is undefined or C has caused the Debian Bug report #852813, regarding rpl: Exception when locale is undefined or C to be marked as done. This means that you claim that the problem

Bug#790544: marked as done (tacacs+: init script should not use + char)

2019-09-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Sep 2019 04:39:43 + with message-id and subject line Bug#838701: Removed package(s) from unstable has caused the Debian Bug report #790544, regarding tacacs+: init script should not use + char to be marked as done. This means that you claim that the problem has

Bug#789651: marked as done (tacacs+: Incomplete systemd integration)

2019-09-07 Thread Debian Bug Tracking System
Your message dated Sun, 08 Sep 2019 04:39:43 + with message-id and subject line Bug#838701: Removed package(s) from unstable has caused the Debian Bug report #789651, regarding tacacs+: Incomplete systemd integration to be marked as done. This means that you claim that the problem has been

Bug#838701: Removed package(s) from unstable

2019-09-07 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libtacacs+1 | 4.0.4.27a-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libtacacs+1-dev | 4.0.4.27a-3 | all tacacs+ | 4.0.4.27a-3 | source, amd64, arm64, armel,

Bug#838701: Removed package(s) from unstable

2019-09-07 Thread Debian FTP Masters
Version: 4.0.4.27a-3+rm Dear submitter, as the package tacacs+ has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/838701

Bug#900229: Removed package(s) from unstable

2019-09-07 Thread Debian FTP Masters
Version: 0.2.19-3+rm Dear submitter, as the package fteproxy has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/900229

shogun is marked for autoremoval from testing

2019-09-07 Thread Debian testing autoremoval watch
shogun 3.2.0-9 is marked for autoremoval from testing on 2019-09-07 It is affected by these RC bugs: 925827: shogun: ftbfs with GCC-9

Bug#900229: Removed package(s) from unstable

2019-09-07 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: fteproxy | 0.2.19-3 | source, all --- Reason --- RoQA; python2-only; orphaned; dead upstream; low popcon --