For many Globus packages only debug symbols available but no binaries

[wvengen]

On Maverick 10.10: for several globus binary packages there seem to be only debugging packages available but not the corresponding 'real' packages.

This is also visible on the Ubuntu manpage repository. Compare:
  http://packages.ubuntu.com/search?keywords=globus&searchon=names&suite=lucid&section=all
  http://packages.ubuntu.com/search?keywords=globus&searchon=names&suite=maverick&section=all

$ aptitude -w 999 search ^globus | awk '{print $2}' >pkgs
$ cat pkgs | sed 's/^\(.*\)-dbg$/\1/p;d' >pkgs_from_dbg
$ for p in `cat pkgs_from_dbg`; do grep -q "^$p\$" pkgs || echo $p; done
globus-authz-callout-error
globus-authz
globus-callout
globus-common
globus-ftp-client
globus-ftp-control
globus-gass-cache
globus-gass-copy
globus-gass-server-ez
globus-gass-transfer
globus-gfork
globus-gram-client
globus-gram-job-manager-callout-error
globus-gram-protocol
globus-gridftp-server-control
globus-gridftp-server
globus-gsi-callback
globus-gsi-cert-utils
globus-gsi-credential
globus-gsi-openssl-error
globus-gsi-proxy-core
globus-gsi-proxy-ssl
globus-gsi-sysconfig
globus-gss-assist
globus-gssapi-error
globus-gssapi-gsi
globus-io
globus-openssl-module
globus-rls-client
globus-rsl-assist
globus-rsl
globus-scheduler-event-generator
globus-usage
globus-xio
globus-xio-gsi-driver
globus-xio-pipe-driver
globus-xio-popen-driver

[Mattias Ellert (mattias-ellert-fysast)]

Your search is a bit broken. You search for ^globus - however, most globus packages are library packages and therefore start with libglobus rather than globus as mandated by the packaging policy. As an example, the globus-ftp-client source package (since you filed the bug for this package) provides the following binary packages:

globus-ftp-client-dbg
libglobus-ftp-client-dev
libglobus-ftp-client-doc
libglobus-ftp-client2

And similarly for the other packages is your list.

[wvengen (wvengen)]

Thanks for your explanation. I understand that there is no binary globus ftp client package, and that the lib(*)-dev packages have have \1-dbg as their debug equivalents. I find that counter-intuitive, but there may be good reasons (like the source package being named such). Ok!