Noel J. Bergman wrote:
> <>...
> At the moment, I'm the one working on the webapp migrations, and, yes, we
> need to get it done pretty soon, but if you have time to take a look and
> come up with a better strategy, that's fine with me.
I assume the database has to be rebuilt and the ids will cha
Jean T. Anderson wrote:
> I'm happy to offer help evaluating strategies to both rebuild the
> database and retain the current ids in some usable form, if you can use
> the help.
Sure. The eyebrowse project is at http://eyebrowse.tigris.org. Daniel
knows the internals as well as anyone, better '
Jean,
As an aside, please note that mod_mbox is now installed on the new mail
archive server, as well as eyebrowse. mod_mbox uses the Message-ID, from
what I can see, and should be more of a proper URI than the fragile
eyebrowse URLs. The eyebrowse webapp would still be the best way to find
anyt
Noel J. Bergman wrote:
>
>
>... the database will have to be rebuilt, and when that happens the
>eyebrowse URLs will break. They aren't based on something content related,
>like the Message-ID or an MD5 of the Message content.
>
>
>http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]
>p
OK, got it -- I appreciate the clarifications!
thanks,
-jean
Noel J. Bergman wrote:
>Jean T. Anderson wrote:
>
>
>
>>I'm deducing from the emails this afternoon that I can't simply
>>replace the nagoya.apache.org with mail-archives.apache.org
>>
>>
>
>No, because the database will have
Jean T. Anderson wrote:
> I'm deducing from the emails this afternoon that I can't simply
> replace the nagoya.apache.org with mail-archives.apache.org
No, because the database will have to be rebuilt, and when that happens the
eyebrowse URLs will break. They aren't based on something content re
I need to state my question in another way. --I've looked back through
my emails and don't see the earlier explanations, so sorry if this is
asking what I should already know. I thought I was on too many email
lists :-) but perhaps I'm not on enough!
Given this url:
http://nagoya.apache.org/eyebr
> When is mail-archives.apache.org expected to start working for
> eyebrowse? Currently it gets "Service unavailable".
http://mail-archives.apache.org/eyebrowse/ works fine, although we still
need to rebuild the database and migrate it to ajax.
> Many Derby web site pages have pointers to specifi
> Wouldn't a straight database dump would preserve the IDs and hence
> the URLs?
We can't. We have to rebuild the databases to big gaps that weren't indexed
in the past as well as fix problems within the databases themselves. And
when we do that, poof ...
I believe that we are concurrently goin
On Thu, Dec 30, 2004 at 03:27:57PM -0800, Jean T. Anderson wrote:
> Noel J. Bergman wrote:
>
> >As previously indicated, the machine name "nagoya" is going away in very
> >short order. Projects should not have any references on their web sites to
> >any Apache machine names, only to domains such
Noel J. Bergman wrote:
>As previously indicated, the machine name "nagoya" is going away in very
>short order. Projects should not have any references on their web sites to
>any Apache machine names, only to domains such as issues, mail-archives,
>etc. Sites still referencing nagoya.apache.org w
Folks,
Please review your site materials and fix any references ASAP.
As previously indicated, the machine name "nagoya" is going away in very
short order. Projects should not have any references on their web sites to
any Apache machine names, only to domains such as issues, mail-archives,
etc.
12 matches
Mail list logo
