#60: fails to let bzr know of all files on a baz import
-------------------------------------------+--------------------------------
Reporter: [EMAIL PROTECTED] | Owner: lele
Type: defect | Status: new
Priority: major | Milestone: VersionOne
Component: tla | Version: 0.9
Resolution: | Keywords:
-------------------------------------------+--------------------------------
Changes (by lele):
* component: tailor => tla
Comment:
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 [EMAIL PROTECTED]/moin--main--0--
patch-1
15:24:38 [I] [Ok]
Output stream:
* checking tree for local changes
* build pristine tree for [EMAIL PROTECTED]/moin--
main--0--base-0
* updating for new patches in archive
* build pristine tree for [EMAIL PROTECTED]/moin--
main--0--patch-1
* applying changeset
A {arch}/moin/moin--main/moin--main--0/[EMAIL PROTECTED]
--seamus-configs/patch-log/patch-1
M farmconfig.py
Error stream:
...
}}}
but really soon starts saying
{{{
$ baz update [EMAIL PROTECTED]/moin--main--0--
patch-3
15:25:11 [I] [Ok]
Output stream:
* checking tree for local changes
* build pristine tree for [EMAIL PROTECTED]/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?
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/60>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
