Control: tags -1 - moreinfo On Wed, Jul 04, 2018 at 10:37:32PM +0200, Michael Biebl wrote: > sound like an sbuild bug. Using pbuilder I have no problems building the > gnupg2 package.
I kinda agree with you here. I actually ran into this bug a while earlier: Unlike systemd-sysv, systemd-shim isn't Multi-Arch: foreign. So installing a foreign libpam-systemd (as some cross builds do) did run into the very same issue for a while already: It tried installing systemd-shim and gave up even though just picking systemd-sysv would have worked. Actually, sbuild defers to apt here, so it would be an apt bug, no? > Can you please reassign this bug report to the appropriate package? I thus filed this bug with apt as #883555. The irc discussion on the matter was unfortunately not reflected on the bug, but essentially deity ruled that solving each and every situation was infeasible and that packages must coordinate better to resolve such issues. In the case of #883555 that meant that both alternatives should share the same Multi-Arch value. So even though this issue can be considered and apt bug, it'll be wontfix there and you'll have to fix it in systemd anyway. I'm Ccing deity here to have them speak up in case they disagree with that analysis. On irc you proposed two solutions: * dropping the -shim alternative * adding the inverse version restriction of the breaks to the -shim alternative As far as I understand, either solution would solve this bug. Helmut
