Bug#683746: rspamd packaging
Laszlo,
On 08/04/2012 10:19 PM, Laszlo Boszormenyi (GCS) wrote:
Hi Vsevolod,
I've seen your ITP of rspamd and thought I may package it instead of
you. But as I see, it's close to ready.
Thanks for taking care of it! I'm using this package for my machines,
but I'm not very familiar with debian packaging policies unfortunately.
I send a patch to make it better. Contains the following fixes:
<skipped>
I've fixed some of that issues in my development (tip) version. I'll
include all your changes I've not still implemented in 0.5.1 release for
sure, thank you for this work!
I couldn't build it with hardening enabled due to this error:
/usr/bin/ld.bfd.real: librspamd-util.a(mem_pool.c.o): relocation R_X86_64_PC32 against symbol `memory_pool_alloc' can not be used when making a shared object; recompile with -fPIC
It's strange as rspamd is built with -fpic -fPIC flags if they are
supported on the targeted architecture. How can I repeat this bug using
my debian system?
The package should be split to lib, -dev and binary.
Library is only used for rspamd client (rspamc), so maybe it would be
better to link it statically for debian package? I think a development
package is only useful when there is any external software that uses the
normal package's API.
Please don't use
debian/changelog as upstream changelog. It's only for packaging changes
and nothing else.
Acknowledged. So on upgrades of this package I should only inlcude lines
like 'Update to version x.x.x', rigth?
--
Vsevolod Stakhov
Reply to: