bzr cat does not work in knitpack repo: lock required

Alexander Belchenko bialix at ukr.net
Sat Nov 17 00:41:41 GMT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel пишет:
> Alexander Belchenko wrote:
>> Robert Collins ?8H5B:
>>> On Sat, 2007-11-17 at 01:11 +0200, Alexander Belchenko wrote:
>>>> It's really annoying. Something should be decided for this locking watershed.
>>> Well, I'm happy to discuss proposals. But at the moment I think the
>>> thing to do is for early adopters to report issues, and us to fix them.
>> I wonder if we can just temporarily make knitpack format as default and run
>> at least blackbox tests to see what tests will fail. Probably some obvious
>> places will be caught automatically?
> 
> It is pretty easy to do
> 
> bzrlib.bzrdir.format_registry.set_default('knitpack-experimental')
> 
> (or just change the very last line in the file.)
> 
> That would certainly be required before we ever make knitpack the default
> format. But since Robert has strong plans to evolve the format anyway, I'm
> guessing we won't be making packs the default for a few months.

But broken commands make dogfooding painful and force me to fallback to knit repo,
because I can't wait several months. That's why I said that some decision would
be desirable.

I wonder why places like broken commands was not caught by test suite? Just because
some commands lacks tests, or because format is not default? If latter, then
probably we need extend or parametrize even blackbox tests to have ability
for testing new experimental formats while they will be evolving.
Am I wrong here?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHPjjFzYr338mxwCURAhoqAJ9cUHADAMBqBJ5EP9trmbxx1TBHPgCfW31t
XPBQsPOludvBpYKcItmpL4M=
=/Guo
-----END PGP SIGNATURE-----



More information about the bazaar mailing list