Your message dated Tue, 13 Sep 2005 15:32:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#316466: fixed in bpalogin 2.0.2-5
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; 1 Jul 2005 03:41:04 +0000
>From [EMAIL PROTECTED] Thu Jun 30 20:41:04 2005
Return-path: <[EMAIL PROTECTED]>
Received: from omta03ps.mx.bigpond.com [144.140.82.155]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DoCOl-0007cz-00; Thu, 30 Jun 2005 20:41:03 -0700
Received: from tyreth.homelinux.org ([147.10.32.86])
by omta03ps.mx.bigpond.com with SMTP
id <[EMAIL PROTECTED]>
for <[EMAIL PROTECTED]>; Fri, 1 Jul 2005 03:40:31 +0000
Received: (qmail 18497 invoked by uid 1000); 1 Jul 2005 03:40:30 -0000
Date: Fri, 1 Jul 2005 13:40:30 +1000
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: bpalogin must not be stopped during upgrade
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.2 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS,
HAS_PACKAGE,NO_REAL_NAME autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: upgrade-reports
Severity: serious
Method: aptitude over ssh
Upgrade date: Sat July 11th 2005 (started, not finished until the
following week)
uname -a: Linux tyreth.homelinux.org 2.4.26 #1 Mon Jul 26 17:03:33 EST
2004 i686 GNU/Linux
I tried to upgrade a computer from Woody to Sarge remotely via SSH, but
it failed during the ugprade process because dpkg stopped bpalogin.
bpalogin is an unofficial login client for cable and ADSL connections on
Telstra Bigpond, one of Australia's largest ISPs.
Without a login client running, no internet traffic can pass to or from
the machine.
Once bpalogin stopped, my SSH session froze and the upgrade stalled at
the next configuration question. The computer was disconnected from the
internet for several days until the owner returned and was able to
restart bpalogin at the console. After that, I was able to complete the
upgrade and all services are now operating normally.
Bpalogin must be treated the same way as SSH and other essential
services: it must not be left in a stopped state while other packages
are upgraded. I understand it may not be possible to fix this problem
for Sarge; if that is so, then a warning should be added to the release
notes.
---------------------------------------
Received: (at 316466-close) by bugs.debian.org; 13 Sep 2005 22:38:30 +0000
>From [EMAIL PROTECTED] Tue Sep 13 15:38:30 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1EFJJu-0001Xp-00; Tue, 13 Sep 2005 15:32:06 -0700
From: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#316466: fixed in bpalogin 2.0.2-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 13 Sep 2005 15:32:06 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: bpalogin
Source-Version: 2.0.2-5
We believe that the bug you reported is fixed in the latest version of
bpalogin, which is due to be installed in the Debian FTP archive:
bpalogin_2.0.2-5.diff.gz
to pool/main/b/bpalogin/bpalogin_2.0.2-5.diff.gz
bpalogin_2.0.2-5.dsc
to pool/main/b/bpalogin/bpalogin_2.0.2-5.dsc
bpalogin_2.0.2-5_i386.deb
to pool/main/b/bpalogin/bpalogin_2.0.2-5_i386.deb
bpalogin_2.0.2-5_sparc.deb
to pool/main/b/bpalogin/bpalogin_2.0.2-5_sparc.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Anibal Monsalve Salazar <[EMAIL PROTECTED]> (supplier of updated bpalogin
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 14 Sep 2005 08:03:06 +1000
Source: bpalogin
Binary: bpalogin
Architecture: source i386 sparc
Version: 2.0.2-5
Distribution: unstable
Urgency: high
Maintainer: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Changed-By: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Description:
bpalogin - login client for the Telstra Bigpond Cable Network (Australia)
Closes: 316466
Changes:
bpalogin (2.0.2-5) unstable; urgency=high
.
* Fixed "bpalogin must not be stopped during upgrade",
closes: #316466.
* Set standards-version to 3.6.2.
* Fixed FSF postal address in debian/copyright.
Files:
1a7e95c68884b575834bedcddac799e6 574 net extra bpalogin_2.0.2-5.dsc
08f23341c54482efd5f25817a4f45dca 6029 net extra bpalogin_2.0.2-5.diff.gz
9f2f98d0fb60bb88146b3d3ea176d8a4 20224 net extra bpalogin_2.0.2-5_i386.deb
7da83cef41711f9245a875a9bf787bb1 20832 net extra bpalogin_2.0.2-5_sparc.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDJ1KqgY5NIXPNpFURAgqzAJsGAA+HZj5nUURv1UiTQd5806laOACg0Dbk
MXHYsik9gw2YCskp+Hc6lF4=
=2r/B
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
