Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- root@2b026bb03a84:~/radon/radon-2.3.1+dfsg# reprotest --help
- usage: reprotest --help [<virtual_server_name>]
- reprotest [options] [-c <build-command>] <source_root> [<artifact_pattern>]
- [-- <virtual_server_args> [<virtual_server_args> ...]]
- reprotest [options] [-s <source_root>] <build_command> [<artifact_pattern>]
- [-- <virtual_server_args> [<virtual_server_args> ...]]
- Build packages and check them for reproducibility.
- positional arguments:
- source_root|build_command
- The first argument is treated either as a source_root
- (see the -s option) or as a build-command (see the -c
- option) depending on what it looks like. Most of the
- time, this should "just work"; but specifically: if
- neither -c nor -s are given, then: if this exists as a
- file or directory and is not "auto", then this is
- treated as a source_root, else as a build_command.
- Otherwise, if one of -c or -s is given, then this is
- treated as the other one. If both are given, then this
- is a syntax error and we exit code 2.
- artifact_pattern Build artifact to test for reproducibility. May be a
- shell pattern such as "*.deb *.changes".
- virtual_server_args Arguments to pass to the virtual_server, the first
- argument being the name of the server. If this itself
- contains options (of the form -xxx or --xxx), or if
- any of the previous arguments are omitted, you should
- put a "--" between these arguments and reprotest's own
- options. Default: "null", to run directly in /tmp.
- Choices: chroot, lxc, lxd, null, qemu, schroot, ssh
- optional arguments:
- --help [VIRTUAL_SERVER_NAME]
- Show this help message and exit. When given an
- argument, show instead the help message for that
- virtual server and exit.
- -f CONFIG_FILE, --config-file CONFIG_FILE
- File to load configuration from. (Default: None)
- basic options:
- --verbosity VERBOSITY
- An integer. Control which messages are displayed.
- -v, --verbose Like --verbosity, but given multiple times without
- arguments.
- --host-distro HOST_DISTRO
- The distribution that will run the tests (Default:
- None)
- -s PATH, --source-root PATH
- Root of the source tree, that is copied to the virtual
- server and made available during the build. If a file
- is given here, then its parent directory is used
- instead. Default: "." (current working directory).
- --source-pattern PATTERNS
- Shell glob pattern to restrict the files in
- <source_root> that are made available during the
- build. Default: empty, i.e. copy the whole
- <source_root> directory with no restrictions.
- -c COMMANDS, --build-command COMMANDS
- Build command to execute. If this is "auto" then
- reprotest will guess how to build the given
- source_root, in which case various other options may
- be automatically set-if-unset. Default: auto
- --store-dir DIRECTORY
- Save the artifacts in this directory, which must be
- empty or non-existent. Otherwise, the artifacts will
- be deleted and you only see their hashes (if
- reproducible) or the diff output (if not).
- --variations VARIATIONS
- Build variations to test as a comma-separated list of
- variation names. Default is "+all", equivalent to
- "+environment, +build_path, +kernel, +aslr, +num_cpus,
- +time, +user_group, +fileordering, +domain_host,
- +home, +locales, +exec_path, +timezone, +umask",
- testing all available variations. See the man page
- section on VARIATIONS for more advanced syntax
- options, including tweaking how certain variations
- work.
- --vary VARIATIONS Like --variations, but appends to previous --vary
- values instead of overwriting them. The last value set
- for --variations is treated implicitly as the zeroth
- --vary value.
- --extra-build VARIATIONS
- Perform another build with the given VARIATIONS (which
- may be empty) to be applied on top of what was given
- for --variations and --vary. Each occurrence of this
- flag specifies another build, so e.g. given twice this
- will make reprotest perform 4 builds in total.
- --auto-build Automatically perform builds to try to determine which
- specific variations cause unreproducibility,
- potentially up to and including the ones specified by
- --variations and --vary. Conflicts with --extra-build.
- --env-build Automatically perform builds to try to determine which
- specific environment variables cause
- unreproducibility, based on a hard-coded whitelist and
- blacklist. You probably want to set --vary=-all as
- well when setting this flag; see the man page for
- details. Conflicts with --extra-build and --auto-
- build.
- --min-cpus NUM Minimum CPUs to use when fixing num_cpus. Default: 1.
- diff options:
- --diffoscope-arg ARG Give extra arguments to diffoscope when running it.
- Default: ['--exclude-directory-metadata']. Arguments
- are {}-formatted with: {0} the name of each experiment
- run, and {1} the path of the experiment output.
- --diffoscope PATH Path to diffoscope(1). Default: diffoscope
- --no-diffoscope Don't run diffoscope; instead run diff(1). Useful if
- you don't want to install diffoscope and/or just want
- a quick answer on whether the reproduction was
- successful or not, without spending time to compute
- all the detailed differences.
- advanced options:
- --testbed-pre COMMANDS
- Shell commands to run before starting the test bed, in
- the context of the current system environment. This
- may be used to e.g. compute information needed by the
- build, where the computation needs packages you don't
- want installed in the testbed itself.
- --testbed-init COMMANDS
- Shell commands to run after starting the test bed,
- before running anything else. Used to e.g. install
- disorderfs in a chroot.
- --testbed-build-pre COMMANDS
- Shell commands to run before each build, even before
- applying variations for that build. Used to e.g.
- install build-dependencies.
- --auto-preset-expr PYTHON_EXPRESSION
- This may be used to transform the presets returned by
- the auto-detection feature. The value should be a
- python expression that transforms the _ variable,
- which is of type reprotest.presets.ReprotestPreset.
- See that class's documentation for ways you can write
- this expression. Default: _
- --no-clean-on-error Don't clean the virtual_server if there was an error.
- Useful for debugging but will leave cruft on your
- system depending on the virtual_server used; we hint
- about some but there may be others.
- --dry-run Don't run the builds, just print what would happen.
- --print-sudoers Print a sudoers file for passwordless operation using
- the given --variations, useful for
- user_group.available, domain_host.use_sudo.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement