bzr email commit hook

Bug #307988
Comment #5

Comment 5 for bug 307988

Revision history for this message

Trevor Jim (trevor-research) wrote on 2008-12-26: Re: [Bug 307988] Re: Central repository email?

brainsik wrote:
> I also use a central server model and I was able to get emails to go out
> from the central server today after commits via bzr+ssh. However, I had
> to put:
>
> post_commit_push_pull = True
>
> in the Bazaar conf to make it work.

Hi, thanks for the pointer. Unfortunately, I'm still having problems.

The server is running CentOS, the client Ubuntu Intrepid.
I am using the latest bzr-email from launchpad.

Mailer on server is /bin/mail, mailer on client is /usr/bin/mail.
These are different programs and the server mailer does not
accept the -a argument.

I modified bzr-email on the server so that it does not use -a.

If I checkout the repository from the server, ON the server,
and then do commits, I get the commit messages; so my -a hack
works when everything is run on the server (with bzr+ssh or file).

If I checkout the repository from the server on the CLIENT,
I get different behavior. If bzr-email is not installed
on the client, there is no mail and no error message when
I do a commit on the client.
If bzr-email is installed on the client, I get an error
message when I do a commit on the client. Seems like this is
because /bin/mail does not exist on the client. (I have
/bin/mail configured in the branch.conf on the server.)

The behavior is the same whether post_commit_push_pull is
set to True or not set at all in the branch.conf file on the
server.

I suppose I could hack things up to get around the different
mailers, but that would not get me to my goal:

What I was trying to do was have the server itself send the
email. I don't want the client to send the email, because I
don't want the client to have to configure things. The client
should not have to install the bzr-email plugin, for example.

Given the behavior I'm seeing I don't understand Robert's comment,

> bzr-email supports this just fine; install it on the server, set up your
> branch.conf appropriately, and be sure to use bzr+ssh for your clients
> so the hooks get invoked on the server.

Thanks for any help,
-Trevor

brainsik wrote:
> I also use a central server model and I was able to get emails to go out
> from the central server today after commits via bzr+ssh. However, I had
> to put:
> 
> post_commit_push_pull = True
> 
> in the Bazaar conf to make it work.

Hi, thanks for the pointer.  Unfortunately, I'm still having problems.

The server is running CentOS, the client Ubuntu Intrepid.
I am using the latest bzr-email from launchpad.

Mailer on server is /bin/mail, mailer on client is /usr/bin/mail.
These are different programs and the server mailer does not
accept the -a argument.

I modified bzr-email on the server so that it does not use -a.

If I checkout the repository from the server, ON the server,
and then do commits, I get the commit messages; so my -a hack
works when everything is run on the server (with bzr+ssh or file).

If I checkout the repository from the server on the CLIENT,
I get different behavior.  If bzr-email is not installed
on the client, there is no mail and no error message when
I do a commit on the client.
If bzr-email is installed on the client, I get an error
message when I do a commit on the client.  Seems like this is
because /bin/mail does not exist on the client.  (I have
/bin/mail configured in the branch.conf on the server.)

The behavior is the same whether post_commit_push_pull is
set to True or not set at all in the branch.conf file on the
server.

I suppose I could hack things up to get around the different
mailers, but that would not get me to my goal:

What I was trying to do was have the server itself send the
email.  I don't want the client to send the email, because I
don't want the client to have to configure things.  The client
should not have to install the bzr-email plugin, for example.

Given the behavior I'm seeing I don't understand Robert's comment,

> bzr-email supports this just fine; install it on the server, set up your
> branch.conf appropriately, and be sure to use bzr+ssh for your clients
> so the hooks get invoked on the server.

Thanks for any help,
-Trevor