Forwarding to the list.
pgp49b9li6ayr.pgp
Description: PGP signature
--- Begin Message ---> so the problem is that alice has to upload 3 big packages, connection is > lost after 1.5 packages being uploaded, bob releases the first one > (db-update ignores the temp file) but alice doesn't notice because the > failed sync doesn't know it has to skip the first (it's not there > anymore so rsync uploads it) and continue from the second. the result > is alice uploading 3 packages again (if connection isn't lost) and the > first package being released twice, no?It is; instead of releasing twice, the second db-update will error. > i think it would be simpler to lock the stage area until all uploads are > done. One of librerelease runs that I did for the new KDE version involved 90 packages, 250 MiB of data and would take more than two hours if there were no network problems. Another user doing a similarly sized upload would wait four hours. > this doesn't avoid the problem of packages being built by two or > more packagers, which is solved by coordination (!) and librerelease > checking if a package was already released[0]. this would solve Alice > having to reupload a package and Bob missing Alice saying "i'll do > package X". This is mostly solved by removing staged packages when db-update considers them already released, except for some rare cases when fullpkg makes incorrect build ordering due to bad metadata (e.g. ruby and graphviz). > [0]: the quickest way i can think of is checking if repo returns http > code 200 by requesting the headers for the file: > > curl --head \ > > http://repo.parabolagnulinux.org/libre/os/i686/linux-libre-3.8.5-1-i686.pkg.tar.xz > \ > | head -n1 | cut -d" " -f2 It would solve only one problem and need 90 HTTP requests, maybe there are simple general solutions without too big performance issues.
Description: PGP signature
--- End Message ---
_______________________________________________ Dev mailing list [email protected] https://lists.parabolagnulinux.org/mailman/listinfo/dev
