Comment 7 for bug 437626
Revision history for this message
| Andrew Bennetts (spiv) wrote Re: exceptions.AssertionError: second push failed to complete a fetch set | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
Hmm. That error is raised by the target repository (so, the local one in these cases), which essentially checks:
a) that all compression bases for the new data are present, and
b) if the target is stacked, that the parent inventories required for stacking correctly are present.
It's that first condition that appears to be triggering, as the missing records are (mostly) texts, rather than all inventories. But it did make me wonder if stacking is involved on the client... perhaps mixing stacked & unstacked branches in one repository might produce this...
Bug reporters: were/are you using stacked branches locally?
I haven't managed to trigger this bug yet, even mixing stacked/unstacked branches locally. I'd love to find a way to reproduce this.