/srv/irclogs.ubuntu.com/2005/12/27/#launchpad.txt

spivmdke: pong12:08
mdkespiv, oh great, hi.12:09
mdkespiv, we would like to get hold of a list of email addresses of users who have accounts on the wiki. how hard is that going to be?12:10
spivAs in, a list of email addresses of users that have ever logged in to the wiki?12:10
mdkespiv, well ideally, those who have ever edited the wiki, but I think we'd settle for logged in12:11
spivHmm.12:11
mdkein normal moin i guess it wouldn't be very hard12:11
mdkebut i don't know what the user database looks like on our moin12:12
spivWell, the changes to our moin aren't that big.12:12
spivIt's basically a two-step process:12:12
mdkeso some kind of search script for /data/user/* would do the trick?12:12
spiv  1) extract a list of user IDs from the moin files12:13
spiv  2) query the launchpad database for the email addresses for those users12:13
mdkeok, so maybe not too bad?12:13
spivFor step 1, you could even trawl through the history of all edits to narrow it down to people that have edited the wiki, but that's more work than just grabbing the id of every user file :)12:14
mdkeyeah the id way works for me12:14
mdkespiv, do you have any idea how long something like that would take to write for one of you super geek guys?12:15
spivWe'll need an admin to do step 1, I don't have access to the wiki data files (although I can help by writing a script for them to run)12:15
mdkethe admin thing shouldn't be a problem12:16
mdkeit's just a question of getting the script written12:16
spivNot very long, let me remind myself what the data files look like :)12:16
=== SteveA [n=steve@195.182.78.95] has joined #launchpad
=== bradb_ [n=bradb@modemcable033.209-70-69.mc.videotron.ca] has joined #launchpad
=== Nafallo is now known as Nafallo_away
=== mdke_ [n=matt@ubuntu/member/mdke] has joined #launchpad
mdke_spiv, sorry, may have missed anything you said since "remind myself what the data files look like", got disconnected12:25
spivmdke_: You didn't miss anything.12:25
mdke_ah cool12:25
=== mdke_ is now known as mdke
spivThe script for the admins to run is easy, though: "ls 12:25
spivbah,12:25
spiv"ls $moin_user_dir" :)12:26
spivmdke: Do you just need this as a once-off?12:26
mdkeyup12:27
mdkewe can work out the exact details with elmo another time12:27
mdkei just wanted to find out how hard/easy it would be12:27
mdkespiv, is stage (2) quite easy too?12:29
spivmdke: Yeah, just a simple matter of SQL.12:29
mdke:)12:30
mdkespiv, ok great, thanks for your time12:30
=== doko [n=doko@dslb-084-059-078-192.pools.arcor-ip.net] has joined #launchpad
dokobradb: ping01:15
bradbdoko: hi01:15
dokosorry, I strongly disagree on #388201:16
bradbdoko: Why?01:17
dokothe whole distro team does work this way: work on one aspect on one package, and then go on to the next one. If I have to subscribe to each package I apply a fix ... that's just administration effort01:17
bradbdoko: You don't have this feature in Bugzilla, AIUI, right?01:18
dokobugzilla is not the measure01:18
=== SteveA [n=steve@195.182.78.95] has joined #launchpad
dokoif I look at debian, they some kind of this feature implemented. it's not just a malone thing. it's about tracking of an upload you make, and taking responsibilty about it. currently I have to poll many different sources for this information:01:20
bradbdoko: I'm not saying your suggestion is a bad one, only that you're the only person I've heard ask for it and, IMHO, it would add more complexity than benefit.01:21
dokopeople.ubuntu.com/~lamont/buildLogs, bugzilla/malone, anastacia output, colin's dapper-probs, etc ...01:21
bradbdoko: How would Malone know when to subscribe you? Can it make these kinds of assumptions for every upload done to Malone? How would it know when to unsubscribe you?01:22
dokobradb: because everybody just polls this information, which seems to be a ridicoulous waste of resources. 01:23
bradbdoko: Okay, let's walk through this. First question: how would Malone know when to subscribe you to all bugmail for a package?01:24
lifelessSteveA: ping01:24
dokobradb: launchpad should know about the uploader field, so that is the information you need. for unsubscription: either unsubscribe when somebody else uploads the package, or terminate the subscribte after some fixed time01:24
dokobradb: subscribe: when somebody makes an upload01:24
bradbdoko: Would that assumption be a helpful one for the majority of cases?01:25
dokowhere upload is: upload signed by this person (which probably will not cover sponsored uploads, I'll have to check this)01:26
lifelessspiv: ping01:26
dokobradb: yes, manual uploads are usually signed by the people who work on the packages. exceptions are syncs from unstable and sponsored packages01:27
bradbdoko: Okay, so will most developers want to start getting bugmail from packages at the moment they do an upload of that package?01:28
dokowe surely can formalize syncs from unstable. for sponsored uploads, we could maybe subscribe the sponsor (uploader) and the person in the changelog01:29
dokobradb: yes, I think that would be helpful. that would elminate the work done by a bug master (currently mdz) assigning bugs to members of the distro team01:30
dokobugs are one aspect, but this kind of sbscription feature should cover all other information related to a package01:31
bradbdoko: And will it be the most helpful option to have Malone unsubscribe developers as pkg bug contacts automatically when someone else does an upload of their package?01:31
bradbs/their/the/01:32
dokobradb: that's one point to discuss. I'm not sure about it. I surely do not want to last the subscription forever. therefore the proposal to terminate the subscription after some time, or terminate it after the next upload done by another person01:33
bradbdoko: What if the person were actually a pkg bug contact by choice as well?01:34
dokothen the point of contact has priority01:34
bradbThis is the kind of complexity to which I'm referring?01:34
bradber, s/\?/:)/01:35
bradbFrom this other questions fall out about the complexity: can a user turn this off? If so, how? How do we communicate clearly to the developer why they suddenly started getting bugmail, and also somehow let them know that it won't continue forever, and don't-worry-we'll-auto-unsubscribe-you-soon-enough, etc?01:36
dokoI know ... please see it from my side. currently I have to poll several sources of information for each package I touch. a) that's work which can be automated b) if I forget/make mistakes, nobody will notice (at least for some time)01:36
=== lifeless raises the spec flag
dokos/user/developer/01:36
bradbdoko: I agree fully with you that wasting your time is bad.01:37
spivlifeless: pong01:37
lifelessthis may be more effective if a spec with use cases is worked through01:37
lifelessthat will make clear whats involved, and let other folk put in feedback, whereas IRC conversation is markedly opaque01:37
lifelessspiv: yoyoyo01:37
lifelessspiv: in DB interfaces01:37
lifelessare related things like 'owner' normally presented as the object or as the underlying db type.01:38
lifelessi.e. in IFoo01:38
dokolifeless: agreed, but IMO there are use cases in the report. I'm just happy about the status change for needinfo->rejected01:38
lifelessif there is an 'owner', and I have something implementing IFoo, would we expect thing.owner to be an 'int' or a 'IPerson'01:38
spivlifeless: The object.  So 'owner' would typically be something providing IPerson, for instance.01:38
lifeless+    owner = Int(01:39
lifeless> +        title=_('Owner'), required=True, readonly=True)01:39
lifelessso that looks wrong to you?01:39
spivYep01:39
spivShould be a ForeignKey.01:39
lifelessyay01:39
dokobradb: I agree that it would be not a minor change to malone/launchpad. should we make this discussion on a mailing list as well?01:39
spivOh, interface.01:39
spivBut yeah, not Int :)01:39
bradbdoko: Sure.01:40
bradbdoko: Do you want me to forward the information somewhere, and where would you prefer to have the discussion take place? (I'm not sub'd on any Ubuntu lists, FWIW.)01:40
dokobradb: I think ubuntu-devel would be appropriate, let's prepare that mail, it's not that urgent. start of January should be fine01:42
spivlifeless: Look at IBugSubscription, for instance01:42
lifelessspiv: its ok01:42
lifelessspiv: I needed to check the expected state, not the 'occuring state'01:42
bradbdoko: Can non-subs post to that list?01:42
lifelessspiv: which is why the source wasn't good enough ;)01:42
lifelessspiv: thanks !01:43
dokobradb: if jdub takes care of these post, yes. so better subscribe ;-)01:43
spivlifeless: Well, IBugSubscription's person attribute looks like what I expect :)01:43
lifelessthanks01:44
dokos/post/posts/01:44
bradbdoko: Hm, I'd rather not subscribe to the list just to get mail about this one thread. I wonder if you'd be happy with this solution: 1. I move the bug report back to "New", 2. You mail ubuntu-devel asking for input on the feature request and Cc me. Is that reasonable?01:47
lifelessspiv: IBugSubscription exposes the bug number rather than the bug.01:47
lifelessspiv: that seems wrong to me.01:47
lifelessspiv: going off what we just discussed01:48
lifelessspiv: while I have your attention, is exposing the 'id' de rigeur ?01:48
dokobradb: ok. I'll prepare an email. let us polish that email until we agree on the points we disagree01:48
spivlifeless: Hmm, there is a BugVocabulary, but it appears to be unused.  I wonder why.01:50
bradbdoko: Sure. BTW, it's not that I "disagree" with your time being important and that Malone should help reduce your development burden as much as possible, only that adding this feature would add a lot more complexity than benefit for most users, IMHO. But, I look forward to enlightenment from your email. ;)01:50
spiv(I guess because Int works well enough...)01:51
=== thierry [n=thierry@modemcable084.72-131-66.mc.videotron.ca] has joined #launchpad
lifelessspiv: well it applies force on IBug to show the db id01:52
lifelessspiv: as we are punning the number and db id01:52
lifelessspiv: anyway, is showing the 'id' usual ?01:52
lifelessor is it explicitly thought through each time ?01:53
spivlifeless: To be honest, I'm not sure.01:53
lifelessok01:54
spivAnd a quick survey of the existing code gives inconsistent results ;001:54
bradbdoko: I marked the bug as "New" again, btw. Thanks for your feedback, and I'm looking forward to hearing what u-d says about it.01:54
spivbradb: mailman allows you to "subscribe", but mark your subscription as "no mail".01:55
bradbspiv: Indeed. How would that help here?01:55
spivbradb: So you can post unrestricted, without being flooded with mail.01:55
bradbAh, ok, good point.01:55
bradbI think doko will do the best job of selling his feature request to u-d.01:57
spivFair enough.01:58
bradblifeless: BTW, my code has spent all day in the #1 spot in pqm by now. It seems like the 40 min estimate earlier may have been optimistic.01:59
bradbEr, "upwards of 40 minutes or more", but that was two and a half hours ago. :)02:00
lifelessbradb: I said upwards for a reason02:00
lifelessbradb: this is what sftp push in bzr does at the moment02:01
lifelessbradb: its extremely inefficient02:01
bradbright02:03
bradbFWIW, I hate whining about pqm and I'm mostly surely a pest about it, but I dislike even more not being able to do my job.02:04
lifelessright02:09
lifelessso right now, how is it blocking you ?02:09
bradblifeless: I need to get at the most recent code in Launchpad to fix the tests and conflicts in my bug status changes branch. I could do a sideways merge, but you said earlier that I can't necessarily trust that.02:14
lifelessbradb: I suggested you do one02:14
lifelessbradb: the trust is whether pqm succeeds in its push or not02:15
bradbOk, I'll do one tomorrow if for some reason I still don't have access to that revision in my usually rsync launchpad-upstream => local merge workflow.02:17
bradbIt's all literally blocking me in the sense that if I'd done that and submitted it immediately after seeing that all the tests pass, it'd still be #3 in pqm's queue right now. This two patches I'm getting through right now are kind of particularly critical to land before causing painful conflicts in almost any other Malone changes.02:19
lifelessunfortunately I cannot make it faster02:19
lifelessthis is where the tech is at at this point02:19
lifelessthe bzr group are working very hard to get improvements in place.02:19
jameshbradb: I'll update my bugzilla default assignees migration script to work with the initial-bug-contacts stuff02:21
bradbjamesh: Ok, great, thanks.02:22
=== kjcole [n=kjcole@pchb1f.gallaudet.edu] has joined #launchpad
=== bradb heads off, later
=== bradb [n=bradb@modemcable033.209-70-69.mc.videotron.ca] has left #launchpad []
jblackDid you guys see http://geekz.co.uk/lovesraymond/archive/clique? 02:26
eruinshuttleworth foundation empire03:36
eruin;)03:36
=== sevrin [n=sevrin@202.75.186.154] has joined #launchpad
=== stub [i=stub@sweep.bur.st] has joined #launchpad
=== robitaille [n=robitail@ubuntu/member/robitaille] has joined #launchpad
=== robitaille [n=robitail@ubuntu/member/robitaille] has joined #launchpad
jblackjamesh: ping06:30
jameshjblack: pong06:30
jblackI think your http://people.ubuntu.com/~jamesh/bzr.smallfixes  branch may be borked06:30
jameshjblack: oh?06:30
jblackbzrlib.errors.MissingText: Branch http://people.ubuntu.com/~jamesh/bzr.smallfixes is missing revision robertc@robertcollins.net-20050919060519-f582f62146b0b458 of cacheremoterevisions.diff-20050615041652-ec41056afda8ec1106:31
jameshthat's unfortunate06:31
jblackohhh....06:31
jblackorrr..06:31
jblackthe supermirror bzr may be too old06:31
jameshI don't think there are any unmerged revisions in that branch though06:31
jblacks06:31
jblackNope.06:44
jblackThat won't do it.06:44
jblackjamesh: Can you branch yourself? 06:44
=== jamesh tries
jameshjblack: "bzr branch" seems to work with my local copy of the branch06:45
=== jblack tries starting over.
jameshjblack: I'm just pushing the branch again06:47
jameshmy local copy includes some extra revisions I'd pulled from bzr.dev06:47
jameshfinished pushing06:49
jblackthanks06:50
jblackjamesh: I think you may need to reweave your branch07:07
jblackWhich I can provide instructions for07:08
=== ubuntulog [n=ubuntulo@port49.ds1-van.adsl.cybercity.dk] has joined #launchpad
=== Topic for #launchpad: launchpad.net | developer meeting: Thur 22 Dec, 1200UTC (wiki:MeetingAgenda) | launchpad-users@lists.canonical.com (wiki:MailingLists) | Channel logs are here: http://tinyurl.com/72w39
=== Topic (#launchpad): set by lifeless at Tue Dec 20 07:52:46 2005
(SteveA/#launchpad) although, there are other forms for multiple men or men and women, and for multiple women09:25
(sivang/#launchpad) eh, niec09:25
(sivang/#launchpad) *nice09:25
(lifeless/#launchpad) thats getting seriously kinky09:26
(sivang/#launchpad) lifeless: lol :)09:26
=== eruin [n=eruin@unaffiliated/eruin] has joined #launchpad
sivangSteveA: seems that Lithuanian is very specific language09:28
lifelessSteveA: were you pinging or just wasving ?09:32
SteveAlifeless: you pinged earlier, when i was asleep09:43
=== tuhl [n=tuhl@p5498D893.dip.t-dialin.net] has joined #launchpad
lifelessmmm, did I09:47
lifelessoh right09:47
lifelessstyle for interfaces. spiv helped me09:47
=== carlos [n=carlos@23.Red-83-55-110.dynamicIP.rima-tde.net] has joined #launchpad
carlosmorning10:08
sivangcarlos: Hola10:08
carlossivang, hola!10:08
=== fabbione [n=fabbione@port49.ds1-van.adsl.cybercity.dk] has joined #launchpad
=== jinty [n=jinty@205.134.224.215] has joined #launchpad
=== lamont [n=lamont@mix.mmjgroup.com] has joined #launchpad
SteveAsivang: for example if you're greeting a group of young women, "sveikos panels!" would be "hello girls!" 10:27
=== mdke writes that down
SteveAi meant, "sveikos panels" means "i smell of donkeys"10:32
lifelessthats not MY donkey10:36
mdkethat will work on the ladies10:37
SteveAwell, it won't work on *all* the ladies10:38
=== SteveA decides to get out of this conversation, and go to lunch instead
sivangSteveA: LOL10:48
=== fabbione [n=fabbione@port49.ds1-van.adsl.cybercity.dk] has joined #launchpad
=== koke [n=koke@ubuntu/member/koke] has joined #launchpad
=== stub [i=stub@sweep.bur.st] has joined #launchpad
=== stub [i=stub@sweep.bur.st] has joined #launchpad
stubjamesh: So you had no luck with that odd foaf pagetest failure?11:45
jameshstub: I've added a couple of syncUpdate() calls in places that look like they need it11:46
jameshand I can't reproduce it anymore, but that might not mean it is solved11:47
stubjamesh: Have these landed? We could reproduce consistantly on the PQM box for no apparent reason11:47
stubjamesh: I was going to attack the problem with pdb thought I better ask in case I was wasting my time11:48
jameshstub: no.  They're in my select-results-len-fix branch11:48
stubok. I might merge that in and see what happens on balleny11:48
jameshstub: search for syncUpdate() for the bits that might be the culprit11:48
jameshit might be easier to just pick out the hunks in question11:49
jameshthere are two hunks which add syncUpdate() calls11:49
tuhlping Daniel Silverstone | Steve Alexander11:51
=== Deepa [n=deepy@bb-dhcp-85-11-204-88.ornskoldsvik.com] has joined #launchpad
Deepacan you no longer get free ubuntu CD's?11:52
stubDeepa: Sure - https://shipit.ubuntu.com11:53
Deepaoops my mistake :P11:53
Deepai was searching around on launchpad.net XD11:53
=== thisfred [n=thisfred@a80-127-80-154.adsl.xs4all.nl] has joined #launchpad
=== salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
salgadostub, around?12:06
stubyes12:07
=== poningru [n=poningru@pool-68-238-172-74.tampfl.fios.verizon.net] has joined #launchpad
salgadostub, do you have a couple minutes to take a look at my DB patch for mirror management (https://chinstrap.ubuntu.com/~dsilvers/paste/filei41vyp.html)?12:07
=== matsubara [n=matsubar@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
matsubaragood morning!12:09
stubsalgado: Should distributionmirror.name have a constraint, or is any old rubbish acceptible as the name?12:10
salgadostub, it needs the valid_name constraint. I added it in the interface but forgot to add here12:10
stubAre there comments available?12:11
salgadonot yet, I forgot them again. will write now, though12:11
stubsalgado: What is an rsync_base_url look like?12:17
stubc/is/does12:18
salgadostub, I expect it's something like rsync://host.tld/some/path12:19
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad
stubsalgado: Ok. Just wanted to make sure it was really a url and not foo.domain:whatever syntax12:21
stubspeed > 0 ?12:21
stubsalgado: ^^12:21
stubOr is that a dbschema12:21
salgadoyep12:21
salgadodbschema12:21
stuband content dbschema?12:22
salgadoyes12:22
stubsalgado: MirrorProbeRecord has a NULLable date_created? Is that correct?12:25
stuband no default12:26
salgadono, it's not. it should default to NOW and be not null. my fault12:26
=== stub tests out his updates
stubsalgado: https://chinstrap.ubuntu.com/~dsilvers/paste/filee4kUpc.html12:50
stubsalgado: Approved patch-40-13-0.sql pending addition of good comments12:50
salgadostub, great. thank you12:50
=== cprov [n=cprov@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
cprovmorning ...12:53
=== bradb [n=bradb@modemcable033.209-70-69.mc.videotron.ca] has joined #launchpad
jblacktick. tick tock01:00
salgadoit's meeting time!01:00
lifelessSteveA: new items for the agenda01:00
=== niemeyer_ [n=niemeyer@201.23.160.9] has joined #launchpad
jblackI have a hunch I know what01:01
SteveAthanks lifeless 01:01
SteveAMEETING TIME01:01
SteveAwho is here today?01:01
jameshme01:01
dafI am01:01
spivme01:01
jblackI am here in body01:01
lifelessmoi01:01
matsubarame01:01
bradbme01:01
BjornTme01:02
cprovme01:02
carlosME01:02
salgadoI am01:02
carlossorry for the caps01:02
SteveAkiko is on vacation01:02
SteveAddaa is on vacation too01:03
SteveAstub?01:03
niemeyer_me01:03
dafKinnison is on vacation, I think01:03
fabbioneme01:03
SteveAhe is, yes01:03
SteveAhi fabbione 01:03
fabbionei am always here01:03
stubHere01:03
fabbioneMHUAAA 01:03
SteveA * Roll call01:03
SteveA * Agenda01:03
SteveA * Next meeting01:03
SteveA * Activity reports01:03
SteveA * Items from last meeting01:03
SteveA * Production / staging (stub)01:03
SteveA * Requiring tests for merges. (lifeless)01:03
SteveA * Keep, Bag, Change01:03
SteveA * Three sentences01:03
SteveA01:03
SteveAnext meeting, 5 january, okay?01:04
lifelessya01:04
spivfine with me, I'll still be on leave ;)01:04
jblackaye01:04
carlosyep01:04
=== ..[topic/#launchpad:SteveA] : launchpad.net | developer meeting: Thur 5 Jan, 1200UTC (wiki:MeetingAgenda) | launchpad-users@lists.canonical.com (wiki:MailingLists) | Channel logs are here: http://tinyurl.com/72w39
stubok. I should be there (I fly back from Penang in the morning on the 5th)01:04
=== beyond [n=beyond@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
SteveAactivity reports: how's all that going?01:05
stubFine01:05
jblackup to date01:05
=== SteveA hasn't sent one for a while. new year's resolution, perhaps...
=== daf just caught up
lifelessup to day01:05
carlosI'm two days behind with the activity reports01:05
niemeyer_I'm up to date01:06
BjornTup to date01:06
matsubaraup to date01:06
=== jamesh is not
=== cprov is up to date
=== bradb is up to date
salgadoI'm up to date, I think01:06
spivI'm behind.01:06
SteveA * items from the last meeting01:06
SteveAi've been slack with the meeting summary from last week01:06
SteveA* RobertCollins to set up a bzr-for-launchpad meeting at a different time to the launchpad developers meeting.01:07
lifelessoh yea, right.01:07
SteveA* Kiko to set up a launchpad community meeting.01:07
lifelessI've been 'getting to that' all week.01:07
SteveAkiko's away, but this hasn't happened still01:07
SteveA* Steve to announce the production of last week's summary on the launchpad-users mailing list.01:07
SteveAno summary, no announcement :-/01:07
stubAnd me or Steve should schedule an infrastructure meeting when people are back from hols01:08
SteveAthere was a wiki page set up for bzr-for-launchpad-development priorities01:08
SteveAi need to do some prioritization there01:09
SteveAmpt wrote a proposal about product groups / projects01:09
SteveAwhich now needs further discussion01:09
SteveAi think that's it01:10
SteveAi'd like to note that kiko and i now have access to change priorities on the admins' RT queue01:10
SteveAor rather, on the launchpad tasks queue in RT01:11
jblackDo you have time to describe the intended process a little? 01:11
SteveAthis should give us a better quality of service for the things that are immediately important01:11
SteveAthe intended process of getting admins to do RT stuff?01:11
jblackOf getting a bump01:11
jblackIt went rough when you and I tried, because you didn't have the bug yet? 01:12
SteveAhttps://rt.admin.canonical.com/01:12
=== sivang is here
SteveAyou can view the launchpad queue there01:12
SteveAthe username and password is the same one as for the wiki01:12
SteveAthe internal canonical wiki, that is01:12
SteveAso, when you add an rt issue, it gets put into a "pending classification" queue, that is not public01:13
cprovsalgado: MM spec was updated with your answers01:13
SteveAwhen an admin has classified it, and put it in the 'launchpad' RT queue, then I or kiko can change its priority, and also change it in other ways01:13
SteveAi'm using a priority of 99 to mean "this should be the next thing in the admins' queue"01:14
SteveAand working down from there01:14
SteveAthe idea is to have urgent things or blocking things registered with a priority of 9901:14
SteveAand to have a mix of quick and longer-term things there01:14
SteveAjblack: does that answer your question?01:14
jblackHow do you want to be requested? 01:15
SteveAin order to make something a high priority, i need to understand why it is important01:15
jblackstrictly email? both email and irc? 01:15
SteveAemail or irc is okay01:15
SteveAirc, when i'm here and listening01:15
SteveAemail when i'm not, and whenever01:16
jblackThanks01:16
SteveAan email saying "RT issue X is important!" isn't much use unless we've already discussed that issue being important01:16
SteveAso, it's important to communicate the rationale01:16
SteveA * Production / staging (stub)01:17
stubAsuka (the  server) was upgraded to breezy and PostgreSQL 8.0 earlier today. Expect it to be unavailable for the next few days as I test out PostgreSQL 7.4 -> 8.0 migration procedures and iron out the bugs.01:17
stubGina has been run on production. Yay. Might need some love from the publishing scripts to be useful, as Gina just creates 'PENDING' packages.01:17
SteveAand let's talk about the gina run and bugzilla imports too01:17
SteveAare we using the launchpad dependencies package in production?01:17
stubProduction update will happen Tuesday from head as of now, unless people require otherwise.01:18
stubAs far as I'm aware, we are not using the launchpad dependencies package in production. That is elmo and Znarl's turf really.01:18
SteveAwe should be using it01:18
jameshI just put some updates for ErrorReportManagement up for review.  It might be nice to have that rolled out01:18
=== stub isn't using it either... not sure where to install it from
SteveAwe should all be using it on our systems too01:18
=== sivang is using it
=== carlos too
carlosstub, universe01:19
SteveAwhat's the name of the package?01:19
stubjamesh: ok. I'll consider rolling out that revision when it lands.01:19
sivangSteveA: launchpad-dependencies01:19
=== duchier [n=duchier@AOrleans-152-1-70-232.w86-195.abo.wanadoo.fr] has joined #launchpad
sivangSteveA: and launchpad-database-dependencies01:20
SteveAthanks01:20
SteveAsteve@einheit:~$ apt-cache policy launchpad-dependencies01:20
SteveAW: Unable to locate package launchpad-dependencies01:20
SteveAmaybe it is only for dapper01:20
dafit's in dapper/multiverse01:21
SteveAi'll file an RT issue to ask the admins to use that package01:21
stubheh... it tells me I don't have bison and ncompress ;)01:21
stubI see it - probably it is in -backports or something01:21
SteveAon gina and bugzilla imports01:22
SteveAi'm concerned about the packages not being visible in the web app01:22
SteveAi don't know what needs to run to make them so01:22
SteveAi think we should not run the bugzilla import until these things are actually visible01:22
SteveAcprov: do you know anything about this?01:22
cprovSteveA: not much about bugzilla-import touched the code yesterday ...01:23
SteveAotherwise, i'll try phoning people who aren't here01:23
stub(launchpad packages are in breezy-updates)01:23
SteveAcprov: do you know what we need to do to get packages showing up in the web pages of launchpad?01:23
dilysMerge to devel/launchpad: [r=bjornt]  Soyuz/Buildd UI fixes, introducing batched list and ordering soyuz tests. (r2934: Celso Providelo)01:23
cprovSteveA: but of course we need a publisher run after gina imports to have "visible" pkgs01:24
=== duchier [n=duchier@AOrleans-152-1-70-232.w86-195.abo.wanadoo.fr] has left #launchpad []
cprovSteveA:  they need " publishing" transition from PENDING to PUBLISHED 01:24
jameshso that's another script for stub to run?01:25
SteveAi'll see if i can talk with kiko later01:25
cprovSteveA: I'm not sure about the current status of RF publisher, but it works fine from my branch01:25
stubI think that requires Daniel in fact01:25
cprovscripts/publish-distro -Cvv -d ubuntu01:25
SteveAkiko will be able to say if it is okay to run on production01:25
stubok. We have backups ;)01:26
cprovit will mode all PENDING to PUBLISHED and obviously create an archive 01:26
lifelessDoIt :)01:26
SteveAon this subject, https://wiki.launchpad.canonical.com/BugzillaImportProcess01:26
cprovmove not mode 01:26
niemeyer_cprov: We should probably talk about that branch integration at some point01:26
SteveAa-moving on with the meeting...01:26
SteveA * Requiring tests for merges. (lifeless)01:26
cprovniemeyer_: NOW ;)01:26
niemeyer_cprov: I mean, with Steve01:26
lifelessrequiring test coverage in commits. Brought up by kiko two weeks back, has my complete support. The idea is that reviewers will be allowed to say01:27
lifeless'this cannot be merged' based on test coverage, irrespective of other criteria.01:27
cprovniemeyer_: right, it probably requires some review team love 01:27
lifelessthis needs lp management to say 'ok' before I can ask the review team to enforce it01:27
lifelessor its just dog-wagging.01:27
SteveAi'm more in favour of cat-swinging01:27
SteveAso +1 from me01:27
lifelessit has my +1.01:28
lifelesswhat does it need ?01:28
SteveAhow about adding needs-tests as a pending reviews status01:28
SteveA(on cat swinging, see http://en.wikipedia.org/wiki/Cat_o%27_nine_tails)01:28
sivangplease ping me when we discuss product-groups instead of projects..I have to attedn to something in the office :-/01:28
lifelesswhy the new state ?01:29
SteveAsivang: that's not on the agenda today01:29
lifelessI mean, the new tests will need review01:29
lifelessso its no different to 'not ready yet' from my perspective01:29
sivangSteveA: ah, ok. thanks01:29
SteveAi suggested it so that the fact that it's good to go except for tests is made clear01:29
SteveAi'm not attached to the idea01:29
SteveAquite possibly, it needs nothing other than a note in the reviewer guidelines01:30
lifelessI'll add  that to the next review meeting as a specific process question01:30
SteveAok01:30
lifelessso - we have the go ahead on this ?01:30
SteveAalso01:30
SteveAi'd encourage people to ask those who are good with tests, for help on how to write good tests for a branch01:30
SteveAwhile the branch is being worked on, even at the start01:30
SteveAit is a good discussion to have01:31
lifelessyes. this should go in the hacking faq too01:31
SteveAmaybe add a "test plan" to specs?01:31
lifelesscould do01:31
SteveAyes, you have the go-ahead with it.01:31
SteveAthis is something to use common sense with01:31
SteveAand not be fanatical about01:31
lifelessof course.01:31
SteveAwe all benefit from having better test coverage01:32
SteveA * Keep, Bag, Change01:32
lifelessbut before it was quite possible for someone to write 4K of pep8 ok code and get it 'oked'01:32
SteveABag: slacking off on meeting summaries01:32
SteveAanything else?01:33
SteveA401:33
SteveA301:33
SteveA201:33
SteveA101:33
SteveA * Three sentences01:33
dafDONE: lots of bug triage, bug prioritisation, docs work on wiki01:33
dafTODO: more bug triage and prioritisation, land various branches, send list of headings to MPT01:33
dafBLOCKED: no01:34
lifelessDONE: b.l.n mirroring, several days of reviews, pqm on balleny01:34
lifelessTODO: story tests, test task list, baz2bzr01:34
lifelessBLOCKED: steveA-Zope3 update, week 501:34
matsubaraDONE: fixed bug on malone being unable to display a public bug that has a private dupe, fixed bug on spec name field triggering database constraint and other trivial bugs01:34
matsubaraTODO: more bug fixing, merge most of the bugs above01:34
matsubaraBLOCKED: nope01:34
carlosDONE: PoMsgSetPage, TranslationUploads merge (finally) and bug triage01:34
jblackDONE: supermirror initial rollout, some launchpad rocketfuel docs, lots of bzr support+mail01:34
salgadoDONE: MirrorManagement, landed ProperSignUpWorkflow, code review, small fixes.01:34
jblackTODO: more of same, primarily rocketfuel01:34
jblackBLOCKED: None01:34
spivDONE: Assorted supermirror stuff.01:34
spivTODO: Supermirror, christmas!01:34
spivBLOCKED: no01:34
BjornTDONE: fixed bugs in the email interface. landed reviewed branches. got started on reducing the number of statuses in the support tracker. reviews. general malone discussions.01:34
BjornTTODO: finish reducing the number of statuses and getting a decent test coverage of the support tracker.01:34
BjornTBLOCKED: no01:34
carlosTODO: PoMsgSetPage, TranslationReview, bug #575101:34
SteveADONE: management stuff, bug triage stuff, brad in vilnius stuff01:34
SteveATODO: vacate, zope3 update01:34
SteveABLOCKED: no01:34
UbugtuError: I cannot access this bug01:34
carlosBLOCKED: no01:34
salgadoTODO: Finish first round of MirrorManagement tomorrow, then vacation01:35
lifelessmuhahaha ubugtu muhhahaa01:35
salgadoBLOCKED: no01:35
jblack?01:35
niemeyerDONE: Soyuz work, Gantry discussions and researching, Smart 0.41 work and release, USA visa, etc01:35
niemeyerTODO: Vacation01:35
niemeyerBLOCKED: Nope01:35
cprovDONE: delivered/tested new queue script and old soyuz branch catch up01:35
cprovTODO: uploader-test clean up and review setup for this branch01:35
cprovBLOCKED: dapper-uploads generation (RT # 1310)01:35
jameshDONE: SelectResults.__len__() removal, ErrorReportManagement stuff, team branch traversal fix, other bug fixes01:35
jameshTODO: bugzilla import, code reviews01:35
jameshBLOCKED: publishing run (before bugzilla import)01:35
stubDONE: fti rollout improvements01:35
stubTODO: PostgreSQL 7.4 -> PostgreSQL 8.0 migration testing01:35
stubBLOCKED: Nothing01:35
bradbDONE: Sprint in Vilnius with SteveA. Landed a few bugfixes. Landed InitialBugContacts.01:35
bradbTODO: Land status changes. Small bugfixes if time. Holidays.01:35
bradbBLOCKED: No.01:36
SteveAanyone else?01:36
dafTODO: get a festivus pole (http://www.festivuspoles.com/pages/Festivuspoles.htm)01:36
SteveAcprov: i'll ask about RT 131001:37
cprovjamesh, stub, SteveA: maybe I can help with publisher if you can't contact Kinnison or kiko ...01:37
SteveAcprov: but this might be delayed until elmo is back01:37
SteveAthanks cprov 01:37
cprovSteveA:  this is BAD ...01:37
SteveAit is festvus tomorrow01:37
SteveAcprov: do you know if anyone other than elmo can do RT 1310 ?01:38
cprovSteveA: I was expecting the upload for the before the crew leave  01:38
cprovSteveA:  not that I know, it requires katie-fu01:38
SteveAi think infinity knows about katie01:39
SteveAalso Kamion does01:39
cprovSteveA: could be, but he is also on leave, isn't he ?01:39
=== jinty_ [n=jinty@205.134.224.215] has joined #launchpad
cprovSteveA: Kamion looks like a good bet, if he was available during this time 01:40
sivangDONE: Getting up to date with mailing list, some comments on RFS, going over some bugs, commenting and providing info.01:41
SteveAhe's going to be around for the distro team meeting01:41
sivangTODO: Help matsubara reproduce spec tracker registeration bug , complete rockefuel checkout using jblack's script01:41
cprovSteveA: don't know if he can handle DC issues like anonymous rsync access setup and storage, but I hope so01:41
SteveAwill anyone but elmo understand what is written in https://rt.admin.canonical.com/index.html?q=131001:41
lifelessSteveA: any word on z3 ?01:41
SteveAlifeless: just "argh"01:41
jblackAnybody going to the FSF gplv3 meeting in Boston? 01:42
sivangBLOCKED: not enough time, still.01:42
=== lifeless drafts up 'blocked; z3 week 7'
cprovSteveA: yes, I think, if not call me anytime01:42
SteveAok01:42
SteveAthat's it then01:42
SteveAwe have time for a countdown of doom today01:42
lifeless001:42
SteveAMEETING ENDS01:43
dafhappy festivus everyone01:43
SteveAthanks folks.  have a vacation.01:43
salgadolifeless, do you have a few minutes? (there's one point from your review that I'd like to discuss. it should be quick)01:43
lifelesssalgado: sure01:43
=== bradb & # shower
carlosok01:44
salgadolifeless, in the subclass of GeneralFormView I've created, the default process() method shouldn't accept a *args, because it must be generic and it won't know how to handle that *args01:44
=== carlos -> lunch
salgadolifeless, although, any subclass can override that method if they want to have *args. 01:45
lifelesssalgado: its just unusual to see **kwargs without *args01:45
lifelessif its deliberate, I'd make a comment and its fine01:45
salgadolifeless, I thought about making the generic process method be "def process(self, *args, **kw)" and then raise an AssertionError if *args was provided01:46
lifelessnote separately that **kwargs in hierarchives should be very juidiciously used. I haven't look at this region of code sufficiently to comment on it here yet01:46
SteveA*args and **kw are kinda evil01:46
lifelessSteveA: jinx!01:46
SteveAwhat's the reason for wanting them?01:46
salgadoSteveA, 1sec. I'll paste it01:47
salgadoSteveA, https://chinstrap.ubuntu.com/~dsilvers/paste/fileVJSuYl.html01:47
lifelessSteveA: its another general form concept01:47
salgadoSteveA, it's a generic generalform that can be used for editviews01:48
lifelessSteveA: very similar to the existing general form, something I think we should look at at a sprint01:48
BjornTsalgado: why can't you use SQLObjectEditView?01:49
SteveAsalgado: what is going to call process() with kw args?01:49
salgadoBjornT, because I want to do some schema validation01:49
salgadoSteveA, GeneralFormView's process_form() 01:50
BjornTsalgado: what kind of schema validation?01:50
salgadoSteveA, BjornT, I also extended the GeneralFormView to make it easier to do schema validation01:50
salgadoBjornT, check if at least one of three widgets is not-None01:51
salgadofor instance01:51
SteveAi get worried when i see methods with generic names calling each other01:51
SteveAit becomes unclear what the division of responsibilities are01:51
=== bradb_ [n=bradb@modemcable033.209-70-69.mc.videotron.ca] has joined #launchpad
BjornTi don't think that we should have both SQLObjectEditView and GeneralFormEditView, we should only have one of them.01:53
salgadoSteveA, well, the GeneralFormView is pretty well documented, I think. it says clearly that if your processing should be done in the subclass' process() method01:53
salgados/if your/your01:53
lifelessI think we need to review the structure of the general form stuff01:53
lifelessit has **kwargs in there already as I recall01:54
salgadolifeless, yes, it does01:54
lifelessand this new use is sympomatic of a flaw in the underpinnings01:54
SteveAi see01:54
lifelessrather than the introduction or regression of a concept01:54
SteveAalso, there is an equivalent thinggie in the new zope3 code01:54
SteveAwhich we should adopt / improve01:54
lifelesswhich is why I am suggesting some intense pair face to face stuff to address this01:54
lifelesseither that or someone who has spare cycles and a refactoring fetish to spend time on it now. But its not AFAICT a design or use problem in salgagos patch per se01:55
salgadoI can't see how to make a generic form view without **kwargs, though01:56
lifelesssalgado: it really depends what you want to factor out01:56
lifelessfor instance, the current 'process' really is 'set_attributes_from_form_request_variables'01:57
lifelesswhich would not be a kwargs method01:57
BjornTlifeless: well, having two different edit view classes is confusing. i think we should create a new GeneralFormView when the new zope3 stuff lands, and until then it's better to customize SQLObjectEditView to fit salgado's use case01:57
lifelessBjornT: I've no opinion on that at this point. salgado - can you please look at that other view, and if they really are this close, and you think its safe to change, do as BjornT is suggesting01:58
salgadoBjornT, we already have the SQLObjectAddView and the GeneralFormView01:58
lifelesssalgado: I think BjornT is saying that there is already another SQLObjectEditView form01:59
lifelesssalgado: which has the same role as your new class01:59
BjornTsalgado: that's two different things. SQLObjectAddView is for adding things, GeneralFormView is for general form processing.01:59
lifelesssalgado: so would rather tweak it to do what you need..01:59
salgadoI don't think I'm making things more confusing with this patch01:59
=== lifeless leaves salgado and BjornT to it. I'm happy code wise with my comments.
lifelessif you two come to an agreement - cool01:59
salgadoBjornT, but GeneralFormView can be used only for processing forms that create new objects02:00
salgadoit can't be used in edit forms02:00
salgadoI could easily change it so it can be used in edit forms02:00
BjornTsalgado: you're adding an edit view with different semantics than the existing edit view. it's easy to customize the existing edit view to do what you like.02:01
salgadoand then I'd do the generic part of my GeneralFormEditView in my own subclass of it02:01
BjornTsalgado: mark told me that he didn't want us to create a GeneralFormEditView, and instead use the existing SQLObjectEditView. (i think we should create new form classes later with the new zope3 stuff, replacing the old ones, though)02:04
salgadoBjornT, okay, what would be the better solution: customize SQLObjectEditView (in the same way I already did for GenericFormView), or change the GenericFormView so it can be used in editforms and do the actual processing in my GenericFormView's subclass?02:05
BjornTsalgado: so, to sum up what i think. if you want to solve your use case generally, customize SQLObjectEditView. otherwise use GeneralFormView and do the extra processing in your specific view classes.02:06
BjornTsalgado: remind me, why can't you use browser:generalform?02:07
SteveAstub, cprov: i just spoke with kiko about publisher runs etc.02:07
salgadoBjornT, because it doesn't set the initial values02:07
cprovSteveA: so, what does he suggest ?02:07
salgadoBjornT, initially, I simply changed it to set the initial values and was doing the processing on my own subclass02:08
SteveAlet's talk on the c-m channel02:08
salgadoBjornT, but then I got tempted to write something generic so I could share between all my subclasses (I have 3 of them in this patch, IIRC)02:08
salgado(subclasses of GeneralFormView, I mean)02:08
BjornTsalgado: ok. let me take a quick look at it. although, if you have 3 classes that requires this, i would suggest to modify SQLObjectEditView to cover your use case.02:09
stubsalgado: Any reason you didn't just extend GeneralFormView to make it more 'general'?02:12
BjornTsalgado: the branch that you did these changes aren't on the PendingReviews page? i'd like to see the changes you did to GeneralFormView02:13
stubc/extend/enhance02:14
salgadostub, I did that. you can subclass it, define an 'initial' property and then it can be used in an edit form. but then I got tempted to write a generic editview that would also set the attributes back in your object when the form is submitted02:14
salgadoBjornT, it's there but I forgot to mirror. I'll mail you the diff02:14
salgadoBjornT, sent02:15
BjornTsalgado: cool. because i think it's worth making GeneralFormView to set initial values, i just want to see how you did it.02:16
SteveAcall it 'initial_values' or something more explicit than 'inintial'02:16
salgadothe patch is at https://chinstrap.warthogs.hbd.com/~salgado/distro-mirror.diff too02:17
salgado(in case anybody else wants to look at it)02:17
=== Nafallo_away is now known as Nafallo
=== eruin [n=eruin@unaffiliated/eruin] has joined #launchpad
BjornTsalgado: why do you need two different error lists? (self.errors and self.schema_errors, where the first one actually contains errors related to the schema)02:26
salgadoBjornT, because self.errors is for the errors that are going to be displayed as a box around the widget that triggered that error. while schema_errors has to be displayed at the beginning of the page, because it will probably apply to multiple widgets02:28
BjornTsalgado: hmm, it's still a bad name. i can't think of a better name, though. in zope3 terms it would be invariant_errors, but since you don't use invariants directly, that doesn't seem right. i guess it's ok for now, and we can re-think it later.02:43
SteveAthis is a view class02:44
SteveAso top_of_page_errors would work too02:44
SteveAoutside_of_form_errors02:44
BjornTyeah, those are better names02:45
salgadoI prefer top_of_page_errors02:45
BjornTsalgado: so, i'd say, keep the modifications for initial values (renaming it to inital_values as SteveA suggested), but drop GeneralFormEditView.02:45
salgadoBjornT, right, and keep using the GeneralFormView on my edit views or use SQLObjectEditView?02:46
BjornTsalgado: i don't care if you modify SQLObjectEditView or do the logic in your specific view classes, do what's easiest for you to do. (modifying SQLObjectEditView would probably be the most useful solution, though)02:47
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #launchpad
SteveAdaf: hi.  do you want to do some more rosetta bug discussion today?03:04
SteveAcarlos: how's the performance refactoring going?  want to talk about it at all?03:04
=== cprov leaves for lunch, PQM is damm slowishhhhhhhhhh.
=== WaterSevenUb [n=WaterSev@195-23-220-11.net.novis.pt] has joined #launchpad
=== GoRoDeK [n=gorodek@p5083EF6D.dip.t-dialin.net] has joined #launchpad
=== beyond is now known as beyond-rango
=== xester good morning
salgadoBjornT, I changed SQLObjectEditView in the same way I did to GeneralFormView. would you review it for me?03:40
BjornTsalgado: sure03:41
SteveAjamesh: does your import script convert default assignees to package bug contacts?03:42
salgadoBjornT, mailed it to you03:42
jameshSteveA: no.  I have a separate script for that03:42
jameshwhich needs some small tweaks for InitialBugContacts03:42
SteveAwhat is the name of this script?03:43
jameshit isn't in the launchpad tree at the moment03:43
SteveAi need a name for BugzillaImportProcess03:43
jameshlet me find it03:43
jameshmigrate-bugzilla-maintainers.py03:44
=== matsubara is now known as matsubara-lunch
Mezo_O03:48
MezI have a highlight in here?03:48
SteveAbradb_: where's the status changes branch up to?03:57
bradb_SteveA: #3 in pqm's queue03:58
SteveAbradb: please update https://wiki.launchpad.canonical.com/BugzillaImportProcess when it lands04:02
bradbSteveA: ok04:02
jameshSteveA: I've got a second round of ErrorReportManagement changes in the review queue.  The main bits are: remove /errors/* pages, put day-of-month in oops ids, better handling of non-ascii data and the port of kiko's log analysis script04:02
SteveAjamesh: can we talk about the log analysis?04:05
jameshsure04:05
SteveAi'm interested in NotFound errors where the Referer's host is one of the ones we care about04:05
SteveAto start with, that includes launchpad hosts, shipit, wiki stuff...04:06
SteveAanything with ubuntu.com or launchpad.net in the host name, i guess04:06
SteveAthese indicate a bad link that we can fix04:06
SteveAi'm also interested in NotFound errors that aren't by robots04:07
jameshshould be pretty easy to get some regexps to detect search engine bots04:08
jameshI suppose this could be presented in a report as "all NotFounds caused by bots", "all by humans", "some of each"04:09
SteveA800 error reports for 2005-12-2104:09
SteveAsome of each?04:09
jameshthe first and third cases usually indicating that we've changed links, the second usually being humans pruning URLs04:09
jameshsome NotFound errors caused by bots, some by humans04:10
salgadolunch04:10
SteveAException-Value: Unknown SQL builtin type: <class 'canonical.launchpad.database.milestone.Milestone'> for <Milestone at 0x2ab815cc10>04:12
SteveAthis is a malone bug04:12
SteveAfrom the advanced search page04:13
SteveAchinstrap:/srv/gangotri-logs/2005-12-21/72434.A36904:13
=== lbm [n=lbm@x1-6-00-13-10-7a-d1-e4.k233.webspeed.dk] has joined #launchpad
SteveAhttps://launchpad.net/distros/ubuntu/+source/cnews/+bugs04:20
SteveAinterestingly, that causes a system error04:20
carlosSteveA, about the suggestions thing... I'm changing most of the methods to use SQL queries, but I need some changes I did as part of the cleanup to implement PoMsgSetPage04:23
cprovmore than that, https://launchpad.net/distros/ubuntu/+source/cnews also crashes04:23
carlosSteveA, so I'm going to add the changes for the suggestion part to the PoMsgSetPage branch04:23
carlosSteveA, the main thing is that with our current code, there are some situations when you don't have an IPOMsgSet and that's why Mark created the methods inside IPOTMsgSet04:24
SteveAbut they are not used, as far as i can see04:25
carlosI added a DummyPOMsgSet object like the DummyPOFile that will let us to assume that we always have such object04:25
carlosSteveA, they are used04:25
carlosSteveA, the IPOMsgSet calls the IPOTMsgSet04:25
carlosmethods04:25
SteveAyes04:25
SteveAso04:25
SteveAwhy?04:25
SteveAwhy have something exist just so it is called by something else?04:26
carloswell there are some of those methods that are also called from another part of the code... but I cannot give you a rationale as I didn't write that code04:26
SteveAi grepped the code for the methods i mentioned in that bug report04:26
SteveAand i cannot find them called04:27
SteveAthat is why i talked about removing those methods from IPOTMsgSet04:27
SteveAand making them occur only in IPOMsgSet04:27
carlosthat's what I'm doing, but for all the methods not just the ones that are called only from IPOMsgSet04:28
carlosso they are methods of the context they use04:29
SteveAokay, i think04:30
=== bradb heads off to catch a flight, back in about 6-8 hours
=== eruin is now known as beskyddaren
SteveAi don't really understand.  so long as you're making the code use SelectResults, make specific SQL queries, and only use shortlist() to listify things rather than list() or list comprehensions,04:31
SteveAthen that sounds like good stuff04:31
carlosSteveA, well, the idea is to do SQL queries and nothing else04:32
carlosthere are many python code that can be moved back to the DB04:32
cprovSteveA: where are the production error reports in chinstrap ?04:32
carlosso no more lists or sorting using python or getting a bunch of records to filter them out using python04:32
SteveAcprov: /srv/gangotri-logs04:33
SteveAcarlos: sounds good04:33
cprovSteveA: thx04:33
SteveAcarlos: it may be good to do this one step at a time, rather than all at once as a very big change04:33
SteveAsuch a change is harder to review04:33
carloshmm04:35
carlosok I will try to extract the needed bits from PoMsgSetPage branch and add them to this new branch04:35
carlosSteveA, ok?04:35
SteveAthat will help reviewers04:36
SteveAso, please do so04:37
SteveAbut also, consider breaking the refactoring into sql queries into smaller chunks04:37
carlosok04:42
=== kjcole [n=kjcole@pchb1f.gallaudet.edu] has joined #launchpad
dilysMerge to devel/launchpad: [r=BjornT]  Malone bug status changes. See (r2935: Brad Bollenbach)04:47
=== matsubara-lunch is now known as matsubara
=== beyond-rango is now known as beyond
=== mdke_ [n=matt@ubuntu/member/mdke] has joined #launchpad
=== WaterSevenUb [n=WaterSev@195-23-220-109.net.novis.pt] has joined #launchpad
carlosSteveA, dude... IPOMsgSet.getCurrentSubmissions is the same as IPOMsgSet.publishedSubmission06:24
SteveAwow06:24
carlosbut using a lot of python code06:24
SteveAi see06:25
SteveAstub: staging seems rather dead06:39
=== Nafallo is now known as Nafallo_away
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad
=== carlos goes out for a while, will be back later
=== reed [n=maffulli@213-140-6-112.ip.fastwebnet.it] has joined #launchpad
reedhi there08:02
reedcan somebody point me to a description of what Launchpad is and wether it is free (as in freedom) software?08:03
reeduhm, never mind, it seems that the wiki answers the first question :)08:04
SteveAlaunchpad isn't free software08:05
dilysMerge to devel/launchpad: [r=spiv]  fix bug 2676, work around python's unfolding of email headers, to make gpg signatures verify properly. (r2936: Bjorn Tillenius)08:05
SteveAit's like google or freshmeat: a free service but not free software08:05
reedSteveA: do you know if there are plans to release it as a free sw package?08:08
reedor also, would that make sense technically or is launchpad just too Ubuntu specific?08:08
SteveAthere are no concrete plans08:11
SteveAmark shuttleworth has said that he wants it to be free software at some point in the future08:11
reedSteveA: thank you08:12
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad
=== koke [n=koke@adsl229-164.unizar.es] has joined #launchpad
=== jinty [n=jinty@205.134.224.215] has joined #launchpad
cprovnight guys 10:14
=== xester good night
=== lamont__ [n=lamont@mib.fc.hp.com] has joined #launchpad
=== LarstiQ_ is now known as LarstiQ
=== Hieronymus [n=jeroen@cp413115-a.tilbu1.nb.home.nl] has joined #launchpad
Hieronymushttps://launchpad.net/malone/assigned?name=motuscience points to my own assigned bugs. The page was linked to from https://launchpad.net/distros/ubuntu/+source/ghemical/+bugs11:09

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