Re: [Pkg-octave-devel] octave transitions
On Thu, Jul 09, 2015 at 12:26:10 +0200, Rafael Laboissiere wrote:
> * Rafael Laboissiere <rafael@laboissiere.net> [2015-07-09 00:13]:
> >Yes, this is not needed for now. We are delaying the upload of Octave 4.0
> >to unstable because this will trigger the liboctave3 transition, but the
> >octave package is itself involved in three other transitions (hdf5,
> >suitesparse, and graphicsmagick)
>
> We should add libstdc++6 to the list.
>
> I am wondering how we should proceed now. Should we wait until all those
> transitions are completed before we upload Octave 4.0 to unstable?
Maybe ask the release team if one way or the other makes their job
easier? OTOH that's a lot of transitions and if we wait we may not even
get to a new Octave before the end of the year.
Should we start working through rdeps of octave to see which packages
need to be patched or updated to work with 4.0?
> Another question: does somebody now how the auto-* transitions are
> triggered? Is it a fully automatic process?
I think the release team still requires a transition bug be filed for
their workflow.
--
mike
Reply to: