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

Nicolás Reynolds fauno at kiwwwi.com.ar
Sun Apr 7 15:26:14 GMT 2013

labs at parabola.nu writes:

> Issue #314 has been reported by mtjm.
> ----------------------------------------
> Bug #314: have per-user staging dirs to support concurrent librerelease runs
> https://labs.parabola.nu/issues/314
> Author: mtjm
> Status: open
> Priority: bug
> Assignee: 
> Category: 
> Target version: 
> Example cases when it's needed:
> * Alice uploads a new KDE release, after hours of uploading
> kdeartwork-wallpapers the network breaks, Bob runs librerelease on a
> single small package, db-update removes kdeartwork-wallpapers, Alice
> spends hours resending it.

> * Alice uploads packages while new ones are building, rsync uploads
> some found after the signing is done, Bob uploads another package and
> db-update run by Bob fails due to missing signatures for Alice's
> packages.
> There are more specific bugs in these cases and it's possible for
> others to be found.  All of them involve different users running
> librerelease and db-update, so using a different staging directory for
> each user and making db-update run on only one such staging directory
> would solve them and doesn't need more complex changes.

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.

it would be better to make db-update ignore rsync tmp files on cleanup
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20130407/287ffaef/attachment.sig>

More information about the Dev mailing list