[Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2011-12-12 Thread Jelmer Vernooij
** Tags added: knits -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/257895 Title: bzr: ERROR: not well-formed (invalid token) To manage notifications about this bug go to: https://bugs.launchpad.ne

[Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2009-08-10 Thread Eric Siegerman
FWIW (which might not be much, this close to blessing 2a as the default format)... Attached is a simple reproduction of what I think is the same problem, using bzr.dev r4596 (which is approximately 1.18rc1, not sure exactly). I'll summarize here. (The attachment contains the requested xml_string

Re: [Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2009-06-26 Thread Martin Pool
To get the inventory you should be able to do this: in your shell, export BZR_PDB=1 run the command that fails when it errors, you should get a debugger prompt in it, type "pp xml_string" and "pp locals()" and paste the output into this bug, either directly if it's short or as an attachment if it

Re: [Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2009-06-26 Thread Martin Pool
It looks like a good next step would be to look at the extracted inventory and see whether the problem looks like on-disk corruption or something that might have originated in bzr Robert is working on a tool that can pull data back from partly-readable repositories. -- Martin

[Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2009-06-26 Thread John Seifarth
Here's a ~/.bzr.log excerpt for commit: Fri 2009-06-26 01:20:18 +0200 0.012 bzr arguments: [u'commit', u'-F', u'commit_message.txt'] 0.021 looking for plugins in /home/users/john/.bazaar/plugins 0.021 looking for plugins in /usr/lib/python2.6/dist-packages/bzrlib/plugins 0.063 encoding stdout

[Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2009-06-25 Thread Martin Pool
This might indicate drive-level corruption. Probably a good thing to do next would be to get the traceback from ~/.bzr.log and also the output of 'bzr info' in that directory. -- bzr: ERROR: not well-formed (invalid token) https://bugs.launchpad.net/bugs/257895 You received this bug notificatio

[Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2009-06-25 Thread John Seifarth
I have a similar problem. I'm running Ubuntu 9.04. I had the problem with the version included in Jaunty, as well as the more up-to-date package from http://ppa.launchpad.net/bzr/ppa/ubuntu I thought that I had a corrupt archive, since I pulled it in off a failing drive. bzr status works, as doe

[Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2009-06-15 Thread Robert Collins
This looks like invalid XML in the repository. Are you using bzr-svn or some other foreign format. Also can you run 'bzr check' please. ** Changed in: bzr Status: New => Incomplete -- bzr: ERROR: not well-formed (invalid token) https://bugs.launchpad.net/bugs/257895 You received this bug

[Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2009-06-15 Thread Jelmer Vernooij
Are there perhaps any files in the repository that contain newlines in their name? -- bzr: ERROR: not well-formed (invalid token) https://bugs.launchpad.net/bugs/257895 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mai

[Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2009-02-09 Thread Andrea Corbellini
** Changed in: bzr (Ubuntu) Importance: Undecided => Low Status: New => Confirmed ** Also affects: bzr Importance: Undecided Status: New -- bzr: ERROR: not well-formed (invalid token) https://bugs.launchpad.net/bugs/257895 You received this bug notification because you are a

[Bug 257895] Re: bzr: ERROR: not well-formed (invalid token)

2009-01-12 Thread Sascha Peilicke
Confirmed, I have the same error here. -- bzr: ERROR: not well-formed (invalid token) https://bugs.launchpad.net/bugs/257895 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https