[01:46] <cjwatson> wgrant: Is https://launchpad.net/ubuntu/+source/python-htmltmpl/1.22-10/+build/221077 a consistency error?  That is still the published version of python-htmltmpl in precise; it should not have been deleted
[01:47] <cjwatson> (Noticed while trying to make my germinate-from-db branch work on dogfood.)
[03:46]  * mwhudson drops a pin
[04:48]  * nigelb catches the pin
[04:48] <nigelb> ...after about 1 hour
[04:55] <nigelb> spm: In other words, all the bits everyone wants to kill with fire (re: soyuz)
[04:55] <nigelb> :D
[04:55] <spm> heh
[04:55] <spm> no comment
[04:55] <nigelb> haha
[05:38] <spm> nigelb: you are truly the master of understatement. 1st it was kill with fire; and now "complicated". /me bows in awe
[05:38] <nigelb> spm: hey, I'll be nice to people who don't know about it ;)
[05:38] <spm> :-D
=== hloeung_ is now known as hloeung
[06:25] <wgrant> cjwatson: It's a bit more sinister than that, I'm afraid.
[06:26] <wgrant> cjwatson: It's impossible to natively publish some archives, even on proudction.
[06:26] <wgrant> cjwatson: Because the files have been inappropriately deleted from the DB.
[06:26] <wgrant> (this also makes it somewhat challenging to republish the primary archive, even non-natively.
[06:29] <wgrant> cjwatson: And I guess that python-htmltmpl is an example of that.
[06:29] <wgrant> I had a list at one point.
[07:59] <uncle_ian> bigjools: o/
[07:59] <bigjools> uncle_ian: GTFO
[07:59] <rick_h__> awesome!
[08:05] <uncle_ian> huwshimi: o/
[08:06] <huwshimi> uncle_ian: Morning :)
[08:54] <cjwatson> wgrant: I wonder what we should do about that.  I could upload rebuilds of affected packages to precise, which would make it irrelevant eventually, but ...
[08:58] <cjwatson> (and it would be ultimately better to stuff the relevant files back into the db so that everything's consistent)
[09:13] <wgrant> cjwatson: I have a script to identify them and reincarnate them from the pool.
[09:16] <cjwatson> I would love it if that were run.  Is it blocked on anything?
[09:17] <wgrant> As would I, but I need to convince bigjools to let me run it.
=== almaisan-away is now known as al-maisan
[09:43] <cjwatson> wgrant: Lucky you're in the same building, then. :-)
[09:44] <wgrant> cjwatson: But MaaS has stolen him :(
[09:45] <cjwatson> arse
[09:46] <wgrant> But I will track him down eventually.
[09:46] <wgrant> http://bazaar.launchpad.net/~wgrant/launchpad/binary-necromancy/revision/13902 has the scipt
[09:46] <cjwatson> well, I guess I'm not convinced that germinate-from-db will actually be viable anyway; the similar work in the publisher only has to compete with apt-ftparchive on performance, but germinate-from-db has to compete with apt reading Packages/Sources off disk
[09:46] <wgrant> Probably fairly bitrotten
[09:46] <wgrant> Yeah
[09:47] <cjwatson> it's mind-numbingly slow on dogfood, and I can't really tell whether that's just dogfood or not
[09:47] <cjwatson> I suppose I could try finishing the work to native-publish Ubuntu and then time that, but I have other things to do this year :)
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
[10:05] <jcsackett> wgrant: https://github.com/mardambey/postoffice
[10:33] <deryck> StevenK, rick_h__ https://one.ubuntu.com/combo/4931/?js/one-yui-meta-min.js&js/yui/yui/yui-min.js&js/loader/loader-min.js
[10:45] <rick_h__> deryck: if you get a sec, diff is uploading: https://code.launchpad.net/~rharding/launchpad/replace_foldables/+merge/87924
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
[11:18] <Laney> https://code.launchpad.net/~laney/launchpad/spph-sponsor/+merge/87929 got approved: can somebody land it?
[11:21] <ayan> maxb: thank you!  that was exactly what i was looking for.
[11:21] <nigelb> Laney: Yay!
[11:21] <Laney> nigelb: only the first step :P
[11:21] <nigelb> Once it lands, I'll show you the scoreboard where we cmpete with wgrant :P
[11:21] <nigelb> *compete
[11:21] <ayan> maxb: how did you find that information?  that still isn't obvious to me after reading the api documentation.
[11:38] <cjwatson> ayan: does https://help.launchpad.net/API/Examples help?  it doesn't have that literal example.
[11:38] <cjwatson> ayan: (which bit isn't obvious?)
[11:40] <cjwatson> ayan: I guess you need to know that a foo_collection_link attribute in apidoc means that there's a corresponding foo object synthesised by launchpadlib corresponding to the collection
[11:41] <cjwatson> ayan: you can sort of deduce that by comparing https://help.launchpad.net/API/launchpadlib#Collections with the apidoc; maxb may well have just known it off the top of his head though since it's a fairly common initial step in a launchpadlib script
[11:42] <maxb> I looked it up using launchpadlib's introspection facilities
[11:45] <maxb> I use a custom lpshell script (http://paste.ubuntu.com/799258/) including a custom describe(x) function (http://paste.ubuntu.com/799260/) which prettyprints the lp_attributes/entries/collections/operations attributes
[11:55] <rick_h__> deryck: http://pad.ubuntu.com/VyfPUoW5Cy
[13:23] <lifeless> gmb: I don't see the tags in the current streams LP emits
[13:23] <lifeless> I was looking to check this thing I said I would...
[13:25] <gmb> lifeless, They're there. Pipe it through grep and look for zope:layer and you should see them.
[13:27] <lifeless> garh
[13:29] <lifeless> gmb: right, I see them, testr is dropping them somehow.
[13:29] <lifeless> gmb: headdesk headdesk headdesk
[13:30] <gmb> Yeah.
[13:30] <lifeless> gmb: this is why you are not seeing the tags I suspect. Digging
[13:31] <gmb> Thanks.
[13:32] <jml> I'm guessing https://bugs.launchpad.net/subunit/+bug/816690
[13:32] <jml> (which apparently I've filed twice)
[13:32] <_mup_> Bug #816690: TestProtocolClient doesn't support tags <subunit:Triaged> < https://launchpad.net/bugs/816690 >
[13:33] <jml> https://bugs.launchpad.net/subunit/+bug/518016 is the other one
[13:33] <_mup_> Bug #518016: No public API for tagging on TestProtocolClient <subunit:Triaged> < https://launchpad.net/bugs/518016 >
[13:33] <gmb> jml, Yes, I'm looking at 518016 now...
[13:33] <jml> I'd mark as a dupe, but my net connection is so poor I can't load the page.
[13:33] <gmb> I'll do it.
[13:34] <jml> gmb: ta.
[13:35] <lifeless> mm
[13:35] <gmb> jml, lifeless: So, IIUC the tags are in the subunit output from zope, but then testr eats them, right?
[13:35] <lifeless> ProtocolTestCase perhaps
[13:42] <lifeless> jml: ThreadsafeForwardingResult drops tags
[13:45] <gary_poster> http://lxc.teegra.net/
[13:47] <jml> lifeless: ah.
[14:27] <cr3> what kind of permissions does a project maintainer have?
[14:29] <bac> cr3: the maintainer can administer the project and do everything required except for those things that require LP admin.  do you have a specific question?
[14:30] <cr3> bac: "everything required" is a bit vague, does he have special permissions for bugs and blueprints that others might not have for example?
[14:30] <bac> yes
[14:34] <cr3> bac: ok, I'll compare the list of options available for a project where I'm maintainer to one where I'm not. it should be rather obvious
=== james_w` is now known as james_w
[14:55] <ayan> So... I'd like to programmatically nominate a bug for a series.  Does it only make sense to nominate a bug_task?  Can someone point me to documenation that explains the relationship between bugs, possibly bug_tasks, and series nomination?
[15:06] <cjwatson> ayan: You nominate bugs, not bug_tasks.  You can tell this because only bug has the addNomination method.  https://launchpad.net/+apidoc/1.0.html#bug
[15:07] <cjwatson> (It might be nice to nominate bug_tasks, but you can see this same thing in the UI; if you nominate a bug with tasks on multiple source packages, it gets nominations for all of them in one go and if you don't want some of them you have to mark them Invalid.)
[15:43] <rick_h__> anyone up for reviewing some JS? https://code.launchpad.net/~rharding/launchpad/replace_foldables/+merge/87924
[15:56] <wgrant> lifeless: Where is gpgverifyd?
[15:56] <wgrant> s/Where //
[16:33] <lifeless> wgrant: bzr+ssh://bazaar.launchpad.net/~lifeless/%2Bjunk/gpgverify/
[16:35] <wgrant> lifeless: Ah!
[16:41] <lifeless> jml: and threadsafeforwardingresult appears to not implement time()
[16:42] <jml> lifeless: right.
[16:52] <lifeless> doesn't need to implement it now I look, but it does have a bug (filed)
[16:52] <jml> lifeless: couldn't tell you off the top of my head
[16:53] <wgrant> bigjools: So, I think we should deploy buildd-manager at 9am tomorrow
[16:54] <wgrant> bigjools: And see if it breaks again :)
[16:54] <bigjools> wgrant: I'd quite like it QAd first
[16:54] <wgrant> That was so effective the last two times... :)
[16:55] <StevenK> bigjools: So instead of doing project work, wgrant and I have to spend hours doing so instead?
[16:55] <bigjools> don't be so melodromatic
[16:55] <StevenK> But buildd-manager QA is easily several houres.
[16:55] <StevenK> s/houres/hours/
[16:56] <bigjools> not at all
[16:56] <bigjools> I said to jtv that we need one of each type of build pushed through
[16:56] <bigjools> s/jtv/allenap/
[16:56] <bigjools> then I would be happy if they all worked without triggering the r/o database code
[16:57] <StevenK> Sure, and if we do that, then we're not checking everything and we may as well deploy it and roll it back
[16:57] <bigjools> we're checking the basics
[16:57] <StevenK> Quick QA of buildd-manager is effectively pointless.
[16:57] <bigjools> are you insane?
[16:58] <StevenK> With a change of this magnatude, *and* it's been rolled back at least twice.
[17:02] <bigjools> I will pop to your room and explain
=== al-maisan is now known as almaisan-away
[17:32] <rick_h__> wallyworld: https://code.launchpad.net/~rharding/launchpad/replace_foldables/+merge/87924
=== salgado is now known as salgado-afk
[18:31] <rick_h__> wallyworld: http://yuilibrary.com/yui/docs/event/#event-whitelist
[18:37] <rick_h__> http://yuilibrary.com/yui/docs/api/classes/Event.html#method_getListeners
=== salgado-afk is now known as salgado