Update aus2-community to current AUS code as of mid-June 2011

RESOLVED FIXED

Status

SeaMonkey
Release Engineering
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: Robert Kaiser, Assigned: Robert Kaiser)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

7 years ago
I'll start work right now on updating the aus2-community server to current AUS code, just want something here in Bugzilla to tell what's up and point to in case of problems.

Here's a list of update URLs I'll check afterward and that I have checked right now on the current version (stating what they do right now):
https://aus2-community.mozilla.org/update/1/SeaMonkey/2.1pre/20110531202824/Linux_x86-gcc3/de/release/update.xml?force=1 - offers 2.1 final
https://aus2-community.mozilla.org/update/1/SeaMonkey/2.2a1pre/20110531202824/Linux_x86-gcc3/de/nightly/update.xml?force=1 - offers current 2.4a1 nightly
https://aus2-community.mozilla.org/update/3/SeaMonkey/2.1.1pre/2009091700/WINNT_x86-msvc/en-US/nightly/Windows_NT%206.1/default/default/update.xml?force=1 - offers nothing right now (looks like a bug!)
https://aus2-community.mozilla.org/update/1/SeaMonkey/2.0pre/2009091700/Linux_x86-gcc3/en-US/nightly/update.xml?force=1 - offers last 2.0.15pre nightly
https://aus2-community.mozilla.org/update/1/SeaMonkey/2.3a2/20110531202824/Linux_x86-gcc3/de/nightly/update.xml?force=1 - offers current 2.3a2 (aurora) build
https://aus2-community.mozilla.org/update/3/SeaMonkey/2.0.4/20100317120533/WINNT_x86-msvc/en-US/release/Linux%202.6.35.1-1.1-desktop%20(GTK%202.21.5)/default/default/update.xml?force=1 - offers 2.0.14

I'll probably try some updates on actual builds well.

As a side note, I wonder if we want to update 2.0/2.1 nightly users to, say, aurora?
(Assignee)

Comment 1

7 years ago
Here's one with a 2.4a1 number just to make sure:
https://aus2-community.mozilla.org/update/1/SeaMonkey/2.4a1/20110531202824/Linux_x86-gcc3/de/nightly/update.xml?force=1 - offers latest 2.4a1 nightly

And those two may change the result when the updates are deployed:
https://aus2-community.mozilla.org/update/1/SeaMonkey/2.3a2/20110531202824/Linux_x86-gcc3/de/nightly/update.xml?force=1 - offers current 2.3a2 (aurora) build (bug, probably!)
https://aus2-community.mozilla.org/update/1/SeaMonkey/2.4a1/20110531202824/Linux_x86-gcc3/de/aurora/update.xml?force=1 - offers nothing right now (bug, probably!)

(In reply to comment #0)
> https://aus2-community.mozilla.org/update/1/SeaMonkey/2.3a2/20110531202824/
> Linux_x86-gcc3/de/nightly/update.xml?force=1 - offers current 2.3a2 (aurora)
> build

And it's the wrong URL for what Aurora build actually send, as it's on the "nightly" channel, see above.

The right one for those builds is:
https://aus2-community.mozilla.org/update/1/SeaMonkey/2.3a2/20110531202824/Linux_x86-gcc3/de/aurora/update.xml?force=1 - offers nothing right now (bug I'm doing this for!)
(Assignee)

Comment 2

7 years ago
The update also contains the changes from bug 660086, the "auroratest" channel goes to comm-aurora-test.

I also tried to add list of platforms that a major update from 2.0* should ignore, including Mac OS X 10.4 - same list as used in bug 640044.
(Assignee)

Comment 3

7 years ago
The update is done now, here's my fast test results:

(In reply to comment #0)
Here's a list of update URLs I'll check afterward and that I have checked right now on the current version (stating what they do right now):

https://aus2-community.mozilla.org/update/1/SeaMonkey/2.1pre/20110531202824/ Linux_x86-gcc3/de/release/update.xml?force=1 - offers 2.1 final
Same post-update.

https://aus2-community.mozilla.org/update/1/SeaMonkey/2.2a1pre/20110531202824/Linux_x86-gcc3/de/nightly/update.xml?force=1 - offers current 2.4a1 nightly
Same post-update.

https://aus2-community.mozilla.org/update/3/SeaMonkey/2.1.1pre/2009091700/WINNT_x86-msvc/en-US/nightly/Windows_NT%206.1/default/default/update.xml?force=1 - offers nothing right now (looks like a bug!)
Same post-update. The bug is that AUS has no updates at all in /opt/aus2/incoming/2/SeaMonkey/comm-2.0/* so it can't offer any. As mentioned before, I'd propose to offer those (and 2.0.* nightly users?) and update to comm-aurora. Given they are on the "nightly" channel, they'll be switched to -central with the next update, though.

https://aus2-community.mozilla.org/update/1/SeaMonkey/2.0pre/2009091700/Linux_x86-gcc3/en-US/nightly/update.xml?force=1 - offers last 2.0.15pre nightly
Same post-update.

https://aus2-community.mozilla.org/update/1/SeaMonkey/2.3a2/20110531202824/Linux_x86-gcc3/de/aurora/update.xml?force=1 - offers nothing right now (bug I'm doing this for!)
Post-update, offers current 2.3a2 (aurora) build \o/

https://aus2-community.mozilla.org/update/3/SeaMonkey/2.0.4/20100317120533/WINNT_x86-msvc/en-US/release/Linux%202.6.35.1-1.1-desktop%20(GTK%202.21.5)/default/default/update.xml?force=1 - offers 2.0.14
Same post-update.

(In reply to comment #1)
> Here's one with a 2.4a1 number just to make sure:
https://aus2-community.mozilla.org/update/1/SeaMonkey/2.4a1/20110531202824/Linux_x86-gcc3/de/nightly/update.xml?force=1 - offers latest 2.4a1 nightly
Same post-update.

And those two may change the result when the updates are deployed:
https://aus2-community.mozilla.org/update/1/SeaMonkey/2.3a2/20110531202824/Linux_x86-gcc3/de/nightly/update.xml?force=1 - offers current 2.3a2 (aurora) build (bug, probably!)
Post-update, offers current 2.4a1 nightly build \o/

https://aus2-community.mozilla.org/update/1/SeaMonkey/2.4a1/20110531202824/Linux_x86-gcc3/de/aurora/update.xml?force=1 - offers nothing right now (bug, probably!)
Post-update, offers current 2.3a2 (aurora) build \o/

> I'll probably try some updates on actual builds well.

Will look into that now, but this should be done!
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Assignee)

Comment 4

7 years ago
(In reply to comment #3)
> > I'll probably try some updates on actual builds well.
> 
> Will look into that now, but this should be done!

Actually, we got a problem there, builds are taking the mozconfigs from buildbot-configs tip, and the patch to set them to the aurora channel landed only on seamonkey-production - and so aurora builds come with the nightly channel set :(
(Assignee)

Comment 5

7 years ago
(In reply to comment #4)
> (In reply to comment #3)
> > > I'll probably try some updates on actual builds well.
> > 
> > Will look into that now, but this should be done!
> 
> Actually, we got a problem there, builds are taking the mozconfigs from
> buildbot-configs tip, and the patch to set them to the aurora channel landed
> only on seamonkey-production - and so aurora builds come with the nightly
> channel set :(

Having that corrected manually in my builds, updates work fine, though, on both nightly (32 bit and 64 bit Linux) and aurora (both en-US and de tested).
You need to log in before you can comment on or make changes to this bug.