Closed Bug 268816 Opened 20 years ago Closed 19 years ago

automatic update updates sparc version to i386

Categories

(Toolkit :: Application Update, defect)

Sun
Solaris
defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: mozilla-bugs, Assigned: bugs)

Details

(Whiteboard: [asaP1])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041105 Firefox/1.0RC1 (Debian package 0.99+1.0RC1-4)
Build Identifier: Unknown. (some 1.0 build, not final, no nightly, origin mozilla.org)

Install firefox on solaris sparc, use the buildin upgrade function and the
result is an i386 version.

Reproducible: Always
Steps to Reproduce:
1.install firefox for solaris sparc
2. auto-update
3. restart (won't work)
4. have a look at the binary and you'll see it's an i386 binary

Actual Results:  
firefox stopped working

Expected Results:  
update to the latest sparc build

Solaris version: Solaris 9 (Generic_112233-10)
OS: other → Solaris
Hardware: Other → Sun
We should probably disable auto-update for platforms we don't support it on or
something....  Completely destroying the installation like this is sorta bad.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Oof. Server-side or client-side?
Severity: normal → critical
Probably client. Ben would know for sure.
If we're planning to push out 1.0.1 via UMO, we need to resolve this one way or
another (disable UMO for non-linux/windows/mac builds, or fix UMO).
Flags: blocking-aviary1.1?
Flags: blocking-aviary1.0.1?
OK, I'll bite. blocking 1.0.1 UMO roll-out. Ben's probably not the right assignee
Flags: blocking-aviary1.0.1? → blocking-aviary1.0.1+
As far as I know, we're not updating anything but Windows from umo's app update
service this first round (scheduled for next week.)
Flags: blocking-aviary1.0.1+
Flags: blocking-aviary1.1? → blocking-aviary1.1+
Whiteboard: [asaP1]
Is this how we work in the new world? Sounds like this shouldn't be a problem.
This bug is fixed by the new software update system.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.