* Sébastien Villemot <[email protected]> [2018-04-03 21:21]:
Package: dh-octave-autopkgtest
Version: 0.3.2
On Tue, Mar 27, 2018 at 09:40:49PM +0200, Sébastien Villemot wrote:
On Mon, Mar 26, 2018 at 07:42:09AM +0200, Rafael Laboissière wrote:
I messed up a little bit with the Git repo for octave-control because I did
my changes, uploaded version 3.1.0-1 to unstable and pushed my commits
without noticing that Sébastien had already done some commits. This is the
reason I uploaded version 3.1.0-2 also.
Sorry for having left the repo in a semi-finished state.
The reason is that I stumbled across a bug in dh_octave_check when updating the
package, and stopped there.
Essentially, dh_octave_check will check the version installed under
/usr/share/octave/packages, if there is one, instead of the version currently
built.
You can reproduce it easily by installing octave-control 3.0.0-5 in a chroot,
and then built octave-control 3.1.0-2 in the same chroot. You will get a build
failure.
The reason is that it does the addpath *before* doing "pkg load all" (two
times, for the .m files, then the .cc).
Swapping the order of the two seems to fix the issue. However I did not test
that it does not break the autopkgtest functionality.
Right now I don't have the time to work on a proper fix. I can open a bug
report if you want, please let me know.
Thereby opening a bug.
Could you please check whether this bug is still present in version 0.5.4
of the dh-octave package?
Thanks,
Rafael
