On Mon, Aug 03, 2015 at 12:53:29PM +0300, Vladimir Stavrinov wrote:
> AND REMOVE such references. But if You ALREADY have found it, what
> prevents You to remove it at this point, at this moment?
Sorry for "pushy" again, but to be clear, the question caused this
conversation is: what for do You s
On Mon, Aug 03, 2015 at 11:57:40AM +0300, Lars Wirzenius wrote:
> > The question was not "why it isn't done YET", but why they are not
> > removing at all, thinking it is a bug. And Yes, if You treat bug as
> > "missing feature", then there are less chances that "it happen faster"
> > to fix it.
>
On Mon, Aug 03, 2015 at 11:51:58AM +0300, Vladimir Stavrinov wrote:
> On Mon, Aug 03, 2015 at 09:53:03AM +0300, Lars Wirzenius wrote:
>
> > fsck does, indeed, not remove references to missing chunks. It's a
> > missing feature. That feature will be implemented when someone has the
> > time and inc
On Mon, Aug 03, 2015 at 09:53:03AM +0300, Lars Wirzenius wrote:
> fsck does, indeed, not remove references to missing chunks. It's a
> missing feature. That feature will be implemented when someone has the
> time and inclination to do it.
>
> Asking why it isn't done yet does not make it happen f
On Mon, Aug 03, 2015 at 09:30:06AM +0300, Vladmimir Stavrinov wrote:
> This means that fsck command does nothing and repository remains
> broken. Why this command does not remove references pointing to
> nonexistent chunk when it finds such ones?
fsck does, indeed, not remove references to missing
Package: obnam
Version: 1.13-1
Severity: normal
Dear Maintainer,
The problem with nonexistent chunks still exists. I have tried to run Your
software few times with options:
--fsck-fix --fsck-rm-unused --no-fsck-ignore-chunks --no-fsck-skip-dirs
--no-fsck-skip-files --no-fsck-skip-generations
6 matches
Mail list logo
