Re: Debian backport or mailfront

Gerrit Pape <[email protected]>
Newsgroups gmane.comp.misc.pape.general
Message-ID <20060203165111.17046.qmail@608c1f30c51e1b.315fe32.mid.smarden.org>
On Thu, Feb 02, 2006 at 04:10:14PM +0000, Jeremy Hinton wrote:
> Dunno if this is the correct place to post this, but i have a question

This list is fine, I'd say.

> for Gerrit. Have you considered doing any backports for some of the
> more rapidly-advancing software like mailfront (0.92 in stable and
> 0.98 in release) that you maintain debian packages for? I'm building a
> new mail-relay server on sarge (new debian user), and thought i'd ask
> before going the source route.

I'm not sure I'll do backports for the public.  But it's not that hard
to do on your own, and maybe if you submit them to backports.org they'll
get accepted.


Either build the packages on sid using the dietlibc, they should then
install fine on a sarge system, e.g.:

On sid add
 deb-src http://ftp.debian.org/debian/ sid main
to /etc/apt/sources.list, and run `apt-get update`.  Install the
dietlibc-dev package, and do

 $ DEB_BUILD_OPTIONS=diet apt-get source -b cvm
 $ DEB_BUILD_OPTIONS=diet apt-get source -b mailfront


Or build the packages on sarge, you'll need to start with the build
dependencies.  First dietlibc-dev, then bglibs-dev, cvm, and finally
mailfront, e.g.:

On sarge add
 deb-src http://ftp.debian.org/debian/ sid main
to /etc/apt/sources.list, and run `apt-get update`.  Then do

 $ apt-get source dietlibc
 $ cd dietlibc-0.29/
 $ debchange -pn 'build for sarge'
 $ dpkg-buildpackage -b -rfakeroot -uc -us
 ...

Install the resulting package as root
 # dpkg -i ../dietlibc_0.29-8.1_i386.deb

Now bglibs-dev
 $ apt-get source bglibs
 $ cd bglibs-1.031/
 $ debchange -pn 'build for sarge'
 $ dpkg-buildpackage -b -rfakeroot -uc -us

 # dpkg -i ../bglibs-dev_1.031-1.1_i386.deb

And the same for cvm, finally mailfront.

HTH, Gerrit.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.