Source: nextpnr
Version: 0.10-1
Severity: serious
X-Debbugs-Cc: Simon Richter <[email protected]>

https://ci.debian.net/data/autopkgtest/testing/i386/n/nextpnr/69592928/log.gz

...
171s The following packages have unmet dependencies:
172s  satisfy:command-line : Depends: nextpnr-ice40-qt but it is not going to 
be installed
172s E: Unable to satisfy dependencies. Reached two conflicting assignments:
172s    1. nextpnr-ice40-qt:i386 is selected for install because:
172s       1. satisfy:command-line:i386=1 is selected for install
172s       2. satisfy:command-line:i386 Depends nextpnr-ice40-qt
172s    2. nextpnr-ice40-qt:i386 Depends nextpnr-ice40-chipdb (= 0.9-1)
172s       but none of the choices are installable:
172s       [no choices]
172s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt 
pinning. Retrying with using all packages from unstable
172s Reading package lists...
172s Building dependency tree...
172s Reading state information...
172s Solving dependencies...
172s Some packages could not be installed. This may mean that you have
172s requested an impossible situation or if you are using the unstable
172s distribution that some required packages have not yet been created
172s or been moved out of Incoming.
172s The following information may help to resolve the situation:
172s 
172s The following packages have unmet dependencies:
173s  satisfy:command-line : Depends: nextpnr-ice40-qt but it is not going to 
be installed
173s E: Unable to satisfy dependencies. Reached two conflicting assignments:
173s    1. nextpnr-ice40-qt:i386 is selected for install because:
173s       1. satisfy:command-line:i386=1 is selected for install
173s       2. satisfy:command-line:i386 Depends nextpnr-ice40-qt
173s    2. nextpnr-ice40-qt:i386 Depends nextpnr-ice40-chipdb (= 0.9-1)
173s       but none of the choices are installable:
173s       [no choices]
173s command3             FAIL badpkg
...


#1072678 was only about 32-bit arm, there was no problem building
the package on i386.

But even changing these back to "Architecture: any" is possible,
by updating the build dependencies to Qt6 which does not have
this problem.

Reply via email to