Closed Bug 1022082 Opened 11 years ago Closed 2 years ago

jsshell packages are being compressed with wrong file modification dates

Categories

(Core :: JavaScript Engine, defect, P5)

Desktop
All
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox97 --- affected

People

(Reporter: ric.valechat, Unassigned)

References

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release) Build ID: 20140605174243 Steps to reproduce: Compare jsshell-*.zip from FTP: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/29.0.1-candidates/build2/ with ftp://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/30.0-candidates/build2/ or ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/ Actual results: Files inside the jsshell packages are being compressed with wrong file modification dates. It happens at least on nightly and beta packages starting with 30b branch. Last good packages I'm aware are the ones for 29.0.1. Expected results: Correct should be what you see in screenshot for 29.0.1.
Severity: normal → major
Version: 30 Branch → 31 Branch

This issue appears to still occur on the current ftp as well (http://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/)
When downloading any jsshell zipped folder and looking into it, it can be noticed that the modification dates of the files are always reset to 1st of Jan 2010.

I don't know if this is caused by zipping them or setting them up in the ftp, but the correct date isn't showing up.
The same issue can be observed for all builds.

While this does not seem to be a serious issue, I will set S3 severity.

Severity: major → S3
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → All
Hardware: x86_64 → Desktop
Version: 31 Branch → Trunk

Julien, could this be a feature of our building machine to make reproducible archive, or is this a very old bug that needs to be solved one day?

Blocks: sm-meta
Severity: S3 → S4
Flags: needinfo?(jcristau)
Priority: -- → P5

Thanks.
I guess this means this was a deliberate choice from Bug 592369.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: