What's happened to nightly trunk builds?

[Uncle Spellbinder]

So, for several days, no updates. Is the updater having issues?

Also, checked here http://www.seamonkey-project.org/dev/nightly for the latest build. Clicked the Windows Installer link and got the following...

Not Found

The requested URL /pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/seamonkey-2.1b3pre.en-US.win32.installer.exe was not found on this server.
Apache/2.2.3 (Red Hat) Server at ftp.mozilla.org Port 80

[WaltS48]

See viewtopic.php?f=6&t=2145503 and viewtopic.php?f=6&t=2140853

I always use check for updates from the help menu.

WLS

[Uncle Spellbinder]

Thanks WLS. But help > check for updates gets me nothing. Maybe no updates the past couple days, I guess. Though it seems odd that the nightly update page provides a 404 error.

[rsx11m]

Which trunk are you talking about? There are Gecko-2.0 (mozilla-2.0 release repository) based SeaMonkey 2.1 and Gecko-2.2 (mozilla-central trunk) based SeaMonkey 2.2 nightlies now. Both are fine for Linux but failed for Windows the last few days, currently building, so maybe there will be one later today. Mac OSX is broken for SeaMonkey 2.2 trunk nightlies.

The requested URL /pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/seamonkey-2.1b3pre.en-US.win32.installer.exe was not found on this server.

The seamonkey-2.1b3pre.en-US.win32.installer.exe builds are now in the parallel latest-comm-2.0 folder, the path you mention now points to the most recent SM 2.2a1pre nightly builds.

[Uncle Spellbinder]

I'm speaking of the 2.1b3pre builds. Just got an update this afternoon.

[rsx11m]

Yepp, the 2.2a1pre nightly came out this afternoon too. Just updated, but lost all add-ons in the process...
So, it definitely seems advised to focus on 2.1b3pre for now until the "real" trunk has quieted down a bit.

[rsx11m]

Heh, it killed the "extensions" folder and ini/sqlite files in my profile, thus even going back to 2.1b3pre didn't help.
It's always good to have a backup...

[rsx11m]

I found bug 646719 on the loss of the default extensions on the 2.2a1pre trunk builds, along with some workarounds.

[rsx11m]

Looks like the March 31 were the last ones for the SM 2.2a1pre "real" trunk builds, all tinderboxes are glowing red right now. Guess it doesn't make much sense following the Gecko-2.2 builds for the time being.

[Philip Chee]

Looks like the March 31 were the last ones for the SM 2.2a1pre "real" trunk builds, all tinderboxes are glowing red right now. Guess it doesn't make much sense following the Gecko-2.2 builds for the time being.

ThunderbirdTrunk is also totally on fire. Reason is the removal of nsAutoLock.h from mozilla-central.

Phil

[James]

http://tinderbox.mozilla.org/showbuilds ... =SeaMonkey
http://tinderbox.mozilla.org/showbuilds ... rbirdTrunk
Click on previous 24 hours for each.

While Firefox seems fine for most part. http://tinderbox.mozilla.org/showbuilds ... ee=Firefox


Now where are the marshmallows...

[rsx11m]

checked here http://www.seamonkey-project.org/dev/nightly for the latest build. Clicked the Windows Installer link and got the following...

Those links are still broken, I've filed bug 647898 on that issue to be fixed. Apparently nobody else noticed this yet.