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

Re: lintian warning native-package-with-dash-version

On Thu, 29 Sep 2005, Justin Pryzby wrote:

On Thu, Sep 29, 2005 at 11:00:47PM -0400, kamaraju kusumanchi wrote:
Marc 'HE' Brockschmidt wrote:
You might consider using the -v option in dh_make to
convert this to a compliant version number.  The second -1 will still be
there in the final package because that is the debian revision.  The
cause that lintian has suggested does not seem to be your case as you
properly identified the source tarball in the dh_make command.

The dh_make command has nothing to do with the places where
dpkg-buildpackage searches for sources. This is *always*
../${NAME}_${UPSTREAM_VERSION}.orig.tar.gz, no matter how you called

But the thing is that the upstream version is 0.2.2-1 and the name of
the .orig.tar.gz created is gnuplotfortran-0.2.2_1.orig.tar.gz  which is
not exactly {NAME}_{UPSTREAM_VERSION}.orig.tar.gz . I think lintian is
looking for something like gnuplotfortran-0.2.2-1.orig.tar.gz and since
it is not finding such a file, it is giving the above error. Is there a
way to do create gnuplotfortran-0.2.2-1.orig.tar.gz instead of
You can do whatever you have to do to create the .orig.tar.gz.
dh_make is a tool which is to be used precisely once for each package,
and if you have an alternate way of getting where you should be, then
that is just as fine as the dh_make way.  Upstream names are allowed
to have hyphens in them.  I don't know about upstream versions,
though..  lintian might be looking for a package called
gnuplotfortran-0.2.2 whose version is 1?

This is exactly how dh_make interprets it. Another issue is that this is a library and dh_make builds a control file with two binary packages. One is a -dev package and the other is reported as gnuplotfortran-0.2.2BROKEN and dh_make tells you to fix it to gnuplotfortran-0.2.21 or something. I have not tried to build library packages before so I am not sure why this is happening.

You can find more information on library packaging at


I took a look at the sourceforge project page and it is not clear whether the upstream intends the -1 to be a version number or something else like a patch level. I see -0.2 -0.2.1 -0.2.2 and then -0.2.2-1. It looks like there needs to be careful naming consideration here.


Carlo U. Segre -- Professor of Physics
Associate Dean for Special Projects, Graduate College
Illinois Institute of Technology
Voice: 312.567.3498            Fax: 312.567.3494
Carlo.Segre@iit.edu    http://www.iit.edu/~segre

Reply to: