Closed Bug 209447 Opened 22 years ago Closed 22 years ago

Release Notes (1.3.1 ~ 1.4) System req.: glibc 2.1 -> 2.2, Debian 2.1 -> Debian 2.2 (or 3.0?)

Categories

(www.mozilla.org :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pp, Assigned: danielwang)

Details

User-Agent: Mozilla/5 (X11) Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.3.1/mozilla-i686-pc-linux-gnu-1.3.1-sea.tar.gz contrary to previous one (1.3), it seems that this build has been compiled against glibc 2.2; 1.3 does run on Debian 2.2 (glibc 2.1) while 1.3.1 won't ("...cannot find GLIBC_2.2...."). Apart from rel.notes mistake, I think 1.3.x binaries should remain glibc 2.1 builds, for consistency with original 1.3, unless there are compelling reasons for using glibc 2.2, that is. Pls also note that Debian 2.1 was a glibc 2.0 system, hence we should read Debian 2.2 for a glibc 2.1 requirement. btw, the same applies to 1.4: wrt Debian distro, it should state 3.0 not 2.2. Reproducible: Always Steps to Reproduce: 1. 2. 3. distro: Debian 2.2r7, glibc 2.1.3-25 note severity: could be minor/trivial, but you download 14MB for nothing, and don't get the upgrade/fixes you were advised to get / looking for.
fixed for 1.3.1 relnotes can anyone verify the minimum Debian version requirements for 1.4 ?
Assignee: mitchell → stolenclover
Component: Miscellaneous → webmaster@mozilla.org
QA Contact: mitchell → malachi
Summary: Rel. notes : System req. : glibc 2.1 (e.g.) Debian 2.1 - but it look for GLIBC_2.2 → Release Notes (1.3.1 ~ 1.4) System req.: glibc 2.1 -> 2.2, Debian 2.1 -> Debian 2.2 (or 3.0?)
Debian 2.2 (Potato) is based on glibc 2.1 Debian 3.0 (Woody) is based on glibc 2.2 hence whatever is compiled against glibc 2.2 requires at least Debian 3.0 (Woody).
thanks. now fixed
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Product: mozilla.org → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.