Re: Transitioning to 4.04 or 4.05
Stéphane Glondu:
> On 02/07/2017 13:18, Ximin Luo wrote:
>> Hey guys, as you know I uploaded 4.04 to experimental a few months ago. 4.05 has been "due" for a few months, I guess it will be out "any day now".
>>
>> Now that the freeze is over, it would be good to start transitioning various packages across to the new compiler version. I know roughly the process is to build stuff in experimental, make sure they are fine, then issue a transition request to the release team.
>
> Usually I rebuild all the packages on my (amd64) machine. We don't "rebuild everything once in experimental, then in unstable" as that would entail many sourceful uploads and we want to minimize them and use binNMUs instead.
>
> I think we can issue the transition request for 4.04.2 now. The 4.04.x series has been out for quite a time, and I believe broken packages must have been fixed upstream now. I would wait a bit for the 4.05.x series. What's your opinion on the matter?
>
I think it's nicer for users to be as up-to-date as possible, especially for Debian unstable. But I don't know what the cost is here - if it would be too much work, or too disruptive, being blocked on 4.05 build failures.
What was your experience with previous transitions? My vague impression was that, because everyone has OPAM, most things would get fixed in a few weeks, and it would likely take us at least that long to do the transition anyways.
>> Are there any scripts to help us do that for the hundreds of ocaml packages that we have?
>
> I haven't (yet) published clean scripts for the local rebuild, but the general idea is to recompile all packages in the same order as in [1]: build one level (using cowbuilder), put the result in a local repository, build the next level, update the local repository with the result, etc. and use the local repository thoughout all the process.
>
We could try to distribute this, I have a decently-powerful new machine. We could set up a mini-dinstall repo on Alioth and upload stuff there.
> For the transition itself, there is no specific script or automation, we basically follow [1]. Schedule one level of binNMU, make sure they compile and/or upload updated packages, wait for the level to be sufficiently completed, then go to the next level, etc.
>
> [1] https://release.debian.org/transitions/html/ocaml.html
>
X
--
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git
Reply to: