> > Pulls in libcrypto++ from universe (LP: #932896).
It can build against libnss instead, just need to pass --with-nss to configure and adjust debian/control. I'd prefer libcrypto++ because the nss APIs kind of suck, but it's security's call. We can use nss for all of our qa if you go that way.
> > Also pulls in libfcgi
Needed for radosgw, but not for RBD. You can build without radosgw with --without-radosgw.
> > google-perftools
Can build without this with --without-tcmalloc, but it is much faster with it, so ideally that could be pulled into main too.
IIRC there is a minimal package that has the tcmalloc libraries only... libtcmalloc-minimal0.
> > libunwind from universe
No idea where that is coming from....
> > Uses python-support (in universe), should be converted to dh_python2.
Looking into this.
I'm also cleaning up the lintian errors. Patches will hit the upstream ceph.git shortly.
> > Pulls in libcrypto++ from universe (LP: #932896).
It can build against libnss instead, just need to pass --with-nss to configure and adjust debian/control. I'd prefer libcrypto++ because the nss APIs kind of suck, but it's security's call. We can use nss for all of our qa if you go that way.
> > Also pulls in libfcgi
Needed for radosgw, but not for RBD. You can build without radosgw with --without-radosgw.
> > google-perftools
Can build without this with --without-tcmalloc, but it is much faster with it, so ideally that could be pulled into main too.
IIRC there is a minimal package that has the tcmalloc libraries only... libtcmalloc- minimal0.
> > libunwind from universe
No idea where that is coming from....
> > Uses python-support (in universe), should be converted to dh_python2.
Looking into this.
I'm also cleaning up the lintian errors. Patches will hit the upstream ceph.git shortly.