[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: towards a reproducible forky



Hi,

* Paul Gevers <elbrus@debian.org> [2025-09-27 17:48]:
On IRC Sebastian also brought up that we'd need to agree on what we'd expect the environment of r.d.n to look like. Obviously CPU, RAM, hostname and exact build times will be different from the buldds, but most other things we'd expect the same, like umasks, timezones and locale settings. Are those the same across all buildds? A point of attention is the packages installed on the buildds which aren't specified in the build dependencies and thus not logged in the buildinfo files: apt, openssl, ca-certificates and fakeroot (the latter depending on Rules-Requires-Root: binary-targets if I get it right).

We assembled a list of differences during the reproducible builds summit in Vienna. Fell free to adopt it for the release team documentation.

General system properties:

  - system time
  - system uptime
  - CPU model, load, number of cores
  - RAM amount, speed
  - kernel version, process scheduling, various kernel settings
  - disk space, speed
  - file order, mtime, ctime, atime, inodes
  - /sys/* (due to different system)

Specific to debrebuild:

  - apt, openssl, ca-certificates not installed by default (not in buildinfo file)
  - fakeroot not used for Rules-Requires-Root (not in buildinfo file)
  - dpkg install order is not guaranteed - can have effects on maintainer scripts, UIDs added by packages..
  - /etc/apt/sources.list* content
  - /run/* (due to mmdebstrap cleaning it up)
  - /var/log/*
  - LD_LIBRARY_PATH does not contain fakeroot when running with RRR: binary-targets

Specific to reproduce.debian.net:

  - tmpfs vs ext4 (will probably be fixed)
  - nice level

Cheers Jochen

Attachment: signature.asc
Description: PGP signature


Reply to: