Ok, i've reroduced the bug, i've downgraded locales and upgraded again, and I get the same errors, in this time, just generating locales with locale-gen solved the problem (without rebooting)
I am using the kernel 2.6.32-4-686 wich was in sid, ( i've just noticed there isn't any longer). I am going to install the latest kernel from sid 2.6.32-5-686 reboot the system and try again to see if i can reproduce it with the last kernel. thanks iker El 26 de mayo de 2010 22:07, Aurelien Jarno <aurel...@aurel32.net> escribió: > On Wed, May 26, 2010 at 09:31:57PM +0200, Iker Salmón San Millán wrote: > > El 26 de mayo de 2010 21:10, Aurelien Jarno <aurel...@aurel32.net> > escribió: > > > > > > > > > > > Actually it may come from new dpkg features. Do you know which version > > > of dpkg was installed at the time of the problem? > > > > > > -- > > > Aurelien Jarno GPG: 1024D/F1BCDB73 > > > aurel...@aurel32.net http://www.aurel32.net > > > > > > > > > Yes, > > dpkg version: 1.15.7.1 > > > > I think it may be an isolated error, my sister's and my girlfriend's > > computers have the same instalation[1] with the same apt-policy and after > I > > rebooted my system and corrected the error I upgraded their computer and > the > > problem did not appear in any case. > > > > If you are interested in it i can try to downgrade locales package and > try > > the upgrade again to see what happen. I don't have the old package in > > /var/cache, but I've readed that there is now kind of archive with all > > versions of packages and I could find it. But if no one else has > reported > > this ... anyway, if I can help debbugind the problem just ask me, this > is > > the only way I can colaborate with debian project rigth now and I really > > want to (colaborate). > > You can try, (the old package should still be on snapshot.debian.org), > but I really doubt you will be able to reproduce it. > > I have discussed with the dpkg developers, providing them the info you > gave me, but it seems very unlikely to be a problem there. In the worst > case scenario, the files would still contains the old content, which > should have been identical (and thus not buggy). > > It is most probably a bug in the kernel, I encourage you to upgrade to > your kernel to the latest version in sid, especially if you are using an > SSD, as it contains a few ext4 fixes. > > -- > Aurelien Jarno GPG: 1024D/F1BCDB73 > aurel...@aurel32.net http://www.aurel32.net >
