Closed
Bug 522681
Opened 17 years ago
Closed 17 years ago
Please start indexing releases/comm-1.9.1 on mxr
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: standard8, Assigned: justdave)
References
Details
Bug 522460 is setting up http://hg.mozilla.org/releases/comm-1.9.1
Please can this be indexed on mxr as well.
I believe mxr runs client.py, if so, it shouldn't need any extra arguments (I don't know if it has any on comm-central at the moment).
| Reporter | ||
Updated•17 years ago
|
Summary: Please start indexing releases/comm-1.9.1 on mxr (once bug 522460 is fixed). → Please start indexing releases/comm-1.9.1 on mxr
Updated•17 years ago
|
Assignee: server-ops → justdave
| Reporter | ||
Comment 1•17 years ago
|
||
I just remembered, we'll be swapping the comm-central builds to pull mozilla/ from mozilla-central not mozilla-1.9.1, so do we need a further change to change the "Hg Log" and "Hg Blame" links?
| Reporter | ||
Comment 2•17 years ago
|
||
Oh and if you hadn't seen we're expecting to formally branch on Thursday 22nd.
| Assignee | ||
Comment 3•17 years ago
|
||
Can you point me at instructions for how to make an initial checkout of this? (and the proper way to update it as well?)
| Reporter | ||
Comment 4•17 years ago
|
||
https://developer.mozilla.org/en/Comm-central_source_code_%28Mercurial%29
https://developer.mozilla.org/En/Simple_Thunderbird_build
In essence, an initial checkout is:
hg clone http://hg.mozilla.org/comm-central/ src
cd src
python client.py checkout
To update the checkout:
cd src
python client.py checkout
For 1.9.1 replace http://hg.mozilla.org/comm-central/ with http://hg.mozilla.org/releases/comm-1.9.1/
Note that until we formally branch tomorrow, pulling comm-central and then doing python client.py checkout will currently get mozilla-1.9.1. You can override that with --mozilla-repo=http://hg.mozilla.org/mozilla-central/. Alternately just wait for us to branch comm-central in which case client.py will archive the old mozilla/ directory and replace with a new clone of mozilla-central.
| Assignee | ||
Comment 5•17 years ago
|
||
OK, so for best performance on MXR I need to wait until you actually branch before I set this up.
| Reporter | ||
Comment 6•17 years ago
|
||
(In reply to comment #5)
> OK, so for best performance on MXR I need to wait until you actually branch
> before I set this up.
We've now done the branch - comm-central will pull mozilla-central, comm-1.9.1 will pull mozilla-1.9.1.
| Reporter | ||
Comment 7•17 years ago
|
||
Just to note: http://mxr.mozilla.org/comm-central has switched itself to mozilla-central, and is now reporting .mozilla-1.9.1/ which is the archived directory, this will obviously need cleaning up.
| Assignee | ||
Comment 8•17 years ago
|
||
So if I push this out tomorrow, the instructions in comment 4 are still valid?
| Reporter | ||
Comment 9•17 years ago
|
||
(In reply to comment #8)
> So if I push this out tomorrow, the instructions in comment 4 are still valid?
Yes.
Comment 10•17 years ago
|
||
(In reply to comment #7)
> Just to note: http://mxr.mozilla.org/comm-central has switched itself to
> mozilla-central, and is now reporting .mozilla-1.9.1/ which is the archived
> directory, this will obviously need cleaning up.
Bug 522460 comment 11.
| Assignee | ||
Comment 11•17 years ago
|
||
Deployed. http://mxr.mozilla.org/comm-1.9.1/
Will probably be a couple hours before you have a searchable index though. Currently set to update daily.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 12•17 years ago
|
||
This isn't quite right:
http://mxr.mozilla.org/comm-1.9.1/source/mozilla/config/milestone.txt
shows 1.9.3a1pre which indicates it is pulling in mozilla-central.
(In reply to comment #4)
> Note that until we formally branch tomorrow, pulling comm-central and then
> doing python client.py checkout will currently get mozilla-1.9.1. You can
> override that with --mozilla-repo=http://hg.mozilla.org/mozilla-central/.
> Alternately just wait for us to branch comm-central in which case client.py
> will archive the old mozilla/ directory and replace with a new clone of
> mozilla-central.
Hmm, I wonder if this confused you, the --mozilla-repo override was only needed in the comm-central version before we did the branch. Apologies if it did confuse you.
Also, I don't yet see comm-1.9.1 on http://mxr.mozilla.org/ - does that get automatically added at some stage?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 13•17 years ago
|
||
I didn't use that option because I was under the impression that you already branched, so I didn't need it anymore.
However, reviewing my command line history, it looks like I forgot to swap the repo name, and indeed did check out comm-central :|
(In reply to comment #12)
> Also, I don't yet see comm-1.9.1 on http://mxr.mozilla.org/ - does that get
> automatically added at some stage?
No, that has to be done manually, too. I forgot that one. I just added it.
The repo is checking out again now, I'll close the bug again when it completes.
| Assignee | ||
Comment 14•17 years ago
|
||
OK, source has been re-checked out. It's indexing now. As before, it may be an hour or so before search works. milestone.txt reads 1.9.1.5pre now.
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Comment 15•17 years ago
|
||
(In reply to comment #13)
> (In reply to comment #12)
> > Also, I don't yet see comm-1.9.1 on http://mxr.mozilla.org/ - does that get
> > automatically added at some stage?
>
> No, that has to be done manually, too. I forgot that one. I just added it.
If you're editing mxr's source code, please either file a MXR bug with a patch or commit the change to the mxr repo (http://hg.mozilla.org/webtools/mxr/) yourself. Having local patches is not fun and just leads to problems in the future.
Comment 16•17 years ago
|
||
(In reply to comment #10)
> (In reply to comment #7)
> > Just to note: http://mxr.mozilla.org/comm-central has switched itself to
> > mozilla-central, and is now reporting .mozilla-1.9.1/ which is the archived
> > directory, this will obviously need cleaning up.
>
> Bug 522460 comment 11.
Please, do delete '/.mozilla-1.9.1' backup dir from comm-central working copy.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 17•17 years ago
|
||
(In reply to comment #16)
> Please, do delete '/.mozilla-1.9.1' backup dir from comm-central working copy.
There is no such directory on the filesystem. Where you do see it?
Comment 18•17 years ago
|
||
(In reply to comment #17)
> Where you do see it?
Example:
[
http://mxr.mozilla.org/comm-central/find?text=&kind=text&string=%2F%5C.cvsignore%24
...
/directory/c-sdk/.cvsignore
/.mozilla-1.9.1/dbm/tests/.cvsignore
...
]
| Assignee | ||
Comment 19•17 years ago
|
||
Ahhh... comm-central, not comm-1.9.1. You confused me by reopening this bug about it. This bug is about comm-1.9.1, not comm-central.
It's gone. The search entries should disappear on the next indexing pass.
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•