Comment 6 for bug 632704
Revision history for this message
| Vincent Ladeuil (vila) wrote Re: After upgrading from 1.10 to 2.2.0 I get "unversioned parent" on one particular repository | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
> Does this information help you?
Yes. But not enough to translate new-141 and new-162 into paths :-/
> The contents from stdout show that nmap and snmp (both 3rd party binaries) seem to be out of synch with the repository:
Well, no. 'bzr st' reports about changes between your working tree and the revision its basis revision. It does not report about the changes
between this revision and master branch on the server. 'bzr missing' can tell us that.
'bzr missing -v' will tells us what changes 'bzr update' fails to bring in, if they are files or directories modified on one side and deleted on the other we may be able to guess which combination is failing and try to reproduce the problem.
Now your working tree contains *a lot* of uncommitted changes so 'bzr update' has even more work to do, to work around the problem, I'd commit first and *then* do the update, or shelve/