Bug 607895 - firefox.i686 should be in x86_64 repositories
Summary: firefox.i686 should be in x86_64 repositories
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: distribution
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Bill Nottingham
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-25 06:32 UTC by Maciej Żenczykowski
Modified: 2014-03-17 03:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-26 18:36:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Maciej Żenczykowski 2010-06-25 06:32:57 UTC
Please provide i686 version of Firefox in x86_64 repositories.
(even if it is not on the install CDs/DVD)

Reasoning: flash still works best with a 32-bit browser.  Once you download and install the i686 firefox rpm (all the dependencies of which are already in the x86_64 repos) you can get a very stable browser (run via setarch i386 firefox).

[If you want to be real clean about it, the firefox spec should probably be fixed so it pulls in pkg.${ARCH} instead of pkg for a couple of its requirements]

Comment 1 Maciej Żenczykowski 2010-11-08 05:27:51 UTC
This is really annoying and should be trivial to fix.

Please?

Comment 2 Elad Alfassa 2011-04-26 15:39:35 UTC
IMO This bug should be closed as WONTFIX. Flash is non-free software, which fedora does not support. We don't do any special things to support non-free software in such way.
Unless you can find another reason to ship i686 build on firefox in x86_64 fedora, we shouldn't do it.

I'm not closing the bug though because I am not part of FESCO, FPC, QA Team or a firefox packager, and it's not up to me to decide.

Comment 3 Bill Nottingham 2011-04-26 18:36:28 UTC
That reasoning is correct. Note that nspluginwrapper.i686 does exist in the x86_64 repository for those that need this case. (And theoretically, Adobe will upgrade the 64-bit version at some point.)


Note You need to log in before you can comment on or make changes to this bug.