[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN Post Commit Email Notifications

From: Chris Wein <cwein_at_mobilygen.com>
Date: 2005-08-30 01:26:25 CEST

At first glance, I am not entirely sure if you are using the right
strategy to get more help on this issue. Nevertheless...

I think a very clear suggestion was made to break the problem down into
small parts. Debugging hook scripts is very similar to debugging cron
jobs. It is almost always about running scripts not as me, with
different environment vars etc. How about these steps...

- Having the hook script just /bin/touch /tmp/itsalive
- Having the hook script echo the rev # to the file /tmp/itsalive
- Having a perl script do same as before but with system calls
- Extend the same perl script to use the same "use XXX" to check your
perl library installation and try again

Perhaps you think that suggesting breaking the problem down into small
parts is rhetoric but I think its very good advice.

On Mon, 2005-08-29 at 16:07 -0700, S I wrote:
> As I mentioned, mail is fully configured on the server by our SYSADMIN and
> it's portable and it works. I tested it.
>
> I also tested my post-commit and commit-email.pl files manually and they run
> find at the command prompt but not triggered by SVN.
>
> You opinion is BIASED as well since you work on SVN as a developer! Things
> should NOT be so hard to configure and administer. The wheel should not be
> reinvented simply because bunch of people were FRUSTRATED an ANNOYED by CVS
> and they decided to form their own alliance to teach CVS people a lesson.
>
> I have WASTED 3 days on this PIECE OF CRAP and instead of, reading my email
> and responding to where I went wrong, you're FIRING OFF with rhetorics!
>
> So far, I DON'T like Subversion. It was forced on me and I had NO say-so on
> the matter as the
> Administrator. Now I'm stuck to learn a clumsy tool that I know nothing
> about.
>
> The chapters 1-3 of the .pdf manual are written so well but somebody just
> got lazy & lackadaisical when it came to Repository Administration chapters
> where most examples were needed for newbies like me. The Admin chapter
> hardly touches on subjects and expects us to be genius mind readers to read
> between the lines.
>
>
> ----Original Message Follows----
> From: Ben Collins-Sussman <sussman@collab.net>
> To: "S I" <xiamak@hotmail.com>
> CC: users@subversion.tigris.org
> Subject: Re: SVN Post Commit Email Notifications
> Date: Mon, 29 Aug 2005 17:45:22 -0500
> MIME-Version: 1.0 (Apple Message framework v734)
> Received: from sanpietro.red-bean.com ([66.146.194.200]) by
> mc9-f17.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 29 Aug 2005
> 15:45:26 -0700
> Received: from [192.168.1.100] (dsl092-129-143.chi1.dsl.speakeasy.net
> [66.92.129.143])(authenticated bits=0)by sanpietro.red-bean.com
> (8.13.3/8.13.3/Debian-6) with ESMTP id j7TMjPVH031686(version=TLSv1/SSLv3
> cipher=RC4-SHA bits=128 verify=NOT);Mon, 29 Aug 2005 17:45:25 -0500
> X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
> References: <BAY105-F43A004597EFC506F0DE65D8AF0@phx.gbl>
> X-Mailer: Apple Mail (2.734)
> Return-Path: sussman@collab.net
> X-OriginalArrivalTime: 29 Aug 2005 22:45:27.0078 (UTC)
> FILETIME=[599E8460:01C5ACEB]
>
>
> On Aug 29, 2005, at 5:31 PM, S I wrote:
> >
> >I tell you SVN is NOT easy to set up and configure. It was created to
> >overcome the idiosyncrasies of CVS, but does it?
>
> Are you seriously comparing CVS and SVN through such a tiny lens?
>
> Subversion gives you a very simple hook for triggering post-commit events.
> But the problem of "setting up a server to send email" is inherently
> time-consuming, and way outside the scope of Subversion itself. Mail is
> complex. Permissions are complex. That's why people hire sysadmins. I
> don't see how anything would have been any easier for you -- in this one
> narrow regard -- with CVS or any other version control system.
>
> Sorry that you're having problems. Before trying anything complex, you
> should break down the task into smaller parts. Write a 'post- commit'
> script that does nothing but echo the revnum into a tmpfile. Once you've
> got that working, you can worry about the various mail scripts and mail
> setup details. There's even a FAQ on debugging hook scripts:
>
> http://subversion.tigris.org/faq.html#hook-debugging
>
>
> --
> www.collab.net <> CollabNet | Distributed Development On Demand
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 30 01:29:31 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.