fails to let bzr know of all files on a baz import

[Vincent.Danjean@…]

Hi, There is a Debian bug report about a problem when converting baz->bzr:

 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369699

Following the indication of the submitter, I can reproduce its bug.

I tried with the latest (development) version of tailor, but then the test fails at the begining (it seems that the bzr repository is not correctly created...)

If someone kowns how to correct this...

Best regards,

Vincent

[lele]

I did some investigation, trying out the easy recipe.

Watching the log on the console, executing tailor -D -v --configfile=case.tailor I can see the first few patches applied by baz, where effectively baz output something like

$ baz update admins@seamus.madduck.net--seamus-configs/moin--main--0--patch-1
15:24:38 [I] [Ok]
Output stream:
* checking tree for local changes
* build pristine tree for admins@seamus.madduck.net--seamus-configs/moin--main--0--base-0
* updating for new patches in archive
* build pristine tree for admins@seamus.madduck.net--seamus-configs/moin--main--0--patch-1
* applying changeset
A   {arch}/moin/moin--main/moin--main--0/admins@seamus.madduck.net--seamus-configs/patch-log/patch-1
M   farmconfig.py
Error stream:
...

but really soon starts saying

$ baz update admins@seamus.madduck.net--seamus-configs/moin--main--0--patch-3
15:25:11 [I] [Ok]
Output stream:
* checking tree for local changes
* build pristine tree for admins@seamus.madduck.net--seamus-configs/moin--main--0--patch-17
* updating for new patches in archive
* tree is already up to date

Since the BazRepository? (or better, the TlaRepository?) backend fills in the details about touched entries reading that information, the target backend obviously finds nothing interesting to do...

Any body has an hint on what's going on here?