[Pkg-octave-devel] Octave 4.2.1 in unstable?
Sébastien Villemot
sebastien at debian.org
Fri Jun 30 10:12:21 UTC 2017
Le mercredi 21 juin 2017 à 00:40 +0200, Rafael Laboissière a écrit :
> > * Sébastien Villemot <sebastien at debian.org> [2017-06-19 12:32]:
>
> > Moreover, the sundials package is in the process of being adopted by a
> > new maintainer, and a new upstream version is waiting in the NEW queue.
>
> Thanks for heads up. The answer to all our problems comes from the
> changelog in the NW queue [1]:
>
> ############################################################################
> sundials (2.7.0+dfsg-1~exp1) experimental; urgency=medium
>
> * New upstream release (Closes: #798331, #809072)
> - Upstream dropped octave support, so the "octave-sundials" package is
> gone
> [snip]
> ############################################################################
>
> That means, when sundials 2.7.0 reaches unstable, we just forget about
> octave-sundials and go ahead with the transition.
Actually, sundials 2.7 may not reach unstable soon, since currently it
is waiting in the NEW queue for reaching experimental.
Anyways, I could verify that the FTBFS of sundials is:
1) not related to octave 4.2 (it also happens with octave 4.0)
2) does not happen when building with sbuild (like on Debian buildds),
because octave can't write $HOME/.octave_hist and therefore exit before
crashing (because HOME=/sbuild-nonexistent/).
So even the current version of sundials should not an actual blocker
for the transition.
--
.''`. Sébastien Villemot
: :' : Debian Developer
`. `' http://sebastien.villemot.name
`- GPG Key: 4096R/381A7594
More information about the Pkg-octave-devel
mailing list