[08:24] <mvo> hi, can someone help me with the snap building in LP? I get an error in https://code.launchpad.net/~mvo/+snap/ubuntu-image - "Err http://ppa.launchpad.net/snappy-dev/tools/ubuntu yakkety InRelease
[08:24] <mvo>   The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F1831DDAFC42E99D" is the error which looks like something in LP is wrong for yakkety snap building?
[08:33] <mvo> cjwatson: maybe an idea about my above question?
[08:34] <wgrant> mvo: Weird, our chroots all have APT::Get::AllowUnauthenticated=1
[08:34] <wgrant> So that error shouldn't be possible.
[08:35] <wgrant> And that should be breaking all PPA builds as well.
[08:37] <mvo> wgrant: hm,hm
[08:38] <wgrant> That basically matches my thoughts.
[08:39] <wgrant> And no new apt for a few days.
[08:39] <wgrant> How odd.
[08:39] <mvo> wgrant: yes, exactly
[08:40] <wgrant> Plus the chroot would start with a very old apt anyway.
[08:40] <wgrant> Oh
[08:40] <wgrant> mvo: That's not fatal.
[08:41] <wgrant> Oh the real error is the same thig just lower down.
[08:41] <wgrant> mvo: Is that final apt call, after "Preparing to pull ubuntu-image", running with the normal apt config?
[08:41] <wgrant> Or is snapcraft or similar constructing its own, I wonder.
[08:42] <mvo> wgrant: oh, that might be it, and its copying the sources from the host maybe, let me look at the snapcraft source
[08:44] <wgrant> mvo: At one point it wasn't copying in sources.list, so it wouldn't have run into this.
[08:44] <wgrant> mvo: But I don't know when that changed.
[08:46] <mvo> wgrant: just a theory right now, I look at the source now
[08:56] <mvo> wgrant: definitely a snapcraft bug, thanks for your help and sorry for the noise (https://bugs.edge.launchpad.net/ubuntu/+bug/1621382)
[23:10] <renatosilva> how do I unsubscribe from all/most mail from launchpad? do I need to go EVERY bug report for muting email?