[Pkg-osg-devel] Bug: #690878 "pkg-config reports wrong path"

[Alberto Luaces]

"Manuel A. Fernandez Montecelo" writes:

> 2012/11/20 Alberto Luaces <aluaces at udc.es>:
>> "Manuel A. Fernandez Montecelo" writes:
>>
>>> 2012/11/19 Alberto Luaces <aluaces at udc.es>:
>>
>> [...]
>>
>>>
>>> So, indeed, lintian also shows these warnings for some of my packages ;)
>>
>> You were right again, in fact I now looked closely to the list of
>> warning messages and noticed that, for example, libosgDB.so was absent
>> from it.  It makes sense that libraries built on top of OSG base ones do
>> not use libc functions directly, hence lintian does not find any of its
>> symbols.
>>
>> I have uploaded all the changes and updated the changelog, ready for a
>> new release.  I guess that it is needed to explicitly ask for permission
>> for the new upload to be considered for avoiding the freeze, but I don't
>> remember how it is done :)
>
> I get this error with debuild + cowbuilder:
>
> -- Removed runtime path from
> "/tmp/buildd/openscenegraph-3.0.1/debian/tmp/usr/lib/osgPlugins-3.0.1/osgdb_serializers_osgmanipulator.so"
> -- Installing: /tmp/buildd/openscenegraph-3.0.1/debian/tmp/usr/lib/osgPlugins-3.0.1/osgdb_serializers_osgparticle.so
> CMake Error at src/osgWrappers/serializers/osgParticle/cmake_install.cmake:42
> (FILE):
>   file INSTALL cannot copy file
>   "/tmp/buildd/openscenegraph-3.0.1/build/osg/lib/osgPlugins-3.0.1/osgdb_serializers_osgparticle.so"
>   to
>   "/tmp/buildd/openscenegraph-3.0.1/debian/tmp/usr/lib/osgPlugins-3.0.1/osgdb_serializers_osgparticle.so".
> Call Stack (most recent call first):
>   src/osgWrappers/serializers/cmake_install.cmake:41 (INCLUDE)
>   src/cmake_install.cmake:54 (INCLUDE)
>   cmake_install.cmake:105 (INCLUDE)
>
> Any clue?  Maybe because of the changes of DESTDIR and so on?  There
> is no "No space left on device" kind of error, but maybe it's because
> of that (/tmp as tmpfs, and no previous errors for similar
> files/paths).
>

I will investigate; in my build, osgdb_serializers_osgparticle.so
compiles and it is also present in the resulting .deb.

>
> Also, I changed the dependency, according to debhelper compat level:
> -Build-Depends: debhelper (>= 7.0.0),
> +Build-Depends: debhelper (>= 9~),
>
> Finally, is it needed compat 9 at all, or can the hardening work with
> previous levels with the current rules file?  As [I think that] I said
> previously, I am not sure if the change is going to be approved this
> late into the freeze if it's possible to achieve the same effect with
> more intrusive changes.  Compat level 9 makes some hardening things
> automatic, but I think that with the following lines that you used is
> possible with 8, not sure with compat 7:
>
> DPKG_EXPORT_BUILDFLAGS = 1
> include /usr/share/dpkg/buildflags.mk
>

The debhelper upgrade to level 9 was one of the things I did on summer.
I don't remember exactly because of lintian or the hardening flags
addition, but somewhere I read that it was advisable to change it.  Then
I followed the documentation in order to know how to use the hardening
flags, and at least at the time, the DPKG_EXPORT_BUILDFLAGS approach was
suggested.

I'll get back to you with new information.

Regards,

-- 
Alberto