QUnit proudly joins ♻️ Reproducible Builds.
Today, the first release minted from our deterministic build process – QUnit 2.14. It was largely made possible by Rollup, with a couple of tweaks to ensure dist files use a date based only on information in the Git repository.
https://github.com/qunitjs/qunit/pull/1542
The SOURCE_DATE_EPOCH standard by @reproducible_builds made things easy to explain and document. No need to come up with our novel way! #standards #qunit #rollup #reproduciblebuilds
https://reproducible-builds.org/docs/source-date-epoch/
December's @reproducible_builds monthly report mentions @CCTG and @microg :).
Check out what's been happening during the last month in the world of @reproducible_builds https://reproducible-builds.org/reports/2020-12/ @conservancy #nixos @debian @CCTG @microg
Our next "office hours" meeting for asking any questions about Reproducible Builds will be held on January 7th at 6pm UTC - see https://lists.reproducible-builds.org/pipermail/rb-general/2020-December/002100.html for more info. 👍
diffoscope 163 released by 💠 https://diffoscope.org/news/diffoscope-163-released/
💠Check out what has been going in the world of
@reproducible_builds recently in our latest monthly report https://reproducible-builds.org/reports/2020-11/ @opensuse #archlinux @debian @conservancy @yoctoproject
Missing an email address results in an unreproducible package. 🤷 (found by ) https://bugs.debian.org/972147
Check out what happened in August in the world of @reproducible_builds 💠💠 https://reproducible-builds.org/reports/2020-08/ feat. @opensuse #archlinux @debian @conservancy @debconf @debian @LeoWandersleb
💠Check out what has been going on during September 2020 in the world of @reproducible_builds 💠 https://reproducible-builds.org/reports/2020-09/ @opensuse #archlinux @debian @conservancy #threema
💠💠💠 Check out what has been going in the world of @reproducible_builds recently 💠💠💠 https://reproducible-builds.org/reports/2020-10/ @opensuse #archlinux @debian @conservancy
This generated config file accidentally includes the process ID of the build process instead of a literal dollar sign (due to '$$' over '\$') https://bugs.debian.org/972336 (found by )
Thank you to ARDC for sponsoring the @reproducible_builds project 💠
https://reproducible-builds.org/news/2020/09/25/ardc-sponsors-the-reproducible-builds-project/ #hamradio #ardc #ampr
An introduction to the @cip_project, one of the @reproducible_builds' supporter projects, as interviewed by 🔷 https://reproducible-builds.org/news/2020/10/21/supporter-spotlight-cip-project/
diffoscope 159 released 💠 https://diffoscope.org/news/diffoscope-159-released/
diffoscope 160 was just released by 💠 https://diffoscope.org/news/diffoscope-160-released/
diffoscope 161 was just released by 💠 https://diffoscope.org/news/diffoscope-161-released/
Join us at 1800 UTC for our second @reproducible_builds IRC meeting https://reproducible-builds.org/news/2020/10/26/reproducible-irc-meeting-2/
Jifeng Xuan will be giving an online talk on the locating the causes of unreproducible builds at 13h00 CET tomorrow (Tuesday 24th) 👍 https://lists.reproducible-builds.org/pipermail/rb-general/2020-November/002077.html
Btw. our corona app builds are @reproducible_builds, at least inside the fdroid defined build env.
This means a few things:
* the build I published earlier will be rebuild by fdroid and published with the same signature if the verification succeeds.
* you can rebuild this yourself and verify the build
I'll probably write some instructions for this in the next few days. It's not as easy as I'd like it yet.
diffoscope 162 released! 💠 https://diffoscope.org/news/diffoscope-162-released/
set of software development practices that create an independently-verifiable path from source code to the binary code used by computers.
Account monitored by @raboof