[braindump] ppa update discontents

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...
>> One approach to the lag in soyuz builds is to test build every package
>> locally, before uploading.  This seems like a bit of an unnecessary
>> kludge, but perhaps it's the most sensible thing for now.
> 
> (Should read the email once before replying :-)
> 
> Why do you consider it a kludge?

I would imagine the permutations hurt here. 10 packages across 5 distro
series means that you need 5 pristine chroots, and a lot of manual labor
time.


> 
>> Our process at the moment is to upload everything into
>> <https://launchpad.net/~bzr/+archive/+proposed> before then promoting
>> it to the regular archive, so that we don't break dependencies between
>> packages.  (Uploading a bzr newer than the plugins support might make
>> them uninstallable, and unlike the main archive(?) ppas don't
>> themselves check for this.)  I think the basic approach of using a
>> staging archive is ok.  We ought to be able to script something that
>> does both the check and the promotion if it succeeds.
> 
> The main archive does not check for this.

I imagine you have some amount of chicken-and-egg problem. If you upload
X that depends on Y, you can't upload either if it would cause it to be
unstable. So you have to allow it to be unstable so you can finish
uploading stuff. I would guess it is slightly easier because uploading
v1.1.1 doesn't immediately remove v1.1.0 from availability (IMBW).

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxv/VIACgkQJdeBCYSNAAOslQCfTx4mGv2cdcWvesoz6yIt3qpg
P3AAn2D3ZQWT5FAq1tJQnaPhB04p36GM
=Ucmi
-----END PGP SIGNATURE-----