[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#237245: install-info: breaks maintainer scripts at least of tar and xemacs21-support

package dpkg
severity 237245 important
tags 237245 unreproducible

On Wed, 2004-03-10 at 14:37, Frank Küster wrote:

> The install-info program seems to have changed its syntax
> incompatibly. This morning, I got an error from tar's postinst, later
> also from xemacs21-support's postinst and prerm. This is the error
> message for tar:
The install-info program hasn't changed since dpkg 1.10.16; I'm almost
positive we'd've noticed this by now...

descent scott# dpkg -i tar_1.13.93-2_i386.deb
Unpacking replacement tar ...
Setting up tar (1.13.93-2) ...
descent scott#

And there's certainly no problem here with dpkg 1.10.19 and tar
1.13.93-2.  I've just tested this on half a dozen machines, upgrading
from various different versions, and I can't trip it.

I'm going to downgrade the severity as this obviously isn't making the
package unusable for everyone, but (so far) just you.

In fact, I'm going to go on a limb, and say this isn't even a dpkg
bug...  could you report the output of the following commands please:

	which install-info
	ls -l $(which install-info)
	dpkg -S $(which install-info)

I don't think you're running the dpkg install-info...

> Unpacking replacement tar ...
> Setting up tar (1.13.93-2) ...
> install-info: No such file or directory for General Commands
This error message does not exist in dpkg install-info, and indeed, dpkg
would tend to quote `General Commands' like that.

> xemacs21-support gives the same message in postinst, in prerm it is: 
> Removing xemacs21-support ...
> install-info: No dir file specified; try --help for more information.
This error message ALSO does not exist in dpkg install-info, and at no
point does dpkg install-info suggest you try --help.

However logging into a RedHat box I had lying about:

[scott@tavi scott]$ strings /sbin/install-info | grep "dir.*info"
No dir file specified; try --help for more information.

I'd like to place a bet that you've got RedHat's install-info somewhere
in your PATH with a higher priority than dpkg's, and that this isn't a
bug in dpkg at all.

Shall we say $100 ?

Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: