Advertisement
Guest User

Untitled

a guest
Oct 22nd, 2018
67
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.73 KB | None | 0 0
  1. root@2b026bb03a84:~/radon/radon-2.3.1+dfsg# reprotest --help
  2. usage: reprotest --help [<virtual_server_name>]
  3. reprotest [options] [-c <build-command>] <source_root> [<artifact_pattern>]
  4. [-- <virtual_server_args> [<virtual_server_args> ...]]
  5. reprotest [options] [-s <source_root>] <build_command> [<artifact_pattern>]
  6. [-- <virtual_server_args> [<virtual_server_args> ...]]
  7.  
  8. Build packages and check them for reproducibility.
  9.  
  10. positional arguments:
  11. source_root|build_command
  12. The first argument is treated either as a source_root
  13. (see the -s option) or as a build-command (see the -c
  14. option) depending on what it looks like. Most of the
  15. time, this should "just work"; but specifically: if
  16. neither -c nor -s are given, then: if this exists as a
  17. file or directory and is not "auto", then this is
  18. treated as a source_root, else as a build_command.
  19. Otherwise, if one of -c or -s is given, then this is
  20. treated as the other one. If both are given, then this
  21. is a syntax error and we exit code 2.
  22. artifact_pattern Build artifact to test for reproducibility. May be a
  23. shell pattern such as "*.deb *.changes".
  24. virtual_server_args Arguments to pass to the virtual_server, the first
  25. argument being the name of the server. If this itself
  26. contains options (of the form -xxx or --xxx), or if
  27. any of the previous arguments are omitted, you should
  28. put a "--" between these arguments and reprotest's own
  29. options. Default: "null", to run directly in /tmp.
  30. Choices: chroot, lxc, lxd, null, qemu, schroot, ssh
  31.  
  32. optional arguments:
  33. --help [VIRTUAL_SERVER_NAME]
  34. Show this help message and exit. When given an
  35. argument, show instead the help message for that
  36. virtual server and exit.
  37. -f CONFIG_FILE, --config-file CONFIG_FILE
  38. File to load configuration from. (Default: None)
  39.  
  40. basic options:
  41. --verbosity VERBOSITY
  42. An integer. Control which messages are displayed.
  43. -v, --verbose Like --verbosity, but given multiple times without
  44. arguments.
  45. --host-distro HOST_DISTRO
  46. The distribution that will run the tests (Default:
  47. None)
  48. -s PATH, --source-root PATH
  49. Root of the source tree, that is copied to the virtual
  50. server and made available during the build. If a file
  51. is given here, then its parent directory is used
  52. instead. Default: "." (current working directory).
  53. --source-pattern PATTERNS
  54. Shell glob pattern to restrict the files in
  55. <source_root> that are made available during the
  56. build. Default: empty, i.e. copy the whole
  57. <source_root> directory with no restrictions.
  58. -c COMMANDS, --build-command COMMANDS
  59. Build command to execute. If this is "auto" then
  60. reprotest will guess how to build the given
  61. source_root, in which case various other options may
  62. be automatically set-if-unset. Default: auto
  63. --store-dir DIRECTORY
  64. Save the artifacts in this directory, which must be
  65. empty or non-existent. Otherwise, the artifacts will
  66. be deleted and you only see their hashes (if
  67. reproducible) or the diff output (if not).
  68. --variations VARIATIONS
  69. Build variations to test as a comma-separated list of
  70. variation names. Default is "+all", equivalent to
  71. "+environment, +build_path, +kernel, +aslr, +num_cpus,
  72. +time, +user_group, +fileordering, +domain_host,
  73. +home, +locales, +exec_path, +timezone, +umask",
  74. testing all available variations. See the man page
  75. section on VARIATIONS for more advanced syntax
  76. options, including tweaking how certain variations
  77. work.
  78. --vary VARIATIONS Like --variations, but appends to previous --vary
  79. values instead of overwriting them. The last value set
  80. for --variations is treated implicitly as the zeroth
  81. --vary value.
  82. --extra-build VARIATIONS
  83. Perform another build with the given VARIATIONS (which
  84. may be empty) to be applied on top of what was given
  85. for --variations and --vary. Each occurrence of this
  86. flag specifies another build, so e.g. given twice this
  87. will make reprotest perform 4 builds in total.
  88. --auto-build Automatically perform builds to try to determine which
  89. specific variations cause unreproducibility,
  90. potentially up to and including the ones specified by
  91. --variations and --vary. Conflicts with --extra-build.
  92. --env-build Automatically perform builds to try to determine which
  93. specific environment variables cause
  94. unreproducibility, based on a hard-coded whitelist and
  95. blacklist. You probably want to set --vary=-all as
  96. well when setting this flag; see the man page for
  97. details. Conflicts with --extra-build and --auto-
  98. build.
  99. --min-cpus NUM Minimum CPUs to use when fixing num_cpus. Default: 1.
  100.  
  101. diff options:
  102. --diffoscope-arg ARG Give extra arguments to diffoscope when running it.
  103. Default: ['--exclude-directory-metadata']. Arguments
  104. are {}-formatted with: {0} the name of each experiment
  105. run, and {1} the path of the experiment output.
  106. --diffoscope PATH Path to diffoscope(1). Default: diffoscope
  107. --no-diffoscope Don't run diffoscope; instead run diff(1). Useful if
  108. you don't want to install diffoscope and/or just want
  109. a quick answer on whether the reproduction was
  110. successful or not, without spending time to compute
  111. all the detailed differences.
  112.  
  113. advanced options:
  114. --testbed-pre COMMANDS
  115. Shell commands to run before starting the test bed, in
  116. the context of the current system environment. This
  117. may be used to e.g. compute information needed by the
  118. build, where the computation needs packages you don't
  119. want installed in the testbed itself.
  120. --testbed-init COMMANDS
  121. Shell commands to run after starting the test bed,
  122. before running anything else. Used to e.g. install
  123. disorderfs in a chroot.
  124. --testbed-build-pre COMMANDS
  125. Shell commands to run before each build, even before
  126. applying variations for that build. Used to e.g.
  127. install build-dependencies.
  128. --auto-preset-expr PYTHON_EXPRESSION
  129. This may be used to transform the presets returned by
  130. the auto-detection feature. The value should be a
  131. python expression that transforms the _ variable,
  132. which is of type reprotest.presets.ReprotestPreset.
  133. See that class's documentation for ways you can write
  134. this expression. Default: _
  135. --no-clean-on-error Don't clean the virtual_server if there was an error.
  136. Useful for debugging but will leave cruft on your
  137. system depending on the virtual_server used; we hint
  138. about some but there may be others.
  139. --dry-run Don't run the builds, just print what would happen.
  140. --print-sudoers Print a sudoers file for passwordless operation using
  141. the given --variations, useful for
  142. user_group.available, domain_host.use_sudo.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement