[Pkg-electronics-devel] Bug#1132122: nextpnr: autopkgtest regression

[Adrian Bunk]

Source: nextpnr
Version: 0.10-4
Severity: serious
X-Debbugs-Cc: Simon Richter <sjr at debian.org>

https://ci.debian.net/data/autopkgtest/testing/amd64/n/nextpnr/69791288/log.gz

...
209s E: Unable to satisfy dependencies. Reached two conflicting assignments:
209s    1. nextpnr-himbaechel:amd64 is selected for install because:
209s       1. satisfy:command-line:amd64=1 is selected for install
209s       2. satisfy:command-line:amd64 Depends nextpnr-himbaechel
209s    2. nextpnr-himbaechel:amd64 Depends nextpnr-himbaechel-gowin-chipdb (= 0.10-2)
209s       but none of the choices are installable:
209s       [no choices]
210s command6             FAIL badpkg
...
239s autopkgtest [23:48:34]: @@@@@@@@@@@@@@@@@@@@ summary
239s command1             PASS (superficial)
239s command2             PASS (superficial)
239s command3             PASS (superficial)
239s command4             PASS (superficial)
239s command5             PASS (superficial)
239s command6             FAIL badpkg
239s blame: nextpnr
239s 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.
239s command7             FAIL badpkg
239s blame: nextpnr
239s 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.



The autopkgtests need updating for the himbaechel changes in 0.10-3.