/srv/irclogs.ubuntu.com/2015/02/11/#launchpad-dev.txt

cjwatsonOK, I think that's all the BUILDERFAILed builds I can see retried.00:12
cjwatsonwgrant: You mentioned making sure AccessArtifact is hot before applying db-git.  Do you think that's still necessary given the staging timings, and if so how do we go about it?00:18
wgrantcjwatson: Yes, it's still necessary. A SELECT COUNT(*) FROM accessartifact; a few times should do it.00:18
wgrantwildcherry IO is sloooooooooow.00:18
cjwatsonOK, I'll put that in the RT.00:19
cjwatsonwgrant: https://wiki.canonical.com/InformationInfrastructure/OSA/LaunchpadProductionStatus#Unusual_Rollout_Requirements look right?00:22
wgrantcjwatson: I'd say "immediately before", but one of us will be handholding anyway I imagine.00:23
cjwatsontweaked00:24
wgrantThanks, looks good.00:25
cjwatsonThat's https://rt.admin.canonical.com/Ticket/Display.html?id=78737 now.00:27
cjwatsonHopefully wildcherry will rest in peace soon.00:28
wgrantQuite.00:28
ePierreHi everyone01:54
ePierreI was checking this page yesterday regarding the Launchpad API : https://help.launchpad.net/API/launchpadlib01:55
ePierreand I saw a link to the reference documentation: https://launchpad.net/+apidoc/01:55
ePierrehowever it looks like the current version of the API is planned to be deprecated in 2 months01:55
ePierreif I want to develop a little Python tool to retrieve and process info from Launchpad, should I still go with launchpadlib?01:56
wgrantePierre: launchpadlib is the way to go, but unless your application is being distributed to end-user systems it should probably be using the 'devel' API version.02:18
wgrant'1.0' will be around for longer than the page states (and even 'beta' still works, as we've had no reason to break it so far), but new applications that can be easily updated should use 'devel' by default.02:19
ePierrewgrant, ok thanks!02:32
ePierreFor now it's just gonna be for personal use (I just would like to tinker a bit with Python and Launchpad to retrieve info more easily than using the web interface)02:33
wgrantePierre: Definitely use devel, in that case.02:34
=== mup_ is now known as mup
cjwatsonwgrant: https://code.launchpad.net/~cjwatson/launchpad/git-basic-model/+merge/248976 should be ready for re-review now.12:39
wgrantAh, you beat me.12:43
wgrantJust finished with the second pass, just about there.12:44
cjwatsonOh zope.publisher why do you despise me12:44
wgrantcjwatson: https://code.launchpad.net/~wgrant/launchpad/xbia-refactor/+merge/249295 and https://code.launchpad.net/~wgrant/launchpad/xbia/+merge/249296 could do with a review if you have time today.12:44
wgrantWhat's it doing to you?12:44
cjwatsonwgrant: will do12:44
cjwatsonUnhelpful response to unexpected exceptions in XML-RPC methods.  (Hacking in traceback.print_exc)12:45
wgrantAh.12:45
cjwatsonEr traceback.print_exception12:45
cjwatsonOtherwise you just get "fatal: remote error: Unexpected Zope exception: TypeError: object.__new__() takes no parameters" and have to drink heavily.12:45
cjwatson</mjg59>12:45
wgrantNothing useful in the appserver log?12:46
cjwatsonNo, but there is if one hacks zope.publisher :)12:46
wgrantHeh12:46
cjwatson        # Create an appropriate Fault object. Unfortunately, we throw away12:46
cjwatson        # most of the debugging information. More useful error reporting is12:46
cjwatson        # left as an exercise for the reader.12:46
wgrant,,,12:46
cjwatsonwgrant: Does it matter (e.g. for determinism of build creation) that the return value of determine_architectures_to_build is no longer sorted?13:00
cjwatsonwgrant: And do we have agreement with Debian ftpmaster (or buildd admins?) on the specification?13:06
wgrantcjwatson: createForSource sorts the output, I think, but let me check.13:06
wgrantcjwatson: It's roughly compatible with the Debian proposal, at least in the ways we're likely to use it.13:07
wgrant(though the Debian proposal hasn't been touched in about a year)13:07
wgrantSteve needs this now, or gross hacks will abound.13:07
wgrantWe figure it'll only be a handful of packages, so even if they adopt a conflicting proposal it's pretty trivial to migrate.13:08
cjwatsonThe output isn't sorted AFAICS.13:08
wgrantcreateForSource sorts by processor.id13:09
cjwatsonOnly for arch_indep_das13:09
cjwatsonneeded_architectures is unsorted13:10
wgrantare you looking at the new code?13:10
wgrantOh, or did I break it in the refactor branch, and fix it in the final...13:10
cjwatsonAh, you would appear to have done13:11
wgrantYeah, sorry, you're right.13:11
cjwatsonOK, I guess we can land in one step.  Let me just reassure myself about the rest of the second branch.13:11
cjwatsonShouldn't there be some kind of assertion in determine_architectures_to_build that if we need an arch-indep build then we actually get one?13:14
cjwatsonOr will that fail later?13:15
wgrantIt may legitimately fail.13:16
wgrantIf I have an "Architecture: powerpc all", it will only build on powerpc. If I don't have powerpc, it shouldn't create any builds.13:16
cjwatsonSo that'll just return the empty dict.  OK.13:18
wgrantRight.13:18
cjwatsonr=me with a couple of comments13:32
wgrantThanks.13:34
wgrantdpkg-architecture is really slow.13:39
wgrantThe build start time estimate tests are the worst thing in the world.14:05
cjwatsonRe GitRepositorySet.set*Default, I was thinking of having those be internal methods which were called by methods that require edit permission on the target; I'm just not far enough up the stack to implement that yet.  But you're right that it shouldn't require edit permission on the repository, and I should make the intended use more clear.14:08
cjwatsons/Set//14:08
wgrantIn that case the automatic clobbering behaviour probably makes less sense.14:09
wgrantMoving them off Edit indeed sounds sensible.14:09
cjwatsonwgrant: I've addressed your second batch of git-basic-model comments.  Thanks.17:12

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!