Dear Maintainer,

while running
$ reprotest .

I've run into the following type of failure independent of the package
I'm trying to test:


dpkg-source: info: utilisation de la liste de patchs de
debian/patches/series
dpkg-source: erreur: impossible de modifier la date de build-
experiment-1/.pc/applied-patches: Invalid argument
dpkg-buildpackage: erreur: le sous-processus dpkg-source --before-build
. a retourné l’état de sortie 22
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line
862, in run
    return 0 if check_func(*check_args) else 1
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line
379, in check
    local_dists += [proc.send(nv) for nv in zip(bnames[1:],
build_variations[1:])]
                    ^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line
339, in corun_builds
    bctx.run_build(testbed, build, os.environ, artifact_pattern,
testbed_build_pre, no_clean_on_error)
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line
218, in run_build
    testbed.check_exec2(build_argv,
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 63,
in check_exec2
    self.bomb('"%s" failed with status %i' % (' '.join(argv), code),
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 70,
in bomb
    raise _type(m)


However, running against .dsc for the same package
$ reprotest ../${SOURCE_PKG}_${DEB_VERSION}.dsc
runs just fine.


I've attached logs for the {,un}happy cases with --verbosity=2.

To my untrained eye,
the main differences in the logs apart from different paths is:

<     sh -ec 'cd "$REPROTEST_BUILD_PATH"; unset REPROTEST_BUILD_PATH;
umask "$REPROTEST_UMASK"; unset REPROTEST_UMASK; dpkg-buildpackage --
no-sign -b'
---
umask "$REPROTEST_UMASK"; unset REPROTEST_UMASK; dpkg-source -x
"unl0kr_2.0.3+dfsg-1.dsc" "$(basename "$PWD")" && cd "$(basename
"$PWD")" && dpkg-buildpackage --no-sign -b'

and

< INFO:reprotest.build:KERNEL variation: SETARCH_ARCH = 'linux64'
SETARCH_OPTS = '--uname-2.6'
< INFO:reprotest.build:NUM_CPUS variation: cpu_list =
2,22,16,11,6,3,19,31,7,24,26,30,12,20,25,13,29
---
SETARCH_OPTS = '--uname-2.6'



Thanks for maintaining reprotest!

Wild guess ... can you try with --vary=-time ?

And maybe with LC_ALL=C.UTF-8 locale if it still spits out errors? :)

reprotest's use of faketime tends to trigger issues with patch
systems...


live well,
  vagrant