Closed Bug 299841 Opened 19 years ago Closed 19 years ago

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: benjamin, Assigned: chase)

References

Details

Currently http://bonsai-l10n.mozilla.org/ does cvslogs and blame, which pull
information directly from the repository, but don't do queries which need a
database. It would be very helpful to have the query features working as well,
so that we can see what changes are being made and enforce a freeze as necessary.

There was a little discussion about this on IRC this morning, so assigning to
coop so he can bug Chase to see whether this is hard or easy.
oh yes, this is so extremly important to get "freeze" really cold.
justdave populated the query database last night, and he is in the process of
verifying that the commit hook is properly setup.

Can people please verify that they are able to query bonsai-l10n in the ways
they want?
Status: NEW → ASSIGNED
unfortunately I didn't get to it last night because of the spreadfirefox
situation, and I'm now on vacation until the end of next week.  Myk might be
able to get it if ask nicely, otherwise I can set it up when I get back.

Just needs an alias set up on mecha to pipe mail into the l10n handlemail.pl
script, configure bonsai's dolog.pl script with that alias in it, and commit it
to the CVSROOT directory (and fix the loginfo hook to point at it).
well, basic functionality works OK, I can query bonsai now! Great :))
Some of the accounts still appears as uidXXX.

There's also small bug - when you display some file in bonsai
(http://bonsai-l10n.mozilla.org/cvsview2.cgi?subdir=l10n/pl/toolkit/chrome/mozapps/update&files=updates.properties&command=DIRECTORY&branch=HEAD&root=/l10n)
and you click on a file it doesn't appear in lxr because the path is
l10n/source/l10n/pl instead of l10n/source/pl
The question of bonsai <-> LXR links is a different bug, already filed I
believe, and is totally not needed for the 1.8 cycle.
Assignee: ccooper → justdave
Blocks: branching1.8
Status: ASSIGNED → NEW
so this should block the branch for 1.8, then?  who's working on it?

/cb
(In reply to comment #4)
> There's also small bug - when you display some file in bonsai
>
(http://bonsai-l10n.mozilla.org/cvsview2.cgi?subdir=l10n/pl/toolkit/chrome/mozapps/update&files=updates.properties&command=DIRECTORY&branch=HEAD&root=/l10n)
> and you click on a file it doesn't appear in lxr because the path is
> l10n/source/l10n/pl instead of l10n/source/pl

That's actually a bug in LXR...  bug 283427.
This is very, very important for us. As we now share the /toolkit directory,
some of the translator have to cooperate because Firefox and Thunderbird are
translated by different people. Not beeing able to track changes through bonsai
makes life a lot harder for us. Please try to get this set up as soon as
possible and please before the branching for 1.5.
Here's what needs to happen to fix this up:

1) a mail alias needs to be set up on mecha if there isn't one already that
directs mail into bonsai's checkin handler (clone the one for the main bonsai
and rename appropriately).
2) dolog.pl from bonsai needs to be modified to mail to that address and
committed to CVSROOT in the l10n repo.
3) loginfo in CVSROOT needs to be set up to invoke the dolog.pl script (check
how it's set up on the main cvsroot repo for examples)
4) cvs history on the l10n bonsai needs to be rebuilt again to get it caught up.
 (when I did it before, it took about 15 minutes)
Severity: normal → critical
Priority: -- → P1
(In reply to comment #9)
> Here's what needs to happen to fix this up:
> 
> 1) a mail alias needs to be set up on mecha if there isn't one already that
> directs mail into bonsai's checkin handler (clone the one for the main bonsai
> and rename appropriately).

I believe I did this back when I set up the bonsai-l10n instance.

> 2) dolog.pl from bonsai needs to be modified to mail to that address and
> committed to CVSROOT in the l10n repo.

The recipient address is set in loginfo, from what it appears.  dolog.pl has
been added to CVSROOT.

> 3) loginfo in CVSROOT needs to be set up to invoke the dolog.pl script (check
> how it's set up on the main cvsroot repo for examples)

loginfo change has been made.

> 4) cvs history on the l10n bonsai needs to be rebuilt again to get it caught up.
>  (when I did it before, it took about 15 minutes)

Okay, I'll kick this off.
Severity: critical → normal
Priority: P1 → --
(In reply to comment #10)
> (In reply to comment #9)
> > 2) dolog.pl from bonsai needs to be modified to mail to that address and
> > committed to CVSROOT in the l10n repo.
> 
> The recipient address is set in loginfo, from what it appears.  dolog.pl has
> been added to CVSROOT.

When committed this landed as dolog.pl,v.  Do I checkout by hand and copy into
l10n/CVSROOT/dolog.pl?  Do I wait for despot to do that for me?
(In reply to comment #11)
> When committed this landed as dolog.pl,v.  Do I checkout by hand and copy into
> l10n/CVSROOT/dolog.pl?  Do I wait for despot to do that for me?

dolog.pl needed to be added to CVSROOT/checkoutlist.  This is fixed.  Rebuilding
the database.
Assignee: justdave → chase
Fixed.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Yay, great news.

We do have some uid6xx on queries, it'd be nice to get those fixed, too.
But that is not a blocker, it would help tracking branches a good deal, though.

I'll make some noise about this tomorrow.
Thanks, Chase!
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.