On 28-07-15 16:15, Alastair McKinstry wrote: > Are we proceeding with the netcdf transition?
Not yet, but we're getting close. I'm in the process of testing the reverse dependencies with the new netcdf packages, and filing bugs for any issues encountered. This is one of those bugs to keep track of what changes are still needed in preparation for or after the start of the netcdf transition. > As of now, this would need to be built in experimental (I have done so > and it works). Correct. I suggest to upload an experimental revision of magics++ with the changes for this issue to experimental for now as you've also done for your other netcdf related packages. Don't upload any changes to unstable that require the new netcdf packages in experimental before you get the go-ahead from the Release Team. > Should we upload netcdf 4.4.0 to unstable? I would be in favour of this, > but we should probably checking with the release managers. When I'm done with my round of rebuilds for the netcdf transition, I'll formally request a transition slot from the Release Team. The new netcdf package will remain in experimental until we get the go-ahead from the Release Team. Then we first need to upload netcdf to unstable, followed by netcdf-cxx, netcdf-cxx-legacy & netcdf-fortran built with the new netcdf for unstable. I'll coordinate the netcdf transition with the Release Team to avoid the problems of uncoordinated transitions. An outstanding question for the netcdf transition is if it will precede the GCC 5 & libstc++ transitions or if it will be triggered by it. For the GCC 5 related transitions we still need to update the symbols files. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
