Bug#316466: bpalogin must not be stopped during upgrade

2005-07-18 Thread Anibal Monsalve Salazar
On Sun, Jul 17, 2005 at 05:08:10AM -0700, Steve Langasek wrote:
Hi Anibal,

Have you had a chance to look at this bug?

I just returned home from debconf5. I'll be working on it this
during the next few days.

Any thoughts on how to solve it?

I don't really know what to do. If you have any suggestion, it
will be appreciated. I'll start researching about how to fix it
soon.

-- 
Steve Langasek
postmodern programmer

Kind regards,

Anibal Monsalve Salazar
--
 .''`. Debian GNU/Linux
: :' : Free Operating System
`. `'  http://debian.org/
  `-   http://v7w.com/anibal


signature.asc
Description: Digital signature


Bug#316466: bpalogin must not be stopped during upgrade

2005-07-17 Thread Steve Langasek
Hi Anibal,

Have you had a chance to look at this bug?  Any thoughts on how to solve it?

-- 
Steve Langasek
postmodern programmer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#316466: bpalogin must not be stopped during upgrade

2005-06-30 Thread kk87
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.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]