[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-octave-devel] Octave 4.2 for stretch



On Tue, Jul 05, 2016 at 22:14:31 +0200, Rafael Laboissière wrote:
> * Rafael Laboissière <rafael@debian.org> [2016-07-04 10:38]:
> 
> > I am preparing now the release of version 4.0.3 to unstable.  After it
> > is done, I will release a version for experimental based on the
> > Mercurial sources.
> 
> Both uploads have been done.  I created a branch called "experimental" in
> Git for the version of the package based on the tip of the upstream
> Mercurial repository.  I used the following versioning schema:
> 4.1.0~hg.20160703.220033-1, which combines the date and the hg revision
> number.

Thank you.

Unfortunately the builds are all failing because of a missing dependency
on bison. In the source tarball that you imported, I see the following:

-rw-r--r-- 1  3719 Jun 30 09:35 octave-4.1.0+/libinterp/corefcn/oct-tex-parser.h
-rw-r--r-- 1  7815 Jul  1 18:40 octave-4.1.0+/libinterp/corefcn/oct-tex-parser.in.yy
-rw-r--r-- 1  7830 Jul  1 19:03 octave-4.1.0+/libinterp/corefcn/oct-tex-parser.yy
-rw-r--r-- 1 60045 Jul  1 19:03 octave-4.1.0+/libinterp/corefcn/oct-tex-parser.cc

In other words, this generated .h file is out of date compared to the
corresponding .in.yy file. You may have built the source tarball in a
directory where you had a partial build before updating from hg.

The best way to build the source tarball from hg is to first update, and
run configure and make dist in a completely clean build directory. This
avoids the presence of any old generated files whose contents may have
not changed, and therefore seem to be eternally out of date to make.

-- 
mike

Attachment: signature.asc
Description: PGP signature


Reply to: