Rafael Laboissiere <rafael@laboissiere.net> writes: > This morning, after an upgrade of my Debian testing system, I got > octave3.2_3.2.4-12+b1 installed. I assume that the HDF5 transition is > over, at least as regards Octave. Yes, the whole transition is over, so the sky is now clear for an upload of octave 3.4 to unstable. I guess Thomas will do that when he gets the time. We have yet to decide whether to upload 3.6.1 before or after all the octave-forge packages. I think we should upload 3.6.1 first if it turns out that packaging it is easy (and it should be). I will check that if I get the time. > I guess you could soon upload 3.4.3 to unstable (or maybe even 3.6.1). I > checked the relationships for this version of the package and saw that it > conflicts with octave3.2. Would that be enough to get a smooth > transition? According to the Policy manual [1], we might also add a > "Replaces: octave3.2" relationship. I am not really sure about this, > since this can potentially break some code from our users, due to > possible incompatibilities between 3.2 and later versions. Thanks for pointing this. Indeed policy §7.6.2 indicates that, in our case, we should have both Conflicts and Replaces. I pushed that change. > It is time also for updating the Octave-Forge packages. I wish I had > time for participating again to the DOG. At any rate, I was looking at > the octave-pkg-dev package and spotted a harmless bug, fixed in the patch > attached below. Thanks, I pushed your patch. -- Sébastien Villemot Researcher in Economics & Debian Maintainer http://www.dynare.org/sebastien Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
Attachment:
pgpLLxyioKckz.pgp
Description: PGP signature