On Sun, 2016-10-16 at 15:53 +0200, Guillem Jover wrote: > Hi! > > On Sat, 2016-10-01 at 21:07:30 +0100, Ben Hutchings wrote: [...] > > You seem to be saying that dpkg won't allow an M-A foreign package to > > satisfy a :native dependency, even if the package is native. Which > > would mean we can't both support cross-building with openssl 1.0, and > > building with openssl 1.1, from the same source package. > > > I think in this particular case, the correct solution is to also fix > openssl 1.0 in unstable with the correct annotations so that there's > no divergence between the suites. Is there any reason that would be > problematic? [...] That doesn't seem problematic to me. It would also need to be updated in jessie-backports. But rather than blocking on that, I will change linux's build-depdendency to: openssl (>= 1.1.0-1~) <!stage1> | openssl:native <!stage1> With that, dpkg-checkbuilddeps seems satisfied with either openssl 1.0.2j-1 or 1.1.0b-2 installed, and with or without the -aarmhf option. Ben. -- Ben Hutchings The world is coming to an end. Please log off
Attachment:
signature.asc
Description: This is a digitally signed message part