1. Join #archlinux-reproducible on <em>irc.libera.chat</em>.
1. Join [#archlinux-reproducible on <em>irc.libera.chat</em>](https://web.libera.chat/?channels=#archlinux-reproducible).
1. Check the unreproducible packages on your system with `arch-repro-status -f BAD`.
Additionally adding `-i` to that command allows you to interactively browse the build
logs and diffoscope output per package.
logs and diffoscope output per package. You can find additional options in [the repository](https://gitlab.archlinux.org/archlinux/arch-repro-status).
1. If you maintain packages in Arch Linux the [Developer Dashboard](https://archlinux.org/devel/)
has a report with your unreproducible packages.
1. Report packaging issues which cause unreproducible packages on the
[bugtracker](https://bugs.archlinux.org).
1. Report packaging issues which cause unreproducible packages on the [Arch Linux Gitlab's issues](https://gitlab.archlinux.org/groups/archlinux/packaging/packages/-/issues).
1. Redesign [reproducible.debian.net](https://reproducible.debian.net/) status
pages using a CSS toolkit like Bootstrap.
1. Redesign [Debian's reproducible builds](https://tests.reproducible-builds.org/debian/reproducible.html) status pages using a CSS toolkit like Bootstrap.
To get help, feel free to ask on the IRC channel or the mailing list. We want
To get help, feel free to ask on the [IRC channel](https://webchat.oftc.net/?channels=#debian-reproducible) or the [mailing list](https://lists.debian.org/). We want
to be friendly, supportive, and have fun experimenting together.
## How to report bugs in Debian
@@ -128,14 +127,14 @@ known issues to get an idea of what you may found. Here is some more advice:
* When a binary has mismatching mtimes for files in `control.tar.gz`, it means
that they are [not adjusted before creating the binary package](https://reproducible.debian.net/issues/not_using_dh_builddeb_issue.html).
*[Timestamps in gzip headers](https://reproducible.debian.net/issues/timestamps_in_gzip_headers_issue.html)
*[Timestamps in gzip headers](https://tests.reproducible-builds.org/debian/issues/unstable/timestamps_in_gzip_headers_issue.html)
are a no-brainer.
* When there's a mismatching `Build ID` in an executable, it means a variation
happens during the compilation. Investigation can be done using
[sources.debian.org](https://sources.debian.org/)(see link at the top).
* First step should be a search for the [`__DATE__`, `__TIME__` or `__TIMESTAMP__`](https://reproducible.debian.net/issues/timestamps_from_cpp_macros_issue.html)
* First step should be a search for the [`__DATE__`, `__TIME__` or `__TIMESTAMP__`](https://tests.reproducible-builds.org/debian/issues/unstable/timestamps_from_cpp_macros_issue.html)
using [codesearch](https://codesearch.debian.net/). Otherwise, try to locate
calls to `date` in `configure.ac`, `Makefile.am`, etc.
@@ -173,8 +172,7 @@ The usual steps are:
1. Use `debdiff` or `git format-patch` to create patches.
1.[Create a new bug report](https://wiki.debian.org/ReproducibleBuilds/Contribute#How_to_report_bugs),
and don't forget to attach the patch!
1. Create a new bug report, and don't forget to attach the patch!
1. Add an entry or reference the bug in `packages.yml` in
@@ -233,17 +231,16 @@ requires some more steps, but the general process is the same:
here), you can find the jenkins administrators in that channel that can do
mass scheduling for you.
1. If the changes don't break anything,
[create a new bug report](https://wiki.debian.org/ReproducibleBuilds/Contribute#How_to_report_bugs).
1. If the changes don't break anything, create a new bug report.
Don't forget to attach patches and to use the `toolchain` usertag.
## Continuous integration platform
Several jobs have been created to regularly test packages (from `main/sid`) on
[jenkins.debian.net](https://jenkins.debian.net). As a result there is the
[reproducible build overview of packages](https://reproducible.debian.net).
[reproducible build overview of packages](https://tests.reproducible-builds.org/debian/reproducible.html).
The setup is explained [in this blog post](http://layer-acht.org/thinking/blog/20140925-reproducible-builds/)
The setup is explained [in this blog post](http://web.archive.org/web/20170810053015/http://layer-acht.org/thinking/blog/20140925-reproducible-builds/)
only, but this post is somewhat outdated by now and needs to be amended.
See the various `reproducible_*` scripts in the
@@ -266,7 +263,6 @@ script for more generic, Debian use cases
*[Announcing Whonix's First Implementation of Verifiable Builds](https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20131209/000009.html)
