I figured out, that command should look like: cvs -d :pserver:anonymous@cvs.otrs.org:/home/cvs co -r rel-2_1 otrs and then files from rel-2_1 are what I'm getting trough. :-) Alex Mihicinac wrote:
Hi Christian,
thanks for your helpful response.
Christian Schoepplein wrote:
On Mon, Feb 26, 2007 at 10:34:08AM +0100, Alex Mihicinac wrote:
I have some difficulties to enable proper use of PGP/signing outgoing mails in OTRS. I've sent status report to otrs@otrs.org, but there was no reply, so I'm trying to get some info here.
Please report that things either on this list or on
Ok, I'll keep that in mind.
AgentTicketCompose.pm 4 martin Fixed not working crypt/sign option in 1.28 days AgentTicketCompose mask.
After that I grabbed this file from CVS and replaced with installed one (OTRS 2.1.5). Then I've noticed that CVS version (2.2.X) does not match with last stable one (2.1.5). Does CVS contain devel branch of 2.1.5?
You have to check out the file from the 2.1 branch and not from cvs head, then it'll work:
cvs -d :pserver:anonymous@cvs.otrs.org:/home/cvs -b rel-2_1 co otrs
hmm... if I execute that command, this happens:
[root@splevta temp]# cvs -d :pserver:anonymous@cvs.otrs.org:/home/cvs -b rel-2_1 co otrs cvs checkout: Updating otrs U otrs/.fetchmailrc.dist U otrs/.mailfilter.dist U otrs/.procmailrc.dist U otrs/CHANGES U otrs/COPYING U otrs/CREDITS U otrs/INSTALL U otrs/INSTALL.RedHat U otrs/INSTALL.SuSE U otrs/README U otrs/README.database U otrs/README.webserver U otrs/RELEASE .....
[root@splevta temp]# cat otrs/RELEASE PRODUCT = OTRS VERSION = 2.2.x CVS [root@splevta temp]#
Is this ok? Again, I got version 2.2.x from CVS?
Best regards,
Alex
_______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Best regards, Alex