I can see some things very quickly:

debian/control, build-depends: you need: debhelper (>= 9.0.0) and maybe: Standards-Version: 3.9.3

debian/compat must be 9 (not 8)

debian/copyright: `see AUTHORS file' might be unacceptable: Debian ftpmasters may reject the package. Better to be safe and copy stuff from the AUTHORS file into debian/copyright

debian/rules: - I haven't looked too closely, I can see it started in 2006 and may not follow the current practices with debhelper, if you are not confident with this file, you could just try making a fresh one, e.g. just copy the rules file from my resiprocate package, study it carefully as you would probably need to change a few details, or you can use the command `dh_make' to create a fresh rules file - the `get-orig-source' stuff - maybe it shouldn't be there, not sure about this

no `debian/kamailio.install' or similar files: - how do you assign the files to packages? I think you need a .install file for each binary package that is mentioned in debian/control. Again, see the resiprocate package for examples:

http://anonscm.debian.org/gitweb/?p=collab-maint/resiprocate.git;a=summary

http://mentors.debian.net/package/resiprocate

Are you also participating in the debian-mentors list? There are many very helpful people there, someone always seems to respond to questions there within a short period of time. You can also upload packages to the mentors site and it makes it very easy for people to evaluate them and give more feedback.

On 25/05/12 12:29, Victor Seva wrote:

Hi,

2012/5/25 Daniel Pocock daniel@pocock.com.au:

...

I notice there has been some attempts to package Kamailio for Debian: http://anonscm.debian.org/viewvc/pkg-voip/kamailio/trunk/debian/control?view...

Yeah. I'm trying to get Kamailio in Debian.

...

The Debian 7 freeze is likely to come in mid-June, that would suggest some initial version of the package needs to be uploaded to the FTP queue within the next 1-2 weeks at the latest

http://lists.debian.org/debian-devel-announce/2012/05/msg00004.html

Yes we have very short time to get into Wheezy.

...

Are other people interested in pursuing this, even if it is just testing the package?

Any help will be much appreciated.

Now I'm stock with a infinite loop building lua module on sid. No problems on squeeze.

Greetings, Víctor

On 25/05/12 13:23, Victor Seva wrote:

Hi Daniel,

2012/5/25 Daniel Pocock daniel@pocock.com.au:

...

I can see some things very quickly:

debian/control, build-depends: you need: debhelper (>= 9.0.0) and maybe: Standards-Version: 3.9.3

debian/compat must be 9 (not 8)

debian/copyright: `see AUTHORS file' might be unacceptable: Debian ftpmasters may reject the package. Better to be safe and copy stuff from the AUTHORS file into debian/copyright

Ok.

...

debian/rules:

• I haven't looked too closely, I can see it started in 2006 and may

not follow the current practices with debhelper, if you are not confident with this file, you could just try making a fresh one, e.g. just copy the rules file from my resiprocate package, study it carefully as you would probably need to change a few details, or you can use the command `dh_make' to create a fresh rules file

I'm not too confident but the rules do their job.

...

• the `get-orig-source' stuff - maybe it shouldn't be there, not sure

about this

From the README of pkg-voip team: "To download the *.orig.tar.gz to the ../tarballs directory, most of the pkg-voip packages have a "get-orig-source" target in their debian/rules. Further, there is a "print-version" target showing the upstream version used for the current packaging. You can run the get-orig-source directly from trunk/ or tags/$version/."

So, this is fine.

That should be ok - I saw it and I didn't look closely enough to see if it gets called during the build phase - Debian policy says something about no downloads during the build phase

Some other things that sponsors will check before accepting the package (or asking you to do more work), have you tried building it with pbuilder?

