Package: reprotest
Version: 0.2
Severity: normal

The virtualization backend binaries provided by autopkgtest are supposed
to be consumable by external tools┬╣. Maybe we are not in a point where
actually doing that is easy/convenient, but having a full copy of the
autopkgtest code base in reprotest does not seem to be right.

I even understand how this helped bootstrap the project and made it
easier at the beginning, but I'm sure you will agree with me that reuse
by copy-and-paste and embedded code copies are not good ideas.

┬╣ see e.g.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reprotest depends on:
ii  apt-utils       1.3~rc4
ii  diffoscope      59
ii  libdpkg-perl    1.18.10
ii  procps          2:3.3.12-2
ii  python3-debian  0.1.29
pn  python3:any     <none>

Versions of packages reprotest recommends:
ii  autodep8     0.8
ii  disorderfs   0.4.3-1
ii  locales-all  2.24-1
ii  qemu-system  1:2.6+dfsg-3
ii  qemu-utils   1:2.6+dfsg-3
ii  schroot      1.6.10-2+b1

reprotest suggests no packages.

-- no debconf information

Attachment: signature.asc
Description: PGP signature

Reproducible-builds mailing list

Reply via email to