Bug#877813: reprotest: regression between 0.7.1 and 0.7.2

2017-10-27 Thread gregor herrmann 
On Fri, 27 Oct 2017 17:26:00 +, Ximin Luo wrote:

> > So I guess I'll stay with excluding domain_host for now.
> > [..]
> > It looks like currently both 0 and 1 cause problems :)
> Yes, I've experienced this too. :( I'm hitting what I think might
> be a bug with nsenter(1), but I have a potential workaround. It'll
> take a while to code up though.

Ok, thanks.
 
> Unfortunately the code from current git, causes some leftover bits
> on your system. You probably want to, in this order:

Thanks for the heads-up.
(I checked everything and found no leftovers luckily.)
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Dido: My Life


signature.asc
Description: Digital Signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#877813: reprotest: regression between 0.7.1 and 0.7.2

2017-10-27 Thread gregor herrmann 
On Fri, 27 Oct 2017 12:06:00 +, Ximin Luo wrote:

> > I've now built a package from git HEAD (3efb86f), and .. hm .. I guess
> > this bug is fixed, it's just that I'm running into another issue
> > which seems related to another recent commit (the domain_host
> > feature):
> I understand it's not nice to keep having to add -disable flags on
> every new reprotest release, sorry about that.

:)
 
> Does it work if you give --vary=domain_host.use_sudo=1? (I think it
> should, if you have root inside the chroot.)

Doesn't work out of the box, I guess this needs some sudo setup
within the chroot:

