xdeb fails if dpkg-cross has nothing to do
Bug #731079 reported by
Steve Langasek
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xdeb (Ubuntu) |
Fix Released
|
High
|
Wookey |
Bug Description
Binary package hint: xdeb
If dpkg-cross fails to output a cross package for a given input, it returns non-zero and causes xdeb to abort. We should trap such errors, identify the package failing to import, and rerun dpkg-cross, excluding the responsible package from the set of packages to cross and from the dependency list of the resulting crossed packages.
Related branches
Changed in xdeb (Ubuntu): | |
assignee: | nobody → Wookey (wookey) |
Changed in xdeb (Ubuntu): | |
status: | New → Confirmed |
Changed in xdeb (Ubuntu): | |
status: | Confirmed → Fix Committed |
To post a comment you must log in.
From what I'm seeing, this also causes more problems than just requiring xdeb to be restarted. Especially when using --only-explicit, the import failure means that, since the package has already been downloaded and the .changes file generated, the package is treated as "built" which stops any further reprocessing of the package upon next invocation... including not attempting to cross-install the packages, so xdeb happily carries on and tries to build the target package without all the cross build-deps installed.