Porters, please read re GitHub auto-generated tarballs vs releases reddit / BSD ---------------------------------------------------------------------- LukeShu · 2018-03-02 21:05 That's a bummer. Around 2011, the auto-generated tarballs were *really* not stable; it would just about never give you the same file twice. Since then (2014-ish, maybe?), they had changed their implementation, and it it started consistently giving the same file, to different parts of the world (ie, probably hitting different clusters), for years. I had assumed that meant GitHub had committed to keeping them stable. It's a bummer that in the last few months they've apparently started breaking that. Though I wonder if that's intentional/allowed, or if it's really just a bug in GitHub. The email quoted > "It is not meant to be reliable or a way to distribute software > releases and nothing in the software stack is made to try to > produce consistent archives." But I can't seem to find a source for that quote. ---------------------------------------------------------------------- liveoneggs · 2018-03-03 01:23 it's because of the caching on fastly, most likely ---------------------------------------------------------------------- BumpitySnook · 2018-03-03 06:21 You'd think the generated cache result could be the same if the backing data didn't change (same git SHA). But it seems like environmental state at the time of packing is leaking into their tarballs. ---------------------------------------------------------------------- kageurufu · 2018-03-03 14:43 Nah, just the order of files in the archive I'd probably not reserved ---------------------------------------------------------------------- BumpitySnook · 2018-03-03 23:31 The files are ordered deterministically in the git directory objects. Using either that order, or sorting, should yield a reproducible tarball output. ---------------------------------------------------------------------- liveoneggs · 2018-03-04 00:09 it's worth researching what actually changes because they don't produce reproducible anything. It's probably timestamps? Anyway it's worthy of being a git bug. Reproducible builds are obvious to security.