Packaging ulogd 2.x
Hello
I'm trying to package the last ulogd version (2.0.1) and I'm willing to
maintain/adopt it in the long run (disclaimer: I'm not a DD neither a DM).
[cc'ed both current ulogd maintainer and reporter of ulogd2 ITP[1]]
I have some doubts with respect to packaging:
1. ulogd vs ulogd2 package name.
I'm not sure why the ITP was filled changing the package name. It's true
the file format has changed but it has changed before too between
versions 1.02-2 and 1.23-1.
I've decided to use the existing package name and document a file syntax
change and use debconf to show a warning (actually it's what the
current package is doing if you upgrade from < 1.23).
It this recommended practice? Is there any policy on this?
2. package version
I'm using 2.0.1-0.1 hoping that someone will do an NMU. Is there any
difference between 2.0.1-1 and 2.0.1-0.1? Policy here?
3. migrating d/copyright to DEP5
Current copyright is here[2] and I would like to migrate it to DEP5.
>From my previous experience it's enough to specify the upstream license
in the 'Header paragraph' and then a 'Files paragraph' for debian/* files.
In [3] you can see that apart from laforge's copyright, there are 3
other names (Daniel, Joerg and Achilleas) involved without copyright.
4. Versioned library dependency
Upstream code requires libnetfilter-conntrack >= 1.0.2 for building[3]
but that dependency is not picked by shlibs:Depends neither by
misc:Depends. The binary package ends depending o
'libnetfilter-conntrack3'. Should I add the versioned dependency manually?
Thanks.
Regards,
maykel
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502305
[2] https://github.com/mmoya/pkg-ulogd/blob/master/debian/copyright
[3]
https://git.netfilter.org/cgi-bin/gitweb.cgi?p=ulogd2.git;a=blob;f=configure.ac;h=10b6e1fe33c1efc7a1f1cc0e45f361417b838d88;hb=a81f4f3e332f527abec1175f2b26228464edc78d#l48
Reply to: