* Mark Purcell [Sun, 08 Mar 2009 15:56:48 +1100]: > Hi Dato,
Hola! > > * secondly, regarding libosip2-4, it is indeed a very small > > transition, though it would get itself tied to the ffmpeg transition > > via linphone. Can you upload it to experimental first to check > > everything rebuilds fine? > libosip2-4 has been in experimental since Nov (3.2.0). There is a new > upstream release available (3.3.0) but that doesn't change soname, so no > transition necessary, unless I upload the new upstream to unstable. rdepends > are bayonne & siproxd & linphone which are all good to go. Of course bayonne > is also tied to the libcommoncpp2 transition ;-) But I think that is almost > clear now. Okay. With "which are all good to go", you mean you have knowledge they'll rebuild fine against libosip2-4? If so, please go ahead and upload at your earliest convenience and let us know when you've done so in order to schedule Bin-NMUs. I guess you'll be uploading libexosip2 as well? > > * finally, does the new linphone fix the FTBFSes that can be seen at > > https://buildd.debian.org/~luk/status/package.php?p=linphone? And, > > can it be uploaded without uploading libosip2-4 unstable (in case > > we'd need to do that)? > Yes the new linphone fixes the FTBFS and does build correctly with > libosip2-3. > However don't we want to sequence the rdepends sourceful uploads in the > correct order to minimise the revisiting of binNMUs. If I upload linphone > without first clearing libosip2-4, then I will need to request a binNMU for > linphone later. Or am I missing something? The point was that if the libosip2-4 transition was going to add "mess" to unstable, as in unbuildable packages, I'd rather wait. But see my question above. > > Thanks in advance for your answers and for contacting us, and for > > patiently waiting our response. > A guide/ howto would be useful for this new way of working. As I > couldn't find this new process documented anywhere. > Something like a library transition howto: > 1. soname bump? check with debian-release - await ack. > 2. upload rdepends in sequence, await NEW & builds on all archs until the > next > sequence is complete. upload next rdepends. cycle on 2 until all sourceful > uploads complete > 3. request bunNMU for non sourceful uploads > 4. feel free to upload to experimental at any time. Yes, this is known. I've promised in the past to write a document about library maintenance, and it would cover all this as well. I've already started writing it some weeks ago, thought it's going to take a bit more until it's finished. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Listening to: Family - Viaje a los sueños polares -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
