[Debian-med-packaging] Bug#806743: figtree: version installed is older than advertised

Andreas Tille andreas at fam-tille.de
Tue Dec 1 07:48:14 UTC 2015


Hi Joseph,

thanks for your bug report and trying to enhance Debian.

Please see my comments to your report inline.

On Mon, Nov 30, 2015 at 01:18:05PM -0500, Joseph W. Brown wrote:
> Package: figtree
> Version: 1.4-2
> Severity: normal
> 
> Dear Maintainer,
> 
> The version of `figtree' advertised is 1.4-2, but the installed version is
> instead 1.4-1.
> 
> Fix: installation should involve the proper version of the package.
> 
> Below is a transcript demonstrating the problem.
> 
> ## search
> $ apt-cache show figtree
> Package: figtree
> Version: 1.4-2

You have installed the Debian package revision number 2 (the '-2' at the
end of the version string) of the figtree version that was downloaded as
version 1.4 according to the version number in the download archive.
Please note that the number behind the last dash is not connected to the
upstream version.  You can read about the changes between this Debian
revision and the previous one (1.4-1) by

  zless /usr/share/doc/figtree/changelog.Debian.gz

which says:

   Force set of JAVA_HOME in debian/rules (Closes: #715225).

which means an internal packaging bug was solved.  This is not connected
to any change of the upstream figtree source.

> ## get version information
> $ figtree -help
> 
>                  FigTree v1.4.1, 2006-2013
                               ^
Please note the '.' instead of the '-' in this version number.  Obviously
upstream decided to let the code in the download archive with version
number 1.4 respond with version 1.4.1 when using the -help option.  This
minor version number is not connected at all to the Debian revision and
there is no sensible way to change this.

I hope this explanation makes clear that the issue you reported is
actually no bug inside the Debian package and thus I'm closing the
bug hereby.

Remark:  If you want us to backport the latest figtree version 1.4.2 to
Jessie backports just ping debian-med at lists.debian.org and we can do so.
There is anyway no other chance to help you on your Debian stable system
since only security relevant bugs will be fixed in Debian stable.

Thanks again for your report anyway

     Andreas.

-- 
http://fam-tille.de



More information about the Debian-med-packaging mailing list