Your message dated Sun, 29 Dec 2002 11:55:45 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Your ssh2 bug
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 3 Dec 2000 04:19:44 +0000
>From [EMAIL PROTECTED] Sat Dec 02 22:19:44 2000
Return-path: <[EMAIL PROTECTED]>
Received: from (mail.epost.de) [64.39.38.70]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 142Qcp-0001ZM-00; Sat, 02 Dec 2000 22:19:43 -0600
Received: from epost.de (62.224.187.234) by mail.epost.de (5.1.055)
id 3A23FA2E00035B41 for [EMAIL PROTECTED]; Sun, 3 Dec 2000 05:18:48
+0100
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 03 Dec 2000 05:18:53 +0100
From: Gilbert Fridgen <[EMAIL PROTECTED]>
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.17 i686; en-US; m18) Gecko/20001103
X-Accept-Language: en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: problems when updating from (open)ssh to ssh2
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
Package: ssh2
Version: 2.0.13-5.1
Package: ssh
Version: 1:1.2.2.0p1-1.1
Hi!
I think the package dependencies in the ssh2-package are not correctly
configured. The package-configuration asks, if I want to leave the old
(open)ssh1-binaries for later use (which I need to connect to older
servers), or if I want to install symlinks to ssh2 instead. The first
one doesn't work, because ssh1 is deinstalled by apt before.......
apt seems to think, that ssh2 is just an upgrade for ssh.
suggested fix: I don't know if there are other dependency problems (e.g.
sshd and sshd2 listening on the same port), but why not just make ssh2
completely independent from ssh?
I hope that problem isn't on the buglist yet, I only saw some comparable
problems relating sshd1/2.
cu
Gilbert
---------------------------------------
Received: (at 78649-done) by bugs.debian.org; 29 Dec 2002 10:55:47 +0000
>From [EMAIL PROTECTED] Sun Dec 29 04:55:46 2002
Return-path: <[EMAIL PROTECTED]>
Received: from smtpzilla5.xs4all.nl [194.109.127.141]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18Sb6g-0002Oe-00; Sun, 29 Dec 2002 04:55:46 -0600
Received: from kalypso (ramstraat29.xs4all.nl [80.126.10.231])
by smtpzilla5.xs4all.nl (8.12.0/8.12.0) with ESMTP id gBTAtjTo078832
for <[EMAIL PROTECTED]>; Sun, 29 Dec 2002 11:55:45 +0100 (CET)
Received: from bas by kalypso with local (Exim 3.36 #1 (Debian))
id 18Sb6f-0003md-00
for <[EMAIL PROTECTED]>; Sun, 29 Dec 2002 11:55:45 +0100
From: Bas Zoetekouw <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Your ssh2 bug
Message-Id: <[EMAIL PROTECTED]>
Sender: Bas Zoetekouw <[EMAIL PROTECTED]>
Date: Sun, 29 Dec 2002 11:55:45 +0100
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-0.7 required=5.0
tests=SPAM_PHRASE_02_03
version=2.41
X-Spam-Level:
Hi!
Ssh2 was removed from the Debian archive this morning. It's
replacement, openssh (ssh package), does not seem to be affected
by this bug; therefore, I'm closing it.
Kind regards,
Bas Zoetekouw.
