"incorrect number of lines" while reading an inventory knit strongly suggests that this is likely to be a duplicate of, or at least related to, bug 3918. Can you take a look at the XML in the error message and see if there appears to be a newline somewhere inside an attribute, e.g.
name="foo
bar"
?
Also, just to be clear, by "commit the first revision" you mean this is a completely new bzr branch (e.g. "bzr init; bzr add; bzr commit") with no prior revision history? I ask because some earlier versions of bzr, depending on how they were installed, might generate and save inventory XML that causes this error when read back in — but current versions should trigger a more appropriate error than KnitCorrupt, and they should trigger it before the invalid inventory XML gets written to disk. So it's surprising that you're reporting a KnitCorrupt here with 1.7.1.
In the meantime I'm marking this as High priority, as KnitCorrupt errors are very alarming.
"incorrect number of lines" while reading an inventory knit strongly suggests that this is likely to be a duplicate of, or at least related to, bug 3918. Can you take a look at the XML in the error message and see if there appears to be a newline somewhere inside an attribute, e.g.
name="foo
bar"
?
Also, just to be clear, by "commit the first revision" you mean this is a completely new bzr branch (e.g. "bzr init; bzr add; bzr commit") with no prior revision history? I ask because some earlier versions of bzr, depending on how they were installed, might generate and save inventory XML that causes this error when read back in — but current versions should trigger a more appropriate error than KnitCorrupt, and they should trigger it before the invalid inventory XML gets written to disk. So it's surprising that you're reporting a KnitCorrupt here with 1.7.1.
In the meantime I'm marking this as High priority, as KnitCorrupt errors are very alarming.