On Sun, Dec 05, 2010 at 06:19:00PM +0100, Guillem Jover wrote:
> Hi!
>
> That specific dpkg string is coming from dpkg --compare-versions, so
> someone somewhere is explicitly calling that one, and thus not really
> a dpkg bug. Kurt could you check the call trace to see exactly who?
> And then reassign?
So strace shows:
[pid 16140] execve("/var/lib/dpkg/info/postgresql-common.postinst",
["/var/lib/dpkg/info/postgresql-co"..., "triggered",
"/usr/share/myspell/dicts"], [/* 18 vars */]) = 0
[...]
[pid 16140] execve("/usr/share/debconf/frontend",
["/usr/share/debconf/frontend", "/var/lib/dpkg/info/postgresql-co"...,
"triggered", "/usr/share/myspell/dicts"], [/* 19 vars */]) = 0
[...]
[pid 16140] clone(Process 16146 attached
[...]
[pid 16146] execve("/var/lib/dpkg/info/postgresql-common.config",
["/var/lib/dpkg/info/postgresql-co"..., "configure",
"/usr/share/myspell/dicts"], [/* 20 vars
*/]) = 0
[...]
[pid 16146] clone(Process 16147 attached
[...]
[pid 16147] execve("/usr/bin/dpkg", ["dpkg", "--compare-versions",
"/usr/share/myspell/dicts", "lt-nl", "71"], [/* 19 vars */]) = 0
I'm not sure which package is at fault here. But it seems that
debconf is turning a triggered into a configure.
Kurt
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
