=== fabo_ is now known as fabo
[12:22] <Laney> https://launchpad.net/~laney is oopsing consistently for me, e.g. OOPS-29f7ba54f72d33e36d4682f396ff82b3
[12:22] <ubot5> https://oops.canonical.com/?oopsid=OOPS-29f7ba54f72d33e36d4682f396ff82b3
[12:23] <cjwatson> Oopses are lagging pretty badly right now, but for me the traceback ends with:
[12:24] <cjwatson> ProgrammingError: syntax error at or near ")"<br /> LINE 1: ...rmaCategory.title FROM KarmaCategory WHERE id IN () ORDER BY...<br /> ^<br /> <br />
[12:24] <cjwatson> wgrant,stub: ^- something to do with the karma fiddling?
[12:25] <stub> yeah, some code assuming there is some karma for something :-/
[12:26] <wgrant> Oh, it must assume that there's at least one KarmaCache for each KarmaTotalCache, I guess.
[12:27] <cjwatson> Should we get webops to run foaf-update-karma-cache?  It's not going to run for quite a few hours otherwise
[12:29] <cjwatson> Pretty sure the offending method is Person._getContributedCategories BTW
[12:29] <cjwatson>         ids = ",".join(str(id) for [id] in cur.fetchall())
[12:29] <cjwatson>         return KarmaCategory.select("id IN (%s)" % ids)
[12:31] <stub> I'm running the script now
[12:32] <stub> Anything to distract me from Cassandra
[12:33] <cjwatson> stub: It takes four hours
[12:37] <stub> Laney: your page is fixed
[12:38] <Laney> ♥
[12:40] <Laney> And I have karma. Not sure I would have been able to go on otherwise.
=== shadeslayer_ is now known as shadeslayer
[14:18] <Odd_Bloke> When built packages in a PPA are awaiting publishing, is there any way of knowing when it will actually happen?
[14:32] <cjwatson> Odd_Bloke: You basically just have to poll; they're awaiting a fairly frequent cron job finishing
[14:33] <cjwatson> Odd_Bloke: In practice it's generally on the order of ten minutes
[14:38] <Odd_Bloke> cjwatson: Cool; never sure if I should go and make a cup of tea or not. :p
=== charles_ is now known as charles
[15:33] <TGreaves> Hi all. I'm having a bit of fun and games with post-build uploads which I've not come across before, whilst trying to do a bit of rough packaging of petsc-master. I have a successful build, but then an unhandled exception when the resulting debs are being uploaded, viz: https://launchpad.net/~fluidity-core/+archive/ubuntu/petsc-experiment/+build/6692422 . Any tips on how to resolve this, or indeed hints as to what I might have done to cause this, woul
[15:34] <cjwatson> TGreaves: Yes, I'm looking into that at the moment, don't know the cause yet
[15:34] <TGreaves> Thank you!
[15:34] <cjwatson> TGreaves: It's not your build's fault - it's affecting all build uploads
[15:37] <TGreaves> OK! I'll sacrifice a few goats over here for you :-) (And come back to my packaging tomorrow)
[15:58] <cjwatson> TGreaves: Fixed and retried.
[17:08] <TGreaves> cjwatson: Many thanks!
=== broder_ is now known as broder
[20:22] <natefoo> i'm unable to get/branch a certain branch in lp, i believe due to a bzr bug that existed during the time that certain branches were created?
[20:22] <natefoo> the branch is lp:ubuntu/trusty/mailman
[20:22] <natefoo> the bug seems to be the same as this https://bugs.launchpad.net/udd/+bug/848064
[20:22] <ubot5> Launchpad bug 888615 in Bazaar "duplicate for #848064 UDD branch freshness checker breaks on incomplete history" [High,Confirmed]
[20:23] <natefoo> could anyone let me know if they're able to branch that?
[20:26] <maxb> natefoo: Yes, I can branch it. (Probably because I have disabled the freshness checker)
[20:27] <maxb> launchpad.packaging_verbosity = off
[20:27] <natefoo> hey, that works. =)
[20:27] <natefoo> thanks,
[20:49] <natefoo> hmm, this isn't even the source branch for trusty's version of the mailman package.
=== s8321414_ is now known as s8321414