Filesystem ext4

thanks

El 26 de mayo de 2010 21:31, Aurelien Jarno <[email protected]> escribió:

> On Wed, May 26, 2010 at 09:10:25PM +0200, Aurelien Jarno wrote:
> > On Wed, May 26, 2010 at 09:03:10PM +0200, Aurelien Jarno wrote:
> > > On Tue, May 25, 2010 at 03:10:49PM +0200, Iker Salmón San Millán wrote:
> > > > I am sorry, i am messing it up with the [email protected].  I am
> starting
> > > > to underestand how works the bugs list.
> > > >
> > > > i guess i have to send to you my emails (just in this case with this
> bug)
> > > > ????
> > >
> > > To me and [email protected]. Usually a reply to all works.
> > >
> > > > Ok, rebooting and regenerating locales with #locale-gen solved the
> problem.
> > > > I don't know what caused the first error, maybe the order of
> configuring the
> > > > packages upgraded?
> > >
> > > The order of the packages should not have any effect, especially given
> > > the upstream version is the same before and after the upgrade.
> > >
> > > > I am sorry i did not try to regenerate the locales without rebooting,
> i
> > > > don't know if it was really necesary rebooting the system.
> > >
> > > The log you sent in the bug report clearly show that the content of the
> > > file was corrupted. OTOH, the content of the file seemed to be correct
> > > before you reboot (at least from the md5sum).
> > >
> > > I have no idea what could have caused that.
> > >
> >
> > Actually it may come from new dpkg features. Do you know which version
> > of dpkg was installed at the time of the problem?
> >
>
> Also which filesystem are you using?
>
> --
> Aurelien Jarno                          GPG: 1024D/F1BCDB73
> [email protected]                 http://www.aurel32.net
>

Reply via email to