[00:04] <cjwatson> infinity: no - the situation on arm64 was a bit unclear and clouded by how unstable they are at the moment
[08:17] <flocculant> I assume people know, but just in case Xubuntu and Ubuntu xenial's didn't build yesterday, ubuntu hasn't today so I'm guessing xubuntu won't either
[09:43] <sil2100> Hello! I'm disabling the system-image importer for a short while again
[22:07] <superm1> could someone help me understand why fwupdate hasn't migrated from proposed?  it looks like all the builds were full of success and it's not in NEW or unapproved
[22:08] <doko> superm1, looks like it's waiting for fwupdate-amd64-signed ?
[22:08] <superm1> doko: how does that happen?
[22:11] <superm1> i'm not sure anything about how the signed packages get built, is it just a manual bump to fwupdate-signed's changelog and it will pull down a new binary from the archive during build?
[22:18] <xnox> superm1, i think you want to poke cyphermox about matching https://launchpad.net/ubuntu/+source/fwupdate-signed upload to get fwupdate migrating.
[22:21] <superm1> cyphermox: is it  just a new upload of fwupdate-signed like this: http://paste.ubuntu.com/14057549/ ? if so i'll upload it
[22:22] <cyphermox> yeah that should be all, if fwupdate didn't change filenames or something
[22:23] <superm1> shouldn't have
[22:24] <cyphermox> right, doesn't look like it did
[22:25] <xnox> superm1, and e.g. signed files look to be in place e.g. http://archive.ubuntu.com/ubuntu/dists/xenial-proposed/main/uefi/fwupdate-amd64/0.5-1/ and http://archive.ubuntu.com/ubuntu/dists/xenial-proposed/main/uefi/fwupdate-i386/0.5-1/ are available.
[22:29] <superm1> okay thanks guys, i'll upload that diff then.  didn't realize the -signed packages were all manually done
[22:31] <xnox> superm1, it's a bit triky, as first package needs to build and publish, then a signed version is published into the archive in magic paths (e.g. /uefi/) and then we build another package which at build time fetched signed copy back from the archive and packages it into a deb.... to publish as normal "apt-get"-able package.
[22:32] <xnox> superm1, new apt has support to download and fetch arbitrary files, maybe eventually such chicken-egg-dances will be gone. and apt will simply download arbitrary files in release manifest.
[22:32] <xnox> superm1, but for obvious reasons builders do not have access to signing keys to do everything in one go.
[22:32] <superm1> xnox: ah yeah i was just wondering about if new apt might help here make this prettier