Re: compiling maildrop with mysql enabled fails on sarge

2004-07-12 Thread Pim Bliek
Any clues on what might have gone wrong in the compile?

Pim

On Sun, 11 Jul 2004 23:24:08 +0100, Pigeon [EMAIL PROTECTED] wrote:
 
 
 On Sun, Jul 11, 2004 at 04:08:11PM -0300, Jeronimo Pellegrini wrote:
   Jul 11 20:07:09 srv1 postfix/pipe[29843]: 359E431346:
   to=[EMAIL PROTECTED], relay=maildrop, delay=526, status=deferred
   (temporary failure. Command output: maildrop: signal 0x0B )
  
  
   It is a long road to getting this to work
 
  I don't know what signal 0x0B means, but maildrop doesn't seem to be
  able to deliver to the mailbox where you told it to do.
 
  Check these:
 
  - Is the path to the mailbox correct? How does it appear in the
database, and what is the path to your maildirs?
  - Permissions and ownership in the mail dir? These should be:
drwx--9 vmailvmail
 
 0x0b is a segfault, so it could be that maildrop still hasn't been
 built properly.
 
 --
 Pigeon
 
 Be kind to pigeons
 Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x21C61F7F
 
 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: compiling maildrop with mysql enabled fails on sarge

2004-07-11 Thread Jeronimo Pellegrini
 ./configure: line 1: mysql_config: command not found
 configure: error: Unable to run mysql_config
 configure: error: /bin/sh './configure' failed for maildrop
 
 I am no developer-person so I am lost here... And I really need the
 mysql-support into maildrop :(.

Install libmysqlclient-dev (or something similar -- in woody, it's
libmysqlclient10-dev)

J.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: compiling maildrop with mysql enabled fails on sarge

2004-07-11 Thread Pim Bliek
That helps!
But now it tells me:

+ install -m 644 -p debian/maildroprc /root/maildrop-1.5.3/debian/maildrop/etc
+ find /root/maildrop-1.5.3/debian/maildrop/usr -type d -empty
+ xargs -r rmdir -p --ignore-fail-on-non-empty
+ dh_installdocs README README.html AUTHORS INSTALL INSTALL.html
maildroptips.txt
+ dh_installchangelogs ChangeLog
+ echo
+ grep -vq nostrip
+ dh_strip
+ dh_compress
+ dh_fixperms
+ cd /root/maildrop-1.5.3/debian/maildrop/usr/bin
+ chgrp mail maildrop lockmail.maildrop
+ cd /root/maildrop-1.5.3/debian/maildrop/usr/bin
+ chmod g+s maildrop lockmail.maildrop
+ dh_installdeb
+ dh_perl
+ dh_shlibdeps
debian/maildrop/usr/bin/maildrop: error while loading shared
libraries: libfakeroot.so.0: cannot open shared object file: No such
file or directory
dpkg-shlibdeps: failure: ldd on `debian/maildrop/usr/bin/maildrop'
gave error exit status 1
dh_shlibdeps: command returned error code 256

What am I missing here?

Pim


On Sun, 11 Jul 2004 14:22:19 -0300, Jeronimo Pellegrini
[EMAIL PROTECTED] wrote:
  ./configure: line 1: mysql_config: command not found
  configure: error: Unable to run mysql_config
  configure: error: /bin/sh './configure' failed for maildrop
 
  I am no developer-person so I am lost here... And I really need the
  mysql-support into maildrop :(.
 
 Install libmysqlclient-dev (or something similar -- in woody, it's
 libmysqlclient10-dev)
 
 J.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: compiling maildrop with mysql enabled fails on sarge

2004-07-11 Thread Jeronimo Pellegrini
 debian/maildrop/usr/bin/maildrop: error while loading shared
 libraries: libfakeroot.so.0: cannot open shared object file: No such
 file or directory
 dpkg-shlibdeps: failure: ldd on `debian/maildrop/usr/bin/maildrop'
 gave error exit status 1
 dh_shlibdeps: command returned error code 256
 
 What am I missing here?

I think you'll find the answer here...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253436

J.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: compiling maildrop with mysql enabled fails on sarge

2004-07-11 Thread Pim Bliek
I got around that as well, found something else to get the deb building.

Anyway, currently I am getting the following when trying to send an email:


Jul 11 20:07:09 srv1 postfix/pipe[29839]: flush_add: site mydomain.nl
id 22D7B31345
Jul 11 20:07:09 srv1 postfix/pipe[29839]: match_hostname: mydomain.nl
~? srv1.mydomain.nl
Jul 11 20:07:09 srv1 postfix/pipe[29839]: match_hostname: mydomain.nl
~? localhost
Jul 11 20:07:09 srv1 postfix/pipe[29839]: match_list_match:
mydomain.nl: no match
Jul 11 20:07:09 srv1 postfix/pipe[29839]: flush_add: site mydomain.nl
id 22D7B31345 status 4
Jul 11 20:07:09 srv1 postfix/pipe[29839]: deliver_request_final: send:  -1
Jul 11 20:07:09 srv1 postfix/pipe[29839]: send attr reason =
Jul 11 20:07:09 srv1 postfix/pipe[29839]: send attr status = 4294967295
Jul 11 20:07:09 srv1 postfix/pipe[29839]: master_notify: status 1
Jul 11 20:07:09 srv1 postfix/pipe[29839]: connection closed
Jul 11 20:07:09 srv1 postfix/pipe[29839]: watchdog_stop: 0x8054ca0
Jul 11 20:07:09 srv1 postfix/pipe[29843]: input attribute name: status
Jul 11 20:07:09 srv1 postfix/pipe[29843]: input attribute value: 0
Jul 11 20:07:09 srv1 postfix/pipe[29843]: private/defer socket: wanted
attribute: (list terminator)
Jul 11 20:07:09 srv1 postfix/pipe[29843]: input attribute name: (end)
Jul 11 20:07:09 srv1 postfix/pipe[29843]: 359E431346:
to=[EMAIL PROTECTED], relay=maildrop, delay=526, status=deferred
(temporary failure. Command output: maildrop: signal 0x0B )
Jul 11 20:07:09 srv1 postfix/pipe[29843]: flush_add: site mydomain.nl
id 359E431346
Jul 11 20:07:09 srv1 postfix/pipe[29843]: match_hostname: mydomain.nl
~? srv1.mydomain.nl
Jul 11 20:07:09 srv1 postfix/pipe[29843]: match_hostname: mydomain.nl
~? localhost
Jul 11 20:07:09 srv1 postfix/pipe[29843]: match_list_match:
mydomain.nl: no match
Jul 11 20:07:09 srv1 postfix/pipe[29843]: flush_add: site mydomain.nl
id 359E431346 status 4
Jul 11 20:07:09 srv1 postfix/pipe[29843]: deliver_request_final: send:  -1
Jul 11 20:07:09 srv1 postfix/pipe[29843]: send attr reason =
Jul 11 20:07:09 srv1 postfix/pipe[29843]: send attr status = 4294967295
Jul 11 20:07:09 srv1 postfix/pipe[29843]: master_notify: status 1
Jul 11 20:07:09 srv1 postfix/pipe[29843]: connection closed
Jul 11 20:07:09 srv1 postfix/pipe[29843]: watchdog_stop: 0x8054ca0


It is a long road to getting this to work

Pim


On Sun, 11 Jul 2004 15:00:09 -0300, Jeronimo Pellegrini
[EMAIL PROTECTED] wrote:
  debian/maildrop/usr/bin/maildrop: error while loading shared
  libraries: libfakeroot.so.0: cannot open shared object file: No such
  file or directory
  dpkg-shlibdeps: failure: ldd on `debian/maildrop/usr/bin/maildrop'
  gave error exit status 1
  dh_shlibdeps: command returned error code 256
 
  What am I missing here?
 
 I think you'll find the answer here...
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253436
 
 J.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: compiling maildrop with mysql enabled fails on sarge

2004-07-11 Thread Jeronimo Pellegrini
 Jul 11 20:07:09 srv1 postfix/pipe[29843]: 359E431346:
 to=[EMAIL PROTECTED], relay=maildrop, delay=526, status=deferred
 (temporary failure. Command output: maildrop: signal 0x0B )
 
 
 It is a long road to getting this to work

I don't know what signal 0x0B means, but maildrop doesn't seem to be
able to deliver to the mailbox where you told it to do.

Check these:

- Is the path to the mailbox correct? How does it appear in the
  database, and what is the path to your maildirs?
- Permissions and ownership in the mail dir? These should be:
  drwx--9 vmailvmail

J.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: compiling maildrop with mysql enabled fails on sarge

2004-07-11 Thread Pigeon
On Sun, Jul 11, 2004 at 04:08:11PM -0300, Jeronimo Pellegrini wrote:
  Jul 11 20:07:09 srv1 postfix/pipe[29843]: 359E431346:
  to=[EMAIL PROTECTED], relay=maildrop, delay=526, status=deferred
  (temporary failure. Command output: maildrop: signal 0x0B )
  
  
  It is a long road to getting this to work
 
 I don't know what signal 0x0B means, but maildrop doesn't seem to be
 able to deliver to the mailbox where you told it to do.
 
 Check these:
 
 - Is the path to the mailbox correct? How does it appear in the
   database, and what is the path to your maildirs?
 - Permissions and ownership in the mail dir? These should be:
   drwx--9 vmailvmail

0x0b is a segfault, so it could be that maildrop still hasn't been
built properly.

-- 
Pigeon

Be kind to pigeons
Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x21C61F7F


signature.asc
Description: Digital signature