https://bugzilla.novell.com/show_bug.cgi?id=441783 Summary: package remains in revision 'upload' Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: mls@novell.com ReportedBy: poeml@novell.com QAContact: adrian@novell.com CC: abauer@novell.com, mrueckert@novell.com Found By: --- This is an old bug, I believe. And it's actually two bugs, I believe, but the second is triggered by the first. 1) the buildservice (or iChain) returns garbage (an empty reply I think). 2) the buildservice keeps the package in revision 'upload' and there it seems to stay. % osc ci -m "use --record-rpm instead of --record" Sending python-mechanize.spec Transmitting file data .Traceback (most recent call last): File "/suse/poeml/bin/osc", line 12, in ? r = babysitter.run(osccli) File "/suse/poeml/osc-trunk/osc/babysitter.py", line 40, in run return prg.main() File "/suse/poeml/osc-trunk/osc/cmdln.py", line 256, in main return self.cmd(args) File "/suse/poeml/osc-trunk/osc/cmdln.py", line 279, in cmd retval = self.onecmd(argv) File "/suse/poeml/osc-trunk/osc/cmdln.py", line 395, in onecmd return self._dispatch_cmd(handler, argv) File "/suse/poeml/osc-trunk/osc/cmdln.py", line 1070, in _dispatch_cmd return handler(argv[0], opts, *args) File "/suse/poeml/osc-trunk/osc/commandline.py", line 1321, in do_commit p.commit(msg) File "/suse/poeml/osc-trunk/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: no element found: line 1, column 0 [2] 5292 exit 1 osc ci -m "use --record-rpm instead of --record" poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % osc ci -m "use --record-rpm instead of --record" Working copy '/suse/poeml/pac/opensuse/devel:languages:python/python-mechanize' is out of date (rev 7 vs rev upload). Looks as if you need to update it first. [2] 5307 exit 1 osc ci -m "use --record-rpm instead of --record" poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % osc up At revision upload. poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % l total 244 -rw-r--r-- 1 poeml suse 240993 2008-02-12 17:02 mechanize-0.1.7b.tar.gz -rw-r--r-- 1 poeml suse 2443 2008-11-05 12:04 python-mechanize.spec poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % osc ci -m "use --record-rpm instead of --record" nothing to do for package python-mechanize poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % osc st poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % osc up At revision upload. poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % osc info Project name: devel:languages:python Package name: python-mechanize Path: /suse/poeml/pac/opensuse/devel:languages:python/python-mechanize API URL: https://api.opensuse.org Source URL: https://api.opensuse.org/source/devel:languages:python/python-mechanize srcmd5: upload Revision: upload Link info: None poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % grep -r upload . /.osc/_files:<directory name="python-mechanize" rev="upload" srcmd5="upload"> poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % osc -d up GET https://api.opensuse.org/source/devel:languages:python/python-mechanize GET https://api.opensuse.org/source/devel:languages:python/python-mechanize/_met... At revision upload. poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % osc req https://api.opensuse.org/source/devel:languages:python/python-mechanize <directory name="python-mechanize" rev="upload" srcmd5="upload"> <entry name="mechanize-0.1.7b.tar.gz" md5="7d431ccec4e64063c7378ce3be53ea34" size="240993" mtime="1202832123" /> <entry name="python-mechanize.spec" md5="9c7bc824710b982f560432b322cc9fac" size="2443" mtime="1225883087" /> </directory> poeml@batavia510 ~/bs/devel:languages:python/python-mechanize % Is there a way that the buildservice could notice that the package wasn't fully committed, and remove the upload revision? I wonder whether osc could do such a cleanup now. I also wonder whether osc could do a cleanup right away, when it runs into a bug and can't commit to the end. However, the stupid bug is very hard to reproduce, so I'm not sure how to tackle it. Micha, I thought I assign this bug to you for the moment because you might have wise input to the above questions. (But in the end, the garbage returned by the api (or the proxy) should be fixed as well.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.