[Dev] [Libretools - Bug #314] (open) have per-user staging dirs to support concurrent librerelease runs

Michał Masłowski mtjm at mtjm.eu
Sun Apr 7 15:42:50 GMT 2013

> what will happen when two concurrent db-update try to write the same
> repo.db file, and one doesn't know the other modified it?  you'll have
> packages missing from repos but correctly released.

Isn't this solved by locking the repos?

> it would be better to make db-update ignore rsync tmp files on cleanup
> IMO.

Doesn't rsync make each file non-tmp when it's complete before sending
other files?  It won't help in these cases, although I'm not sure now if
they are possible.

Shouldn't this be discussed at labs.parabola.nu?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20130407/f2aad520/attachment.sig>

More information about the Dev mailing list