Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 37367 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
As of 26842, when Mono compiles C# code, it uses a zero timestamp, such that multiple repeated builds of the same code always are bit-identical. See https://wiki.debian.org/ReproducibleBuilds/About for background on why this is good.
The same does not apply to mdoc output, which includes "real" timestamps for the files inside the .zip. e.g. https://reproducible.debian.net/dbd/unstable/amd64/mono_220.127.116.11+dfsg2-5.diffoscope.html
So to be clear, you're referring to the output from `mdoc assemble` ?
mdoc uses SharpZipLib to write the zip file ... I can/will do some digging, but are you aware of any best-practices here? Should I set the all of the timestamps on the file to DateTime.MinValue, or something?
(In reply to Joel Martinez from comment #1)
> So to be clear, you're referring to the output from `mdoc assemble` ?
> mdoc uses SharpZipLib to write the zip file ... I can/will do some digging,
> but are you aware of any best-practices here? Should I set the all of the
> timestamps on the file to DateTime.MinValue, or something?
MinValue, or pick a static date, or use another static date from somewhere (e.g. ship a release date with releases, and use that). As long as the date isn't DateTime.Now, it's fine
Thanks ... I've created a GH issue to track this feature.