updating doesn't work anymore

[Markus Schönhaber]

19.05.2010 23:06, Joep L. Blom:

> Markus Schönhaber wrote:
> 
>> Maybe this file simply got corrupted somehow. What does it contain?
>> Here's what mine looks like:
>> | $ cat /var/lib/dpkg/info/libc-bin.triggers
>> | interest ldconfig
>> | $ hexdump -C /var/lib/dpkg/info/libc-bin.triggers
>> | 00000000  69 6e 74 65 72 65 73 74  20 6c 64 63 6f 6e 66 69  |interest
>> ldconfi|
>> | 00000010  67 0a                                             |g.|
>> | 00000012
>> (note the LF at the end of the file).
>>
> 
> Markus, thanks. I followed your recipe and mine is:
> 
> ~$ hexdump -C /var/lib/dpkg/info/libc-bin.triggers
> 00000000  13 a9 41 c8 19 99 5d bb  b7 e0 f4 c4 7a ce 86 99 
> |..A...].....z...|
> 00000010  e1 9d                                             |..|
> 00000012
> 
> Mine is as you can see different but has also an LF at the end.

No, there's no LF char in it. Anyway, it looks like garbage.
Might be interesting to find out how it got corrupted. Maybe the
modification time of the file can be linked to some particular event
(installation, crash etc.).

> I wonder where this file originates and what is its purpose. I don't 
> think I can use yours.

AFAICT it's created during install of the libc-bin package. When I look
into the contents of the libc-bin_x.y.deb, I see a triggers file inside
control.tar.gz with just the content I showed above.

> I also wonders what happens if I remove it (i.e. 
> rename).

I'm not really an expert wrt the Debian packaging system, therefore I
can only guess: if the trigger is removed, ldconfig won't be run after
the installation of any package. This might result in libraries not
being found due to a stale linker cache.

The first thing I'd try is to rename the file and reinstall libc-bin. If
that doesn't work/isn't possible, I'd create a new file with the same
content as mine.

-- 
Regards
  mks