On Sun, 02 Feb 2020 00:23:59 +0100 Johannes Schauer wrote: > Quoting Francesco Poli (2020-02-01 16:52:47) > > The only differences shown in the resulting report_diffoscope.html file seem > > to be: > > > > • the generated files in the content > > of ./boot/initrd.img-5.4.0-3-amd64 have differing creation > > timestamps (but this is obvious, since the two initrd were not > > created exactly at the same time!) > > > > • ./var/lib/initramfs-tools/5.4.0-3-amd64 files differ (but they seem > > to include some checksum of the initrd, hence the difference should > > be consequence of the first point) > > this should go away when you set SOURCE_DATE_EPOCH to something like $(date > +%s) -- why didn't you set it in your tests?
It's plain simple: because I am an idiot! ;-)
I just failed to think about it...
After setting the same SOURCE_DATE_EPOCH, the only remaining
differences were the machine-id and the hashlib.cpython-37.pyc file!
>
> > • ./etc/machine-id and ./var/lib/dbus/machine-id files differ (but I
> > think this should not be surprising...)
>
> In the next mmdebstrap release /etc/machine-id will be set to an empty file.
OK.
>
> > • ./usr/lib/python3.7/__pycache__/hashlib.cpython-37.pyc files have
> > some different hex values (I am not sure why, but it's compiled
> > Python code, maybe it includes a compilation timestamp or
> > something?!?)
>
> This is a known bug that I have yet to report to the Python maintainers.
Ah, interesting.
I encourage you to report this bug, as it might help the Reproducible
Builds effort...
>
> > I am under the impression that the two .tar files are to be considered
> > equivalent.
> > Do you agree?
>
> Yes. :)
OK, in the meanwhile I got around to check whether the .qcow2 image is
actually working as autopkgtest testbed.
Unfortunately, no, it's not working! :-(
$ autopkgtest --output-dir ./${PKG}_${VERS}_autopkgtest.out \
--summary ./${PKG}_${VERS}_autopkgtest.summary \
-B ./${PKG}_${VERS}_amd64.changes \
-- qemu ~/Downloads/TEST/debian-unstable.qcow2
autopkgtest [16:23:45]: version 5.11
autopkgtest [16:23:45]: host ${HOST}; command line: ${CMDLINE}
qemu-system-x86_64: terminating on signal 15 from pid 8488 (/usr/bin/python3)
<VirtSubproc>: failure: timed out waiting for "login prompt on ttyS0"
autopkgtest [16:24:45]: ERROR: testbed failure: cannot send to testbed:
[Errno 32] Broken pipe
Could you help me to investigate the issue?
Is the command line correct?
Where did I go wrong?
--
http://www.inventati.org/frx/
There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgp86n5EiaIx2.pgp
Description: PGP signature
