Mailinglist Archive: opensuse-buildservice (216 mails)

< Previous Next >
Re: [opensuse-buildservice] Interrupted commits
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Mon, 15 Mar 2010 16:42:36 +0100
  • Message-id: <201003151642.36966.adrian@xxxxxxx>
Am Montag, 15. März 2010 16:24:26 schrieb Guido Berhoerster:
* Adrian Schröter <adrian@xxxxxxx> [2010-03-15 15:59]:
Am Montag, 15. März 2010 15:15:15 schrieb Guido Berhoerster:
what happens when a commit is interrupted? Recently, the upload
of a large source file during a commit was interrupted so I
repeated the commit and this time the commit appeared to succeed,
however there are now inconsistencies on the server, in
* osc ls -l project package shows no sources at all,
* osc diff shows all local sources as new,
* the build fails, in this case with "no source uploaded" (in a
previous case with "failed to determine a packager: no person
with role bugowner or maintainer for project/package")m
* the webinterface on the other hand shows all sources, and
* osc cat project package file allows me to download files.

The only way to resolve this seems to delete and recreate the
package. What's going on here? Can the package be fixed on the
server in such a case?

It depends a bit how you upload the sources, but the general osc
case is that each new file get uploaded to the "upload" revision.
After uploading all files, a "commit" transaction is running,
telling the server which exact files to be taken for commit X.

If an upload failed, you may have some files in upload revision.
Depending on your tool, you may see them or not (if it shows upload
revision or last committed one).

"no source uploaded" is still true, even when you have files uploaded,
but no commit happened yet.

Hint: run "osc -d ..." to see what calls a particular call is doing.

OK, I see. It was a new package, thus there were no previous
revisions of files. But the thing is after the first upload
failed I just repeated the same commit, it was completed
successfully and I still got those "no source uploaded". How do I
complete the commit transaction then? Is the commit transaction
itself (after the upload) atomic?


Or how come I got this "failed
to determine a packager" in another case?

If the commit did not succeed, but osc is not doing it again on next try,
we have a bug.

What is "osc log" telling you ? Does a commit log entry exists ?


Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups