Hi Michael, On 04-07-18 12:48, Michael Biebl wrote: > the latest systemd upload triggered various, new regressions. > E.g. looking at nftables, I can't really make sense out this error message: > > Building dependency tree... > Reading state information... > E: Unable to locate package [linux-any] > E: Couldn't find any package by glob '[linux-any]' > E: Regex compilation error - Invalid range end > E: Couldn't find any package by regex '[linux-any]' > E: Unable to locate package [linux-any] > E: Couldn't find any package by glob '[linux-any]' > E: Regex compilation error - Invalid range end > E: Couldn't find any package by regex '[linux-any]' > E: Unable to locate package [linux-any] > E: Couldn't find any package by glob '[linux-any]' > E: Regex compilation error - Invalid range end > E: Couldn't find any package by regex '[linux-any]' > autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt > pinning. Retrying with using all packages from unstable > Reading package lists... > Building dependency tree... > Reading state information... > Starting pkgProblemResolver with broken count: 0 > Starting 2 pkgProblemResolver with broken count: 0 > Done > 0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Setting up autopkgtest-satdep (0) ... > Reading package lists... > Building dependency tree... > Reading state information... > E: Unable to locate package [linux-any] > E: Couldn't find any package by glob '[linux-any]' > E: Regex compilation error - Invalid range end > E: Couldn't find any package by regex '[linux-any]' > E: Unable to locate package [linux-any] > E: Couldn't find any package by glob '[linux-any]' > E: Regex compilation error - Invalid range end > E: Couldn't find any package by regex '[linux-any]' > E: Unable to locate package [linux-any] > E: Couldn't find any package by glob '[linux-any]' > E: Regex compilation error - Invalid range end > E: Couldn't find any package by regex '[linux-any]' > systemd-service-test.sh FAIL badpkg > blame: nftables > badpkg: Test dependencies are unsatisfiable. A common reason is that > your testbed is out of date with respect to the archive, and you need to > use a current testbed or run apt-get update or use -U. > autopkgtest [04:35:09]: @@@@@@@@@@@@@@@@@@@@ summary > command1 FAIL badpkg > blame: nftables > badpkg: Test dependencies are unsatisfiable. A common reason is that > your testbed is out of date with respect to the archive, and you need to > use a current testbed or run apt-get update or use -U. > internaltest-shell.sh FAIL badpkg > blame: nftables > badpkg: Test dependencies are unsatisfiable. A common reason is that > your testbed is out of date with respect to the archive, and you need to > use a current testbed or run apt-get update or use -U. > systemd-service-test.sh FAIL badpkg > blame: nftables > badpkg: Test dependencies are unsatisfiable. A common reason is that > your testbed is out of date with respect to the archive, and you need to > use a current testbed or run apt-get update or use -U. > > > Do you have any idea what's going on here? I have noticed them in a couple of logs already myself, but I haven't had the time to investigate yet. It looks like a bug to me. I think I saw them before autopkgtest 5.4, but I'd like to confirm that. If only after autopkgtest 5.4 I think the "Versioned Provides" is suspicious. If this is from before 5.4, maybe apt? Paul
Attachment:
signature.asc
Description: OpenPGP digital signature