Comment 10 for bug 1641615

Hmm, one of the remaining differences between LP:ppa and LP:main builds are that the LP:main builds have proposed enabled as it should be but the ppa's have not.

I knew that but didn't realize due to the raciness in general that it might be important.
Remember that even with proposed enabled on the LP based chroot I only got it reproduced once.

I compared the buildlogs and found that between good and bad (with proposed).
That list looks promising in regard to the issue I have, especially since there is gnuttls in it.

  Different:
  Get: http://ftpmaster.internal/ubuntu zesty-proposed/main amd64 linux-libc-dev amd64 4.8.0-27.29 [856 kB]

  On-Top:
  Get: http://ftpmaster.internal/ubuntu zesty-proposed/main amd64 libgnutls30 amd64 3.5.6-4ubuntu1 [626 kB]
  Get: http://ftpmaster.internal/ubuntu zesty-proposed/main amd64 libsasl2-modules-db amd64 2.1.27~72-g88d82a3+dfsg-1 [15.1 kB]
  Get: http://ftpmaster.internal/ubuntu zesty-proposed/main amd64 libsasl2-2 amd64 2.1.27~72-g88d82a3+dfsg-1 [48.8 kB]
  Get: http://ftpmaster.internal/ubuntu zesty-proposed/main amd64 libgssapi-krb5-2 amd64 1.15~beta1-1 [120 kB]
  Get: http://ftpmaster.internal/ubuntu zesty-proposed/main amd64 libkrb5-3 amd64 1.15~beta1-1 [274 kB]
  Get: http://ftpmaster.internal/ubuntu zesty-proposed/main amd64 libkrb5support0 amd64 1.15~beta1-1 [31.8 kB]
  Get: http://ftpmaster.internal/ubuntu zesty-proposed/main amd64 libk5crypto3 amd64 1.15~beta1-1 [83.9 kB]

This might also be a false assumption based on the bad reproducibility out of the main LP upload - but worth a check.
So I changed the ppa dependencies and pushed another upload to the ppa to confirm.