504283 - ftp://../seamonkey/nightly/latest-trunk/ was deleted, so QA "Latest Builds" was 404

Status: VERIFIED FIXED

(SeaMonkey :: General, defect)

Description

[Tobias Fischer]

Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1pre) Gecko/20090714 Mnenhy/0.7.5.20005.h4 SeaMonkey/2.0b1pre

Since yesterday the Directory:
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/
was deleted on the mozilla.org ftp-mirrors, so using the QA-Menu Entry: "Latest Builds" result in an "404 Not Found" Error. 

Due this change the possibility for an easy access to the "Latest Builds" download directory was lost 

So the URL in:
http://mxr.mozilla.org/comm-central/source/suite/debugQA/content/debugQAMenuOverlay.xul

234 <menuitem label="Latest Builds"
235           oncommand="openTopWin('http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/');"/>

should be changed to point to an existing directory. Unfortunately SeaMonkeys Trunk-Builds from ../latest-comm-central-trunk/ were not in state for daily testing at this time, but using ../latest-comm-1.9.1/ Branch-Directory is no real alternative.

Comment 1

[Robert Kaiser]

I think we should use latest-comm-1.9.1 actually right now, as that really is what the official nightlies are.

Comment 2

[Tobias Fischer]

Attachment: Simple Patch as KaiRo suggested

Well, just change the URL into ../nightly/latest-comm-1.9.1/ following KaiRo.

But this should be changed again at least, when SM 2.0 was released.

Comment 3

[Robert Kaiser]

(In reply to comment #2)
> But this should be changed again at least, when SM 2.0 was released.

Actually, it should be changed on trunk once we have branched the repository for the 1.9.1-based releases.

Comment 4

[Karsten Düsterloh]

Pushed as <http://hg.mozilla.org/comm-central/rev/b61398141cd8>.

Comment 5

[Tobias Fischer]

Verified=Fixed, tested on Windows and Linux with todays 2009072001 and 00 Nightly-Builds. Thanks for the push. 

We should keep in Mind to change the URL again, when development move back to mozilla-central after the SM 2.0 Release.

Comment 6

[Robert Roessler]

Not to be argumentative, but wasn't the original bug really about the removal of the latest-trunk *symlink*?  And if this is the case, then shouldn't the [eventual] fix involve recreating a symlink (that would point to the appropriate place) with this name?

Comment 7

[Robert Kaiser]

The symlink was removed intentionally to avoid confusion and this was announced beforehand in http://home.kairo.at/blog/2009-07/changes_to_seamonkey_nightlies_and_tinde Phase II (third bullet)