Bug#703718: marked as done (rm libpam-sshauth/0.1-1)
Your message dated Fri, 22 Mar 2013 19:09:24 +0000
with message-id <[🔎] 1363979364.24071.3.camel@jacala.jungle.funky-badger.org>
and subject line Re: Processed: reassign 703719 to release.debian.org, retitle 703719 to rm libnss-sshsock/0.2-1, affects 703719
has caused the Debian Bug report #703718,
regarding rm libpam-sshauth/0.1-1
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 owner@bugs.debian.org
immediately.)
--
703718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703718
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libpam-sshauth should not be released with wheezy
- From: Vagrant Cascadian <vagrant@debian.org>
- Date: Fri, 22 Mar 2013 09:50:24 -0700
- Message-id: <20130322165024.GJ4037@talon.fglan>
Package: libpam-sshauth
Version: 0.1-1
Severity: serious
Very recently(i.e. this month), libpam-sshauth has been going through a major
rewrite upstream. The version in wheezy, while somewhat useable, is not likely
to receive the support it needs for the full release cycle of wheezy.
As the maintainer of libpam-sshauth, I think it would be best to remove it from
wheezy.
It does appear to have some users in popcon, though not many; I intend to
maintain backports of the newer versions if that pans out to be a viable
future.
live well,
vagrant
--- End Message ---
--- Begin Message ---
On Fri, 2013-03-22 at 18:54 +0000, Debian Bug Tracking System wrote:
> Processing commands for control@bugs.debian.org:
>
> > reassign 703719 release.debian.org
[...]
> > # removals ought to be filed against release.debian.org
Well yes, but I already added removal hints for both packages earlier
when I saw the bugs vagrant filed. :-)
Regards,
Adam
--- End Message ---
Reply to: