Your message dated Sat, 21 Nov 2009 17:24:04 +0100
with message-id <[email protected]>
and subject line Re: Bug#551331: dpkg: remove doesn't work for broken/not 
working packages
has caused the Debian Bug report #551331,
regarding dpkg: remove doesn't work for broken/not working packages
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 [email protected]
immediately.)


-- 
551331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551331
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.14.25
Severity: normal

Hello,

tspc doesn't wrk anymore. So if I try to remove it, dpkg delivers the following:

dpkg -r tspc
(Reading database ... 175350 files and directories currently installed.)
Removing tspc ...
Shutting down IPv6 tunnel: invoke-rc.d: initscript tspc, action "stop" failed.
dpkg: error processing tspc (--remove):
 subprocess pre-removal script returned error exit status 1
Setting up IPv6 tunnel: Status error 303 in tunnel negociation: 303 Unsupported 
tunnel mode


Error is 303: 303 is not defined as a client error, might be a TSP error?
TSP session done
invoke-rc.d: initscript tspc, action "start" failed.
dpkg: error while cleaning up:
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 tspc


I have seen such behaviour also with an foreign .deb provided by Brther Inc.
It looks like dpkg needs a force option to ignore the exit code of broken
scripts from packages to remove.


Greetings
        Juergen


-- System Information:
Debian Release: 5.0.3
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'stable')
Architecture: i386 (i586)

Kernel: Linux 2.6.26-2-486
Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages dpkg depends on:
ii  coreutils                     6.10-6     The GNU core utilities
ii  libc6                         2.7-18     GNU C Library: Shared libraries
ii  lzma                          4.43-14    Compression method of 7z format in

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt                      0.7.20.2+lenny1 Advanced front-end for dpkg

-- no debconf information

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.




--- End Message ---
--- Begin Message ---
Hi!

On Sat, 2009-10-17 at 13:03:16 +0200, Juergen Kosel wrote:
> Package: dpkg
> Version: 1.14.25
> Severity: normal

> tspc doesn't wrk anymore. So if I try to remove it, dpkg delivers the 
> following:
> 
> dpkg -r tspc
> (Reading database ... 175350 files and directories currently installed.)
> Removing tspc ...
> Shutting down IPv6 tunnel: invoke-rc.d: initscript tspc, action "stop" failed.
> dpkg: error processing tspc (--remove):
>  subprocess pre-removal script returned error exit status 1
> Setting up IPv6 tunnel: Status error 303 in tunnel negociation: 303 
> Unsupported tunnel mode
> 
> 
> Error is 303: 303 is not defined as a client error, might be a TSP error?
> TSP session done
> invoke-rc.d: initscript tspc, action "start" failed.
> dpkg: error while cleaning up:
>  subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>  tspc

> I have seen such behaviour also with an foreign .deb provided by Brther Inc.
> It looks like dpkg needs a force option to ignore the exit code of broken
> scripts from packages to remove.

I'm closing this bug report as this is a duplicate of 554912, which I
already replied to.

regards,
guillem


--- End Message ---

Reply via email to