Hi Dominik, thanks very much.
Actually, I need you to type:
dpkg -S `which install-info`
not
dpkg -S which install-info
But so far I can say this: the output from your install-info --version
is different from what it ought to be. Jaunty's install-info is dpkg's
(and from the dpkg -S output you gave, dpkg agrees). Your dpkg version
is the same one I have; but it doesn't say "GNU install-info 4.12", it
says "Debian install-info version 1.14.24ubuntu1", which identifies it
as the one that comes from dpkg. And GNU install-info 4.12 can't come
from the latest Jaunty texinfo package anyway (which you've already
shown as not installed), since that package is currently at
4.11.dfsg.1-4.
The problem is clearly that "install-info" is not invoking the one at
/usr/sbin/install-info, as it expects to, but some other one that's been
injected in a directory closer to the start of your PATH environment
variable. So it's not a bug in wget, nor in dpkg. The remaining question
is, where is it, and where did it come from, and what do all of you have
in common that is provoking this symptom. The corrected "dpkg -S"
command above should help us discover that.
An additional item: GNU install-info shouldn't emit this error _either_,
provided it was configured at build time to look in the correct place
for "dir". texinfo's "ginstall-info" is misconfigured* to look at /dir,
and apparently so is your install-info, which is why, when it doesn't
find /dir (or whatever file it's misconfigured to look for instead of
/usr/share/info/dir), it complains that you didn't tell it where to put
the wget info entry.
* "misconfigured", but possibly intentionally, if the packager was
worried about Bad Things Happening when both dpkg's install-info and
ginstall-info are messing with the same file, in possibly incompatible
ways.
If any of you are still waiting around for a workaround to your borked
situation, note that if you edit /var/lib/dpkg/info/wget.postinst (as
root), and replace "install-info" with "/usr/sbin/install-info", and
then run "sudo dpkg --configure --pending", it should resolve the
situation. Please don't stop participating in this bug, though, so we
can find out where the glitch came from, and inform the appropriate
people so they can fix it.
** Changed in: dpkg (Ubuntu)
Status: Incomplete => Invalid
** Changed in: dpkg (Ubuntu)
Assignee: Dominik Wujastyk (wujastyk) => (unassigned)
--
package wget 1.11.4-2ubuntu1.1 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/444917
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
