Hi,
some days ago I promised to share the perl code I wrote to
create tickets via an external HTML form using the commandline.
I created some HTML files and made them available on:
Any comments, hints, ideas are welcome.
Ritschi =B-)
Lose your dreams and you will lose your mind
Rolling Stones - Ruby Tuesday
I’m curious - why this approach rather than a NoAuth web page
within RT?
Thanks,
Steve
At 07:10 PM 2/17/2004 +0100, Joachim Ritschmann wrote:
Failed to fetch
http://people.debian.org/~sjq/debian/dists/woody/rt3/binary-i386/Packages
404 Not Found
Failed to fetch
http://people.debian.org/~sjq/debian/dists/woody/rt3/source/Sources 404
Not Found
So, these seem to have disappeared. Are they coming back? Is there
another repository? Those packages made life so nice! 
Greig McGill
I’m curious - why this approach rather than a NoAuth web page
within RT?
I have the same question, although it looks like what you’ve done is
nice.
I’m personally in the middle of attempting to modify SelfService so it
would actually use custom fields – we definitely need specific
information from users, and I don’t think making everyone privileged is
a decent solution. I find it interesting that the perl code for ticket
creation in SelfService is rather different than the code used for
ticket creation in the privileged interface (under /share/html/Ticket).
Of course, being new to perl doesn’t make it any easier.
ph.
Greig McGill wrote:
Failed to fetch
http://people.debian.org/~sjq/debian/dists/woody/rt3/binary-i386/Packages
404 Not Found
Failed to fetch
http://people.debian.org/~sjq/debian/dists/woody/rt3/source/Sources 404
Not FoundSo, these seem to have disappeared. Are they coming back? Is there
another repository? Those packages made life so nice!
or perhaps they have been updated. did you run apt-get update?
sometimes this happens if you try to retrieve something during a mirror
update.
Failed to fetch
http://people.debian.org/~sjq/debian/dists/woody/rt3/binary-i386/Packages
404 Not Found
Failed to fetch
http://people.debian.org/~sjq/debian/dists/woody/rt3/source/Sources
404 Not FoundSo, these seem to have disappeared. Are they coming back? Is there
another repository? Those packages made life so nice!or perhaps they have been updated. did you run apt-get update?
sometimes this happens if you try to retrieve something during a mirror
update.
Yep - that was from an apt-get update. The ~sjq package repository is no
longer there.
Greig McGill
I’m personally in the middle of attempting to modify SelfService so it
would actually use custom fields – we definitely need specific
information from users, and I don’t think making everyone privileged is
a decent solution. I find it interesting that the perl code for ticket
creation in SelfService is rather different than the code used for
ticket creation in the privileged interface (under /share/html/Ticket).Of course, being new to perl doesn’t make it any easier.
I found it easier just to take the Ticket/Create.html doc and make a
custom version of it.
Then I made custom versions of /Ticket/Elements/EditCustomFields and
/Ticket/Elements/EditCustomField and pointed my newly created document
(Systems-Create.html) to the new EditCustomFields doc, which needed to
be changed to point to my new EditCustomField doc.
EditCustomFields isn’t very different from stock at all, mainly it’s
additions to point to a new mason doc that I created so that you can
click on a link and pop up a little window that displays a table with
values and descriptions for the clicked custom field.
I modified EditCustomField more heavily. It has dynamic rowsize for
custom fields of type ‘FreeformMultiple’ with a max of 30. And also a
few cheesy lines that choose different SELECTED items for custom
fields of type ‘Select’, like:
$Default = “CSS” if $CustomField->Name eq “Group”;
% if ($TicketObj) {
<% $Values->HasEntry($value->Name) && ($selected = 1) && ‘SELECTED’ %>
% } elsif ($Default) {
<% ($Default eq $value->Name) && ($selected = 1) && ‘SELECTED’ %>
% }
Andy Harrison
(full headers for details)
Greig McGill wrote:
Failed to fetch
http://people.debian.org/~sjq/debian/dists/woody/rt3/binary-i386/Packages
404 Not Found
Failed to fetch
http://people.debian.org/~sjq/debian/dists/woody/rt3/source/Sources
404 Not FoundSo, these seem to have disappeared. Are they coming back? Is there
another repository? Those packages made life so nice!or perhaps they have been updated. did you run apt-get update?
sometimes this happens if you try to retrieve something during a mirror
update.Yep - that was from an apt-get update. The ~sjq package repository is no
longer there.
didn’t notice you were pulling from a user’s directory. Sorry about
that. 3.0.8 is in unstable and 3.0.6 is in sarge (the next release).
Sarge is shaping up nicely, you might want to consider upgrading.
Otherwise, backporting it should not be too hard. The worst of it will
probably be the perl depends.
didn’t notice you were pulling from a user’s directory. Sorry about
that. 3.0.8 is in unstable and 3.0.6 is in sarge (the next release).Sarge is shaping up nicely, you might want to consider upgrading.
Otherwise, backporting it should not be too hard. The worst of it will
probably be the perl depends.
Hmmm, I think you’re missing my point!
Someone already has backported it to woody. That someone being Stephen
Quinney. Duplicating all that work would be a waste of time.
I’m simply wondering where the existing backport has gone.
By the way, sorry for CC’ing you before. The webmail client I’m using has
no reply-to-list function, and this list doesn’t do reply-to munging it
seems. Guess which side of that holy way I fall on? 
Greig McGill
didn’t notice you were pulling from a user’s directory. Sorry about
that. 3.0.8 is in unstable and 3.0.6 is in sarge (the next release).Sarge is shaping up nicely, you might want to consider upgrading.
Otherwise, backporting it should not be too hard. The worst of it will
probably be the perl depends.Hmmm, I think you’re missing my point!
Someone already has backported it to woody. That someone being Stephen
Quinney. Duplicating all that work would be a waste of time.
I’m simply wondering where the existing backport has gone.
Apologies for not saying anything about this before now.
When Debian had some of its servers cracked a while back all the stuff
in people’s public_html directories on people.debian.org got removed
and we all lost our logins for a while. Since then i’ve not had the
time to recreate all the backports of packages needed to get rt3 for
woody.
There is also the fact that people are seeing such huge improvements
with perl 5.8.3 over any previous version of perl. This suggests to me
that I shouldn’t really be encouraging people to use rt3 with perl 5.6.
As it stands I am not going to have the time for a while to get back
to this, (we may or may not want woody packages of rt3 at my work). I
would recommend that people seriously consider running a sarge box if
they want rt3 with Debian now. It has all the packages you need and
should be using to run rt3, with full support from myself and the
other maintainer of the request-tracker3 package.
Stephen Quinney
signature.asc (189 Bytes)
Apologies for not saying anything about this before now.
When Debian had some of its servers cracked a while back all the stuff
in people’s public_html directories on people.debian.org got removed
and we all lost our logins for a while. Since then i’ve not had the
time to recreate all the backports of packages needed to get rt3 for
woody.There is also the fact that people are seeing such huge improvements
with perl 5.8.3 over any previous version of perl. This suggests to me
that I shouldn’t really be encouraging people to use rt3 with perl 5.6.As it stands I am not going to have the time for a while to get back
to this, (we may or may not want woody packages of rt3 at my work). I
would recommend that people seriously consider running a sarge box if
they want rt3 with Debian now. It has all the packages you need and
should be using to run rt3, with full support from myself and the
other maintainer of the request-tracker3 package.Stephen Quinney
Thanks Stephen. Mystery solved!
Greig.