Closed Bug 1308739 Opened 8 years ago Closed 8 years ago

Firefox downloads get the same filename regardless of locale and 32bit or 64bit

Categories

(Release Engineering :: Release Automation, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: dv5678, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 Build ID: 20161007004004 Steps to reproduce: Visit https://www.mozilla.org/en-US/firefox/all/ Click any download. Actual results: 1a) Every download link under "Windows" or "Windows 64-bit" downloads a file named "Firefox Setup 49.0.1.exe", REGARDLESS of language or 32-or-64. 1b) Every download link under "Linux" or "Linux 64-bit" downloads a file named "Firefox Setup 49.0.1.tar.bz2", regardless of language or 32-or-64. 1c) Every download link under "OS X" downloads a file named "Firefox Setup 49.0.1.tar.bz2", regardless of language. 2) Anyone who downloads a 32 and a 64 (for use on several owned computers) is forced to track the files by renaming or placing them in separate folders. When downloading two files quickly, the result is (for example) "Firefox Setup 49.0.1.exe" and "Firefox Setup 49.0.1(1).exe". It's easy to lose track of which file is which version. 3) As soon as the download starts, there is no record which version was downloaded. (Which language, and 32-or-64.) If you lose track, or think you accidentally downloaded the wrong language, there is no way to find out FROM THE FILE because the file names are all the same, and other ways to find out are also lacking (metadata shamefully fails to disclose language or 32-or-64, ANOTHER issue). [Sorry if this delivery and packaging and issue might not belong HERE. (This report belongs somewhere, even if no place has been provided.)] Expected results: 32bit and 64bit Windows downloads must have different file names. 32bit and 64bit Linux downloads must have different file names. Each language must download a different named file. (Why would anyone depart from such an obvious scheme?) Also, metadata (Windows: Properties:Details) must contain the name of the software, the language or locality, and 32-or-64 bit, instead of being completely EMPTY. Also, the 64-bit installer, when run in 32-bit Windows, should either not start (use a 64bit executable) or stop itself before extracting the 64bit installer, not after.
Component: Untriaged → Releases
Product: Firefox → Release Engineering
QA Contact: rail
Version: 49 Branch → unspecified
File naming schema is a convention that may break many many systems, internal and external. I'm not convinced it's worth changing it. > Also, metadata (Windows: Properties:Details) must contain the name of the software, the language or locality, and 32-or-64 bit, instead of being completely EMPTY. Can you file a separate bug under Core::Build Config. > Also, the 64-bit installer, when run in 32-bit Windows, should either not start (use a 64bit executable) or stop itself before extracting the 64bit installer, not after. Can you file a separate bug under Firefox :: Installer?
Component: Releases → Release Automation
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.