Closed Bug 350911 Opened 18 years ago Closed 18 years ago

software update nightlies stopped at version 2 alpha 1 (20060816) tbird on 10.4.7 intel mac (ub / ppc / update issue?)

Categories

(Thunderbird :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WONTFIX
Thunderbird2.0

People

(Reporter: moco, Assigned: mscott)

Details

software update nightlies stopped at version 2 alpha 1 (20060816) tbird on 10.4.7 intel mac

when I manual check updates, none are found.


preed writes:  According to http://users.ox.ac.uk/~clar0239/upwatch/latest/, I don't see any current issues with Tbird 1.8 nightly updates.

What's the full build ID of the build you're trying to update? Are you sure
it's checking the nightly channel?

my user agent is Thunderbird 2.0a1 (Macintosh/20060816) and app.update.channel
is nightly.

I'll try setting the appropriate app.update.log.* prefs to see if I can tell
what's going on.

after setting the logging prefs, I see this in my console:

update url:
https://aus2.mozilla.org/update/1/Thunderbird/2.0a1/2006081605/Darwin_ppc-gcc3/en-US/nightly/update.xml

checkForUpdates: sending request to
https://aus2.mozilla.org/update/1/Thunderbird/2.0a1/2006081605/Darwin_ppc-gcc3/en-US/nightly/update.xml

onLoad: request completed downloading document

Updates available: 0

Going to
https://aus2.mozilla.org/update/1/Thunderbird/2.0a1/2006081605/Darwin_ppc-gcc3/en-US/nightly/update.xml

gives me <updates></updates>

I'd expect there to be at least one <update> there, taking me to the latest
nightly.

maybe 8/16 is "too long ago" for nightlies and the update.xml has been removed?


preed writes:

Hrm... I think the bigger problem here is that those builds are UB (I think?),
but the update URL is using a PPC only platform.

Note that:

https://aus2.mozilla.org/update/1/Thunderbird/2.0a1/2006081605/Darwin_Universal-gcc3/en-US/nightly/update.xml

gives the right update.

Do the current nightlies have this problem? It may be that we fixed updates,
and older nightlies will not get updates because they're checking the wrong
platform.
I think they're checking the right platform (what they really are), but no provision has been made for moving PPC users over to the UB. 

Checking https://aus2.mozilla.org/update/1/$app/$version/2006030100/Darwin_ppc-gcc3/en-US/nightly/update.xml
as an example of a really old build, so that AUS returns the latest build for that platform and branch, gets

$app		$version	complete build offered
Thunderbird	1.5.0.5		2006-06-25-05 UB (by size)
Thunderbird	2.0b1		2006-08-16-05 PPC
Thunderbird	3.0a1		2006-07-06-04 PPC
Firefox		1.5.0.5		none (been Universal for ages)
Firefox		2.0b1		2006-06-30-04 PPC
Firefox		3.0a1		2006-08-12-04 PPC

(Version is not significant here, I'm just using it as a branch identifier)

So the Tb 1.5.0.x builds will be ok, but that was an accident; and updates only started working again for that branch a couple of days ago.

For the other 4, Paul would know if we can copy some UB snippets over to the PPC part of the AUS datastore, and what patcher would make of that. I guess we'd want to avoid disrupting the UB->UB updates.
coop/preed, do we have to do something server side for nightly 1.8.1 branch PPC users to get updated to UB builds? 
Flags: blocking-thunderbird2+
Target Milestone: --- → Thunderbird2.0
I talked to preed about this and there's a lot of manual work on the update side that would have to happen to move PPC nightly build testers to UB.

It sounds like the fix for nightly test users is to download a UB nightly from the usual spot. nightly updates are working just fine again once you download a new build after 08/16. 

Marking this WONTFIX per my talk with the release team.

Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
verified.

I was able to go get a slightly older nightly (but after 8/16) run it, and then update to the latest (version 2 alpha 1, 20060905).
Status: RESOLVED → VERIFIED
Removing the tb2 blocking flag since this is "WONTFIX"
Flags: blocking-thunderbird2+
You need to log in before you can comment on or make changes to this bug.