Bug#898949: schroot: PAM config should use common-session-noninteractive
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 that only exists outside the chroot.
Packages that use $XDG_RUNTIME_DIR are expected to have some sort of
reasonable fallback behaviour if it is not set at all (for example
dbus disables the features that need it, and some other packages use
~/.cache/foo as a fallback version of $XDG_RUNTIME_DIR/foo), but they
often do not have a graceful fallback path if $XDG_RUNTIME_DIR is set
to a path that is inaccessible, on the basis that they should do their
best to obey explicit requests from the user/environment ("the user is
always right").
smcv
cronolog_1.6.2+rpk-3_source.changes ACCEPTED into unstable
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 Description: cronolog - Logfile rotator for web servers Launchpad-Bugs-Fixed: 71177 Changes: cronolog (1.6.2+rpk-3) unstable; urgency=medium . * QA upload [ Luca Falavigna ] * Grab Ubuntu patch: - debian/patches/050_cronolog_getopt_long.diff (LP: #71177): - Last record of a struct option must be NULL, so add a NULL record at - the bottom of long_options, thanks Carlo Marcelo Arenas Belon! * Set compat level to 12 * Bump std-version to 4.4.0 Checksums-Sha1: 2aa868a6a8012e58138f635e8519702e770917f1 1746 cronolog_1.6.2+rpk-3.dsc 518febc8443da14e5f6e334544b4bf66a2cd0202 9704 cronolog_1.6.2+rpk-3.debian.tar.xz f91e16d84e832abb71431ea44ef716e9039edc13 6973 cronolog_1.6.2+rpk-3_source.buildinfo Checksums-Sha256: 8744154fd4d1c50b713a32ab1827fbff92afc729490560575fe1a3d2b1604279 1746 cronolog_1.6.2+rpk-3.dsc 06ed987901a3ae0ba92e27aad4c008a7b3dbd1ada8ce70614935d3e470031a2a 9704 cronolog_1.6.2+rpk-3.debian.tar.xz 3affbb36fd4d317ac2a75d89254078a36d66ab1a46bccd3cf35f171adc040652 6973 cronolog_1.6.2+rpk-3_source.buildinfo Files: aad79bd33b02619b354f48d3ee2ebfb0 1746 web optional cronolog_1.6.2+rpk-3.dsc 49059886e6c3d567870e50ac06075f84 9704 web optional cronolog_1.6.2+rpk-3.debian.tar.xz 3246b17da18b0b2b8d28946213456640 6973 web optional cronolog_1.6.2+rpk-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl1zuoMACgkQ808JdE6f XdlP/w/7BFNUYXmP2P3SLHvjGIIbpWTADSVH3mEexlAHUTxrgqbvEVDYJi+q5hQ3 s59NvR1+lrEqtX5OOAnaDLjh9iZ1/xtLXn8ufKKPBGfq6+AITwrdm3+nqde6mKwf G4x7hTQeVsihbAGCXnNJYLZpJyC6/Y4rNHf/+PDCAuP3Amj3hxIO5TWvLqOr2mCC d0qgrY5UYatfz+2mrqdAofvrremI1zHsz91GquValZbAbp3aUxqkq7OXCUf6BkBx SbrLsN1o7Liw4rndOdj7M1kfC32dEPu/ZnNgiOc1mOa0V46bDK7rvDaCs4m/j3r0 XnFsRyBOY0+iMjqmy1MqXkGQvP7pozhL1yeDE7zo2nrlAMYGekPY45UoSzSEez7q jmH0UNI1CU2ZfdUQXmcxbse7fxX+FGCWYzhhPcWK3c6mAQa4aEG62H2XAsnkDgGI q8XTaHzHoMJ6Xj14VBkWDL6MwqZiqvOi0tuwQu7nShQe3uHMzlYXeXtXRGh83Dk/ lqQND430my/wBN0gJV2y022ulLefQcQ+X/whGmOA9r5HqSBojelNNRi4gF/mYAk8 xZxRiZc34S180hCMQxMupg6VufNbGQkjo6zNNcp4Uaona5mbZJtl5WINAyku+5Ju EkzgJSBHeRyckPf1hPo1zohBuc6ZMCULOJa7eZr6ZcUPTGOb3YY= =ECQr -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processed: Re: cronolog segfaults on [sic] cronolog --vesion
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 architecture '' Unable to make a source version for version '1.6.2+rpk-3' Marked as fixed in versions 1.6.2+rpk-3. Marked as fixed in versions 1.6.2+rpk-3. > close -1 Bug #743186 [cronolog] cronolog segfaults on [sic] cronolog --vesion Bug #715757 [cronolog] [Mayhem] Bug report on cronolog: cronolog crashes with exit status 139 Marked Bug as done Marked Bug as done -- 715757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715757 743186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#743186: cronolog segfaults on [sic] cronolog --vesion
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
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)
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 dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tacacs+ Version: 4.0.4.27a-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:tacacs+ If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- 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 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#936567: marked as done (fteproxy: Python2 removal in sid/bullseye)
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 dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fteproxy Version: 0.2.19-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:fteproxy If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- 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 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#727103: marked as done (tacacs+: Please implement the patch to support PAM for PAP authentication)
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 you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 727103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tacacs+ Version: 4.0.4.19-11 Severity: wishlist Hi! Could you please apply the patch mentioned at http://www.shrubbery.net/pipermail/tac_plus/2012-March/001117.html to the wheezy package? It would be great to have PAM support for PAP authentication! Best regards, Frank -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- 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 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#852813: marked as done (rpl: Exception when locale is undefined or C)
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 has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 852813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rpl Version: 1.5.7-1 Severity: important Dear Maintainer, The program fails with a TypeError Exception when locale is undefined or set to C: root@notus:~# touch /tmp/rpl_test ; LANG=C rpl 'a' 'b' /tmp/rpl_test Replacing "a" with "b" (case sensitive) (partial words matched) .Traceback (most recent call last): File "/usr/bin/rpl", line 314, in main() File "/usr/bin/rpl", line 246, in main matches = blockrepl(f, o, regex, old_str, new_str, 1024) File "/usr/bin/rpl", line 97, in blockrepl outstream.write(tonext.encode(encoding=encoding, errors='ignore')) TypeError: encode() argument 1 must be str, not None root@notus:~# touch /tmp/rpl_test ; LANG=en_US rpl 'a' 'b' /tmp/rpl_test Replacing "a" with "b" (case sensitive) (partial words matched) . A Total of 0 matches replaced in 1 file searched. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.5-guest (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rpl depends on: pn python3:any rpl recommends no packages. rpl suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Considering a non-reply and that bug was already fixed, I am closing it. Feel free to reopen if needed. Regards, Eriberto--- End Message ---
Bug#790544: marked as done (tacacs+: init script should not use + char)
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 been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 790544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 44-2 Severity: minor Dear Maintainer, I think this is just a cosmetic bug. I'm not sure from reading LSB whether "+" is allowed in LSB headers or not. If it's not, feel free to reassign to the package tacacs_plus. After installing tacacs_plus the following message appears in syslog on every daemon-reload. I'm not seeing any other problems so it might be just a cosmetic issue, but one side is not adhering to LSB specs apparently. Jun 11 12:45:39 ops02 systemd[1]: Reloading. Jun 11 12:45:39 ops02 systemd[1]: [/etc/init.d/tacacs_plus:3] Failed to add LSB Provides name tacacs+.service, ignoring: Invalid argument root@ops02:/# grep Provides /etc/init.d/tacacs_plus # Provides: tacacs+ -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii dpkg 1.16.3 ii initscripts 2.88dsf-22.1 ii libacl1 2.2.51-7 ii libaudit01:1.7.18-1.1 ii libc62.13-33 ii libcap2 1:2.22-1 ii libcryptsetup4 2:1.4.3-1 ii libdbus-1-3 1.6.0-1 ii libkmod2 8-2 ii liblzma5 5.1.1alpha+20110809-3 ii libpam0g 1.1.3-7.1 ii libselinux1 2.1.9-2 ii libsystemd-daemon0 44-2 ii libsystemd-id128-0 44-2 ii libsystemd-journal0 44-2 ii libsystemd-login044-2 ii libudev0 175-3.1 ii libwrap0 7.6.q-23 ii udev 175-3.1 ii util-linux 2.20.1-5 Versions of packages systemd recommends: ii libpam-systemd 44-2 Versions of packages systemd suggests: ii python2.7.2-10 pn python-cairo pn python-dbus pn systemd-gui -- no debconf information --- End Message --- --- Begin Message --- 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 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#789651: marked as done (tacacs+: Incomplete systemd integration)
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 dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 789651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tacacs+ Version: 4.0.4.27a-1 Severity: normal Description: tacacs+ is missing 'is-enabled' systemd integration: # systemctl is-active tacacs_plus.service active # systemctl enable tacacs_plus.service Synchronizing state for tacacs_plus.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d tacacs_plus defaults Executing /usr/sbin/update-rc.d tacacs_plus enable # systemctl is-enabled tacacs_plus.service Failed to get unit file state for tacacs_plus.service: No such file or directory Expected result: # systemctl is-enabled tacacs_plus.service enabled Workaround: Check if the link /etc/rc5.d/S02tacacs_plus exist or not, instead of using 'systemctl is-enabled' command. --- End Message --- --- Begin Message --- 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 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#838701: Removed package(s) from unstable
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, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; python2-only; orphaned; dead upstream; low popcon -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 838...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/838701 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#838701: Removed package(s) from unstable
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 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#900229: Removed package(s) from unstable
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 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
shogun is marked for autoremoval from testing
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
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 -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 900...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/900229 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
