[02:45] <ByPasS> Hi quick question I'm backporting some packages and I have this issue since I added an gpg key : http://paste.ubuntu.com/10681852/ it cant upload
[02:47] <ByPasS> I can assure that "Trove" doesnt have any packages in it (was there but been deleted and not showing in the website)
[03:10] <sarnold> does anyone know why there's no .gpg files in my newly cretaed ppa?
[03:10] <sarnold> http://ppa.launchpad.net/seth-arnold/icehouse-proposed/ubuntu/dists/trusty/
[03:18] <wgrant> sarnold: A person or team's PPA signing key is only generated after the first source upload to one of their PPAs, so the first PPA can be published unsigned the first time.
[03:18] <wgrant> The next change to the suite will cause it to be signed.
[03:19] <sarnold> wgrant: interesting, so mine is unsigned because i've only copied binaries into it rather than building from source?
[03:19] <wgrant> sarnold: s/upload //, then :)
[03:19] <wgrant> Basically, we don't generate PPA keys until the person or team has a non-empty PPA.
[03:20] <wgrant> And key generation isn't instantaneous, so it is often the case that the PPA gets published before the key is generated.
[03:20] <sarnold> I did wonder briefly about that, but the keyid is listed inthe graphical interface, and a cloud instance had the key in /etc/apt/trusted... already
[03:21] <sarnold> I wondered if the signture generation might also be async -- I'm glad I didn'tjust wait until tomorrow to find out :)
[03:22] <wgrant> There's currently no mechanism to force a suite to be republished without a publication change.
[21:41] <micahg> hi lamont,  the lcy01-* builders seem to be preoccupied for a couple days now, would you be able to have a look?
[21:42] <lamont> micahg: see #webops
[21:43] <micahg> ah, thanks
[21:43] <micahg> lamont: I can't see that anymore :)
[21:43] <micahg> but if it's handled, I trust you
[21:49] <lamont> micahg: oh.  sorry.  #canonical-sysadmins this channel
[21:49] <lamont> er, singular
[21:50] <micahg> ah, should I ask there, no one seems to be around