history: fix typos

accurately.

Second attempt used `debugedit` which is used by Fedora and

other to change the source paths to a canonical location after the

others to change the source paths to a canonical location after the

build. Unfortunately, `gcc` write debug strings in a *hashtable*.

`debugedit` will not reorder the table after patching the strings, so

the result is still unreproducible. Adding this feature to `debugedit`

`-fno-merge-debug-strings` but this is space expensive. The [second

large scale rebuild](https://wiki.debian.org/ReproducibleBuilds/Rebuild20140126) used

the latter approach. It was still difficult to guess the initial build

path properly. Stéphane Glondu was the first to [suggest to using a

path properly. Stéphane Glondu was the first to [suggest using a

canonical build

path](http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20140217/000065.html)

to solve the issue.

At the end of September 2014, Holger Levsen started to work on

[jenkins.debian.net](https://jenkins.debian.net/) to perform

continuous integration for build reproducibility. Packages from *sid*

started to be built and rebuild. This initially introduced variations

started to be built and rebuilt. This initially introduced variations

for time and file ordering, and was extended later on to also use

different users, groups, hostnames, and locales.

[reproducible.debian.net](https://reproducible.debian.net/)

website. The process of analyzing reproducibility failures could now be

more easily shared. New contributors indeed showed up and started

submitting sorting out common issues and providing patches.

submitting fixes, sorting out common issues and providing patches.

In July of 2015, [Vagrant begins hosting ARM

boards](https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20150727/002492.html)

*  [tracker.debian.org](https://tracker.debian.org) inclusion, see [739497](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739497)

*  [Debian Developer's Packages Overview](https://qa.debian.org/developer.php) (DDPO) inclusion

*  debbindiff gained .rpm support

*  [Debian Maintainer Dashbord](https://udd.debian.org/dmd/) inclusion

*  [Debian Maintainer Dashboard](https://udd.debian.org/dmd/) inclusion

Finally, for now, not even two weeks after FOSDEM 2015 a mail with the

subject "[Reproducible Builds --- proof of concept successful for 83%

of all sources in

main](https://lists.debian.org/debian-devel-announce/2015/02/msg00007.html)"

was send to

[debian-devel-announce@lists.ddebian.org](https://lists.debian.org/debian-devel-announce/)

[debian-devel-announce@lists.debian.org](https://lists.debian.org/debian-devel-announce/)

officially anouncing the project to the Debian developer community at

large.

## Google Summer of Code 2015

During the summer of 2015 akira and Dhole will be working on moving

During the summer of 2015 akira and Dhole worked on moving

forward reproducible builds as a Google Summer of Code project. Follow

the links to check the accepted [akira's

application](https://wiki.debian.org/SummerOfCode2015/StudentApplications/MariaValentinaMarinRodrigues)

## DebConf15

To be written: the first real life meeting of the Debian team. Talk

given, roundstable discussion, hacking session. Mentioned in several

given, roundtable discussion, hacking session. Mentioned in several

talks, incl DPL key note.

[SOURCE_DATE_EPOCH]({{ "/docs/source-date-epoch" | relative_url }})

was invented around this time too.

## Continous tests for Coreboot, OpenWrt, NetBSD, FreeBSD, Arch Linux and Fedora

## Continuous tests for Coreboot, OpenWrt, NetBSD, FreeBSD, Arch Linux and Fedora

to be written: tests for these six projects have been added between June

and December 2015...

In January 2017 we learned, that John Gilmore [wrote an interesting

mail about how Cygnus.com worked on reproducible builds in the early

1990s](https://lists.reproducible-builds.org/pipermail/rb-general/2017-January/000309.html).

It's eye opening to see how the dealt with basically the very same

It's eye opening to see how they dealt with basically the very same

problems we're dealing with today, how they solved them and then to

realize that most of this has been forgotten and bit-rotted in the last

20 years. How will we prevent history repeating itself here?

On August 21st 2017 reproducible-builds where first mentioned in Debian

On August 21st 2017 reproducible-builds were first mentioned in Debian

Policy, 4.1.0.

On October 16th 2017 intrigeri reported successes in reproducing [Tails](https://tails.boum.org) ISO images

In April 2020, Arch Linux announced their official [reproducible.archlinux.org rebuilderd

instance](https://reproducible-builds.org/reports/2020-04/) and [reached

out](https://lists.reproducible-builds.org/pipermail/rb-general/2020-April/001905.html)

for community-ran instances to double-check their reported results.

for community-run instances to double-check their reported results.

A workshop about [reproducing official Arch Linux packages from source

code](https://lists.reproducible-builds.org/pipermail/rb-general/2020-April/001892.html)

## 2023

In May 2023, problems with Linux' build-time generated module signing keys were

In May 2023, problems with Linux's build-time generated module signing keys were

[raised on the reproducible-builds mailing

list](https://lists.reproducible-builds.org/pipermail/rb-general/2023-May/002991.html).

## ToDo

please see the old [Reproducibile Builds Publicity](https://wiki.debian.org/ReproducibleBuilds/About#Publicity) page in the Debian wiki

please see the old [Reproducible Builds Publicity](https://wiki.debian.org/ReproducibleBuilds/About#Publicity) page in the Debian wiki

which we still need to migrate to reproducible-builds.org.

## Contributors