In particular, you should verify it with --twice, something like this I think (I've put -j12 for faster build on a multi-core CPU):

cd kamailio-x.y.z /usr/bin/pdebuild --debbuildopts -j12 -- --twice

...

Are you also participating in the debian-mentors list? There are many very helpful people there, someone always seems to respond to questions there within a short period of time. You can also upload packages to the mentors site and it makes it very easy for people to evaluate them and give more feedback.

I'm already member of the pkg-voip team so I hope someone of team will sponsor the upload when it will be ready. But yeah, maybe I need to ask on mentors about this problem.

Ok, great, all you have to do is register at http://mentors.debian.net and then you can upload the package there for potential sponsors to review

Although I have some packages in Debian, I am still at an early phase of the Debian signup process and sponsor's upload them for me, so I can't offer to help the kamailio upload but I'm happy to try the packages after you put them on the mentors site.

Hi Daniel,

I have problems building the lua module on a sid|wheezy chroot. Make process gets stocked on a loop. This behaviour doesn't show up on a squeeze chroot. Did any of you build successfully the 3.2.3 version with lua modules on a sid|wheezy machine?

Thanks in advance.

El Fri, 25 May 2012 23:01:43 +0200 Jon Bonilla (Manwe) manwe@aholab.ehu.es escribió:

El Fri, 25 May 2012 15:28:06 +0200 Victor Seva linuxmaniac@torreviejawireless.org escribió:

...

Hi Daniel,

I have problems building the lua module on a sid|wheezy chroot. Make process gets stocked on a loop. This behaviour doesn't show up on a squeeze chroot. Did any of you build successfully the 3.2.3 version with lua modules on a sid|wheezy machine?

I'm having this problem with latest git branch 3.2. Not sure what the chroot was because I was building for several distros.

For the stable release, it built well.

http://deb.kamailio.org/kamailio32/pool/main/k/kamailio/kamailio-lua-modules...

I'll check the logs of the builds to see what new packages or commits made this happen.

I use static charoots to build instead of using debootstrap for every build. This is the last apt log before the infinite loop started for the lua module in wheezy:

Commandline: apt-get -y dist-upgrade Install: libswscale2:i386 (0.8.2-1, automatic), dnet-common:i386 (2.57, automatic), libavutil51:i386 (0.8.2-1, automatic), libportaudio2:i386 (19+svn20111121-1, automatic), libapt-pkg4.12:i386 (0.9.3, automatic), libx264-123:i386 (0.123.2189+git35cf912-1, automatic), libept1.4.12:i386 (1.0.6.1, automatic), libroar-compat2:i386 (1.0~beta0-1, automatic), libopenjpeg2:i386 (1.3+dfsg-4+b1, automatic), python-dbus-dev:i386 (1.1.0-1, automatic), libpostproc52:i386 (0.8.2-1, automatic), libslp1:i386 (1.2.1-9, automatic), libasprintf0c2:i386 (0.18.1.1-7, automatic), libx11-xcb1:i386 (1.4.99.901-2, automatic), libjbig0:i386 (2.0-2), libgettextpo0:i386 (0.18.1.1-7, automatic), libavformat53:i386 (0.8.2-1, automatic), libroar2:i386 (1.0~beta0-1, automatic), libdnet:i386 (2.57, automatic), gstreamer0.10-ffmpeg:i386 (0.10.13-5, automatic), libmp3lame0:i386 (3.99.5+repack1-3, automatic), libasyncns0:i386 (0.8-4, automatic), libboost-iostreams1.49.0:i386 (1.49.0-3, automatic), libxtst6:i386 (1.2.1-1, automatic), libavcodec53:i386 (0.8.2-1, automatic), libpulse0:i386 (1.1-3.2, automatic), libva1:i386 (1.0.15-4, automatic), libapt-inst1.5:i386 (0.9.3, automatic), libspeexdsp1:i386 (1.2~rc1-3.1, automatic)

Upgrade: libopenal1:i386 (1.13-6, 1.14-3), aptitude:i386 (0.6.6-1, 0.6.7-1), python-apt:i386 (0.8.3+nmu1, 0.8.4), libapt-pkg-perl:i386 (0.1.26, 0.1.26+b1), apt-utils:i386 (0.8.15.10, 0.9.3), gettext:i386 (0.18.1.1-5, 0.18.1.1-7), apt:i386 (0.8.15.10, 0.9.3), python-dbus:i386 (0.84.0-3, 1.1.0-1), gettext-base:i386 (0.18.1.1-5, 0.18.1.1-7), libtiff4:i386 (3.9.6-2, 3.9.6-5), libopenal-data:i386 (1.13-6, 1.14-3), libwebkitgtk-1.0-0:i386 (1.6.3-1, 1.8.1-2), libjavascriptcoregtk-1.0-0:i386 (1.6.3-1, 1.8.1-2)

Remove: libept1:i386 (1.0.5)