Can't commit due to perl upgrade

Started by Alvaro Herreraover 19 years ago3 messages
#1Alvaro Herrera
alvherre@commandprompt.com

Hi,

I just tried to commit a patch to CVS and got this error:

cvs commit: cannot exec /usr/local/bin/activitymail: No such file or directory

I went and checked /usr/local/bin/activitymail, and it's there, but the
#! header points to /usr/local/bin/perl5.8.7 while on postgresql.org I
see /usr/local/bin/perl5.8.8 instead.

Thanks,

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

#2Marc G. Fournier
scrappy@postgresql.org
In reply to: Alvaro Herrera (#1)
Re: Can't commit due to perl upgrade

Try now, should be fixed ... not sure why it was hard coded with 5.8.7,
but I've reinstalled, and seems to run fine now ...

On Sun, 23 Apr 2006, Alvaro Herrera wrote:

Hi,

I just tried to commit a patch to CVS and got this error:

cvs commit: cannot exec /usr/local/bin/activitymail: No such file or directory

I went and checked /usr/local/bin/activitymail, and it's there, but the
#! header points to /usr/local/bin/perl5.8.7 while on postgresql.org I
see /usr/local/bin/perl5.8.8 instead.

Thanks,

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

#3Alvaro Herrera
alvherre@commandprompt.com
In reply to: Marc G. Fournier (#2)
Re: Can't commit due to perl upgrade

Marc G. Fournier wrote:

Try now, should be fixed ... not sure why it was hard coded with 5.8.7,
but I've reinstalled, and seems to run fine now ...

Yeah, it worked. Thanks.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support