Debian Bug report logs - #4468
dpkg cannot cope with erased postrm script

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Christoph Lameter <clameter@miriam.fuller.edu>

To: submit@bugs.debian.org

Subject: dpkg cannot cope with erased postrm script

Date: Tue, 10 Sep 1996 13:54:36 -0700

package: dpkg
version: 1.3.14

I have a netdiag package from which I removed the postrm script. Here is a result of trying to install the package after that change:

# dpkg -i netdiag*5_i386.deb
(Reading database ... 20335 files and directories currently installed.)
Preparing to replace netdiag 0.2-3 (using netdiag_0.2-5_i386.deb) ...
Unpacking replacement netdiag ...
Removing easy access links for traceroute and tcpdump
rm: /usr/bin/traceroute: No such file or directory
rm: /usr/bin/tcpdump: No such file or directory
dpkg: warning - old post-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
dpkg: error processing netdiag_0.2-5_i386.deb (--install):
 there is no script in the new version of the package - giving up
Errors were encountered while processing:
 netdiag_0.2-5_i386.deb

I think it should just accept that there is no such thing as a postrm script anymore.

Message #10 received at 4468@bugs.debian.org (full text, mbox, reply):

From: Herbert Xu <herbert@greathan.apana.org.au>

To: 4468@bugs.debian.org

Subject: Re: dpkg cannot cope with erased postrm script

Date: Sat, 14 Dec 1996 20:19:42 +1100 (EST)

Christoph Lameter wrote:
> 
> package: dpkg
> version: 1.3.14
> 
> I have a netdiag package from which I removed the postrm script. Here is a result of trying to install the package after that change:
> 
> # dpkg -i netdiag*5_i386.deb
> (Reading database ... 20335 files and directories currently installed.)
> Preparing to replace netdiag 0.2-3 (using netdiag_0.2-5_i386.deb) ...
> Unpacking replacement netdiag ...
> Removing easy access links for traceroute and tcpdump
> rm: /usr/bin/traceroute: No such file or directory
> rm: /usr/bin/tcpdump: No such file or directory
> dpkg: warning - old post-removal script returned error exit status 1
> dpkg - trying script from the new package instead ...
> dpkg: error processing netdiag_0.2-5_i386.deb (--install):
>  there is no script in the new version of the package - giving up
> Errors were encountered while processing:
>  netdiag_0.2-5_i386.deb
> 
> I think it should just accept that there is no such thing as a postrm
> script anymore.

What does it do if you simply did "dpkg --remove netdiag"? The same behaviour
should be present in both cases.

-- 
Debian GNU/Linux 1.2 is out! { http://www.debian.org/ }
Email:  Herbert Xu ~{PmV>HI~} <herbert@greathan.apana.org.au>
{ http://greathan.apana.org.au/~herbert/ }
PGP Key:  pgp-public-keys@pgp.mit.edu or any other key sites

Message #15 received at 4468-done@bugs.debian.org (full text, mbox, reply):

From: Ian Jackson <ian@chiark.greenend.org.uk>

To: Christoph Lameter <clameter@miriam.fuller.edu>, 4468-done@bugs.debian.org

Subject: Re: Bug#4468: dpkg cannot cope with erased postrm script

Date: Wed, 13 Aug 97 18:49 BST

Christoph Lameter writes ("Bug#4468: dpkg cannot cope with erased postrm script"):
> package: dpkg
> version: 1.3.14
> 
> I have a netdiag package from which I removed the postrm script.
> [ and things broke ]

Don't do that then.

I'm closing this bug report.

Ian.

Message #20 received at 4468@bugs.debian.org (full text, mbox, reply):

From: Christoph Lameter <clameter@waterf.org>

To: Ian Jackson <ian@chiark.greenend.org.uk>

Cc: 4468@bugs.debian.org

Subject: Re: Bug#4468: dpkg cannot cope with erased postrm script

Date: Mon, 18 Aug 1997 10:05:03 -0700 (PDT)

Sorry Ian, but it should be possible to upgrade a package that previously
had a postrm script so that the upgrade does not have a postrm script
anymore.

Please reopen the bug report until the problem is fixed.

On Wed, 13 Aug 1997, Ian Jackson wrote:

>Christoph Lameter writes ("Bug#4468: dpkg cannot cope with erased postrm script"):
>> package: dpkg
>> version: 1.3.14
>> 
>> I have a netdiag package from which I removed the postrm script.
>> [ and things broke ]
>
>Don't do that then.
>
>I'm closing this bug report.
>
>Ian.
>
>

--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---

Message #27 received at 4468-maintonly@bugs.debian.org (full text, mbox, reply):

From: remco@blaakmeer.student.utwente.nl (Remco Blaakmeer)

To: 4468-maintonly@bugs.debian.org

Subject: Old bugs need to be looked at

Date: Sun, 1 Feb 1998 12:22:59 +0100 (CET)

This is an automated message sent to all bugs older than one year.

This bug is very old. Please take a look at it and see if you can fix it.
If it has already been fixed, please close it.

If you have problems fixing it or if you don't have the time to fix it,
please ask the people on debian-devel@lists.debian.org for help, so that
at least the oldest bugs can be solved before Debian 2.0 is released.

Remco Blaakmeer

Message #32 received at 4468@bugs.debian.org (full text, mbox, reply):

From: "Zephaniah E, Hull" <warp@whitestar.soark.net>

To: 4468@bugs.debian.org

Subject: State of this bug

Date: Wed, 25 Nov 1998 20:25:06 -0500

[Message part 1 (text/plain, inline)]

As nobody has touched this bug in over a year and as far as I can see
this is not a bug in the view of the maintainer I am setting the
severity to fixed, if anyone has issues with this please set the
severity back to normal and send a note to this bug report explaining
why..

Zephaniah E, Hull.

-- 
 PGP EA5198D1-Zephaniah E, Hull <warp@whitestar.soark.net>-GPG E65A7801
    Keys available at http://whitestar.soark.net/~warp/public_keys.
           CCs of replies from mailing lists are encouraged.

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.