Am 24.10.2017 um 10:45 schrieb Linux O'Beardly: > First, it seems that you're actually trying to install different > revisions of the same package. You had libc-bin (2.19-18+deb8u9) in your > first email, and libc-bin (2.19-18+deb8u10) in your second. While this > is a minor difference, I've seen it cause issues. I spun a test Debian > Wheezy system in VirtualBox and then upgraded to Devuan Jessie. I could > not recreate the problem. Do you think you may have a corrupted > package? Did you try removing the libc-bin package, then running a > fresh update and reinstalling?
In June I upgraded 2 servers from Debian Wheezy to Devuan Jessie. At this time "libc-bin (2.19-18+deb8u9)" was the actual package. Meanwhile they have also got the 2.19-18+deb8u10 upgrade. The last server upgrade was in October, so this should be the reason for the newer libc-bin package. > rm /var/cache/archives/libc-bin_2.19-18+deb8u10_amd64.deb AND/OR > rm /var/cache/archives/libc-bin_2.19-18+deb8u9_amd64.deb > apt-get update What has removing of cached packages to do with 'apt-get update'? IMO nothing. > apt-get install --reinstall libc-bin As I wrote before reinstalling does not solve the problem. As far as I understand, package libc-bin registers dpkg (?) triggers scripts which are executed on every update of any package. How can I find out, which trigger script of libc-bin causes this error? There must be a place, where dpkg stores this scripts. But where? Regards Thomas _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
