[Git][reproducible-builds/reproducible-website][master] 2 commits: contribute: fix links
Chris Lamb (@lamby)
gitlab at salsa.debian.org
Wed Oct 30 18:11:10 UTC 2024
Chris Lamb pushed to branch master at Reproducible Builds / reproducible-website
Commits:
1274584d by Alba Herrerias at 2024-10-30T18:00:59+00:00
contribute: fix links
- - - - -
12826f09 by Alba Herrerias at 2024-10-30T18:00:59+00:00
contribute: improve consistency across guides
- - - - -
5 changed files:
- contribute/archlinux.md
- contribute/debian.md
- contribute/guix.md
- contribute/nixos.md
- contribute/opensuse.md
Changes:
=====================================
contribute/archlinux.md
=====================================
@@ -6,17 +6,20 @@ permalink: /contribute/archlinux/
## Task suggestions for Arch Linux
-1. Join #archlinux-reproducible on <em>irc.libera.chat</em>.
+### Join the discussion
+ 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`.
+### Check unreproducible packages
+ 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/)
+### For package maintainers
+ 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).
+### Reporting issues
+ Report packaging issues which cause unreproducible packages on the [Arch Linux Gitlab's issues](https://gitlab.archlinux.org/groups/archlinux/packaging/packages/-/issues).
## External links
=====================================
contribute/debian.md
=====================================
@@ -6,32 +6,41 @@ permalink: /contribute/debian/
## Task suggestions for Debian
-1. If you maintain a package for Debian, you can make sure that your package
+### Join the discussion
+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.
+
+### Upgrade to a modern debhelper style
+ If you maintain a package for Debian, you can make sure that your package
uses a [modern debhelper style](https://salsa.debian.org/debian/debhelper/blob/main/dh)
(e.g. one-liner `debian/rules` with overrides as needed). We aim to fix many
causes of non-deterministic builds in the debhelper suite directly, so
packages that use debhelper will be much easier to make reproducible with
just an upgrade of the toolchain.
-1. [Inventory issues](#inventorying-issues) found by the continuous integration
+### Inventory known issues
+ [Inventory issues](#inventorying-issues) found by the continuous integration
platform.
-1. [Fix known reproducibility issues](#fixing-issues). See the
+### Fix reproducibility issues
+ [Fix known reproducibility issues](#fixing-issues). See the
[inventory of identified issues](https://reproducible.debian.net/index_issues.html).
-1. [Do responsible NMUs of packages with existing patches](https://udd.debian.org/dev/bugs.cgi?release=any&patch=only&merged=ign&reproducible=1&sortby=id&sorto=asc&format=html#results)
+### NMUs for packages with existing patches
+[Do responsible NMUs of packages with existing patches](https://udd.debian.org/dev/bugs.cgi?release=any&patch=only&merged=ign&reproducible=1&sortby=id&sorto=asc&format=html#results)
by uploading to DELAYED/15.
-1. Improve our common [tools]({{ "/tools/" | relative_url }}):
- [diffoscope](https://tracker.debian.org/diffoscope),
- [strip-nondeterminism](https://tracker.debian.org/strip-nondeterminism),
- [disorderfs](https://tracker.debian.org/disorderfs).
+### Contribute to common tools
+Improve our common [tools]({{ "/tools/" | relative_url }}):
+ [diffoscope](https://tracker.debian.org/pkg/diffoscope),
+ [strip-nondeterminism](https://tracker.debian.org/pkg/strip-nondeterminism),
+ [disorderfs](https://tracker.debian.org/pkg/disorderfs).
-1. Redesign [reproducible.debian.net](https://reproducible.debian.net/) status
- pages using a CSS toolkit like Bootstrap.
+### Redesign reproducibility status pages
+Help us 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 be friendly, supportive, and have fun experimenting together.
+### Reporting issues
+Reporting issues is a great way to contribute. Please read our guide below on [how to report bugs in Debian](#how-to-report-bugs–in-debian).
## How to report bugs in Debian
@@ -125,17 +134,14 @@ The page for a given package should open on the
[diffoscope](https://tracker.debian.org/diffoscope) output. Read the list of
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 +179,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 (read our guide on [how to report bugs in Debian](#how-to-report-bugs–in-debian)), and don't forget to attach the patch!
1. Add an entry or reference the bug in `packages.yml` in
[reproducible-notes](https://salsa.debian.org/reproducible-builds/reproducible-notes).
@@ -233,17 +238,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 +270,6 @@ script for more generic, Debian use cases
## External links
-* [Reproducible installs](https://wiki.debian.org/ReproducibleBuilds/ReproducibleInstalls)
* [Announcing Whonix's First Implementation of Verifiable Builds](https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20131209/000009.html)
* [Whonix Verifiable Builds](https://www.whonix.org/wiki/Verifiable_Builds)
* [Tails reproducible builds blueprint](https://tails.boum.org/blueprint/reproducible_builds/)
=====================================
contribute/guix.md
=====================================
@@ -4,10 +4,12 @@ title: Contribute to reproducible builds in GNU Guix
permalink: /contribute/guix/
---
+## Task suggestions for GNU Guix
+
This page explains how you can contribute to reproducible builds in
[GNU Guix](https://guix.gnu.org).
-## Finding reproducibility issues
+### Check unreproducible packages
You can monitor reproducibility issues by running [`guix
challenge`](https://guix.gnu.org/manual/en/html_node/Invoking-guix-challenge.html).
@@ -32,7 +34,7 @@ If the new build result differs from the one that was already in store,
the failed build is kept as `/gnu/store/…-git-1.2.3-check`, allowing you
to compare it with the original one (without the `-check` suffix).
-## Reporting issues
+### Reporting issues
Please report issues by sending email to `bug-guix at gnu.org`. Each
message opens a new issues visible in the [bug
@@ -42,6 +44,7 @@ When investigating, be sure to check [Debian’s reproducibility issue
inventory](https://tests.reproducible-builds.org/debian/index_issues.html)
for known problems and solutions.
+### Join the discussion
You can also discuss these issues with other developers on [the Guix
development mailing list and on the IRC
channel](https://guix.gnu.org/en/contact).
=====================================
contribute/nixos.md
=====================================
@@ -4,21 +4,23 @@ title: Contribute to NixOS
permalink: /contribute/nixos/
---
-## Community Discussion
+## Task suggestions for NixOS
+
+### Join the discussion
For real-time conversations, join the [`#reproducible-builds:nixos.org`](https://matrix.to/#/#reproducible-builds:nixos.org) channel on Matrix.
-## Project Status
+### Project Status
- **Project Board**: To keep track of ongoing tasks and open issues concerning
reproducible builds, view our [GitHub Project Board](https://github.com/orgs/NixOS/projects/30).
- **Pull Requests & Issues**: Browse current [pull requests](https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+is%3Apr+label%3A%226.topic%3A+reproducible+builds%22) and [issues](https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aissue+label%3A%226.topic%3A+reproducible+builds%22) labeled with "reproducible builds."
- **Internal Resources**: Our internal website, [reproducible.nixos.org](https://reproducible.nixos.org), provides additional information and status updates. More details on specific problems can be found on [this pad](https://pad.sfconservancy.org/p/nixos-reproducible-builds-progress).
-## Reporting Issues
+### Reporting Issues
Use the [issue template](https://github.com/NixOS/nixpkgs/issues/new?assignees=&labels=0.kind%3A+enhancement%2C6.topic%3A+reproducible+builds&template=unreproducible_package.md&title=) on GitHub to report your issues and hopefully, your solution.
-## Additional Projects
+### Additional Projects
- [trustix](https://github.com/nix-community/trustix)
=====================================
contribute/opensuse.md
=====================================
@@ -4,24 +4,25 @@ title: Contribute to openSUSE
permalink: /contribute/opensuse/
---
-## Community Discussion
+## Task suggestions for openSUSE
+
+### Join the discussion
For real-time conversations, join the
[`#reproducible-builds:opensuse.org`](https://matrix.to/#/#reproducible-builds:opensuse.org)
channel on Matrix.
-## Project Status
+### Project Status
See the tracking bug linked in the next section.
-[The openSUSE r-b CI graph has package
+- [The openSUSE r-b CI graph has package
counts.](http://rb.zq1.de/compare.factory/graph.png)
-
-[Status reports of reproducible builds in openSUSE can be found on the openSUSE
+- [Status reports of reproducible builds in openSUSE can be found on the openSUSE
Factory
mailinglist.](https://lists.opensuse.org/archives/search?q=reproducible-builds&page=1&mlist=factory%40lists.opensuse.org&sort=date-desc)
-## Reporting Issues
+### Reporting issues
Report your issue on [the openSUSE
Bugzilla](https://bugzilla.opensuse.org/enter_bug.cgi?classification=openSUSE)
@@ -29,7 +30,7 @@ and ensure the Blocks field has a bug in the dependency tree of the [openSUSE
reproducible builds tracking
issue](https://bugzilla.opensuse.org/show_bug.cgi?id=1081754).
-## Sending changes
+### Sending changes
The [overview of the openSUSE workflow of submitting changes links to detailed
documentation on how to submit
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/compare/db04180b0c3efb11836c54ba2790927ce21cb29d...12826f098963e1b00cee8a17cc36a884be25d904
--
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/compare/db04180b0c3efb11836c54ba2790927ce21cb29d...12826f098963e1b00cee8a17cc36a884be25d904
You're receiving this email because of your account on salsa.debian.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.reproducible-builds.org/pipermail/rb-commits/attachments/20241030/e5a14209/attachment.htm>
More information about the rb-commits
mailing list