[cvsnt] Mantis and "Travis"

[Bo Berglund]

What it means is that the loginfo script file must be changed to use
/ in paths instaed of \.
>From now on \ is always treated as an escape indicator and paths with
/ specified will be properly decoded depending on the operating system.
This is true for all of the scripts, they use a common decoding engine,
which is what causes the error message to pop up in this release. The
decoding was decentralized before.

Just edit the script text and you will be fine.
You might be forced to edit in place in the repository in order to let
your proper CVS commit of the same edit through, though.

AFAICT the / path separator has worked for some time already so one
suggestion is to first change the path separator before upgrading CVSNT.
Then it will be seamless.

Bo

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Luigi D. Sandon
Sent: den 22 april 2005 16:40
To: cvsnt at cvsnt.org
Subject: [cvsnt] Mantis and "Travis"


Just upgraded to the last CVSNT release, and while committing the Mantis 
PHP script called in loginfo (ALL C:\Apps\PHP5\php.exe 
"C:\Apps\mantis-0.19.2\core\checkin.php") to store bug data in its 
database too, which worked ok with the previous version began to emit 
some errors:

<--  uPOPProcessor.pas
new revision: 1.17; previous revision: 1.16
done
Unknown escape character '\A' ignored.
Unknown escape character '\P' ignored.
Unknown escape character '\p' ignored.
Unknown escape character '\A' ignored.
Unknown escape character '\m' ignored.
Unknown escape character '\c' ignored.
Unknown escape character '\c' ignored.
Script execution failed

***** CVS exited normally with code 0 *****

What does happens? Is CVSNT "escaping" something now? Did the format of 
data changed? I am using build 1927.

--
Luigi D. Sandon
cp at sandon.it
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt