[18:36] <idnar> anyone know what would cause the error seen at https://buildbot.twistedmatrix.com/builders/debian-easy-no-zope-py2.6-epoll/builds/186/steps/bzr-svn/logs/stdio ?
[18:38] <idnar> the branch in question is an SVN branch via bzr-svn
[18:44] <jelmer> hi idnar
[18:46] <jelmer> idnar: so, it looks like for some reason the revspec is trying to get a write lock while the branch is read-only locked
[18:46] <idnar> hi jelmer
[18:46] <jelmer> idnar: actually, it seems like this is being triggered by ghosts
[18:46] <jelmer> so the revspec (before:) is trying to use some revision data that is not present in the svn branch
[18:47] <jelmer> it tries to fetch that data into the branch, but that is not possible because the branch is read-only locked
[18:51] <idnar> okay, I was thinking something along those lines but wasn't familiar with the internals
[18:52] <idnar> should I file a bug report against...bzr-svn, I guess?
[18:54] <jelmer> idnar: I think this is a bug in bzr itself, in the before: revspec
[18:57] <jelmer> idnar: it just happens to be triggered by bzr-svn, or this particular situation
[19:01] <idnar> okay, I filed https://bugs.launchpad.net/bzr/+bug/1132932
[19:14] <jelmer> thanks idnar
[19:32] <jelmer> idnar: it should be possible to work around the issue by simply forcing a write lock in bzr log
[19:33] <idnar> apparently it's been worked around by using a different revspec that accomplishes the same thing
[22:10] <bamvac> I'm getting error "No module named xml.parsers.expat" when trying to `bzr init-repo ProjectX`
[22:16] <bamvac> `zypper in expat` was successful, but problem persists
[22:21] <jelmer> bamvac: sounds like you are missing an xml library
[22:21] <jelmer> bamvac: how did you install bzr?
[22:24] <bamvac> I built the OS with suseStudio using a JeOS base image. I'm rebuilding another using the Server base now.
[22:29] <bamvac> jelmer: do you suggest I include bzr with the selected software, or install it after configuring the OS?
[22:31] <spiv> bamvac: that module is part of the standard python installation IIRC
[22:32] <spiv> bamvac: so I guess make sure that your OS build includes that part of Python (for simplicity, I'd just make sure it has the whole Python standard library; it's not very large)
[22:42] <bamvac> spiv: Including python-xml package solved my issue.