maildrop build fails: debian/rules build exit status 2, Questions about building debs

Hi there,

long time courier user here, also slightly fed up with the Debian 
situation. We need to fix this. Anyway...

I could use a little help with the build process. As I don't want to 
compile on the production machine, I tried to create debs with the 
tarball-method:


1. Can I somehow pass options to 'configure' when running the 
'courier-debuild' script so I could customize my build?
(Should I anyway? Or could I mess up the creation of debs if I did?)


2. I have already created (and installed) debs for courier-unicode, 
courier-authlib and courier-imap with courier-debuild -us -uc.

The maildrop build runs into an error with some testsuite:


(...)
make[3]: Verzeichnis 
„/home/mybuilduser/courier/tmp/maildrop-3.1.6/deb/maildrop-3.1.6/libs/maildrop“ 
wird betreten
VALGRIND="`which valgrind 2>/dev/null`"; export VALGRIND; /bin/bash 
./testsuite >testsuite.diff || exit 1; diff -U 3 testsuite.diff 
./testsuite.txt.idn || exit 1; rm -f testsuite.diff
--- testsuite.diff      2024-07-13 10:58:10.149442473 +0200
+++ ./testsuite.txt.idn 2023-04-03 04:43:07.000000000 +0200
@@ -1,10 +1,8 @@
  Parameters: -f  [email protected]
  Subject: test-forward
-From mybuilduser Sat Jul 13 10:58:09 2024
  Subject: msg1


-From mybuilduser Sat Jul 13 10:58:09 2024
  Subject: msg2

  -rw-------
@@ -715,7 +713,7 @@
  Content-Type: text/plain; charset=iso-8859-1

  --
-Message envelope sender=mybuilduser
+Message envelope sender=MAILER-DAEMON
  maildrop: Attempting ./testsuite.recipe
  Tokenized echo
  Tokenized string: "VERBOSE=$VERBOSE"
@@ -809,7 +807,7 @@
  ./testsuite.recipe(14): Creating dotlock testsuite.lock
  ./testsuite.recipe(15): Opening logfile /dev/null
  ./testsuite.recipe(18): Creating flock testsuite.lock
-Message envelope sender=mybuilduser
+Message envelope sender=MAILER-DAEMON
  maildrop: Attempting ./testsuite.recipe
  Tokenized foreach
  Tokenized regexp: /Header: (.*)/
@@ -1028,7 +1026,7 @@
  alpha
  BETA
  ./testsuite.recipe(35): unset i
-Message envelope sender=mybuilduser
+Message envelope sender=MAILER-DAEMON
  maildrop: Attempting ./testsuite.recipe
  Tokenized string: "KEYWORDS"
  Tokenized =
@@ -1042,7 +1040,7 @@
  maildrop: Delivery complete.
  alpha
  beta
-Message envelope sender=mybuilduser
+Message envelope sender=MAILER-DAEMON
  maildrop: Attempting ./testsuite.recipe
  Tokenized if
  Tokenized (
make[3]: *** [Makefile:1139: check-am] Fehler 1
make[3]: Verzeichnis 
„/home/mybuilduser/courier/tmp/maildrop-3.1.6/deb/maildrop-3.1.6/libs/maildrop“ 
wird verlassen
make[2]: *** [Makefile:927: check] Fehler 2
make[2]: Verzeichnis 
„/home/mybuilduser/courier/tmp/maildrop-3.1.6/deb/maildrop-3.1.6/libs/maildrop“ 
wird verlassen
make[1]: *** [Makefile:850: check-recursive] Fehler 1
make[1]: Verzeichnis 
„/home/mybuilduser/courier/tmp/maildrop-3.1.6/deb/maildrop-3.1.6“ wird 
verlassen
dh_auto_test: error: make -j16 check "TESTSUITEFLAGS=-j16 --verbose" 
VERBOSE=1 returned exit code 2
make: *** [debian/rules:8: build] Fehler 25
dpkg-buildpackage: Fehler: Unterprozess debian/rules build lieferte 
Exitstatus 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -vvv failed


(Ignore the -vvv, it doesn't do anything as it seems.)


Unfortunately I have zero experience with valgrind or whatever does 
this, let alone this stack of generator scripts, so I'm a bit stuck 
here. testsuite.recipe seems to be autogenerated along the process, and 
there are a number of testsuite-files in the tree, none of them ending 
on .recipe.

Any hints on what to look at?


I'm on debian 12 bookworm. Installed packages: git autoconf automake 
libtool libldap2-dev libmariadb-dev libz3-dev libsqlite3-dev libpq-dev 
libgdbm-dev libpam0g-dev expect libltdl-dev devscripts debhelper 
xsltproc docbook docbook-xml docbook-xsl w3c-sgml-lib elinks tidy 
libltdl7 libmariadb-dev-compat libidn2-dev libcourier-unicode-dev 
sysconftool gnutls-dev gnutls-bin libpcre2-dev libgcrypt-dev valgrind


3. Is there a way to do this from the source you just pull from github? 
The tarball-method looks a bit quirky to me. Maybe there's a build-deb 
target...?

d.


_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users