Steven M. Bellovin --> pkgsrc-users (2007-03-22 13:36:23 -0400):
> On Thu, 22 Mar 2007 12:51:34 -0400
> "George Georgalis" <george@galis.org> wrote:
> 
> > 
> > >I believe that that conflicts with builds using pkg_comp -- at least,
> > >I had trouble because of that.
> > 
> > haven't used pkg_comp, is the error because there is no mailer in
> > the chroot? what do you think should be done?
> > 
> I don't know why...

The problem is invoking postdrop(1) (via mail(1) -> sendmail(1)) in
the chroot because it doesn't have access to the queue directory. I
use mail/ssmtp to work around this problem.

However, IMHO it would be nice if pkg_add(8) had an option to send the
install message by mail (in addition to print it to stdout as it already
does). Any comments?


Regards, Jukka


> Here are a few messages from December about it;
> that's all I know:
> 
> 
> From: "Steven M. Bellovin" <smb@cs.columbia.edu>
> To: Jukka Salmi <j+nbsd@2006.salmi.ch>
> Cc: pkgsrc-users@NetBSD.org
> Subject: Re: 'postdrop' problem when using pkg_comp
> Date: Wed, 27 Dec 2006 10:27:49 -0500
> Sender: pkgsrc-users-owner@NetBSD.org
> X-Mailer: Claws Mail 2.6.1 (GTK+ 2.8.20; i386--netbsdelf)
> Organization: Columbia University
> 
> On Wed, 27 Dec 2006 15:28:41 +0100
> Jukka Salmi <j+nbsd@2006.salmi.ch> wrote:
> 
> > Hi,
> > 
> > Steven M. Bellovin --> pkgsrc-users (2006-12-27 09:09:49 -0500):  
> > > On several of my machines, I did a massive package rebuild using
> > > pkg_comp.  It worked fine on most of them, but on one I got many
> > > messages like this:
> > > 
> > > postdrop: warning: mail_queue_enter: create file
> > > maildrop/991808.8467: No such file or directory
> > > 
> > > I assume it had to do with invoking postfix in a chrooted
> > > environment. However, I've never seen this before, and it didn't
> > > happen on the other machines.  Any theories?  (Most of the machines
> > > in question run -current, including the failing one and some of the
> > > successful ones; one is on 3.0.1.)  
> > 
> > Is PKGSRC_MESSAGE_RECIPIENTS set in the chroot's mk.conf? If yes, try
> > unsetting it.
> >   
> Good catch; that was it. 
> 
> 
> 
> 
> 		--Steve Bellovin, http://www.cs.columbia.edu/~smb

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~