Re: Any progress with FIS GT.M?

[Andreas Tille <andreas@an3as.eu>]

On Sat, Jun 30, 2012 at 06:59:03PM -0400, Luis Ibanez wrote:
> 
> Here are some interesting observations.
> 
> a) When building with "debuild" instead of "cowbuilder",
>     the resulting package:
> 
>      fis-gtm-5.5.000_5.5-000+git104-g4077ab8-1_amd64.deb
> 
>     doesn't report that many warning.
> 
>      More specifically, running lintian in the .desc file returns:
> 
> lintian fis-gtm_5.5-000+git104-g4077ab8-1_amd64.changes
> 
> W: fis-gtm source: newer-standards-version 3.9.3 (current is 3.9.1)

That's because of your squeeze VM.  You should probably install lintian
from unstable using

   apt-get -t unstable install lintian

(after having added unstable to your sources.list and not to forget to
set preferences to make sure stable is prefered over unstable - if I
remember correctly I posted the according entries to make in /etc/apt in
the MoM period somewhere - if you can not find it and it is not clear
what to do just ask again)

> W: fis-gtm-5.5.000: executable-not-elf-or-script
> ./usr/lib/fis-gtm/V5.5-000_x86_64/gtmprofile
> W: fis-gtm-5.5.000: executable-not-elf-or-script
> ./usr/lib/fis-gtm/V5.5-000_x86_64/gtmprofile_preV54000
> W: fis-gtm-5.5.000: executable-not-elf-or-script
> ./usr/lib/fis-gtm/V5.5-000_x86_64/gtmstart
> W: fis-gtm-5.5.000: executable-not-elf-or-script
> ./usr/lib/fis-gtm/V5.5-000_x86_64/gtcm_run
> W: fis-gtm-5.5.000: executable-not-elf-or-script
> ./usr/lib/fis-gtm/V5.5-000_x86_64/gtmstop
> W: fis-gtm-5.5.000: executable-not-elf-or-script
> ./usr/lib/fis-gtm/V5.5-000_x86_64/gtmcshrc
> W: fis-gtm-5.5.000: executable-not-elf-or-script
> ./usr/lib/fis-gtm/V5.5-000_x86_64/gtcm_slist

This should be easy to fix.  Either there is a shebang line missing in
the scripts or the permissions are not correctly set.  Most probably
this also could (should) be changed upstream as well.

> W: fis-gtm-5.5.000: extra-license-file
> usr/lib/fis-gtm/V5.5-000_x86_64/COPYING

If this file is somewhere used inside the code a lintian override might
make sense here.

> W: fis-gtm-5.5.000: shlib-with-executable-stack
> usr/lib/fis-gtm/V5.5-000_x86_64/libgtmshr.so
> W: fis-gtm-5.5.000: shared-lib-without-dependency-information
> ./usr/lib/fis-gtm/V5.5-000_x86_64/libgtmutil.so
> W: fis-gtm-5.5.000: shared-lib-without-dependency-information
> ./usr/lib/fis-gtm/V5.5-000_x86_64/utf8/libgtmutil.so

This needs further inspection (I have not seen such warnings before).
 
> c) What is missing in this case is the setuid for
> 
>                           gtmsecshr

Could be set inside debian/rules file.
 
> d)  The permissions seems to have been already
>      like this in the local build:
> 
> ls
> luisibanez-fis-gtm-4077ab8/debian/fis-gtm-5.5.000/usr/lib/fis-gtm/V5.5-000_x86_64/
> -l | grep "^...x"
> 
> -rwxr-xr-x 1 ibanez ibanez 2038776 Jun 30 17:34 dse
> ...
> 
> So.. something is unfolding differently in the cowbuilder environment.
> One thing that comes to mind is that in the CMakeList.txt file we
> are expecting to find CMake 2.8.5 (or higher).

This should be expressed in a versioned Build-Depends.  While this is
fullfilled in current testing + unstable it should prevent build failures
in other systems.  (Done in SVN)

> In the manual build
> (with debuild ) I have been building a local cmake (from the source
> in the Git repository of CMake) and then running "debuild -d" so
> it ignores the fact that the cmake dependency is not preset (as an
> installed debian package).

Also in this case I would rather do something like

   apt-get -t unstable install cmake 

> It would look like something in the cowbuilder environment is preventing
> the installation scripts from setting the right permissions, or maybe
> from knowing that it has to modify the permissions....

I admit that I never experienced that debuild and cowbuilder showed this
kind of different behaviour and I do not have a sensible explanation for
your observation.  Further investigation is actually needed.

Kind regards

        Andreas.

-- 
http://fam-tille.de