Closed Bug 542659 Opened 14 years ago Closed 14 years ago

Can't update older builds of Minefield

Categories

(AUS Graveyard :: General, defect)

Product:
AUS Graveyard
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: limi, Assigned: morgamic)

Details

My build didn't get an update after not being used for a while, it was using the following URL to check for updates:

https://aus2.mozilla.org/update/3/Firefox/3.7a1pre/20090908175823/Darwin_x86-gcc3/en-US/default/Darwin%2010.2.0/default/default/update.xml?force=1

Suggestion would be to serve the latest update file instead of a empty update file when it doesn't exist.

Build ID:
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a1pre) Gecko/20090908 Minefield/3.7a1pre
From the Darwin_x86-gcc3 in the URL you have a shark build, or stripped the PPC portion of a universal binary. Either way we don't offer updates. Shark might be possible depending on how we solve bug 534954.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Ah, that would explain it. Thanks!
Updates of shark builds would be ideal, but until then, is there any way we can disable the "Check for Updates" for those builds, so it's a bit more obvious what's going on?
nthomas, it *might* be a good thing to disable the updater (removes check for updates, etc.) for shark builds until there is a fix for bug 534954... I'm fine either way.
It would be quick to disable the updater for shark, at the cost of never updating people who grab a build between now and fixing 534954 (which we're aiming for this quarter). Pick one!
Let's leave it enabled... there aren't many people using Shark builds that fall into this category and those that do will update to the latest when that is fixed.
Yeah, if you're aiming to get Shark builds updating this quarter, leave it in. Thanks for the help in figuring it out. :)
You need to log in before you can comment on or make changes to this bug.