In terms of general timelines, I’d expect RT2 to be significantly
more usable within the month. Once we have better admin tools and
ACLS (both of which I’m working on), It’ll be time for an alpha 
jesse
jesse reed vincent — root@eruditorum.org — jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
“Mary had a crypto key / She kept it in escrow
And everything that Mary said / The Feds were sure to know” – Sam Simpson
In terms of general timelines, I’d expect RT2 to be significantly
more usable within the month. Once we have better admin tools and
ACLS (both of which I’m working on), It’ll be time for an alpha
HaloO from a newbie to the list.
Does that mean the current state of the CVS could be used for experiments?
Or in other words is it useful for something else than development?
Regards, TSa.
Thomas Sandlaß, Orthogon GmbH
Does that mean the current state of the CVS could be used for experiments?
Or in other words is it useful for something else than development?
Absolutely.
Spell checkers are for wimps
(please send feedback on all typos)
Does that mean the current state of the CVS could be used for experiments?
Or in other words is it useful for something else than development?Absolutely.
…but, as the current CVS probably contains bugs, and as it doesn’t have
admin-tools, it’s generally not that interessting unless you have a little
bit of development skills
Spell checkers are for wimps
(please send feedback on all typos)
HaloO Tobias,
Does that mean the current state of the CVS could be used for experiments?
Or in other words is it useful for something else than development?Absolutely.
Ahh, sounds great. And since you answer to me directly I would like to ask
some questions and to offer help as far as that is possible. I didn’t talk
to my boss yet but I have some hopes that I persuade him to join your
effort. At least as alpha tester with programming background. I mean I’m
hacking our main product, the ODS Toolbox and used to program in Perl 4.0
when I was a sysadmin at the university of Stuttgart.Does that qualify me for something useful?
Certainly
What would you suggest as a starter?
Give RT2 installation a shot. Play with it.
Start poking through the code
Our main problem here is that we are using GNATS for bug tracking and
Jitterbug as trouble ticket system for customers with support contracts.
And some customers track their requests as well. So for a typical incident
we have three ids! But the worst is that no immediate status reports
can be generated. They have to be grep’ed from GNATS and Jitterbug
And lot’s of branches with customers specific enhancements in CVS
complicate things even more.
Yikes!
Questions:
- How hard coded is the status of a request? We need definitly
more than 3 (open, stalled, resolved). I’ve seen it is just a 10 character
field in the Tickets table. But I’ve no idea yet how much the Perl code
has the states hard-wired.
Right now it’s hard coded in 2-3 places. it should get modified to be hardcoded
in only one place in the near future
I have of course read the schedule on the Web:
August
2.1 Extensions to RT core for “Bug tracking”September
2.1/2.3 Extensions to RT core for basic “Project Management”Which seems to be what we need.
- Does “Project Management” involve a CVS interface? What I think of
is basically a new table with branch versus bug state.
Project managment was meant =~ ms project, rather than an IDE…
If anything, that would fall under bug tracking. It would help a great deal
if you could start by figuring out definite requirements of such a system.
-j
Regards, TSa.
±-------------------- Thomas Sandlaß, Orthogon GmbH ------------------+
| Vaihinger Str. 169, 70567 Stuttgart |
| E-Mail: Thomas.Sandlass@orthogon.de |
±-------- Tel: +49-711-78 19 60-26, Fax: +49-711-78 19 60-21 ---------+ORTHOGON and ODS Toolbox are registered trademarks of Orthogon GmbH
jesse reed vincent — root@eruditorum.org — jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
Gur SOV jnagf gb znxr guvf fvt vyyrtny.
OK, found the issue with the PERL stuff - seems that some of their C
code had the definition order reversed. Once I fixed it, no worries!
Now, the perennial problem with the mail gateway. Once I found the
permissions error with the log directory (needs 777 set on the top
level, since nobody (web), rt and daemon all write to it) and got that
error fixed, I started having other issues.
Here is the error I am seeing when trying to send mail to rt-abuse. RT
v1 is still up and running correctly, and when I repoint the aliases
file can successfully build a ticket, so I am fairly confident that no
new users need to be created.
Possible unintended interpolation of @inflow in string at
/opt/rt2/etc/config.pm line 142.
Use of uninitialized value in split at /usr/local/lib/perl5/5.6.1/Cwd.pm
line 103.
Create user failed in mailgateway: Could not create user
Could not create userNo recipient addresses found in header
Can’t locate object method “warn” via package “Log::Dispatch” (perhaps
you forgot to load “Log::Dispatch”?) at /dev/fd/3 line 511.
554 |"/opt/rt2/bin/rt-mailgate --queue abuse --action correspond"…
unknown mailer error 255
I re-installed Log::Dispatch (it was already there, just a minor rev
behind) and it completed all tests sucessfully, sending the test email
to my INBOX. Still getting this error.
Is there any other debug info I could send along to help?
Thanks,
OK, found the issue with the PERL stuff - seems that some of their C
code had the definition order reversed. Once I fixed it, no worries!Now, the perennial problem with the mail gateway. Once I found the
permissions error with the log directory (needs 777 set on the top
level, since nobody (web), rt and daemon all write to it) and got that
error fixed, I started having other issues.
The config file should have a note about the fact that this directory
must be writable by members of group ‘rt’. It will in 1.3.100
Possible unintended interpolation of @inflow in string at
/opt/rt2/etc/config.pm line 142.
Sounds like you have an unescaped @ in your config.pm
Use of uninitialized value in split at /usr/local/lib/perl5/5.6.1/Cwd.pm
line 103.
Dunno about this one.
Create user failed in mailgateway: Could not create user
Could not create userNo recipient addresses found in header.
That sounds a little weird, but I’d have to see the message and DB to
know for sure.
Can’t locate object method “warn” via package “Log::Dispatch” (perhaps
you forgot to load “Log::Dispatch”?) at /dev/fd/3 line 511.
Sorry. this will be fixed in 1.3.100. it should have been ‘warning’.
For now, just change ‘warn’ to ‘warning’ on line 511 of rt-mailgate
554 |“/opt/rt2/bin/rt-mailgate --queue abuse --action correspond”…
unknown mailer error 255
jesse reed vincent – root@eruditorum.org – jesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
Emacs is a pretty good operating system, but Unix has a better editor.
OK, fixed line 511, that cleared up the rejection via email. Also
escaped the ‘@’ in the email address, so that error is resolved.
Now, it appears that the email is going through OK, but the ticket never
shows up in the database, and there are some strange errors in the log
files.
All told, the database is only 23K when gzipped, and the log files are
miniscule.
Should I attach them to the list? Or to you privately?
Much appreciation for the help.
Date: Tue, 12 Jun 2001 21:15:43 -0400
From: Jesse jesse@fsck.com
To: “Ed Vazquez, Jr.” evazquez@inflow.com
Cc: rt-users@lists.fsck.com
Subject: Re: [rt-users] RT2On Tue, Jun 12, 2001 at 04:57:30PM -0600, Ed Vazquez, Jr. wrote:
OK, found the issue with the PERL stuff - seems that some of their C
code had the definition order reversed. Once I fixed it, no worries!Now, the perennial problem with the mail gateway. Once I found the
permissions error with the log directory (needs 777 set on the top
level, since nobody (web), rt and daemon all write to it) and got that
error fixed, I started having other issues.The config file should have a note about the fact that this directory
must be writable by members of group ‘rt’. It will in 1.3.100Possible unintended interpolation of @inflow in string at
/opt/rt2/etc/config.pm line 142.Sounds like you have an unescaped @ in your config.pm
Use of uninitialized value in split at /usr/local/lib/perl5/5.6.1/Cwd.pm
line 103.Dunno about this one.
Create user failed in mailgateway: Could not create user
Could not create userNo recipient addresses found in header.That sounds a little weird, but I’d have to see the message and DB to
know for sure.Can’t locate object method “warn” via package “Log::Dispatch” (perhaps
you forgot to load “Log::Dispatch”?) at /dev/fd/3 line 511.Sorry. this will be fixed in 1.3.100. it should have been ‘warning’.
For now, just change ‘warn’ to ‘warning’ on line 511 of rt-mailgate554 |“/opt/rt2/bin/rt-mailgate --queue abuse --action correspond”…
unknown mailer error 255