[opensuse-buildservice] Problem with osc ci
Hi, I got following error after osc ci: File "/usr/bin/osc", line 12, in <module> r = babysitter.run(osccli) File "/usr/lib64/python2.6/site-packages/osc/babysitter.py", line 40, in run return prg.main() File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 256, in main return self.cmd(args) File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 279, in cmd retval = self.onecmd(argv) File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 395, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib64/python2.6/site-packages/osc/cmdln.py", line 1070, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib64/python2.6/site-packages/osc/commandline.py", line 1337, in do_commit p.commit(msg) File "/usr/lib64/python2.6/site-packages/osc/core.py", line 763, in commit root = ET.parse(f).getroot() File "<string>", line 45, in parse File "<string>", line 32, in parse SyntaxError: undefined entity: line 32, column 4 Now 'osc st' shows the same amount of updated files while 'osc ci' brings up lots of unmodified files. What should I do? Bernhard -- Bernhard Walle, SUSE Linux Products GmbH, Architecture Development -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
* Bernhard Walle [2009-01-12 11:16]:
Now 'osc st' shows the same amount of updated files while 'osc ci' brings up lots of unmodified files.
What should I do?
Well, the contents seems to be up to date, but the BS doesn't build. I think that's not really a topic for that mailing list, but I'm also not sure if it's a bug for Bugzilla. Is there some address like buildservice [at] suse.de for such kind of problems? Bernhard -- Bernhard Walle, SUSE Linux Products GmbH, Architecture Development -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2009-01-12 11:16:58 +0100, Bernhard Walle wrote:
commit root = ET.parse(f).getroot() File "<string>", line 45, in parse File "<string>", line 32, in parse SyntaxError: undefined entity: line 32, column 4
This might be an issue with the commit log - I've seen something similar some time ago. But to be sure it would be nice to know the project and package.
Now 'osc st' shows the same amount of updated files while 'osc ci' brings up lots of unmodified files.
What should I do?
About which project and package are you talking? Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
* Marcus Hüwe [2009-01-12 18:21]:
On 2009-01-12 11:16:58 +0100, Bernhard Walle wrote:
commit root = ET.parse(f).getroot() File "<string>", line 45, in parse File "<string>", line 32, in parse SyntaxError: undefined entity: line 32, column 4
This might be an issue with the commit log - I've seen something similar some time ago. But to be sure it would be nice to know the project and package.
Now 'osc st' shows the same amount of updated files while 'osc ci' brings up lots of unmodified files.
What should I do?
About which project and package are you talking?
Project: Kernel:kdump Package: crash Bernhard -- Bernhard Walle, SUSE Linux Products GmbH, Architecture Development -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2009-01-13 13:25:32 +0100, Bernhard Walle wrote:
* Marcus Hüwe [2009-01-12 18:21]:
On 2009-01-12 11:16:58 +0100, Bernhard Walle wrote:
commit root = ET.parse(f).getroot() File "<string>", line 45, in parse File "<string>", line 32, in parse SyntaxError: undefined entity: line 32, column 4
This might be an issue with the commit log - I've seen something similar some time ago. But to be sure it would be nice to know the project and package.
Now 'osc st' shows the same amount of updated files while 'osc ci' brings up lots of unmodified files.
What should I do?
About which project and package are you talking?
Project: Kernel:kdump Package: crash
It seems to be caused by some encoding issue in the frontend/backend (at least I think so). When looking at line 1071 of the history log you'll see some "weird" characters instead of an '%'. Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2009-01-13 17:58:01 +0100, Marcus Hüwe wrote:
It seems to be caused by some encoding issue in the frontend/backend (at least I think so). When looking at line 1071 of the history log you'll see some "weird" characters instead of an '%'.
This is caused by the "decode_line()" method in BSFileDB.pm where it tries to decode strings from URI format. It matches the '%' and tries to decode the next characters which can't work because the stored string is already decoded. The question is if we really need this decoding at all because normally all strings which are stored in the history file are already decoded (as far as I can see in all cases when fdb_add* is called the strings are already "normalized"). Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Bernhard Walle -
Marcus Hüwe