Bug#764795: autopkgtest: Binaries in .changes are registered in wrong order
Tristan Seligmann
mithrandi at mithrandi.net
Sat Oct 11 07:15:25 UTC 2014
Package: autopkgtest
Version: 3.5.5
Severity: normal
When passing a .changes containing binary packages to --changes, the
binary and source packages seem to be registered in the wrong order,
causing the dependency installation to fail as the binary packages from
the .changes are not yet available. Passing the binary package(s)
manually using --binary *before* --changes fixes the problem.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_ZA.utf8, LC_CTYPE=en_ZA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages autopkgtest depends on:
ii apt-utils 1.0.9.2
ii libdpkg-perl 1.17.16
ii procps 2:3.3.9-8
ii python3 3.4.2-1
ii python3-debian 0.1.24
autopkgtest recommends no packages.
Versions of packages autopkgtest suggests:
ii lxc 1:1.0.6-2
pn qemu-system <none>
pn qemu-utils <none>
ii schroot 1.6.10-1+b1
-- no debconf information
More information about the autopkgtest-devel
mailing list