Closed
Bug 443168
Opened 16 years ago
Closed 16 years ago
uninstallable on Debian Etch
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 440004
People
(Reporter: a_geek, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Due to very aggressive library requirements, FF3 is uninstallable on Debian Etch, which is both the current release, and will probably be around for quite some time.
Reproducible: Always
Steps to Reproduce:
1. unpack FF3 on an Etch system
2. run the FF binary
3. observe the error message dialogue
I consider dropping platform support "in the middle of the game" to be a design/policy/process bug. It will prevent me from upgrading to FF3 for at least half a year, should Lenny arrive quickly enough to make it half a year only.
Comment 1•16 years ago
|
||
always include the error messae in a bug report.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Comment 2•16 years ago
|
||
In the middle of the game? We publicly proposed these requirements more than a year in advance of release. Based on what the distros recommended, no less!
See http://steelgryphon.com/blog/?p=101 for more details...
Status: RESOLVED → VERIFIED
Yes, you "publicly" announced the "requirements" (or rather ideas, at that stage), in a place only an insider to the Mozilla environment would discover, and you don't find it worth a single word to mention how the questions posed there were invalid right from the start (ie, asking only Ubuntu and not Debian).
FWIW, the mentioned article contains not a single bit of explanation about what these "reasons" you considered in your decision, actually were.
But I'm almost used to Mozilla catering for the "main stream only", and am looking forward to the day when it will support Windows, and maybe Mac OS-X, exclusively.
You need to log in
before you can comment on or make changes to this bug.
Description
•