#launchpad-dev 2009-11-01 <maxb> Ah, that's better, SSHServerLayer tests are happier now I've uninstalled bzr-svn * maxb is starting to wonder if xx-resetpassword-of-sso-account.txt requires you to have canonical-identity-provider to pass :-/ <wgrant> maxb: Where does that live? I can't see it anywhere. <maxb> ./lib/lp/registry/stories/foaf/xx-resetpassword-of-sso-account.txt <wgrant> Oh. <wgrant> Doesn't exist in db-devel. <wgrant> WTF. <wgrant> That seems like a somewhat concerning bug. <wgrant> Oh, it's just brand new. <wgrant> Nevermind. <wgrant> But yes, that should live in c-i-p <maxb> well, goody, that means ztk-2.5 is still alive and unbitrotten <wgrant> Excellent. <rockstar> sinzui, do you happen to be reviewing projects right now? <sinzui> rockstar: I did a few hours ago <rockstar> sinzui, ah, okay. I just noticed the project count was dropping. <rockstar> sinzui, I've been doing them in 20 project increments because it's so fucking tedious. <sinzui> rockstar: okay. reviewed some commercial projects, those that has test in their descriptions, <rockstar> sinzui, cool. I'm trying to get that backlog out so that gmb doesn't have that much to do. <sinzui> I was thinking of writing a script to send a license info email all "don't know" projects and mark them as reviewed <sinzui> I see 1/3 of projects need a license and all that we can do is ask for one an mark it reviewed <rockstar> sinzui, yeah, I was wondering if project review stuff was available through the API. I'd be happy to script it out if it was. <rockstar> Basically, does it have branding? Approve. Does it have a designated team as driver? Approve. Does it have branches or bugs or translations? Approve. <rockstar> That's what I've been doing. <sinzui> I approved all those this morning <sinzui> well all the obvious ones <sinzui> After I disabled or approved all 'test' projects, I approved all projects that had code, or bugs, or was creates by someone with a lot of karma, or was created by a canonical employee <sinzui> I cannot identify projects with branding or announcements :( <mwhudson> why do i have 300 emails to look through :( <sinzui> rockstar: I just tried a script that sent a variation of the license-info email to most the unreviewed undecided projects. 6 were skipped. I need to look at them to learn why <sinzui> oh, I see. It was right to script them. They were dual/multi-license. <thumper> mwhudson: when did you want to chat? <thumper> mwhudson: I'm down to 80 odd emails from 300 <mwhudson> thumper: now ish is good i guess <mwhudson> thumper: gimme a minute to refill my cup :-) <thumper> mwhudson: ok <thumper> mwhudson: I installed the gnome-desktop to try to debug some karmic issues <thumper> mwhudson: and it installed pulse audio <thumper> mwhudson: I need to work out how to kill it for kde <mwhudson> thumper: aaron posted advice to warthogs on that i think * mwhudson wonders why all the staging cronscripts are barfing <matgeek> Hi! <matgeek> Just new to launchpad development. I am interested in working on modular backend plugins. Git is really interesting to me, now that GNOME, the Linux kernel, and KDE are using it within their projects. It is the DCVS that has buy-in with all the development communities. Seamless integration is te name of the game. It would be good to be able to work on a project with the VCS that the project uses, with out having to know about <lifeless> matgeek: your paragraph was too long and IRC cut it off at 'to know about' <lifeless> matgeek: but have you seen bzr-git? it gives seamless git integration.. <matgeek> lifeless: So I don't have to know any bzr commands to work with the launchpad web interface? I can continue to use git as my development VCS without having to use bzr? <lifeless> matgeek: other way around, you can use bzr without having to know any git commands :) <thumper> matgeek: kinda, but Launchpad only supports bzr as a branch repository storage, and can mirror git repositories <matgeek> lifeless: That will not lead to buy-in from the development projects. I use git myself on top of svn, and I don't want to have to know about bzr. Is the launchpad - bzr backend based on a modular API? <matgeek> lifeless: that is if I was from GNOME, project or working on kernel. <matgeek> lifeless: hypothetical situation I know, but wanting to see if there is a case for making git another first class launchpad backend. <lifeless> if you want to use git and push to launchpad, there is a git-bzr too, I believe <matgeek> Mmmmm, I will have to explore further with my own Debian package, netscript-2.4 <lifeless> matgeek: the lp backend uses bzrlib, but bzrlib can talk to git, so in terms of /code/ it could be done. However we don't want the overhead of supporting many different VCS backends throughout the system <lifeless> how to scale storage, ensure consistent backups, etc all are very simple at the moment <matgeek> lifeless: From my POV, it doesn't matter what backend launchpad uses, as long as it is seamless with the VCS a project is using. <lifeless> I may not quite understand your criteria / rationale then <matgeek> lifeless: OK, I am coming from the hypothetical POV of being a project developer interacting with launchpad. It struck me that we want to get it to the point where everybody just wants to use it because it is so good. <matgeek> lifeless: Not knowing about bzr gets a big VCS elephant out of the room if you want a major project to actually start using launchpad itself. <lifeless> matgeek: so, you don't need to use the VCS services of launchpad to use launchpad <matgeek> lifeless: Yess, you just use the web frontend to point it at your project VCS of choice, the Web application uses bzr to get source trees etc, but the developers don't even have to type a bzr command, it is all transparent and just works! <lifeless> matgeek: we have that today <lifeless> https://help.launchpad.net/Code/Imports <matgeek> lifeless: Ta! I will have a play around with my Debian package. I am trying to come up with something useful for the launchpad project. Where can I help? <lifeless> thumper: ^ <lifeless> I'm not sure where the hotspots needing help are right now. thumper may. <thumper> lifeless: on a call right now, so I can't focus here right now <matgeek> thumper: I will hang around till you have finished your call, if you want to chat with me. * thumper is off the call and reading scroll-back <thumper> matgeek: what sort of help were you thinking about? <thumper> matgeek: developing features? fixing bugs? <thumper> matgeek: QA? <matgeek> thumper: fixing a few bugs at first to get familiar with the code base, and then looking at some minor features before getting into the major stuff. * thumper nods <thumper> ok <thumper> matgeek: firstly get on the beta tester team if you aren't already <thumper> matgeek: then get the code building locally <thumper> matgeek: then davidhull@example.net/launchpad-project <thumper> matgeek: there should be some easy ones tagged trival or easy <thumper> matgeek: the way we tend to work is: <thumper> 1) identify what to fix <thumper> 2) talk through the proposed fix with someone <thumper> 3) fix it <thumper> 4) submit the fix for merging, and go through the code review process <matgeek> thumper: Cool, I will need a day or two to get to the bug list, as I have to get some things done today. Are people on this channel in the evening NZ time? <thumper> matgeek: yes, where are you based? <matgeek> Dunedin. <thumper> matgeek: we should meet <thumper> matgeek: I'm in dunners too <thumper> matgeek: are you going to kiwipycon? <matgeek> That would be good. I am going to Earthlight this afternoon where I work on a Radius accounting project, using python. <matgeek> When and where is kiwipycon? Could we meet today or tomorrow, or later this week? <thumper> matgeek: you sent me an email the other week :) <thumper> matgeek: if you hadn't heard, it is a little late as kiwipycon is this weekend in Christchurch, and sold out <matgeek> Yes, I did email you. I have applied for a couple of Ubuntu positions already. <matgeek> thumper: About kiwipycon, a pity, but I can easily get accommodation up there with family. It is only a bus ride or drive. Are they full-house at the moment. <thumper> I believe so. <thumper> matgeek: you should also hang out in #nzpug <thumper> matgeek: also get on the launchpad-dev and launchpad-users mailing lists <matgeek> thumper: Will do. Will subscribe tonight. <thumper> ok <thumper> I'm not usually on at NZ evening <thumper> but the europeans are just starting <thumper> and there are quite a few of them :) <thumper> however, <thumper> I do respond to email :) (eventually) <jml> hello antipodes <MTecknology> jml: hi <MTecknology> if that includes me - long word <jml> MTecknology, only if you are in Australia or New Zealand, normally <MTecknology> jml: :( <MTecknology> well... then I take back my hi <mwhudson> jml: hello <mwhudson> jml: a very euro-centric definition of antipodes!! <jml> mwhudson, it's rather me-centric, actually <RAOF> jml: Hello antipodes! * wgrant whinges a bit about the lack of APAC RMs and Soyuz people. <thumper> wgrant: RM as in release manager? <thumper> wgrant: you wanting a release-critical stamp? <thumper> jml: hi <jml> thumper, RAOF: hello <thumper> I've finally booked my accomodation for kiwipycon <wgrant> thumper: RM as in release manager, yes. It's not quite that simple -- I have ~1200 lines of branches that we need in the next couple of weeks for Debian compatibility. It would only need to be CPed onto a couple of the Soyuz machines, but there are safe enum and other DB changes that the appservers need as well. <wgrant> The urgency of this only came to light two days ago, unfortunately. <mwhudson> wgrant: well at least the RM is noodles so he should understand the issues more easily than some <MTecknology> When is stu online? I want to ask him some questions....... <thumper> MTecknology: it depends <thumper> MTecknology: sometimes he is on in 3 to 4 hours, other times later <MTecknology> thumper: ok - I was trying to figure out how he's managing the branches - but now that I'm looking at last revision times; it seems like there's little point in worrying about it <wgrant> I think we are talking about different Stus here. <MTecknology> thumper: heck - if they need the branches - then they can do bzr push and it'll all be happy <MTecknology> stuart metcalfe <wgrant> You mean Stuart Metcalfe. <wgrant> thumper means stub. <MTecknology> oh <thumper> ah <thumper> sorry <thumper> misread stu as stub <MTecknology> So when is this version of stu normally around? <wgrant> His timezone suggests in about 9 hours. <wgrant> But he's not around here. <MTecknology> Where is he normally at? <wgrant> I've never seen him on freenode, I don't think. <wgrant> He lurks in the realms of ISD, I would imagine. <MTecknology> oh - so I guess it's only when I ask him that he comes around #launchpad-dev 2009-11-02 <mwhudson> Tear down canonical.testing.layers.TwistedAppServerLayer in 3 minutes 0.938 seconds. <mwhudson> this seems excessive :( <lifeless> probably swapped out <mwhudson> yeah <thumper> mwhudson: got a few minutes to talk about test strategy for a change I ahve <thumper> ? <mwhudson> thumper: sure <wgrant> As what DB user do the tests run by default? <mwhudson> wgrant: launchpad <wgrant> mwhudson: Ah. Thanks. <wgrant> Hm. * thumper gains even more dislike of the librarian for tests <wgrant> Because it takes FOREVER to start up, or something more sinister? <lifeless> singleton.slow. functional-not-unit. <mwhudson> or maybe because you have to commit all over the place when using it? <thumper> failed to shutdown in this instance <thumper> also for those other reasons, but in this particular time, for failing to die <mwhudson> that's a lot of reasons for hate between us <wgrant> There are more. * thumper EODs for dinner making <mwhudson> programming can be terrible some times <wgrant> What's going wrong? <mwhudson> oh just zope.interface crap <wgrant> Ah. <stub> The librarian could be mocked for many tests - the transaction rules are well documented and the interface simple. Nobody has bothered though (since it is a per test-run cost rather than a per-test cost?) <lifeless> stub: I think you mean stubbed (no pun intended) - Mocks are not suitable for keeping true to the transaction rules. * wgrant tries to remember the URL to that stubs vs. mocks. vs. fakes thing that was around a while ago. <lifeless> wgrant: all are test doubles; mocks assert a sequence of calls with seeded result values <wgrant> Ah. <wgrant> I can never remember which is which. <lifeless> stubs are generally limited functionality doubles that do stuff <lifeless> and fakes do even less <lifeless> anyhow, the rule to remember is 'mocks do not meet contracts' - each and every test has its own mock, or they aren't actually mocks. <lifeless> on the upside you can create a mock by decorating a realobject and recording the input/output sequence it sees. <lifeless> which can be a good way to make mocks, and with a little glue, turn them on/off on a per-run basis <lifeless> to let one validate that the mock hasn't altered test validity asynchronously. <mwhudson> it's on mumak.net somewhere i currently can't find <mwhudson> _so many_ places reference next_mirror_time :( <MTecknology> stub: hi <MTecknology> stub: we were just talking about you earlier <mwhudson> and mostly for lame, or at least non-intent revealing, reasons <stub> Talking about me for lame and non-intent revealing reasons? O_o <MTecknology> I decided I can either do more crappy documentation in the 30min I'll be awake, start reading an article I need to do a presentation on, tweak my bot some, install stumbleupon and use it, or..... do nothing.... Problem is that none of them sound appealing <MTecknology> stub: I was asking about stu and thumper thought I was talking about you. But then we did talk about you and I realized we like the same kind of ice cream <stub> stu flavoured ice cream? This is getting more dubious. <MTecknology> lol * mwhudson eods <wgrant> stub: Can you have a quick glance at http://pastebin.ubuntu.com/307257/ and tell me if i'm doing anything horrifyingly forbidden ? I'd really really like to get this in before 3.1.10, and need to discuss it with Soyuz people tonight. Basically, I need a way to restrict permissible source package formats by distroseries. This is it. <stub> wgrant: We normally use a integer/enum instead of a string where there is a fixed set of allowed options, and strings for free text. I suspect 'format' is not free text and should be an enum. <stub> wgrant: The table name sounds a little dubious, but that will shake out in discussions with soyuz. Is this table defining the formats that are allowed for a distroseries or the formats that have been used in a distroseries? <wgrant> stub: Right, I wondered about that. But to be consistent, that would mean migrating a column (sourcepackagerelease.dsc_format) from a string to an enum too. <wgrant> stub: It's the same scheme used for ComponentSelection and SectionSelection, but I will discuss it with Soyuz. It defines the formats allowed in a distroseries. <stub> We are inconsistent in many places - if you are correct, adding a comment in comments.sql is fine rather than migrating the column now. We can't be as agile with the DB schema as we are with Python. <stub> a string field might be fine in this case if it is 'whatever apt or tool x tells us' rather than some value Launchpad needs to actually understand. <wgrant> All values in that column should currently be identical, but it still sounds messy. <wgrant> It does have to be understood. <wgrant> At the moment there is only one valid value. After my branch, there will be three, defining different sets of allowed files in the sourcepackagerelease. <wgrant> The formats are defined by dpkg. <stub> So in general with the Python code we want to avoid "if format == '1.0'" and instead have "if format == PackageFormat.WHATEVER" <stub> If it turns out in discussion that a string is the right choice for this column, I'll want some vague justification. <stub> But no babies will die either way. <wgrant> What's the best way to do this? Define the DBEnumeratedType and then a dict mapping '1.0', '3.0 (quilt)' etc. to its items? Or does DBEnumeratedType have some builtin way to do this, like lazr.restful seems to use? <sridher> got an error to run > make schema <wgrant> sridher: Which error? <sridher> http://paste.ubuntu.com/307272/ <wgrant> sridher: Python 2.6 is not supported. <wgrant> sridher: Only 2.4 (and nearly 2.5, but it's not merged yet) at this point. <sridher> ok thank you sir <wgrant> sridher: Did you use the rocketfuel-setup script as described on https://dev.launchpad.net/Getting? <sridher> yes sir <sridher> i got error that "developer-dependency" package not found <wgrant> sridher: Which version of Ubuntu are you using? <sridher> karmic <wgrant> That should just work. <wgrant> Try running rocketfuel-setup again. <sridher> ok sir <sridher> Package `launchpad-developer-dependencies' is not installed and no info is available. <wgrant> apt-get update <sridher> ok <sridher> http://paste.ubuntu.com/307275/ <wgrant> sridher: You have the launchpad PPA enabled (probably in /etc/apt/sources.list.d/launchpad-dev.list)? <sridher> yes sir <wgrant> sridher: pastebin the output of 'apt-get update' <sridher> http://paste.ubuntu.com/307278/ <wgrant> I do not know what the problem is. <wgrant> Unless you are using something other than i386 or amd64. <sridher> iam amd64 <wgrant> What is in /etc/apt/sources.list.d/launchpad-dev.list? <sridher> deb http://ppa.launchpad.net/launchpad/ppa/ubuntu karmic main <sridher> deb http://ppa.launchpad.net/bzr/ppa/ubuntu karmic main <wgrant> That's fine. <sridher> is it work with python 2.4? <wgrant> sridher: Yes. I presume you modified your copy to use python2.6 manually? <wgrant> al-maisan: Morning. <al-maisan> good afternoon wgrant, how are things? <sridher> after getting an 2.4 error i changed /devel/Makefile version to 2.6 <wgrant> al-maisan: Not too bad. Just finishing off my v3 source format branch. One thing I came across in the tests was that the 'absolutely-anything' upload policy doesn't accept PPA uploads -- do you know if this is deliberate? I need it to for my tests, and enabling PPA uploads in it doesn't break other tests in lp.archiveuploader. <wgrant> But who knows what other tests might lurk elsewhere. <al-maisan> wgrant: I don't know off-hand but will take a look. <wgrant> al-maisan: (this branch recently became very important, as Debian has started uploading 3.0 (quilt) sources) <al-maisan> wgrant: gotcha. <al-maisan> wgrant: would the importance be diminished in any way of we sunc'ed lucid from testing as opposed from unstable? <al-maisan> s/of/if/ <wgrant> al-maisan: That would delay it by ten days at most, and with the current backlash it's unclear exactly what is going to happen to Lucid syncs. <al-maisan> wgrant: I see. <al-maisan> wgrant: re. the 'absolutely-anything' upload policy I find this snippet in AbstractUploadPolicy.rejectPPAUploads(): <al-maisan> """Reject uploads targeted to PPA. <al-maisan> We will only allow it on 'insecure' and 'buildd' policy because we <al-maisan> ensure the uploads are signed. <al-maisan> """ <al-maisan> wgrant: why would it be so important for PPA uploads to be signed? <wgrant> al-maisan: Seems like absolutely-anything (only used in tests) should be safe, however. <sridher> http://paste.ubuntu.com/307284/ <wgrant> al-maisan: I don't know. It works OK once I enable it in the policy, so the code is fine with unsigned uploads. <wgrant> There is some special signature treatment with PPA uploads (stripping signatures from stored .changes), but that seems to handle a lack of signature fine. <al-maisan> wgrant: if the policy in question is only used in tests then I guess "It's better to beg forgiveness than ask permission" applies ;) <wgrant> al-maisan: OK. Thanks. <noodles775> Morning <wgrant> Morning noodles775. <noodles775> Hi wgrant :) <wgrant> noodles775: Almighty RM, I need your advice. <noodles775> thumper: your branch is rc-approved... (just in case you didn't see the email). <noodles775> wgrant: for the v3sources? <wgrant> noodles775: Right. Debian has started uploading them, so it's pretty important no. <wgrant> +w <noodles775> yep, definitely. But it's also the kind of thing that I'd like to have tested on dogfood thoroughly before r-cing, which means it might be best as a CP... but bigjools will be around later... <wgrant> noodles775: The branches are pretty much done (save a conversion from a string to an enum in one place, which I'm finishing off now), but they're bigish. <wgrant> Right. <wgrant> But there are DB changes (safe) that are needed. <noodles775> He'll be able to check your branch on df... <noodles775> ouch <noodles775> btw: Thanks so much for gettin in there and fixing those! <wgrant> But assuming those get into 3.1.10, there are CPs required on Soyuz machines and appservers. <wgrant> Plus somebody needs to get the new dpkg on the buildds and Soyuz machines... not sure who to talk to about that. <wgrant> But lucid won't open for a few days, and the v3 packages can be survived without for a while, so that's not quite as critical as the DB changes. <noodles775> right. Have you got a branch with the db changes ready for review? <wgrant> Not on its own yet, as I need to convert a column to an enum. <wgrant> There is a new table, plus some new enum values on SourcePackageFileType that will cause appservers to explode if they don't know about them. <wgrant> appservers and builddmaster, that is. <noodles775> OK. So assign the db changes to stub+jml, bigjools can take a look when he's in and plan the best course of action. <wgrant> Will do. Thanks. <noodles775> Thank you! <wgrant> noodles775: Any recommendations for what to rename the table listing permitted formats by distroseries? I've currently called it SourceFormatSelection (because of ComponentSelection and SectionSelection), but I'm sure that's suboptimal. <noodles775> wgrant: re-name? <wgrant> noodles775: Well, to you it's just naming it. <noodles775> :) * noodles775 changed the topic of #launchpad-dev to: This is Launchpad Development Channel | Week 4 of 3.1.10 Release Critical - release manager is noodles775 (flacoste, BjornT)| I am Zero OOPS and So Can You! http://is.gd/4fkLl | PQM is OPEN | https://dev.launchpad.net/ | Get the code: https://dev.launchpad.net/Getting | On-call review in #launchpad-reviews | Use http://paste.ubuntu.com/ for pastes | This channel is logged: http://irclogs.ubuntu.com/ * noodles775 changed the topic of #launchpad-dev to: This is Launchpad Development Channel | Week 4 of 3.1.10 | PQM is release-critical Release Critical - release manager is noodles775 (flacoste, BjornT) | I am Zero OOPS and So Can You! http://is.gd/4fkLl | https://dev.launchpad.net/ | Get the code: https://dev.launchpad.net/Getting | On-call review in #launchpad-reviews | Use http://paste.ubuntu.com/ for pastes | This channel is logged: http://irclogs.ubuntu.com/ * noodles775 changed the topic of #launchpad-dev to: This is Launchpad Development Channel | Week 4 of 3.1.10 | PQM is release-critical only - release manager is noodles775 (flacoste, BjornT) | I am Zero OOPS and So Can You! http://is.gd/4fkLl | https://dev.launchpad.net/ | Get the code: https://dev.launchpad.net/Getting | On-call review in #launchpad-reviews | Use http://paste.ubuntu.com/ for pastes | This channel is logged: http://irclogs.ubuntu.com/ <noodles775> wgrant: SourceFormatSelection seems fine to me - if it's suboptimal, it's because of the other columns that you've based it on. The db reviewers will be in a better position to comment. <wgrant> noodles775: Well, stub said to ask Soyuz... <noodles775> wgrant: ah ok. so, as I said, SFSelection seems fine to me. bigjools will comment later I'm sure . <thumper> noodles775: ta <wgrant> What's the Storm equivalent of an EnumCol? <wgrant> StormMigrationGuide has that as an unanswered question down the bottom. <noodles775> wgrant: I haven't used it, but http://twistedmatrix.com/users/radix/storm-api/storm.properties.Enum.html <noodles775> gr, no, that's not a db enum. <wgrant> Looks like it is. <wgrant> I see it used for that purpose in PackageCopyRequest, with a utility to convert the DBET. <noodles775> Great. <wgrant> Thanks. <noodles775> np. <wgrant> noodles775: Looks like canonical.database.enumcol.DBEnum is what I actually want, as it supported DBETs directly. <noodles775> wgrant: good to know. <noodles775> wgrant: can you update the migration guide (if you haven't already). Thanks! <wgrant> noodles775: Will do. <adeuring> good morning <wgrant> Can I look up a DBItem given a DBEnumeratedType and the item's title? <al-maisan> Good morning adeuring <adeuring> hi al-maisan! <noodles775> wgrant: why not use the actual enum? Like PackagePublishingStatus.PENDING? (but you can do PackagePublishingStatus.getTermByToken('Pending') too?). <wgrant> noodles775: I need to convert a string representation of a format from the .dsc (eg. '3.0 (quilt)'). <wgrant> I'll try that. <noodles775> Great. <wgrant> I thought that would go the other way. <wgrant> Oh, woops. Was wondering why my enum was throwing strange SyntaxErrors. Then realised the names started with digits. <wgrant> FORMAT_1_0 rather than 1_0, perhaps? <bigjools> wgrant: good <insert time of day here>, I hear you're working on https://bugs.edge.launchpad.net/soyuz/+bug/293106 <mup> Bug #293106: does not support debian v3 source formats <feature> <motu> <ppa> <soyuz-upload> <Soyuz:In Progress by wgrant> <https://launchpad.net/bugs/293106> <wgrant> bigjools: Good morning. I am. Shall we discuss the plan? <bigjools> please do <bigjools> is it blocking anything in the distro that you know of? <bigjools> I assume some v3 packages need to be synced now? <wgrant> Not right now, but Lucid will open in a few days, and the first v3 packages have appeared in Debian. <wgrant> Then it will be blocking things, although not critically to start with. <wgrant> Now, the code is done and works. <bigjools> ok can this bump to the 3.1.11 milestone? <wgrant> I don't think it can. <bigjools> massive changes 2 days before a release make me very nervous <wgrant> However, if we get some safe bits in now, the rest can be CPed to Soyuz machines at your leisure. <bigjools> /o\ <bigjools> I love coming back from holidays! <wgrant> All that needs to be applied everywhere is a new table, a few new SourcePackageFileType values, a trivial function on DistroSeries, and four lines in CopyChecker. <bigjools> wgrant: what have you done to fix it? <wgrant> The big invasive changes are only needed on cesium, germanium and cocoplum. <bigjools> have you got a branch I can see? <wgrant> https://code.edge.launchpad.net/~wgrant/launchpad/distroseries-source-format-selection has it all. I'm just finishing off a change recommended by Stuart. <bigjools> and why can't it wait a month, do you expect a lot of v3 packages? <wgrant> I don't know. But distro people were eeking about it, and Lucid will freeze very early. <wgrant> I don't think anyone can say how many v3 packages will appear in the next month and a bit. <bigjools> is there a workaround to sync them if we can't upload v3? <wgrant> They should be convertible to 1.0 with a little effort, I guess. <bigjools> wgrant: why the new table? <wgrant> bigjools: To restrict which series can have the new formats. <bigjools> why is that needed? <bigjools> I don't know anything about the new format BTW :/ <wgrant> bigjools: Only >= karmic's dpkg supports the new formats. <bigjools> ok <wgrant> So the old chroots will be very unhappy (and maybe chrootwait; I'm not quite sure) <al-maisan> could we control the source format selection w/o a schema change, at least initially? <al-maisan> i.e. by a piece of python logic that ascertains "Only >= karmic's dpkg supports the new formats" <wgrant> You could hardcode the series name, I guess. <bigjools> ew <wgrant> Yes. <al-maisan> .. and clean up things in 3.1.11 <bigjools> I'm not sure what that would buy us, it's still an invasive change <al-maisan> no question about that <al-maisan> but we'd at least avoid "last minute" db schema changes <wgrant> Absolutely awful timing, I know, but Debian only revealed its intentions at the end of last week :( <bigjools> I am still -1 on this going in unless someone from distro steps in and says it must <wgrant> Right. <wgrant> I'm talking to them now. <bigjools> where "someone from distro" = cjwatson :) <bigjools> this is a 4k diff branch - that's just insane to put in at this stage <bigjools> err wait <bigjools> diff fail <wgrant> Last I checked it was 1.6klines <al-maisan> 1581 lines of diff <al-maisan> still a massive change <wgrant> And a tiny fraction of that is needed *right now*. <wgrant> But yes, it is big. <bigjools> ok now I am diffing against db-devel :) <wgrant> Ahaha. <wgrant> That would do it. <bigjools> wgrant: your sample data change changes the archive table, why? <wgrant> bigjools: external_archive_deps change wasn't in there previously. <bigjools> ah you can blame me for that <wgrant> Yup :P <wgrant> SourceFormatSelection is changing to an enum at the moment. <bigjools> you're removing the table? <wgrant> No. <wgrant> It's just going to use an enum rather than a string for the format. <bigjools> wgrant: from canonical.database.enumcol import DBEnum <wgrant> bigjools: By that I mean I'm rerunning the tests after completing the change. <bigjools> wgrant: what's different with the 3.0 format then? <wgrant> bigjools: New types of files. <wgrant> And massive incompatibility. <wgrant> And new compression formats. <wgrant> (although we're following dak and not supporting lzma, only gzip and bzip2, at cjwatson's direction) <bigjools> lzma dropped entirely? <bigjools> interesting <wgrant> Right. Trivial regex change to bring it back if we need to. <wgrant> (lzma deb support remains) <wgrant> Oh. Curses. SourcePackageFormat already exists. <wgrant> Any suggestions on what to call it? <bigjools> SourceUploadFormat? <wgrant> That's even more of a lie than the old SourcePackageFormat. <wgrant> It's a property of the source package, and nothing really to do with the upload. <bigjools> yeah * bigjools -> OTP <wgrant> OTP? <wgrant> This #ubuntu-devel is going to get messy! <wgrant> +discussion <wgrant> (my best idea is to rename the old SourcePackageFormat to SourcePackageType or something like that, as it is only mentioned on 7 lines, but I guess that would get me even more murdered than I will anyway) <bigjools> wgrant: ok back (On The Phone BTW) <wgrant> bigjools: Oh, right. <bigjools> wgrant: +1 on renaming SourcePackageFormat <wgrant> bigjools: Great, 'cause I've done it. <bigjools> heh <bigjools> SourcePackageType ? <wgrant> That's the one. <bigjools> perfecto <bigjools> one day we might even start using it for something useful and support RPM <wgrant> Perhaps. <wgrant> Hm. <wgrant> FS corruption. <wgrant> That is not good. <wgrant> (product.py started complaining of SyntaxErrors, when I hadn't touched it. it is now full of garbage) <wgrant> I wonder what else just got eaten. <bigjools> ext4? :) <wgrant> indeed. <wgrant> But the file size changed. <wgrant> So it's not the OMG KITTENS ARE DIEING BUT ONLY THREE PEOPLE HAVE REPORTED IT bug. <wgrant> bigjools: Can I safely raise an UploadError in one of NU's error generators if I want to reject the upload and stop right there, or do I have to move the check to another function? <bigjools> good question * wgrant traces it all the way up. <bigjools> suck it and see I guess <wgrant> Just this last failure case to handle... <bigjools> wgrant: EarlyReturnUploadError <wgrant> bigjools: Ah, handy. Thanks. <wgrant> (NU is too convoluted) <bigjools> no kidding <bigjools> it was refactored big-time a couple of years ago <wgrant> I recall. <wgrant> But that didn't get finished. <bigjools> and it improved things a lot, if you can beloeve that <wgrant> I cannot. <bigjools> :) <wgrant> Maybe I will revert the tree later and realise how lucky I am. <jml> ahh, nascentupload <wgrant> jml: You were privileged to be able to experience it before leaving engineering. <jml> wgrant, indeed. <jml> wgrant, I hope I made an improvement * wgrant isn't touching those bits. <wgrant> NU might not be so bad if it was properly tested, too. <deryck> Morning, all. <wgrant> bigjools: OK, it seems that most of the rest of my FS survived. I've just finished off that change. <bigjools> wgrant: most of? :) <wgrant> bigjools: Well, I've only found that one eaten file. All the packaged files check out fine, my branches are fine, and fsck is happy, so I presume most of it is OK. <wgrant> But it seems odd that there would be only file, given that I haven't written to it. <bigjools> yes <wgrant> bigjools: Broken sample data is currently being fixed :/ <bigjools> wgrant: what's broken? <wgrant> bigjools: There is a firefox-0.9.2.orig.tar.gz used in tests (note the '-' in place of '_'). That previously worked, as the type check just looked for endswith('.orig.tar.gz'). But now it uses a regex which needs a '_'. <bigjools> wgrant: this is in the data/suite/* stuff? <wgrant> bigjools: No, no. archiveuploader would never accept that. This is in a doctest that grabs an existing LFA and SPR.addFile()s. <bigjools> ah ok * wgrant directs significant volumes of hate at even more crackful sampledata. <leonardr> jml, you seem to know a lot about rickspencer3's whereabouts. do you know where in the world is rickspencer3 today? <jml> leonardr, if I had to guess, I'd say he's in the west coast of the continental united states of america. <leonardr> hmm <leonardr> i will hunt him down! <jml> leonardr, I only half-followed your recent conversation with al-maisan -- is exposing a dict over the API really that tricky? * al-maisan cocks up one ear <leonardr> jml: it's never been done before. making the lazr.restful changes to expose a dict should not be *that* difficult <leonardr> but al-maisan wanted to expose a dict _of lists_ <jml> leonardr, why is that important? <wgrant> Wasn't it a dict of Entries? <leonardr> al-maisan can correct be, but i believe it was a dict that mapped a person to a list of strings <jml> there are now two interesting branches of this conversation :) <jml> leonardr, isn't a dict of lists a fairly standard json construct? <al-maisan> leonardr: actually it was a dict {pocket : object } .. let me check again <jml> al-maisan, it was mapping a pocket enum to a branch object iirc. <al-maisan> that would be right <leonardr> i don't remember this. i remember people mapped to the types of reviews they'd been assigned to <leonardr> anyway, the problem is that the arguments to a named operation have to be described in wadl, and recursively defined data types are difficult to define in wadl <jml> leonardr, ahh, I see. <leonardr> a recursively defined data type is a sign that things are getting too complicated and you should rethink your resource design <jml> leonardr, I can see the point <wgrant> Ahhhh. Tests pass a little better when one of the data files used in a few tests *hasn't* been corrupted by a stupid filesystem. <jml> as much as I like "for your own good"-style design. <jml> *dislike* <jml> (one of them Freudian mothers) <al-maisan> leonardr, jml: this is what I was trying at that time: http://pastebin.ubuntu.com/300148/ <leonardr> jml: what i've said is kind of seat-of-pants stuff. my knowledge of that part of lazr.restful is cached on disk. <jml> leonardr, heh <leonardr> somewhat literally, in that i would have to go into the code and re-learn it <al-maisan> leonardr: : so, the problematic part in this case was the return type of the collection returned. <al-maisan> anyway, since that did not work I resorted to: https://code.edge.launchpad.net/~al-maisan/launchpad/352094 <jml> leonardr, I know the feeling. <mpt> What's a "package set"? <mpt> I see <https://dev.launchpad.net/Soyuz/Specs/PackagesetsAndDistroseries> and <https://dev.launchpad.net/Soyuz/Specs/PackagesetsAndDistroseries/OriginalAnalysis>, but they don't seem to mention what a package set is <al-maisan> mpt: https://dev.launchpad.net/VersionThreeDotO/Soyuz/StoryCards#packagesetacl <mpt> ahh, security <mpt> thanks al-maisan <al-maisan> you are welcome :) <Ursinha> hey bigjools-lunch :) can you tell me what's exactly the meaning of the pending milestone you have in soyuz? after getting back from lunch, of course :P <bigjools> Ursinha: one word: "Celso" <Ursinha> bigjools, oh crap <Ursinha> bigjools, but do you know his rationale behind it? <bigjools> Ursinha: it was a place for him to put stuff he didn't want to forget about <Ursinha> bigjools, I see <Ursinha> bigjools, you're not using it? <bigjools> and it turned into a general pool of bugs that we need to sort out <bigjools> sort of <Ursinha> bigjools, I see <Ursinha> bigjools, I asked because I have some bugs that are depending on others to be fixed, not our bugs, and as we don't have a Pending status I considered using a Pending milestone <bigjools> Ursinha: as you know, things have changed focus recently so it's fallen to the side a little. But its general concept will be re-used for LP generally soon. <bigjools> ah <bigjools> go for it <Ursinha> cool <Ursinha> thanks bigjools :) <bigjools> any time <gary_poster> bigjools: hi! I have this on my QA page from Francis. Am I right that I can push it over to your guys' page? "r9807 [r=adeuring][ui=none][bug=458833] Protect Build attributes using launchpad.Edit. (Landed on behalf of Julian.)" <bigjools> gary_poster: yes please do <gary_poster> bigjools: cool thanks <bigjools> gary_poster: are you going to stick it on my QA wiki page? <gary_poster> bigjools: sorry yes. Trying to reply to mthaddon on a nother channel then was going to do that. If you want to do it before me, feel free. ;-) <bigjools> gary_poster: yeah I can do that, what's your test plan URL? <gary_poster> bigjools: thanks https://dev.launchpad.net/FoundationsTestPlan/3.1.10 <bigjools> shoulda guessed that really :) <gary_poster> :-) <bigjools> gary_poster: umm release yer edit lock :) <gary_poster> bigjools: sorry done <bigjools> ta <bigjools> done <wgrant> bigjools: Have you a definitive answer from cjwatson? <bigjools> wgrant: not definitive, but there's no clear requirement that I can see for putting this in 3.1.10 <bigjools> wgrant: if the default dpkg format changes then he points out that we're fucked <wgrant> bigjools: Right. And that was planned to happen. <wgrant> But might not be any more... hard to tell. <sinzui> bac: EdwinGrubbs: barry: I was able to test the product-release-finder. 1 bug is fixed, the other is not. I am going to work on the bad item <bigjools> wgrant: did stub review your db changes <wgrant> bigjools: He commented that the table name was a bit odd, but that it was a Soyuz decision, and also that it should use an enum rather than a string. <wgrant> The latter is done, and you seem fine with the former. <bigjools> wgrant: yeah it follows some convention I guess <bigjools> wgrant: so I am thinking that we should land the schema changes only, in case the brown smelly stuff hits the fan this month <wgrant> The cut down (that is, without the big archiveuploader changes) diff (excluding sample data) is ~500 lines. <barry> sinzui: cool <bigjools> wgrant: we don't even need that, we can just land the sql patch on db-devel <bigjools> that's the thing that would stop a CP if it came to that, so this increases our options <wgrant> True. <bigjools> so if you can make a separate branch with that, create an MP, get jml and stub to review it, I'll land it for you <bac> sinzui, barry: here are the portlets called on the distroseries page: http://pastebin.ubuntu.com/307675/ <bac> sinzui, barry: for karmic, all render but the third one: https://edge.launchpad.net/ubuntu/karmic/@@+table-milestones <sinzui> bac: I bet it is the status counts for bugs and blueprints <sinzui> bac: barry: The counts are a loop in python, Maybe the code can be made faster, or we can change the model to provide the summary. I prefer the first option because the code is also used to count assignees <sinzui> ps. you rock bac <Ursinha> hi sinzui, about the BAD items, I see you're working on bug 415595. do you know about the others? <mup> Bug #415595: Product release finder should import all files <story-product-release-finder> <Launchpad Registry:In Progress by sinzui> <https://launchpad.net/bugs/415595> <sinzui> We are working on all bad items * sinzui has a fix for Bug #415595 <mup> Bug #415595: Product release finder should import all files <story-product-release-finder> <Launchpad Registry:In Progress by sinzui> <https://launchpad.net/bugs/415595> <Ursinha> sinzui, right! in your opinion, any of these are release blockers? <kfogel> http://paste.ubuntu.com/307767/ <kfogel> anyone know why my rocketfuel-get is failing as per above paste? <barry> sinzui: i'm back now; what can i look at? <kfogel> "bzrlib.errors.BzrError: xmlrpc protocol error connecting to https://xmlrpc.edge.launchpad.net/bazaar/: 502 Bad Gateway" ? <sinzui> Ursinha: I think the timeouts on distroseries defintely are <sinzui> Ursinha: the release finder could slip <Ursinha> sinzui, right <sinzui> The bad CSS must be fixed or we can revert the entire branch <kfogel> jml: curious if you recognize the error (see my paste a few lines above) <jml> kfogel, it rings a bell. are you behind a proxy? <kfogel> jml: indeed I am. But I could easily not be. <jml> kfogel, try that. <Ursinha> sinzui, are you working in the old bug numbers or have you opened new ones? <Ursinha> by you I mean registry team <sinzui> Ursinha: I reopened the old because because our changes do not represent a partial fix <bac> barry: ping <barry> bac: pong <Ursinha> sinzui, and the others? <sinzui> I am testing the one that I can test. <sinzui> Ursinha: I do not know how to test salgado's change. I am not even sure it is a regisrty issue <sinzui> barry: ping <Ursinha> sinzui, actually I'm talking about the BAD items you say registry team is working on. I see you reopened the bug of yours, want to know about the others :) <sinzui> They are inprogress I think <barry> sinzui: pong <sinzui> Ursinha: https://edge.launchpad.net/launchpad-registry/+milestone/3.1.10 <sinzui> ^ sort by status * Ursinha looks <sinzui> barry: I was going to ask for you help with new member + mailing list tests, but I get an oops with my test candidate: https://staging.launchpad.net/~haibunku <Ursinha> thanks sinzui <barry> sinzui: that oops looks related to my team privacy portlet change <sinzui> yes <barry> sinzui: like. some code didn't get updated perhaps? <sinzui> but I saw your style fix on edge it it worked <barry> sinzui: does it work in lp.dev? <barry> (i should try it) <sinzui> barry: staging is borked <barry> sinzui: gotcha <sinzui> barry: db-deel has the right template, but not the right view <sinzui> barry: did you land the fix in two branches? * sinzui sees the visibility_portlet_class in devel but not db-devel <kfogel_> jml: urgk. this one ring a bell to you? http://paste.ubuntu.com/307835/ "bzrlib.errors.BzrCheckError: Internal check failed: Cannot add revision(s) to repository: missing chk node(s) for parent_id_basename_to_file_id maps" (I've gotten out from behind the proxy now.) <barry> sinzui: i don't think so. i had two bugs each with a branch but that particular feature should have landed in one branch <barry> sinzui: oh, that's sick <jml> kfogel_, umm, no, sorry. <jml> kfogel_, that's #bzr territory <barry> sinzui: i'm grabbing db-devel now <sinzui> barry: ../db-devel/lib/lp/registry/browser/person.py line 3248 should be our missing method <barry> sinzui: how did registry/templates/team-index.py get the change but not browser/person.py? <barry> sinzui: oh wait <sinzui> barry: gremlins from the kremlin? Aliens for Mars? The Illuminati? <barry> sinzui: db-devel's team-index.pt did not get the change <sinzui> oh, I revered the issue? <kfogel_> jml: thought probably -- but you did so well with the last question that I wanted to ask :)-. <barry> sinzui: i just bzr-tool-grep'd db-devel. there's no visibility_portlet_class in the code at all <barry> sinzui: so, wtf is staging running?! <Ursinha> hi noodles775, are you there? <Ursinha> hmm, no <Ursinha> is it just me or edge is really slow? <rockstar> Ursinha, I've noticed it's really slow as well. <Ursinha> rockstar, maybe we should poke a losa <rockstar> Ursinha, yeah, maybe. Forking to do that is not something I have bandwidth for right now though. <Ursinha> hehe <Ursinha> mbarnett, hey <mbarnett> Ursinha: heya <mbarnett> Ursinha: we are in the midst of a rolling update <mbarnett> Ursinha: which is why edge is a bit slow <Ursinha> mbarnett, oic <Ursinha> rockstar, ^ <Ursinha> mbarnett, for how long will it be like this? <mbarnett> Ursinha: i'll check on the progress <Ursinha> mbarnett, cool <beuno> barry, can you think of any reason why we wouldn't want to expose what mailing lists people are subscribed to on ther profiles? <Chex> Ursinha: sorry, one of the edge workers was slow to come up, should be OK now, let me know if it isn't? <mbarnett> what he said! <barry> beuno: for public lists? i think it would be interesting to know that <Ursinha> sure mbarnett and Chex <Ursinha> thanks both <Ursinha> :) <beuno> barry, perfect answer <barry> beuno: facepad! <thumper> why has no-one booted buildbot into touch? <thumper> the db_devel builder is still fubared <thumper> and we're in testfix because of it <thumper> it has been over 12 hours!!!!!! <beuno> barry, don't reveal my secret plan! <barry> beuno: as long as it's not spacepad :) <beuno> barry, do we store ML messages on the db at all? <barry> beuno: in general, no. we only store ones that are held for moderation <jml> thumper, hi <thumper> jml: hi <beuno> barry, how complicated would it be to store subjects and authors? <jml> thumper, up for a skype call? <thumper> jml: how long do you need? <thumper> jml: have normal stand up soon <jml> thumper, ~30 mins. When's your standup? <thumper> in 10 minutes <barry> beuno: you'd probably also want message-ids. i think not complicated, but i don't know how expensive it would be (performance- or space- wise) <beuno> barry, and date :) <barry> beuno: you probably just want to store successfully posted messages, so you'd need to hook into that process, but i think not hard to do <barry> beuno: yep <beuno> barry, so we could tell people what kind of traffic a ML has, and what the latest messages where <beuno> barry, secondly, are there any good proprietary archiving softwares? (you've said there aren't any open ones) <barry> beuno: well, if you did that, you'd /have/ to give them links to those messages. /me remembers our last conversation <jml> thumper, is after the standup ok? <thumper> jml: yeah, I think so <barry> beuno: i'm not familiar with any commercial archivers <jml> thumper, cool. can you ping me please? <thumper> yep <beuno> barry, ok, thanks <mwhudson> morning <james_w> morning mwhudson <james_w> mwhudson: thanks for your work on branch-distro.py <mwhudson> james_w: np, is everything working ok for you? <james_w> seems to be fine <mwhudson> cool! <thumper> rockstar: want to host? <rockstar> thumper, sure. <rockstar> mwhudson, abentley, skype? <mwhudson> rockstar: yep <Ursinha> hello gary_poster, could you triage bug 423447, please? <mup> Bug #423447: Trying to add an email that's already registered as a SSO account but not a person, oopses <oops> <Launchpad Foundations:New> <https://launchpad.net/bugs/423447> <gary_poster> Ursinha: a bit busy on buildbot right now <Ursinha> ok gary_poster, no problem <thumper> jml: ready <jml> thumper, oh sorry <gary_poster> Ursinha: triaged <Ursinha> gary_poster, thank you <maxb> gary_poster: Hi! Good news: ztk-2.5 still fine as of my weekend re-test. Bad news: There's a new test, xx-resetpassword-for-sso-account.txt, on devel that *requires* canonical-identity-provider to pass - bit of a downer for me! <maxb> (sorry to pick on you, but salgado isn't here, and it was [r=gary] :-) ) <gary_poster> maxb: heh and urg <maxb> Let me know if you'd like it filed as a bug <gary_poster> maxb: I'm swamped ATM. Make a bug for me, and I'll assign it? Yes please <maxb> Filed as bug 471724 <mup> Bug #471724: Test lib/lp/registry/tests/../stories/foaf/xx-resetpassword-of-sso-account.txt fails if canonical-identity-provider absent <Launchpad Foundations:New> <https://launchpad.net/bugs/471724> <wgrant> jml: Can you please review https://code.launchpad.net/~wgrant/launchpad/distroseries-source-format-selection-db/+merge/14304? <jml> wgrant, will do. <jml> wgrant, if not tonight, first thing tomorrow <wgrant> jml: Thanks. <jml> wgrant, np <mars> silly question: do we still use the lpwindmill.py script for windmill test authoring? <mars> if so, where may I find the documentation on the wiki? <mars> rockstar, if you are still around: have you written any windmill tests recently? <rockstar> mars, I've ported some, am probably going to write some before the sprint, why? <mars> rockstar, I've been trying to test the YUI 3 upgrade, and was going to run the windmill suite. However, I can't run windmill, or start the test authoring tools <rockstar> mars, how are you doing it? <mars> and I can't find anything about writing windmill tests on the wiki <rockstar> mars, I think we need to update them. <mars> rockstar, $ bin/py lib/lp/scripts/utilities/lpwindmill.py firefox http://launchpad.dev:8085 <rockstar> mars, if you'd like, I can call you and get you up to speed on the new way of running windmill. <rockstar> mars, yeah, it's changed recently. <mars> rockstar, that's ok, I don't have skype. Windmill starts using bin/test, but I'm wondering about authoring <mars> ok <rockstar> mars, no idea how to use the authoring tools. I've never used them. <mars> rockstar, how did you write windmill tests in the past? <rockstar> mars, vim <mars> rockstar, I mean, did you use the lpwindmill script to set up a test server on port 8085, then start poking at the DOM with the windmill interface? <rockstar> mars, no, I just had my dev server and firebug, and would write the test, run it, fix it, etc. <mars> ok <mars> rockstar, after upgraded to Karmic, I'm getting SSL errors when I try to run the windmill suite. It looks like the bin/test suite is not using port 8085, at least, not to log into the site <rockstar> mars, turn off your dev server when you run the tests. <rockstar> Windmill and the dev server have never really played well. <mars> I thought we fixed that :( <thumper> mwhudson: what do you need to qa your last two items? <rockstar> mars, not that I've ever seen. <mars> I'll try again, doubly sure <mwhudson> thumper: oh i did one <mwhudson> thumper: and the other i need some queries running i guess <mars> "Error in sys.excepthook:" oops. <mars> :) <wgrant> Can I access the API anonymously yet without patching waddlib to use the browser-accessible root? <mars> wgrant, you used the word "yet" - have you heard of a plan to allow such access? <mars> just curious <mars> I've been away for a while <rockstar> wgrant, I'm not aware
{'channel': 'launchpad-dev', 'month': 11}