| === cinerama_ is now known as cinerama | ||
| === Logan_ is now known as y | ||
| === mmrazik is now known as mmrazik|lunch | ||
| === mmrazik|lunch is now known as mmrazik | ||
| === wedgwood_away is now known as wedgwood | ||
| === mmrazik is now known as mmrazik|afk | ||
| === deryck is now known as deryck[lunch] | ||
| 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:36 |
|---|---|---|
| idnar | the branch in question is an SVN branch via bzr-svn | 18:38 |
| jelmer | hi idnar | 18:44 |
| 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:46 |
| jelmer | it tries to fetch that data into the branch, but that is not possible because the branch is read-only locked | 18:47 |
| idnar | okay, I was thinking something along those lines but wasn't familiar with the internals | 18:51 |
| idnar | should I file a bug report against...bzr-svn, I guess? | 18:52 |
| jelmer | idnar: I think this is a bug in bzr itself, in the before: revspec | 18:54 |
| jelmer | idnar: it just happens to be triggered by bzr-svn, or this particular situation | 18:57 |
| idnar | okay, I filed https://bugs.launchpad.net/bzr/+bug/1132932 | 19:01 |
| ubot5 | Launchpad bug 1132932 in Bazaar "before: revspec trying to write to branch with read-only lock" [Undecided,New] | 19:01 |
| === deryck[lunch] is now known as deryck | ||
| jelmer | thanks idnar | 19:14 |
| === wedgwood is now known as wedgwood_away | ||
| === wedgwood_away is now known as wedgwood | ||
| jelmer | idnar: it should be possible to work around the issue by simply forcing a write lock in bzr log | 19:32 |
| idnar | apparently it's been worked around by using a different revspec that accomplishes the same thing | 19:33 |
| bamvac | I'm getting error "No module named xml.parsers.expat" when trying to `bzr init-repo ProjectX` | 22:10 |
| bamvac | `zypper in expat` was successful, but problem persists | 22:16 |
| === _thumper_ is now known as thumper | ||
| jelmer | bamvac: sounds like you are missing an xml library | 22:21 |
| jelmer | bamvac: how did you install bzr? | 22:21 |
| bamvac | I built the OS with suseStudio using a JeOS base image. I'm rebuilding another using the Server base now. | 22:24 |
| bamvac | jelmer: do you suggest I include bzr with the selected software, or install it after configuring the OS? | 22:29 |
| spiv | bamvac: that module is part of the standard python installation IIRC | 22:31 |
| 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:32 |
| bamvac | spiv: Including python-xml package solved my issue. | 22:42 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!