I discovered exactly this bug today while updating my Sarge machine. This is strange as I never see this before and I don't remenber having changed something significant. Here are my last updated package using 'ls -altr /var/lib/dpkg/info' :

-rwxr-xr-x  1 root root    4001 2006-09-20 14:19 mailman.config
-rw-r--r--  1 root root   16347 2006-09-20 14:19 mailman.templates
-rwxr-xr-x  1 root root    1378 2006-09-20 14:19 mailman.prerm
-rwxr-xr-x  1 root root    1203 2006-09-20 14:19 mailman.preinst
-rwxr-xr-x  1 root root    1073 2006-09-20 14:19 mailman.postrm
-rwxr-xr-x  1 root root   15150 2006-09-20 14:19 mailman.postinst
-rw-r--r--  1 root root      45 2006-09-20 14:19 mailman.conffiles
-rw-r--r--  1 root root  216979 2006-09-20 14:19 mailman.md5sums
-rwxr-xr-x  1 root root     160 2006-09-23 12:03 gdhcpd.postrm
-rwxr-xr-x  1 root root     185 2006-09-23 12:03 gdhcpd.postinst
-rw-r--r--  1 root root     725 2006-09-23 12:03 gdhcpd.md5sums
-rw-r--r--  1 root root    1346 2006-09-23 12:28 toolame.md5sums
-rw-r--r--  1 root root      74 2006-09-25 22:55 nfs-kernel-server.list
-rw-r--r--  1 root root     977 2006-09-25 22:55 gzip.list
-rw-r--r--  1 root root     525 2006-09-25 22:55 libgnutls11.list
-rw-r--r--  1 root root    1148 2006-09-25 22:55 libgnutls11-dev.list
-rw-r--r--  1 root root     230 2006-09-25 22:55 libisc11.list
-rw-r--r--  1 root root     242 2006-09-25 22:55 libisccfg1.list
-rw-r--r--  1 root root     230 2006-09-25 22:55 libdns21.list
-rw-r--r--  1 root root     240 2006-09-25 22:55 libbind9-0.list
-rw-r--r--  1 root root     236 2006-09-25 22:55 liblwres9.list
-rw-r--r--  1 root root      60 2006-09-25 22:55 alsaplayer.list
-rw-r--r--  1 root root     266 2006-09-25 22:55 libalsaplayer0.list
-rw-r--r--  1 root root     672 2006-09-25 22:55 gdhcpd.list
-rw-r--r--  1 root root     299 2006-09-25 22:55 mindi-kernel.list
-rw-r--r--  1 root root     876 2006-09-25 22:55 toolame.list
-rw-r--r--  1 root root     742 2006-09-25 22:55 nfs-user-server.list
-rw-r--r-- 1 root root 4978 2006-09-26 19:50 mozilla-thunderbird.templates -rwxr-xr-x 1 root root 1284 2006-09-26 19:50 mozilla-thunderbird.postinst
-rwxr-xr-x  1 root root     878 2006-09-26 19:50 mozilla-thunderbird.prerm
-rwxr-xr-x  1 root root    1209 2006-09-26 19:50 mozilla-thunderbird.preinst
-rwxr-xr-x  1 root root     558 2006-09-26 19:50 mozilla-thunderbird.postrm
-rw-r--r--  1 root root   41684 2006-09-26 19:50 mozilla-thunderbird.md5sums
-rw-r--r--  1 root root    6545 2006-09-30 12:06 libssl0.9.7.templates
-rwxr-xr-x  1 root root      15 2006-09-30 12:06 openssl.prerm
-rwxr-xr-x  1 root root     665 2006-09-30 12:06 openssl.preinst
-rwxr-xr-x  1 root root     120 2006-09-30 12:06 openssl.postinst
-rw-r--r--  1 root root   27288 2006-09-30 12:06 openssl.md5sums
-rw-r--r--  1 root root      21 2006-09-30 12:06 openssl.conffiles
-rwxr-xr-x  1 root root      15 2006-09-30 12:06 libssl-dev.prerm
-rwxr-xr-x  1 root root      15 2006-09-30 12:06 libssl-dev.postinst
-rw-r--r--  1 root root   30394 2006-09-30 12:06 libssl-dev.md5sums
-rw-r--r--  1 root root      53 2006-09-30 12:06 libssl0.9.7.shlibs
-rwxr-xr-x  1 root root      15 2006-09-30 12:06 libssl0.9.7.prerm
-rwxr-xr-x  1 root root      15 2006-09-30 12:06 libssl0.9.7.preinst
-rwxr-xr-x  1 root root     321 2006-09-30 12:06 libssl0.9.7.postrm
-rwxr-xr-x  1 root root    3866 2006-09-30 12:06 libssl0.9.7.postinst
-rw-r--r--  1 root root     739 2006-09-30 12:06 libssl0.9.7.md5sums
-rw-r--r--  1 root root  128451 2006-10-05 13:18 mailman.list
-rw-r--r--  1 root root   50056 2006-10-05 13:18 libssl-dev.list
-rw-r--r--  1 root root     507 2006-10-05 13:18 libssl0.9.7.list
-rw-r--r--  1 root root   17073 2006-10-05 13:18 openssl.list
-rw-r--r--  1 root root   30210 2006-10-05 19:08 mozilla-thunderbird.list

I remember seeing the bug only while doing the late two updates, the 2006-10-05 13:18 and the 2006-10-05 19:08. The only special thing on that machine is that it is NFS root, but I usualy don't have problem with that (expect that I have to use user space NFS instead of kernel space NFS for re-exporting).

Any hit how to work around this problem ?
--
Jean-Christian de Rivaz


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to