Small packaging problem with dh_strip

[Xavier Grave]

Hi,

In the narval packages, I have some code that allow some kind of plugin
as a shared library. The code promote some symbols only for the plugin.
During the stripping of the code, the corresponding code is been removed.

The strip command allow a --keep-symbol option that I can't find in
dh_strip.

I'd like to avoid to remove stripping from the packaging for these
binaries, does anyone have some idea how to do it ?

My options (as far as my imagination is concern):
- no strip
not very good because of already huge binaries
- strip not using dh_strip but standard strip command
I really prefer to do the things with debian helper
tool
- put your good idea here :)

Thanks in advance, xavier

[Ludovic Brenta]

Post by Xavier Grave
In the narval packages, I have some code that allow some kind of
plugin as a shared library. The code promote some symbols only for the
plugin. During the stripping of the code, the corresponding code is
been removed.

Do you mean that the symbols are neither in /usr/lib/libnarval.so.1.10.1
(package libnarval1.10.1) nor in
/usr/lib/debug/usr/lib/libnarval.so.1.10.1 (package libnarval-dbg)?

Post by Xavier Grave
The strip command allow a --keep-symbol option that I can't find in
dh_strip.

Is this not equivalent to --dbg-package or --keep-debug?

[xavier grave]

Post by Ludovic Brenta
Do you mean that the symbols are neither in /usr/lib
/libnarval.so.1.10.1
(package libnarval1.10.1) nor in
/usr/lib/debug/usr/lib/libnarval.so.1.10.1 (package libnarval-dbg)?

Post by Xavier Grave
The strip command allow a --keep-symbol option that I can't find in
dh_strip.

Is this not equivalent to --dbg-package or --keep-debug?

I had a look in the package libnarval-dbg it seems that the interesting
symbols are missing also there.

I will try a "phantom" call to one of the routines to see if the strip
command can be fooled.

xavier

[Xavier Grave]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by xavier grave

Post by Ludovic Brenta
Do you mean that the symbols are neither in /usr/lib
/libnarval.so.1.10.1
(package libnarval1.10.1) nor in
/usr/lib/debug/usr/lib/libnarval.so.1.10.1 (package libnarval-dbg)?

Post by Xavier Grave
The strip command allow a --keep-symbol option that I can't find in
dh_strip.

Is this not equivalent to --dbg-package or --keep-debug?

I had a look in the package libnarval-dbg it seems that the interesting
symbols are missing also there.
I will try a "phantom" call to one of the routines to see if the strip
command can be fooled.

During my investigations about the problem I discovered a transition bug
coming from the transition from GLADE to PolyORB. dh_strip was not the
responsible of the problem, it was me :) (the transition missed the
- -rdynamic present in the GLADE building process)

- --
xavier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzzop8ACgkQVIZi0A5BZF7fLwCePzQINKKAyssCBIPh7TwYDPAh
VRsAoJQUtBCCIkhr7TEpPbwWtJtxEL2A
=UgyU
-----END PGP SIGNATURE-----

[Ludovic Brenta]

Post by Xavier Grave
During my investigations about the problem I discovered a transition bug
coming from the transition from GLADE to PolyORB. dh_strip was not the
responsible of the problem, it was me :) (the transition missed the
-rdynamic present in the GLADE building process)

OK, the next steps for you are:
1. File a bug describing the problem and its consequences; is the bug in
polyorb or in narval? If in polyorb, is it necessary to rebuild narval?
2. If the bug is release-critical, upload a fix to unstable
(and change *only* what is needed to fix the bug)
3. If the bug is release-critical, request that the fixed package(s) be
allowed into testing by filing a (second) bug against the pseudo-package
release.debian.org. Consider requesting a BinNMU of narval if necessary.

[Xavier Grave]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Ludovic Brenta

Post by Xavier Grave
During my investigations about the problem I discovered a transition bug
coming from the transition from GLADE to PolyORB. dh_strip was not the
responsible of the problem, it was me :) (the transition missed the
-rdynamic present in the GLADE building process)

1. File a bug describing the problem and its consequences; is the bug in
polyorb or in narval? If in polyorb, is it necessary to rebuild narval?

Only narval

Post by Ludovic Brenta
2. If the bug is release-critical, upload a fix to unstable
(and change *only* what is needed to fix the bug)

not a RC bug since generic actors are still usable but without narval
parameters available for C/C++ code

Post by Ludovic Brenta
3. If the bug is release-critical, request that the fixed package(s) be
allowed into testing by filing a (second) bug against the pseudo-package
release.debian.org. Consider requesting a BinNMU of narval if necessary.

Thanks for procedure reminder.
O+ xavier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzzzdMACgkQVIZi0A5BZF44gQCdHHlKKyu9oh1J1A5KB+evUAe9
yusAn1pYNkmxieiIi27NxvnrDXNBplH1
=uYNR
-----END PGP SIGNATURE-----