#v+
INFO:root:build successful, copying artifacts
INFO:root:copying /tmp/reprotest.RUYyhx/artifacts-control/ back from virtual 
server's /tmp/tmphv2wjego/control
INFO:root:build "experiment-1": vary environment, FIX build_path, FIX 
user_group, vary fileordering, vary domain_host, vary home, vary kernel, vary 
locales, vary exec_path, vary time, vary timezone, vary umask
INFO:root:copying . over to virtual server's 
/tmp/reprotest.RUYyhx/build-experiment-1/
INFO:root:starting build with source directory: 
/tmp/reprotest.RUYyhx/build-experiment-1/, artifact pattern: ./../*.deb
Note, using directory './.' to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
INFO:root:executing build in /tmp/reprotest.RUYyhx/const_build_path/

Nous espérons que vous avez reçu de votre administrateur système local les 
consignes traditionnelles. Généralement, elles se concentrent sur ces trois 
éléments :

#1) Respectez la vie privée des autres.
#2) Réfléchissez avant d'utiliser le clavier.
#3) De grands pouvoirs confèrent de grandes responsabilités.

sudo: pas de tty présent et pas de programme askpass spécifié

Nous espérons que vous avez reçu de votre administrateur système local les 
consignes traditionnelles. Généralement, elles se concentrent sur ces trois 
éléments :

#1) Respectez la vie privée des autres.
#2) Réfléchissez avant d'utiliser le clavier.
#3) De grands pouvoirs confèrent de grandes responsabilités.

sudo: pas de tty présent et pas de programme askpass spécifié

Nous espérons que vous avez reçu de votre administrateur système local les 
consignes traditionnelles. Généralement, elles se concentrent sur ces trois 
éléments :

#1) Respectez la vie privée des autres.
#2) Réfléchissez avant d'utiliser le clavier.
#3) De grands pouvoirs confèrent de grandes responsabilités.

sudo: pas de tty présent et pas de programme askpass spécifié

Nous espérons que vous avez reçu de votre administrateur système local les 
consignes traditionnelles. Généralement, elles se concentrent sur ces trois 
éléments :

#1) Respectez la vie privée des autres.
#2) Réfléchissez avant d'utiliser le clavier.
#3) De grands pouvoirs confèrent de grandes responsabilités.

sudo: pas de tty présent et pas de programme askpass spécifié
cleanup failed with exit code 1
#v-

If I add the output of `reprotest --print-sudoers ...' to
/etc/sudoers.d/local-reprotest within the chroot, as recommended in
README.rst, and continue with --vary=domain_host.use_sudo=1, I get a
different error:

#v+
INFO:root:build successful, copying artifacts
INFO:root:copying /tmp/reprotest.dHanan/artifacts-control/ back from virtual 
server's /tmp/tmp_9z3obv4/control
INFO:root:build "experiment-1": vary environment, FIX build_path, FIX 
user_group, vary fileordering, vary domain_host, vary home, vary kernel, vary 
locales, vary exec_path, vary time, vary timezone, vary umask
INFO:root:copying . over to virtual server's 
/tmp/reprotest.dHanan/build-experiment-1/
INFO:root:starting build with source directory: 
/tmp/reprotest.dHanan/build-experiment-1/, artifact pattern: ./../*.deb
Note, using directory './.' to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
INFO:root:executing build in /tmp/reprotest.dHanan/const_build_path/
unshare: cannot change root filesystem propagation: Argumento inválido
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 802, in run
return 0 if check_func(*check_args) else 1
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 351, in 
check
local_dists = [proc.send(nv) for nv in zip(bnames, build_variations)]
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 351, in 

local_dists = [proc.send(nv) for nv in zip(bnames, build_variations)]
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 317, 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 211, in 
run_build
kind='build')
  File

Bug#877813: reprotest: regression between 0.7.1 and 0.7.2

2017-10-26 Thread gregor herrmann 
On Thu, 26 Oct 2017 22:40:00 +, Ximin Luo wrote:

> gregor herrmann:
> > - reprotest called as 
> >   env -u TMPDIR -- reprotest --variations=+all,-build_path,-user_group 
> > --verbosity 1 . -- schroot default 2>&1 | [..]
> Thanks, this helped me reproduce the bug locally. I was having
> trouble before, because the bug only occurs when fileordering is
> switched on but user_group is not switched on.

Thanks, that's excellent news.
And sorry for not providing the command I used earlier.
 
> The bug is because disorderfs was being run as root inside the
> schroot, but the build was being run as the normal unprivileged
> user. This was because I was dropping privs in the wrong place,
> I've fixed in commit e367967, see if it works for you:
> https://anonscm.debian.org/git/reproducible/reprotest.git/commit/?id=e367967

I've now built a package from git HEAD (3efb86f), and .. hm .. I guess
this bug is fixed, it's just that I'm running into another issue
which seems related to another recent commit (the domain_host
feature):

#v+
INFO:root:build successful, copying artifacts
INFO:root:copying /tmp/reprotest.5Ab5ie/artifacts-control/ back from virtual 
server's /tmp/tmpo1_ukgqc/control
INFO:root:build "experiment-1": vary environment, FIX build_path, FIX 
user_group, vary fileordering, vary domain_host, vary home, vary kernel, vary 
locales, vary exec_path, vary time, vary timezone, vary umask
WARNING:root:Not using sudo for domain_host; it is recommended. Your build may 
fail.
WARNING:root:Be sure to `echo 1 > /proc/sys/kernel/unprivileged_userns_clone` 
if on a Debian system.
INFO:root:copying . over to virtual server's 
/tmp/reprotest.5Ab5ie/build-experiment-1/
INFO:root:starting build with source directory: 
/tmp/reprotest.5Ab5ie/build-experiment-1/, artifact pattern: ./../*.deb
Note, using directory './.' to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
INFO:root:executing build in /tmp/reprotest.5Ab5ie/const_build_path/
unshare: unshare failed: ²»ÔÊÐíµIJÙ×÷
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 802, in run
return 0 if check_func(*check_args) else 1
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 351, in 
check
local_dists = [proc.send(nv) for nv in zip(bnames, build_variations)]
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 351, in 

local_dists = [proc.send(nv) for nv in zip(bnames, build_variations)]
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 317, 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 211, in 
run_build
kind='build')
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 63, in 
check_exec2
adtlog.AutopkgtestError)
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 69, in bomb
raise _type(m)
reprotest.lib.adtlog.AutopkgtestError: "su -s /bin/sh gregoa -c set -e; 
run_build() {
mkdir -p /tmp/reprotest.5Ab5ie/build-experiment-1-aux && \
mv /tmp/reprotest.5Ab5ie/build-experiment-1/ 
/tmp/reprotest.5Ab5ie/const_build_path && \
mv /tmp/reprotest.5Ab5ie/const_build_path/ 
/tmp/reprotest.5Ab5ie/const_build_path-before-disorderfs/ && \
mkdir -p /tmp/reprotest.5Ab5ie/const_build_path/ && \
disorderfs -q --shuffle-dirents=yes 
/tmp/reprotest.5Ab5ie/const_build_path-before-disorderfs/ 
/tmp/reprotest.5Ab5ie/const_build_path/ && \
umask 0002 && \
export REPROTEST_BUILD_PATH=/tmp/reprotest.5Ab5ie/const_build_path/ && \
export REPROTEST_UMASK=$(umask) && \
faketime +373days+7hours+13minutes \
linux32 \
unshare -r --uts sh -ec '
hostname reprotest-capture-hostname
domainname "reprotest-capture-domainname"
"$@"' - \
sh -ec 'cd "$REPROTEST_BUILD_PATH"; unset REPROTEST_BUILD_PATH; umask 
"$REPROTEST_UMASK"; unset REPROTEST_UMASK; dpkg-buildpackage --no-sign -b'
}

cleanup() {
__c=0; \
export PATH="/tmp/reprotest.5Ab5ie/bin:$PATH" || __c=$?; \
fusermount -u /tmp/reprotest.5Ab5ie/const_build_path/ || __c=$?; \
rmdir /tmp/reprotest.5Ab5ie/const_build_path/ || __c=$?; \
mv /tmp/reprotest.5Ab5ie/const_build_path-before-disorderfs/ 
/tmp/reprotest.5Ab5ie/const_build_path/ || __c=$?; \
mv /tmp/reprotest.5Ab5ie/const_build_path 
/tmp/reprotest.5Ab5ie/build-experiment-1/ || __c=$?; \
rm -rf /tmp/reprotest.5Ab5ie/build-experiment-1-aux || __c=$?; \
exit $__c
}

trap '( cleanup )' HUP INT QUIT ABRT TERM PIPE #

Bug#877813: reprotest: regression between 0.7.1 and 0.7.2

2017-10-05 Thread gregor herrmann 
On Thu, 05 Oct 2017 22:59:00 +, Ximin Luo wrote:

> gregor herrmann:
> > [..]
> > sudo: Î޷¨½âÎöÖ÷»ú£ºjadzia
> > tail: Î޷¨´ò¿ª'debian/changelog' ¶ÁȡÊý¾: ȨÏ޲»¹»
> > dpkg-buildpackage: erreur: fin de debian/changelog a produit une erreur de 
> > sortie de type 1
> > [..]
> > sudo: impossible de déterminer le nom de l'hôte jadzia
> > tail: no se puede abrir 'debian/changelog' para lectura: Permiso denegado
> > dpkg-buildpackage: error: tail of debian/changelog gave error exit status 1

> tail(1) apparently can't read debian/changelog. 

Yes, after manually installing fakeroot, which I didn't need to do
for reprotest <= 0.7.1.

And the error before "tail: can't open ..." (in Spanish) is still
"sudo: can't determine hostname ..." (in French).

I might be wrong, but this still sounds like a problem related to
sudo to me.

Full disclosure: I'm not running systems in the Ubuntu-style of "sudo
all all nopasswd everything ". And so far both autopkgtest
and reprotest (which are both using the same schroot chroot, and are
the only ones, as for building I'm using cowbuilder) just worked.

> I don't know how you set up your schroot, but reprotest is coded
> against the sbuild-createchroot stuff. Have you tried using that?

That's a good question :) And I'm not entirely sure since I did this
years ago and I only use the schroot chroot for autopkgtest and
reprotest; but I think it was sbuild-createchroot as well.
 
> What command line are you running to get these errors?

Another good question; I call reprotest from a wrapper script:

https://anonscm.debian.org/cgit/pkg-perl/packages/pkg-perl-tools.git/tree/examples/check-build#n86

Which, run under 'sh -x' looks like:

#v+
+ read -n 1 -p 'reprotest? y/N ' REPRO
reprotest? y/N y+ '[' y = y ']'
+ REPROTESTLOG=../build-area/openpgp-applet_1.0-2_amd64_reprotest.log
+ '[' -x /usr/bin/schroot ']'
+ schroot -l
+ grep -q default
+ REPROTEST_VIRT_SERVER=schroot
+ REPROTEST_VIRT_SERVER_ARGS=default
+ '[' -n schroot ']'
++ dpkg-query -f '${Version}\n' -W reprotest
+ REPROTESTVERSION=0.7.2
+ dpkg --compare-versions 0.7.2 ge 0.7
+ REPROTESTPARAMS='--variations=+all,-build_path,-user_group --verbosity 1 . '
+ env -u TMPDIR -- reprotest --variations=+all,-build_path,-user_group 
--verbosity 1 . -- schroot default
+ tee ../build-area/openpgp-applet_1.0-2_amd64_reprotest.log
preset auto-selected: ReprotestPreset(build_command='\nif [ "$(id -u)" 
= 0 ]; then\nsudo -E -u "$LOGNAME" sh -ec \'dpkg-buildpackage 
--no-sign -b\';\nelse\nsh -ec \'dpkg-buildpackage --no-sign 
-b\';\nfi\n', artifact_pattern='../*.deb', testbed_pre=None, 
testbed_init='apt-get -y --no-install-recommends install disorderfs faketime 
locales-all sudo util-linux; test -c /dev/fuse || mknod -m 666 
/dev/fuse c 10 229; test -f /etc/mtab || ln -s ../proc/self/mounts 
/etc/mtab', testbed_build_pre='apt-get -y --no-install-recommends build-dep 
./"."', source_pattern=None, diffoscope_args=[])
STARTING VIRTUAL SERVER 
['/usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-virt-schroot', 
'default']
reprotest [01:25:00]: version @version@
reprotest [01:25:00]: host jadzia; command line: /usr/bin/reprotest 
--variations=+all,-build_path,-user_group --verbosity 1 . -- schroot default
reprotest [01:25:00]: testbed package architecture: amd64
reprotest [01:25:01]: testbed running kernel: Linux 4.12.0-2-amd64 #1 SMP 
Debian 4.12.13-1 (2017-09-19)
Reading package lists...
[.. first build ..]
executing: if ( mv /tmp/autopkgtest.eYrFOo/build-control/ 
/tmp/autopkgtest.eYrFOo/const_build_path && umask 0022 && export 
REPROTEST_BUILD_PATH=/tmp/autopkgtest.eYrFOo/const_build_path/ && export 
REPROTEST_UMASK=$(umask) && linux64 --uname-2.6 sh -ec 'cd 
"$REPROTEST_BUILD_PATH"; unset REPROTEST_BUILD_PATH; umask "$REPROTEST_UMASK"; 
unset REPROTEST_UMASK; 
if [ "$(id -u)" = 0 ]; then
sudo -E -u "$LOGNAME" sh -ec '"'"'dpkg-buildpackage --no-sign 
-b'"'"';
else
sh -ec '"'"'dpkg-buildpackage --no-sign -b'"'"';
fi
' ); then
( __c=0; mv /tmp/autopkgtest.eYrFOo/const_build_path 
/tmp/autopkgtest.eYrFOo/build-control/ || __c=$?; exit $__c; );
else
__x=$?;
if ( __c=0; mv /tmp/autopkgtest.eYrFOo/const_build_path 
/tmp/autopkgtest.eYrFOo/build-control/ || __c=$?; exit $__c; ); then exit $__x; 
else
echo >&2; "cleanup failed with exit code $?"; exit $__x;
fi;
fi

sudo: unable to resolve host jadzia
dpkg-buildpackage: error: fakeroot not found, either install the fakeroot
package, specify a command with the -r option, or run this as root
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/reprotest/__init_

Bug#877813: reprotest: regression between 0.7.1 and 0.7.2

2017-10-05 Thread gregor herrmann 
On Thu, 05 Oct 2017 22:16:00 +, Ximin Luo wrote:

> gregor herrmann:
> > [..]> dpkg-buildpackage: error: fakeroot not found, either install the 
> > fakeroot
> > package, specify a command with the -r option, or run this as root
> > [..]
> > 
> > This seems to be related to the "sudo" use in the output above (or
> > the funny output in the first line?), or
> > 
> >   * Improve the dsc+schroot preset to run builds as non-root.
> > 
> > in the changelog, or 62416ab in git.
> > 
> > After that, my python knowledge and domain knowledge ends; but
> > unfortunately this means that reprotest 0.7.2 is unusable for me.
> > 

> Hi gregor, does it work if log into your "default" schroot and
> install the "fakeroot" package?

Thanks for your super-fast reply.

Unfortunately, the answer is no:

After installing fakeroot in the schroot chroot and upgrading
reprotest again to 0.7.2 the result is -- hm, well different than
before. The first build succeeds, the second aborts with

package 1:

#v+
dpkg-buildpackage: info: binary-only upload (no source included)
copying /tmp/autopkgtest.uaX6su/artifacts-control/ back from virtual server's 
/tmp/tmp0i8yh6gh/control
build "experiment-1": vary environment, FIX build_path, FIX user_group, vary 
fileordering, vary home, vary kernel, vary locales, vary exec_path, vary time, 
vary timezone, vary umask
copying . over to virtual server's /tmp/autopkgtest.uaX6su/build-experiment-1/
starting build with source directory: 
/tmp/autopkgtest.uaX6su/build-experiment-1/, artifact pattern: ./../*.deb
Note, using directory './.' to get the build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
executing: if ( mv /tmp/autopkgtest.uaX6su/build-experiment-1/ 
/tmp/autopkgtest.uaX6su/const_build_path && mv 
/tmp/autopkgtest.uaX6su/const_build_path/ 
/tmp/autopkgtest.uaX6su/const_build_path-before-disorderfs/ && mkdir -p 
/tmp/autopkgtest.uaX6su/const_build_path/ && disorderfs --shuffle-dirents=yes 
/tmp/autopkgtest.uaX6su/const_build_path-before-disorderfs/ 
/tmp/autopkgtest.uaX6su/const_build_path/ && umask 0002 && export 
REPROTEST_BUILD_PATH=/tmp/autopkgtest.uaX6su/const_build_path/ && export 
REPROTEST_UMASK=$(umask) && faketime +373days+7hours+13minutes linux32 sh -ec 
'cd "$REPROTEST_BUILD_PATH"; unset REPROTEST_BUILD_PATH; umask 
"$REPROTEST_UMASK"; unset REPROTEST_UMASK; 
if [ "$(id -u)" = 0 ]; then
sudo -E -u "$LOGNAME" sh -ec '"'"'dpkg-buildpackage --no-sign 
-b'"'"';
else
sh -ec '"'"'dpkg-buildpackage --no-sign -b'"'"';
fi
' ); then
( __c=0; export PATH="/tmp/autopkgtest.uaX6su/bin:$PATH" || __c=$?; 
fusermount -u /tmp/autopkgtest.uaX6su/const_build_path/ || __c=$?; rmdir 
/tmp/autopkgtest.uaX6su/const_build_path/ || __c=$?; mv 
/tmp/autopkgtest.uaX6su/const_build_path-before-disorderfs/ 
/tmp/autopkgtest.uaX6su/const_build_path/ || __c=$?; mv 
/tmp/autopkgtest.uaX6su/const_build_path 
/tmp/autopkgtest.uaX6su/build-experiment-1/ || __c=$?; exit $__c; );
else
__x=$?;
if ( __c=0; export PATH="/tmp/autopkgtest.uaX6su/bin:$PATH" || __c=$?; 
fusermount -u /tmp/autopkgtest.uaX6su/const_build_path/ || __c=$?; rmdir 
/tmp/autopkgtest.uaX6su/const_build_path/ || __c=$?; mv 
/tmp/autopkgtest.uaX6su/const_build_path-before-disorderfs/ 
/tmp/autopkgtest.uaX6su/const_build_path/ || __c=$?; mv 
/tmp/autopkgtest.uaX6su/const_build_path 
/tmp/autopkgtest.uaX6su/build-experiment-1/ || __c=$?; exit $__c; ); then exit 
$__x; else
echo >&2; "cleanup failed with exit code $?"; exit $__x;
fi;
fi

disorderfs: shuffling dirents
disorderfs: reversing dirents
sudo: Î޷¨½âÎöÖ÷»ú£ºjadzia
tail: Î޷¨´ò¿ª'debian/changelog' ¶ÁȡÊý¾: ȨÏ޲»¹»
dpkg-buildpackage: erreur: fin de debian/changelog a produit une erreur de 
sortie de type 1
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 720, in run
return 0 if check_func(*check_args) else 1
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 332, in 
check
local_dists = [proc.send(nv) for nv in zip(bnames, build_variations)]
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 332, in 

local_dists = [proc.send(nv) for nv in zip(bnames, build_variations)]
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 298, in 
corun_builds
bctx.run_build(testbed, build, artifact_pattern, testbed_build_pre)
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 186, in 
run_build
kind='build')
  File "

Bug#877813: reprotest: regression between 0.7.1 and 0.7.2

2017-10-05 Thread gregor herrmann 
Package: reprotest
Version: 0.7.2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

reprotest 0.7 and 0.7.1 work fine for me, 0.7.2 explodes horribly:

#v+
preset auto-selected: ReprotestPreset(build_command='\nif [ "$(id -u)" 
= 0 ]; then\nsudo -E -u "$LOGNAME" sh -ec \'dpkg-buildpackage 
--no-sign -b\';\nelse\nsh -ec \'dpkg-buildpackage --no-sign 
-b\';\nfi\n', artifact_pattern='../*.deb', testbed_pre=None, 
testbed_init='apt-get -y --no-install-recommends install disorderfs faketime 
locales-all sudo util-linux; test -c /dev/fuse || mknod -m 666 
/dev/fuse c 10 229; test -f /etc/mtab || ln -s ../proc/self/mounts 
/etc/mtab', testbed_build_pre='apt-get -y --no-install-recommends build-dep 
./"."', source_pattern=None, diffoscope_args=[])
STARTING VIRTUAL SERVER 
['/usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-virt-schroot', 
'default']
reprotest [23:26:51]: version @version@
reprotest [23:26:51]: host jadzia; command line: /usr/bin/reprotest 
--variations=+all,-build_path,-user_group --verbosity 1 . -- schroot default
reprotest [23:26:52]: testbed package architecture: amd64
reprotest [23:26:52]: testbed running kernel: Linux 4.12.0-2-amd64 #1 SMP 
Debian 4.12.13-1 (2017-09-19)
Reading package lists...
Building dependency tree...
[..]
executing: if ( mv /tmp/autopkgtest.03NT2s/build-control/ 
/tmp/autopkgtest.03NT2s/const_build_path && umask 0022 && export 
REPROTEST_BUILD_PATH=/tmp/autopkgtest.03NT2s/const_build_path/ && export 
REPROTEST_UMASK=$(umask) && linux64 --uname-2.6 sh -ec 'cd 
"$REPROTEST_BUILD_PATH"; unset REPROTEST_BUILD_PATH; umask "$REPROTEST_UMASK"; 
unset REPROTEST_UMASK; 
if [ "$(id -u)" = 0 ]; then
sudo -E -u "$LOGNAME" sh -ec '"'"'dpkg-buildpackage --no-sign 
-b'"'"';
else
sh -ec '"'"'dpkg-buildpackage --no-sign -b'"'"';
fi
' ); then
( __c=0; mv /tmp/autopkgtest.03NT2s/const_build_path 
/tmp/autopkgtest.03NT2s/build-control/ || __c=$?; exit $__c; );
else
__x=$?;
if ( __c=0; mv /tmp/autopkgtest.03NT2s/const_build_path 
/tmp/autopkgtest.03NT2s/build-control/ || __c=$?; exit $__c; ); then exit $__x; 
else
echo >&2; "cleanup failed with exit code $?"; exit $__x;
fi;
fi

sudo: unable to resolve host jadzia
dpkg-buildpackage: error: fakeroot not found, either install the fakeroot
package, specify a command with the -r option, or run this as root
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 720, in run
return 0 if check_func(*check_args) else 1
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 332, in 
check
local_dists = [proc.send(nv) for nv in zip(bnames, build_variations)]
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 332, in 

local_dists = [proc.send(nv) for nv in zip(bnames, build_variations)]
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 298, in 
corun_builds
bctx.run_build(testbed, build, artifact_pattern, testbed_build_pre)
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 186, in 
run_build
kind='build')
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 61, in 
check_exec2
adtlog.AutopkgtestError)
  File "/usr/lib/python3/dist-packages/reprotest/lib/adt_testbed.py", line 370, 
in bomb
raise _type(m)
reprotest.lib.adtlog.AutopkgtestError: "sh -ec if ( mv 
/tmp/autopkgtest.03NT2s/build-control/ /tmp/autopkgtest.03NT2s/const_build_path 
&& umask 0022 && export 
REPROTEST_BUILD_PATH=/tmp/autopkgtest.03NT2s/const_build_path/ && export 
REPROTEST_UMASK=$(umask) && linux64 --uname-2.6 sh -ec 'cd 
"$REPROTEST_BUILD_PATH"; unset REPROTEST_BUILD_PATH; umask "$REPROTEST_UMASK"; 
unset REPROTEST_UMASK; 
if [ "$(id -u)" = 0 ]; then
sudo -E -u "$LOGNAME" sh -ec '"'"'dpkg-buildpackage --no-sign 
-b'"'"';
else
sh -ec '"'"'dpkg-buildpackage --no-sign -b'"'"';
fi
' ); then
( __c=0; mv /tmp/autopkgtest.03NT2s/const_build_path 
/tmp/autopkgtest.03NT2s/build-control/ || __c=$?; exit $__c; );
else
__x=$?;
if ( __c=0; mv /tmp/autopkgtest.03NT2s/const_build_path 
/tmp/autopkgtest.03NT2s/build-control/ || __c=$?; exit $__c; ); then exit $__x; 
else
echo >&2; "cleanup failed with exit code $?"; exit $__x;
fi;
fi
" failed with status 2
#v-

This seems to be related to the "sudo" use in the output above (or
the funny output in the first line?), or

  * Improve the dsc+schroot preset to run builds as non-root.

in the changelog, or 62416ab in git.

After that, my python knowledge and domain knowledge ends; but
unfortunately this means that reprotest 0.7.2 is unusable for me.

I'm happy to provide any further information or do any tests.


Cheers,
gregor


- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500,

Re: Bug#844431: Revised patch: seeking seconds

2017-08-13 Thread gregor herrmann 
On Sat, 12 Aug 2017 15:34:35 -0700, Sean Whitton wrote:

> diff --git a/policy/ch-source.rst b/policy/ch-source.rst
> index 127b125..6e32870 100644
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -661,6 +661,28 @@ particularly complex or unintuitive source layout or 
> build system (for
>  example, a package that builds the same source multiple times to
>  generate different binary packages).
>  
> +Reproducibility
> +---
> +
> +Packages should build reproducibly, which for the purposes of this
> +document [#]_ means that given
> +
> +- a version of a source package unpacked at a given path;
> +- a set of versions of installed build dependencies;
> +- a set of environment variable values;
> +- a build architecture; and
> +- a host architecture,
> +
> +repeatedly building the source package for the build architecture on
> +any machine of the host architecture with those versions of the build
> +dependencies installed and exactly those environment variable values
> +set will produce bit-for-bit identical binary packages.
> +
> +It is recommended that packages produce bit-for-bit identical binaries
> +even if most environment variables and build paths are varied.  It is
> +intended for this stricter standard to replace the above when it is
> +easier for packages to meet it.
> +
>  .. [#]
> See the file ``upgrading-checklist`` for information about policy
> which has changed between different versions of this document.
> @@ -790,3 +812,7 @@ generate different binary packages).
> often creates either static linking or shared library conflicts, and,
> most importantly, increases the difficulty of handling security
> vulnerabilities in the duplicated code.
> +
> +.. [#]
> +   This is Debian's precisification of the `reproducible-builds.org
> +   definition `_.


Seconded.

Thanks to everyone for their work on this.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [rt.cpan.org #118824] Test failures

2016-11-20 Thread gregor herrmann 
On Sun, 20 Nov 2016 10:51:44 -0500, Steffen Ullrich via RT wrote:

> https://rt.cpan.org/Ticket/Display.html?id=118824 >

> > The results are a bit mixed:
> > success on the buildd and the ci.debian.net server:
> > https://buildd.debian.org/status/logs.php?pkg=libnet-sip-perl=0.702-1
> > https://ci.debian.net/packages/libn/libnet-sip-perl/unstable/amd64/
> > 
> > But failures on the 3 reproducible-build machines:
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnet-sip-perl.html
> > -->
> > https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libnet-sip-perl_0.702-1.rbuild.log
> > https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/libnet-sip-perl_0.702-1.rbuild.log
> > https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/libnet-sip-perl_0.702-1.rbuild.log

> This looks for me like a very strange network setup on these
> systems where localhost IP 127.0.0.1 does not exist or cannot
> properly used to bind a socket (to a random port). 

Indeed, I was surprised about those messages as well.

> I think I've
> seen similar strange setups in some container environments. Could
> you please check the setup of these systems?

I can't check myself but I've added the Debian reproducible build
folks in Cc who can probably tell us more about the setup or might
even have an idea about the failures.

I don't think it's a general "can't bind to 127.0.0.1" case because
then we'd see tons of failure for all packages with some kind of
network tests. But somethings weird indeed …

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Aimee Mann: Susan


signature.asc
Description: Digital Signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] Bug#828636: Bug#828636: libembperl-perl: please make the build reproducible

2016-06-26 Thread gregor herrmann 
On Sun, 26 Jun 2016 17:16:52 +0200, Reiner Herrmann wrote:

> > Sorry, but that's wrong:
> > 
> > → dpkg -L libembperl-perl | egrep man/de/man./
> > /usr/share/man/de/man3/Embperl::Features.3pm.gz
> > → man /usr/share/man/de/man3/Embperl::Features.3pm.gz
> > 
> > That's clearly my mother tongue. :-)
> 
> Sorry, I assumed Embperl::Features was also misdetected (because the
> original file ends with D) and haven't looked into it.

Oops, sorry, I missed that too when applying Reiner's patch.

Looking at the manpage:

Das standart Layout einer Website can einmal definiert werden

I have a hard time defining this as German though :/
 

So yes, I guess we can remove this document.

Implemented in git; I'm holding off with a second hasty upload, sorry
for the first one.

Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Reproducible-builds] Bug#774869: libmodule-build-perl: please output data in stable order

2015-01-08 Thread gregor herrmann 
On Thu, 08 Jan 2015 16:30:27 +0100, Jérémy Bobbio wrote:

 Jonas Smedegaard:
  Seems you missed the attachment, though...
 Oops. :)
 It's also available from
 git://git.debian.org/reproducible/libmodule-build-perl.git

Module::Build is both in libmodule-build-perl and in perl-modules, so
you probably want the more or less same patch there as well.
 

Cheers,
gregor


-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT  SPI, fellow of the Free Software Foundation Europe
   `-   NP: Willi Resetarits + Stubnblues: noan wia mia


signature.asc
Description: Digital Signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds