[03:01] <mpt> Goooooooooooooooooooooooood afternoon Launchpadders!
[03:14] <cprov> mpt: hey
[03:15] <cprov> mpt: may I have you oppinion for a new page/action about  builds
[03:17] <mpt> cprov, sure
[03:18] <cprov> mpt: we new a RESET ALL page and there the user might choose one or more "resetable" state 
[03:18] <mpt> To reset what?
[03:18] <cprov> mpt: I'm thinking in a form with check-boxes, is it ok ?
[03:18] <cprov> build records
[03:19] <cprov> massive reset all build records in a defined set of states
[03:19] <cprov> brutal force for buildd-admins 
[03:20] <mpt> Resetting all the build records for a single build machine? Or for all build machines?
[03:21] <cprov> mpt: it's context sensitive, as most of the +builds pages 
[03:22] <cprov> mpt: did you get it ? or I was confusing ?
[03:24] <mpt> cprov, resetting all the build records for a single build machine? Or for all build machines?
[03:26] <cprov> mpt: if you are in /+builds/foo-builder/+resetall for all foo-builder records if you are in /distro/ubuntu/hoary/+builds/+resetall for all ubuntu/hoary builds, that's context sensitive ...
[03:26] <mpt> oh, ok
[03:27] <mpt> cprov, why would you want to reset all the build records?
[03:27] <cprov> is this more complexity than we are looking for ?
[03:27] <cprov> it's the usual retry they do once a while 
[03:28] <mpt> Sorry, I don't understand that
[03:28] <mpt> Is this to keep the list of builds short?
[03:28] <mpt> to remove records that are no longer relevant?
[03:28] <cprov> when we have builder spare time and want to retry every failure just for fun ;) I mean, just to check if they can build 
[03:29] <cprov> mpt: not just it, but it can check if the things can be "more sane"
[03:29] <cprov> mpt: catch up false "failures" and so on
[03:31] <cprov> mpt: does it make any sense for you ?
[03:31] <mpt> Not really :-(
[03:31] <mpt> "more sane" how?
[03:31] <mpt> How do you "catch up" on a failure?
[03:32] <cprov> mpt: reset failures by dependency waiting that now can be satisfied, reset all failures by DC power/net outage (hehe this is fun) and weird things like that
[03:34] <mpt> cprov, so how often would people want to do this? Once a day? Once a week? Once a month?
[03:36] <cprov> mpt: dependes on admins freakness, but never more ofen than day (I can say for sure, may weekly)
[03:36] <cprov> maybe
[03:38] <cprov> it's indeed a very low hit page, protected by builddAdmin, so a very restricted page
[03:38] <mpt> cprov, what would the checkboxes be necessary for? One checkbox per build?
[03:38] <cprov> mpt: no one per "resetable" state, currently: DEPWAIT, FAILED, BUILDERFAIL, CHROOTFAIL
[03:40] <cprov> read by this:  I want to reset ALL build in XXX state in this context
[03:40] <mpt> ok
[03:41] <cprov> mpt: I'm ok if you say it's too fluf for UI atm and we should do this as a special cmd-line tool
[03:41] <mpt> cprov, I think this should be a section at the bottom of the +builds page, rather than a separate page
[03:41] <cprov> it would same me time, btw
[03:41] <cprov> really ?
[03:41] <mpt> wrapped in <tal:admin condition="required:launchpad.Admin"> or whatever the appropriate permission is
[03:42] <cprov> uhmm good idea
[03:42] <mpt> So people who can do it see it, and people who can't don't
[03:43] <mpt> One of my branches up for review does that for team +members pages
[03:44] <cprov> it's a good idea, I can mock it up and show you tomorrow on mawson (dogfood) .. thank you dude
[03:48] <mpt> no problem
[03:52] <cprov> stub: hi stub
[03:53] <cprov> mpt: good, thanks
[03:53] <stub> cprov: morning
[03:54] <cprov> stub: good morning (here late night ;))
[03:55] <cprov> stub: so, did you cherrypick this manual fix we did in production DB ?
[03:56] <stub> Not yet. I'll need to cherry pick it when I tag the production branch for the rollout tomorrow.
[03:57] <cprov> stub: ok, up to you, we just can't forget.
[03:57] <stub> Actually, I think I'll just tag the production release from r3199 so no cherry picking neccessary
[04:00] <cprov> good
[04:40] <cprov> stub:  which is current DB patch number ?
[04:40] <stub> where?
[04:41] <cprov> RF
[04:41] <cprov> i need to send a new patch, new field in build table, of course to be aplied/cherrypicked before rollout
[04:43] <stub> Just use a high number like 99 - I allocate the real patch number when it is approved.
[04:43] <cprov> okay
[04:43] <stub> You will probably get -23-0.sql if this happens soon though
[04:44] <cprov> in 10 minutes
[05:01] <cprov> stub: sftp://chinstrap/home/warthogs/archives/cprov/launchpad/small-fixes
[05:02] <stub> Can you paste the db patch?
[05:02] <stub> Or did you want a review of the entire branch?
[05:03] <cprov> stub: no, it's a single file -> https://chinstrap.ubuntu.com/~dsilvers/paste/fileS3OMjV.html
[05:04] <stub> It needs a comment in comments.sql
[05:04] <stub> What is 'depends'? Should that be dependancies?
[05:05] <stub> Or is that the term used in .deb packaging
[05:05] <cprov> stub: uhm, does it sounds more readable for you ?
[05:05] <cprov> stub: it will store a dependency line generated by builder when a job is DEPWAIT
[05:05] <stub> 'depends' is the present tense form of the verb 'depend'
[05:06] <stub> This should be a noun
[05:06] <stub> So dependencies would be better
[05:06] <cprov> queuebuilde will tweak it removing satisfied deps from this line as soon as they get published and move the recored to PENDING when the field gets empty
[05:07] <cprov> queuebuilder ...
[05:07] <stub> (note I used the incorrect spelling before)
[05:08] <stub> (depends would be the correct column name for a foreign key relationship, where foo depends on bar)
[05:08] <cprov> i won't loose the "present" state of the concepts, some thing like "still_depending" 
[05:09] <stub> dependencies has the necessary concept of 'present'
[05:09] <cprov> ideally it should map across binarypackagereleases, but the text notation is easier
[05:09] <cprov> ok "dependencies"
[05:10] <stub> Is there much code breakage? I'll let you land it like it is if you add  bugreport to do the rename later.
[05:11] <cprov> stub: there is no code yet, I can rename it now, wait a second
[05:11] <stub> Ok. approved with the new column name and a comment in comments.sql that describes the format.
[05:11] <cprov> right
[05:11] <stub> patch-40-23-0.sql
[05:13] <cprov> ehe, Build table has no comment at all, shit ... will write them all and request a small review from you
[05:17] <stub> cprov: or open a bug and assign it to yourself.
[05:17] <cprov> stub: will write it now, have that time
[05:17] <stub> It might be getting a bit late :)
[05:28] <cprov> stub: done, generating a diff for you
[05:29] <cprov> stub: late for me or for you ?
[05:30] <stub> for you
[05:30] <cprov> stub: https://chinstrap.ubuntu.com/~dsilvers/paste/filetMuaR2.html
[05:30] <stub> Just coming up to lunchtime here
[05:30] <cprov> stub: no way, I have more 8 hour of work with adam, i', in AU time today and tomorrow :(
[05:31] <stub> I remember now
[05:31] <stub> That is the old paste?
[05:31] <cprov> stub: check the diff out for english error, or bad phrases, pleas
[05:31] <cprov> stub: I suck 
[05:32] <cprov> stub: https://chinstrap.ubuntu.com/~dsilvers/paste/fileWGLOwk.html
[05:34] <stub> COMMENT ON COLUMN Build.processor IS 'Points the Distroarchrelease available processor target for this build.' should be 'Points to the Distroarchrelease...'
[05:34] <cprov> right, will add "to" after all "points"
[05:35] <stub> COMMENT ON COLUMN Build.sourcepackagerelease IS 'Sourcepackagerelease which originate this build.' should be 'The Sourcepackagerelease which originated this build.' (past tense)
[05:35] <cprov> right
[05:35] <stub> +COMMENT ON COLUMN Build.pocket IS 'Store the target pocket idenfier for this build.' should be 'Stores the target pocket identifier' (present tense)
[05:35] <stub> (and store is the verb form)
[05:36] <stub> everything else is good
[05:36] <cprov> right, thanks, r=stub ?
[05:36] <stub> Yes. r=stub
[05:37] <cprov> stub: good
[05:38] <stub> Do you need me in the next hour? I need to grab some lunch and pay some bills at the bank, but I can delay that if I'm needed here.
[05:45] <stub> mpt: Have the files been bzr added? Or did you accidently commit them (bzr status might help)
[05:46] <cprov> stub: no, go for it, ping me when you get back
[05:46] <cprov> stub: it would be nice if we can cherrypick this on production
[05:46] <mpt> stub, this is a branch recently converted from baz
[05:47] <mpt> Now I see that the test I'm changing shows up as "unknown:" in bzr status (along with dozens of other files)
[05:47] <mpt> Do I need to bzr add all of them? :-/
[05:47] <stub> cprov: I've applied the patch to the production database
[05:47] <cprov> stub: you rock, thanks 
[05:48] <stub> mpt:'bzr add .' works to add everything in the current directory and below
[05:48] <stub> (unless it is  ignored like .pyc and foo~ files)
[05:48] <mpt> Yeah, I was just going to ask if I'd need to do a make clean first :-)
[05:50] <stub> Otherwise 'bzr missing | xargs bzr add' might do the trick if what you are trying doesn't work
[05:50] <mpt> stub, now I have both 30-add-edit-package-infestation.txt and 30-add-edit-package-infestation.txt.disabled
[05:50] <mpt> should I use rm on the first one, or bzr rm?
[05:51] <stub> I use bzr rm - not sure what is best practive
[05:51] <stub> practice
[05:51] <mpt> (given that that test is supposed to disabled)
[05:51] <mpt> +be
[05:54] <spiv> mpt: Hmm, is one a copy of the other?
[05:54] <mpt> yes
[05:55] <spiv> Are you changing that file in this branch, or is this just some temporary hackery?
[05:55] <mpt> I was trying to change it to make the pagetest pass, that's all
[05:55] <mpt> Pretty quickly I realized it would never pass because we don't have infestations
[05:55] <spiv> I ask because when this branch gets merged to rocketfuel, you don't want an existing file to look like it's been deleted then re-added as a whole new file with no history.
[05:56] <mpt> So rocketfuel has 30-add-edit-package-infestation.txt.disabled, which presumably has history preserved by bzr mv
[05:57] <spiv> Right.  So if you don't want the non-disabled one, just delete it?
[05:57] <mpt> I've bzr added, then bzr rmed, 30-add-edit-package-infestation.txt
[05:57] <spiv> (and bzr rm it if you accidentally added it)
[05:57] <spiv> All good then :)
[05:57] <mpt> So I think I'm ok
[05:57] <spiv> I'll shut up and let you get on with it :)
[05:57] <mpt> except that bzr diff against rocketfuel now gives me a whole crapload of stuff that I didn't do
[05:57] <spiv> Hmm.
[05:58] <spiv> And presumably "bzr status" tells you you've changed stuff you didn't change?
[05:58] <mpt> yes
[05:58] <mpt> added: cronscripts/check-cve.py, database/schema/pending/HideObscureLanguages.sql, etc
[05:59] <spiv> Sounds like something wonky in the conversion from baz...
[06:00] <spiv> I *think* it may be the case that those are all old files that the baz2bzr script doesn't remove from the working copy.
[06:00] <spiv> i.e. a freshly converted branch is likely to have an unclean "bzr status", because of files that should be deleted are still lying around.
[06:01] <mpt> ok, that looks about right
[06:01] <mpt> all the files marked as "added:" are ones that don't exist in rocketfuel
[06:02] <spiv> Both of cronscripts/check-cve.py and database/schema/pending/HideObscureLanguages.sql aren't in current rocketfuel, so I think you might want to check each of these files, make sure they're obsolete, and "bzr rm" and/or "rm" them as appropriate.
[06:04] <spiv> mpt: Don't forget the "how long will it take me to answer that question" part of that calculation ;)
[06:04] <spiv> mpt: And the "how long witll it take me to answer the meta-question" question ;)
[06:04] <mpt> That's a dead-weight loss no matter which option I choose
[06:18] <stub> Ahh.... I seem to recall that the newly converted branch needs to be 'bzr reverted' to make it clean
[06:19] <mpt> I've fixed about four bugs on this branch, and I don't really want to fix them again
[06:20] <stub> If you start with a fresh converted branch though you could copy across the files you have modified. Hindsight will tell for sure :)
[06:22] <mpt> hmmmmmmm, that's a possibility
[06:22] <stub> You need to undo all the changes in those files you didn't touch though (bzr revert) rather than committing or you will be committing obsolete code
[06:22] <stub> (if you attempt to rescue your current branch that is)
[06:24] <mpt> If bzr log listed the files I'd changed with each commit, I could do that
[06:24] <mpt> but it doesn't
[06:24] <spiv> mpt: --verbose
[06:25] <mpt> ahhhh
[06:29] <mpt> So, I converted the branch, then merged rocketfuel as revno 2371
[06:29] <mpt> then fixed bugs in 2372, 2373, etc
[06:29] <mpt> So, bzr revert -r 2370?
[06:30] <dilys> Merge to devel/launchpad/: [r=stub]  New field in Build to store DEPWAIT current dependencies line, comments on Build fields (code is in soyuz production branch) (r3200: Celso Providelo)
[06:31] <stub> mpt: 'bzr uncommit' will uncommit the most recent commit. That is the only way I'm aware of to revert history apart from generating the inverse diff of the changes and applying that.
[06:33] <mpt> ok, I think I'll be converting the branch from baz again
[06:34] <stub> bzr uncommit can be run multiple times
[06:35] <stub> (so bzr uncommit; bzr uncommit; bzr uncommit; should get you back to where you started)
[06:35] <stub> Followed by a 'bzr revert' and 'bzr clean-tree' to give everything a good scrub
[09:05] <Martolod> hello all
[09:05] <Martolod> i have a lot of questions !
[09:06] <Martolod> i'm a translator of Gnome with CVS access and i would like to know how rosetta can be able to commit .po files ?
[09:06] <Martolod> i don't understand the utility of rosetta to translate gnome in fact
[09:06] <Martolod> anyone to explain to me ?
[09:10] <jamesh> Martolod: someone would need to export the PO files from rosetta and commit them to Gnome CVS
[09:10] <Martolod> manually ?
[09:11] <Martolod> i don't see the of rosetta so !
[09:11] <Martolod> but if i want to translate ubuntu for instance
[09:12] <jamesh> Martolod: for Ubuntu, we export PO files and generate language packs containing translations for everything in the desktop
[09:12] <Martolod> i don't need to have any cvs account to ubuntu, just a launchpad account and it's all ?
[09:12] <jamesh> yeah
[09:12] <Martolod> ok thank you.
[09:12] <Martolod> ah a last question !
[09:12] <jamesh> there are long term plans to make it easier for upstreams to pull info from rosetta
[09:12] <jamesh> if upstream is using bzr, the idea is that Rosetta would publish a branch containing up to date translations
[09:13] <Martolod> so if i translate with roseta a gnome application of Ubuntu, do the same application will be translated in the official gnome package ?
[09:13] <jamesh> which the developers would be able to merge from
[09:13] <Martolod> ok
[09:13] <jamesh> Martolod: only if someone imports the translations into Gnome CVS
[09:14] <jamesh> you'd need to check with your language team in the GTP about it
[09:14] <Martolod> yes i'm the leader of the team
[09:15] <Martolod> so i need to commit manualy and regularly po files from rosetta to gnome cvs
[09:15] <Martolod> it's what i wanted to know
[09:16] <Martolod> thank you.
[09:16] <jamesh> well, if the rest of the members of your team decided that they wanted to use Rosetta, and coordinated getting the translations back into Gnome CVS, then you could start using Rosetta
[09:29] <ddaa> hello
[09:30] <ddaa> So, I used to have a meeting on monday morning, with mgmt
[09:31] <ddaa> the problem is, SteveA is on travel
[09:31] <ddaa> and lifeless is on leave
[09:31] <ddaa> "Let's have a meeting, shall we?"
[09:32] <ddaa> "Mh, is there really a point?"
[09:32] <ddaa> "I'm not sure, but you know it's unprofessional to miss meetings"
[09:32] <ddaa> "I guess so. Let's have meeting in 27 mins"
[09:33] <carlos_> morning
[09:33] <ddaa> hey Carl
[09:33] <ddaa> mgn
[09:33] <ddaa> hey carlos_
[09:47] <carlos> spiv: hi
[09:47] <carlos> spiv: around?
[10:15] <ddaa> spiv: ping
[10:15] <ddaa> daf: ping
[10:16] <ddaa> jamesh: ping
[10:18] <carlos> daf: hi, could you give me some input on https://launchpad.net/products/rosetta/+bug/33020 ?
[10:18] <Ubugtu> malone bug 33020 in rosetta "Rosetta Imports page is not able to handle lot of entries" [Normal,Unconfirmed]  
[10:18] <carlos> jordi: and you?
[10:22] <cprov> carlos: hey carlos
[10:22] <cprov> carlos:  how are the automatic rosetta imports ?
[10:22] <cprov> carlos: can we consider it "released" ?
[10:29] <carlos_> daf: jordi: did you see my question? I got disconnected so I don't know if you answered
[10:58] <ddaa> duh... kiko is on holiday too...
[10:58] <ddaa> no management in sig
[10:59] <ddaa> in sight today, let's have a giant game of nettris!
[11:02] <daf> ddaa: pong
[11:02] <ddaa> hey daf
[11:02] <daf> carlos: looking at it now
[11:02] <carlos> daf: ok, thanks
[11:03] <ddaa> daf: can you spare some time to fix the ProductSeries.branch oops this week, please. It will become suddenly VERY painful next week.
[11:03] <ddaa> When bzr imports will be published.
[11:03] <daf> carlos: (1) only show the first 20 imports (2) batch it
[11:04] <daf> carlos: what do you think?
[11:04] <ddaa> daf: I'd really really like that bugfix to be up in production next week.
[11:04] <ddaa> I  need your help.
[11:04] <daf> ddaa: can you remind me what the bug number is?
[11:04] <carlos> daf: yeah, that's another option
[11:04] <carlos> (2)
[11:04] <carlos> I don't think we should implement (1)
[11:04] <carlos> as people would think their import is not there
[11:05] <daf> ok
[11:05] <daf> batching it is
[11:05] <carlos> do we have already a way to do batching on launchpad?
[11:05] <carlos> or should I implement my own stuff?
[11:05] <ddaa> daf: bug 32117
[11:05] <Ubugtu> malone bug 32117 in launchpad "Template productseries-hctstatus-core.pt is wrongly calling getPackageName" [Normal,Confirmed]  http://launchpad.net/bugs/32117
[11:05] <carlos> I think mpt said that we are going to have a standard way to do batching on launchpad, but I don't have more details
[11:06] <daf> ddaa: thanks
[11:07] <daf> ddaa: I can work on that today
[11:07] <ddaa> daf: fantastic
[11:07] <daf> ddaa: I will let you know how it's going
[11:07] <ddaa> daf: there's a bit of UI design involved, don't be afraid being creative. The old UI sucked.
[11:07] <ddaa> daf: but timeliness is of the essence.
[11:08] <carlos> mpt: hi
[11:08] <daf> ddaa: noted :)
[11:08] <mpt> hi carlos
[11:08] <carlos> mpt: I need to implement batching for the page at /rosetta/imports
[11:08] <carlos> mpt: do we have a standard way to do that?
[11:09] <carlos> or should I do my own stuff ?
[11:09] <mpt> carlos, no :-(
[11:09] <carlos> I think you said that we are going to have a way to do it
[11:09] <carlos> mpt: https://launchpad.net/malone/bugs/33020
[11:09] <Ubugtu> malone bug 33020 in rosetta "Rosetta Imports page is not able to handle lot of entries" [Major,Confirmed]  
[11:09] <carlos> mpt: could you take a look to it?
[11:09] <daf> carlos: we do have standard ways of doing batching
[11:09] <carlos> mpt: daf suggested to solve it using batching
[11:10] <mpt> carlos, yes, but the design hasn't been finished yet, let alone the implementation
[11:10] <mpt> http://wiki.launchpad.canonical.com/StandardizedBatching
[11:10] <daf> ok
[11:11] <daf> in the long term, there will be One True Batching Method
[11:11] <daf> as designed by mpt
[11:11] <daf> in the short term, we have some infrastructure for doing batching
[11:11] <daf> and the imports page can use that
[11:11] <carlos> mpt: could you give me some input on that bug, please?
[11:11] <carlos> daf: Where could I see the interface?
[11:11] <daf> carlos: look at DistributionAllPackagesView for an example
[11:11] <carlos> ok
[11:11] <carlos> daf: thanks
[11:12] <daf> and the corresponding distribution-allpackages.pt template
[11:12] <daf> de nada
[11:14] <mpt> carlos, I have nothing useful to add to that bug report
[11:14] <sivang> morning shiney people :)
[11:14] <mpt> shiny people??
[11:16] <mpt> carlos, mainly because I haven't sat behind you or jordi and watched the imports happening, so I have no idea how it works. Perhaps you can show me at the sprint.
[11:16] <carlos> mpt: sure
[11:16] <carlos> mpt: anyway, I need to implement something as the page is broken atm with the amount of entries from dapper
[11:17] <carlos> and we don't have all packages imported...
[11:17] <carlos> I will go for the batch solution as it's the easier to implement
[11:33] <sivang> mpt: why not shiney?
[11:47] <ddaa> is there a policy (or not?) about deleting old bzr branches from chinstrap?
[11:48] <Kinnison> jamesh: ping?
[11:51] <cprov> see you tonight ...
[11:52] <mpt> sivang, Launchpad's not shiny yet
[11:55] <sivang> mpt: :)
[12:36] <jordi> oh dude
[12:37] <jordi> carlos: haven't had time to think about it
[12:37] <jordi> hmm.
[12:37] <carlos> jordi: hi
[12:37] <jordi> I just arrived from Bruxelles
[01:17] <daf> mpt: https://launchpad.net/people/daf -- why is the "Registered Details" bit floating off to the right?
[02:38] <carlos> stub: hi
[02:38] <carlos> around?
[02:39] <stub> carlos: yes
[02:39] <carlos> stub: could you run a SQL sentence on production for me, please?
[02:39] <carlos> SELECT COUNT(*) FROM TranslationImportQueueEntry;
[02:43] <stub> carlos: 1434
[02:43] <carlos> stub: thanks
[03:40] <daf> carlos: how's the batching?
[03:41] <carlos> daf: bad, we need other changes before that. I'm finishing an email with an analysis of the problem and the solution I'm going to take. Will ping you when it's done to get some input from you
[03:42] <daf> sounds like a good plan
[03:42] <daf> can you give me some input on this bug?
[03:42] <daf> https://launchpad.net/products/rosetta/+bug/29944
[03:42] <Ubugtu> malone bug 29944 in rosetta "Import queue: ForbiddenAttribute: pofile oopses when importing gnome-panel for Georgian" [Normal,In progress]  
[03:42] <daf> should the 'pofile' attribute be in the interface?
[03:44] <carlos> daf: yes, I guess that's the problem
[03:44] <daf> ok
[03:44] <daf> thanks
[03:44] <carlos> daf: anyway, the changes I'm planning to do will touch those files and that logic so I can fix that bug at the same time
[03:45] <daf> oh, cool
[03:45] <daf> I'll assign it you then
[03:45] <daf> oh, it already is
[03:45] <daf> never mind
[03:45] <carlos> daf: yeah ;-)
[03:45] <daf> I thought it was assigned to me for some reason
[03:47] <carlos> daf: it was
[03:47] <carlos> I changed it this weekend
[03:47] <daf> ok, that will be why
[03:47] <daf> no hay problema
[04:06] <G0SUB> how do I get my tranlation team to be the official tranlation team for my language? https://launchpad.net/rosetta/groups/ubuntu-translators/
[04:08] <carlos> G0SUB:  please, read https://wiki.ubuntu.com/RosettaFAQ
[04:08] <G0SUB> thanks
[04:09] <ddaa> spiv: jamesh: ping
[04:12] <soumyadip> any admins around ?
[04:13] <ddaa> it depends on which kind of admin action your require
[04:14] <soumyadip> well I seem to have duplicate accounts at launchpad
[04:15] <soumyadip> one registered as soumyadip@softhome.net and the other as soumyadip.modak@gmail.com
[04:15] <soumyadip> now I followed the procedure to merge the two accounts, yet I cannot find gmail.com email address in the list of addresses for soumyadip@softhome.net
[04:15] <ddaa> if you have still access to the other email address, there's a feature to merge them
[04:16] <soumyadip> nor can I add that address
[04:16] <soumyadip> I have access to both the addresses
[04:16] <ddaa> carlos: ^ I think you know about merging
[04:17] <carlos> ddaa: well, my knowledge is limited...
[04:17] <carlos> soumyadip: did you get the emails in both accounts to do the merge?
[04:18] <carlos> soumyadip: I'm not sure if you will get two of them or just one to the address in the account you are going to merge into your main account
[04:19] <soumyadip> well I did receive a mail at my gmail.com account, which I'm trying to merge into the softhome.net account
[04:19] <soumyadip> carlos, and I followed the instructions, and clicked the link
[04:19] <carlos> soumyadip: and you didn't get any timeout or error, right?
[04:19] <soumyadip> nope
[04:19] <carlos> then the merge should be done soon
[04:20] <soumyadip> my gmail.com account probably points to something like people/soumyadip-modak-merged
[04:20] <carlos> I think it's done by a cron script after you confirm it, but I'm not sure, How long since you confirmed it?
[04:20] <hanover> what's up with launchpad? I have to reset my password every time I want to login.
[04:21] <soumyadip> carlos, well about 15 minutes ago
[04:22] <jblack> carlos: do you have a launchpad-dependancies package installed?
[04:22] <carlos> jblack: yes, I do
[04:22] <jblack> You're on breezy, right?
[04:23] <carlos> soumyadip: then it should be merged soon, if it's not merged after an hour or so, ping us again (better if you mail to launchpad-users)
[04:23] <carlos> jblack: no, dapper
[04:23] <jblack> lifeless: What are you doing here? You should be.. off doing things.
[04:23] <soumyadip> carlos, ok thanks a lot
[04:23] <jblack> mind mailing me your sources.list?
[04:24] <carlos> stub: around?
[04:24] <carlos> jblack: just a second...
[04:25] <stub> carlos: yes
[04:25] <carlos> stub: could you take a look at soumyadip's problem?
[04:25] <carlos> stub: I did a search and see weird things...
[04:25] <carlos> stub: https://launchpad.net/people/?name=soumyadip&searchfor=all
[04:25] <carlos> stub: the one with 'merged' on the name is not valid
[04:26] <carlos> stub: it gives a 404 error
[04:27] <stub> An already merged account. It should not be appearing in the search results.
[04:28] <soumyadip> stub, yup, I was merging that account into the first one
[04:30] <soumyadip> stub, anything that I have to do now ?
[04:30] <hanover> bah... i just want to be able to login
[04:30] <soumyadip> I mean when can I add the email addy of the -merged account into the original account ?
[04:31] <carlos> hanover: It works for me without problems...
[04:31] <carlos> hanover: could be a problem with your browser's cookies?
[04:32] <hanover> i've had to reset my password three times today... I can believe I typo'd the same thing twice, but not 6 times or so...
[04:32] <stub> soumyadip: Do you know if anyone else has tried to fix your problem? Your account data is currently in a theoretically impossible state and I'm trying to work out how that happened.
[04:32] <carlos> hanover: but once you are logged, you don't need to loggin again...
[04:33] <carlos> daf: email sent, could you take a look, please?
[04:33] <soumyadip> stub, eek !! no, I just came here and asked when I couldn't add my email address to the first account
[04:33] <carlos> jblack: upps, I forgot your request. Just a second....
[04:33] <daf> hi Steve
[04:33] <daf> carlos: sure
[04:33] <SteveA> hello
[04:33] <stub> Ooh...  I wonder what happens if you respond to an email address validation message for an account that has since been merged into another one?
[04:33] <SteveA> ddaa: hello
[04:33] <jblack> carlos: thanks
[04:33] <soumyadip> stub, you can maybe remove both the accounts, I'll re register if necessary
[04:33] <hanover> hmmmm... just cleared cookies and cache... no joy. Also getting oopses when trying to submit anything
[04:33] <ddaa> SteveA: hello, the meeting today was fun
[04:34] <stub> soumyadip: I've fixed it
[04:34] <carlos> hanover: could you give us the oops number?
[04:34] <carlos> hanover: that way we can know what's going on
[04:34] <soumyadip> stub, hey thanks a ton
[04:35] <hanover> carlos: OOPS-58C278
[04:35] <Ubugtu> https://chinstrap.ubuntu.com/~jamesh/oops.cgi/58C278
[04:35] <hanover> getting a few other numbers too
[04:35] <hanover> but yeah, something is hosed with FF... moz gets me in.
[04:35] <carlos> hanover: just one of them is enough
[04:36] <carlos> hanover: that oops number is a page not found error
[04:41] <soumyadip> guys, I don't know if this question belongs here or not, but I'll ask anyway
[04:41] <soumyadip> I maintain a few packages in Debian
[04:41] <soumyadip> Can I take them over in Ubuntu too ?
[04:41] <carlos> jblack: sent
[04:42] <carlos> soumyadip: is better if you ask at #ubuntu-devel
[04:42] <soumyadip> carlos, ok, thanks for the tip
[04:42] <carlos> we provide the tools but we don't develop Ubuntu itself
[04:42] <hanover> I'm thinking it shouldn't give a page not found in response to clicking submit...
[04:43] <hanover> carlos: hmmm... what's a 58D326?
[04:43] <hanover> that's what i'm getting now....
[04:43] <jblack> carlos: thanks
[04:44] <carlos> hanover: right, I forgot the 'POST' part
[04:44] <carlos> hanover:  I think that's a bug on malone, could you file a bug with the OPs code?
[04:44] <hanover> ahh... ;)
[04:44] <hanover> i have one filed for the first one. Should I do another for the second code?
[04:45] <hanover> or just ammend the previous one?
[04:45] <carlos> hanover: I cannot see the second one 
[04:45] <hanover> you can't see the 58D326?
[04:45] <carlos> just wait some extra minutes until our system syncs with the erros so I can know what's going on with it
[04:46] <carlos> hanover: yes, there is a delay between the time you see it and when we can see it
[04:46] <hanover> stupid system... hanover SMASH ;)
[04:47] <carlos> hanover: it's only 5 minutes dude ;-)
[04:47] <hanover> dude... i'm in IT... I have no patience ;)
[04:47] <jblack> carlos: Are you sure you have a package called launchpad-dependancies, and that you ran apt-get install to get it?
[04:48] <carlos> carlos@aragorn:~$ apt-cache policy launchpad-dependencies
[04:48] <carlos> launchpad-dependencies:
[04:48] <carlos>   Installed: 0.4
[04:48] <carlos>   Candidate: 0.4
[04:48] <carlos>   Version table:
[04:48] <carlos>  *** 0.4 0
[04:48] <carlos>         500 http://es.archive.ubuntu.com dapper/multiverse Packages
[04:48] <jblack> hmm. maybe you got it in breezy.
[04:48] <carlos>         100 /var/lib/dpkg/status
[04:48] <carlos> jblack: dapper, this machine is installed from the scratch with dapper
[04:50] <jblack> aha.
[04:50] <jblack> I bet it would help if I spelled dependencies right.
[04:51] <hanover> see... I've always said that if you get a word, or a number 99% right, a computer should just figure it out... do what I meant, not what I said. Ya know?
[04:52] <jblack> I've always spelled the world dependancies, which is a valid, but minimalized, spelling of dependencies
[04:52] <carlos> hanover: same problem as before
[04:52] <hanover> like if I dial 214-555-1234, but meant 214-555-1231, it should dial my ISP and not 90+ hot chix0rs
[04:53] <carlos> hanover: you can add that opps code to the same bug report
[04:53] <hanover> okie dokies
[04:57] <hanover> updated
[04:58] <hanover> guess I'll forget trying to submit that bug for now...
[04:58] <hanover> carlos: thx for the help
[04:58] <hanover> also gotta figure out why firefox is borked
[04:59] <hanover> did you try ff, or another browser?
[05:01] <hanover> well, ain't FF, at least not 1.5... a different machine works using a different account...
[05:01] <hanover> grrrr....
[05:01] <carlos> hanover: hmm No idea, note that on the bug report, perhaps it's a problem with your browser installation...
[05:03] <hanover> maybe.... cookie is getting set... it's the site that says my user/pass don't match
[05:05] <carlos> hanover: well, the error is not related with authentification but with a 404 page
[05:06] <daf> carlos: hmmmm
[05:06] <daf> carlos: how do you calculate which queue a request belongs to?
[05:06] <carlos> SteveA: hi, did you get my review reply? I had some mail problems last week so I'm not sure if it was delivered or not
[05:06] <carlos> daf: when? after it's attached to the system?
[05:07] <hanover> well, i'm still on 1.0.7... guess i could try updating it
[05:07] <daf> "Both are represented in our data model as a single table and whether a
[05:07] <daf> entry belongs to one queue or to the other is calculated on load time.
[05:07] <daf> "
[05:07] <hanover> but i can login to other sites fine
[05:07] <daf> carlos: how do you make that calculation?
[05:07] <carlos> daf: did you read the whole email?
[05:07] <carlos> daf: ITranslationStatusQueueEntry.status that it's a RosettaImportStatus DB schema
[05:08] <daf> that's the new design, right?
[05:08] <daf> how does the view do it right now?
[05:09] <carlos> daf: yes, the new design
[05:09] <carlos> daf: we have a ITranslationStatusQueueEntry.is_blocked for the blocked list
[05:09] <daf> ok, then how about this:
[05:10] <carlos> daf: and the others, depend on getting a value from ITranslationStatusQueueEntry.import_into
[05:10] <daf> do ORDER BY is_blocked
[05:10] <daf> and just do the simple batching
[05:10] <carlos> daf: no, the blocked ones are not an issue, the problem are with hte ones that are ready to be imported and the ones that need review
[05:10] <daf> or ORDER BY (import_into IS NOT NULL, is_blocked)
[05:11] <carlos> daf: import_into is python code 
[05:11] <daf> ah
[05:11] <daf> well, your plan sounds ok; I'm just trying to work out if there's something simpler we can do
[05:12] <daf> this might be a stupid question, but:
[05:12] <carlos> daf: yeah, I tried that too...
[05:12] <carlos> daf: tell me
[05:12] <daf> we have one table -- why do we show it as two queues?
[05:12] <daf> is it so the reviewers can see the ones which are blocked?
[05:12] <carlos> daf: to represent different status to the user
[05:12] <carlos> daf: yes
[05:12] <daf> ok
[05:12] <carlos> daf: and the users know the status of their import request
[05:13] <carlos> it's a way to group the imports
[05:13] <daf> I suggest: have /imports use one batched table
[05:13] <daf> the status is shown in a clear way
[05:13] <daf> it's sorted by date
[05:13] <daf> and status
[05:14] <daf> have a separate page for reviewers
[05:14] <daf> it only shows items that need to be reviewed
[05:15] <hanover> ls
[05:15] <daf> it can use the same view code
[05:16] <daf> how does that sound?
[05:16] <carlos> daf: and links to jump to a concrete status? (changing the offset not going to a new page)
[05:16] <carlos> daf: so you can go directly to the blocked ones, or the deleted ones, etc... ?
[05:17] <carlos_> daf: sorry, my link went down
 it only shows items that need to be reviewed
 daf: and links to jump to a concrete status? (changing the offset not going to a new page)
 daf: so you can go directly to the blocked ones, or the deleted ones, etc... ?
[05:17] <daf> hmm
[05:17] <carlos> hmm, it's not down
[05:17] <daf> I see two use cases:
[05:17] <daf>  - "why hasn't my PO file been imported yet?"
[05:17] <daf>  - "I want to review PO files for import"
[05:18] <carlos> right
[05:18] <daf> for the first one, the user needs to be able to find their PO file in the list
[05:18] <carlos> I like the idea of a single table for users
[05:18] <carlos> it's easier for them, yes
[05:18] <daf> why don't we add a page <pofile>/+import-status?
[05:19] <daf> /products/foo/1.0/+translations/foo/cy/+import-status
[05:19] <carlos> daf: that's what I suggested on the bug report
[05:19] <daf> heh :)
[05:19] <carlos> daf: but I don't think we should use that path yet
[05:19] <carlos> let's fix first the main import queue
[05:19] <daf> or perhaps put it on POTemplate
[05:19] <carlos> daf: POTemplate is better or even sourcepackage/productseries
[05:19] <daf> yeah, I agree
[05:20] <carlos> daf: there are use cases where we don't have an IPOTemplate
[05:20] <daf> I think right now, it's more important to get the reviewer use case working
[05:20] <carlos> right
[05:20] <daf> and we can look at making it easier to see the import status for some specific PO file later
[05:20] <carlos> the single queue suggestion
[05:20] <carlos> would work for both use cases
[05:20] <daf> ok
[05:21] <daf> one question:
[05:21] <carlos> we could improve it later
[05:21] <daf> what's the difference between WAITING and REVIEW?
[05:21] <carlos> WAITING for being imported by poimport script
[05:21] <daf> hmm, perhaps APPROVED?
[05:21] <carlos> REVIEWING -> waiting for a rosetta expert to review it
[05:22] <carlos> or that our automatic system is able to "approve" it automatically due some related change done (for instance two imports of cy.po for evolution, the first is fixed by jordi and the second one is automatically handled by our code following jordi's review for the first entry)
[05:23] <carlos> daf: yes, it's better. Thanks
[05:23] <daf> and perhaps NEEDS_REVIEW instead of REVIEWING
[05:23] <daf> I do like the data schema change
[05:24] <daf> I just want to find the quickest way to make things work again :)
[05:24] <carlos> me too, it simplifies a bit our data model and exposes to the users the whole import process
[05:24] <carlos> me goes with NEEDS_REVIEW
[05:24] <daf> right
[05:25] <daf> cool, so I'll reply to the list with a summary of what we discussed
[05:25] <carlos> daf: ok, perfect, thank you for your input!
[05:25] <daf> de nada
[05:26] <jordi> carlos: so I was thinking about the timeout
[05:26] <carlos> daf: my only concern is to show a lot of information on that table so it overflows like current one
[05:26] <jordi> would just showing multiple pages help at all?
[05:26] <jordi> ie, 300 items, 1-50, 51-100, etc?
[05:26] <carlos> jordi: yes, but not with our current code
[05:26] <jordi> nod
[05:27] <carlos> jordi: that's what we are going to do when the batching is implemented
[05:27] <jordi> ok
[05:27] <carlos> jordi: there is a workaround for the timeout but it's more work for you :-P
[05:27] <carlos> I did it this morning
[05:27] <jordi> oh no
[05:27] <carlos> but it's too boring ;-)
[05:27] <LarstiQ> moin
[05:27] <carlos> jordi: it's a matter of guessing the id 
[05:27] <carlos> then, you get the edit form per entry
[05:27] <LarstiQ> daf: were you at fosdem too, or did I mistake someone for you?
[05:28] <daf> LarstiQ: yes, I was
[05:28] <daf> LarstiQ: did we meet?
[05:28] <carlos> you submit it, get a timeout (the submit is saved anyway) and go to guess the next entry :-P
[05:28] <jordi> carlos: lol
[05:28] <LarstiQ> daf: I'm afraid not, just passed each other a couple of times
[05:28] <jordi> carlos: you must be kidding me :)
[05:28] <carlos> jordi: then I realized that we had already more than 1400 entries and give up and went to cook a final solution
[05:29] <jblack> Ok. I need some time from a launchpad dev that also knows how to build debs. I have some new packages ready, but could use a vetting.
[05:29] <jordi> oh :)
[05:29] <jordi> carlos: thanks for the consideration ;)
[05:30] <carlos> jordi: https://launchpad.net/rosetta/imports/+blocked
[05:30] <carlos> jordi: I fixed already glib ;)
[05:31] <jordi> that'll be needed again with 2.10.1, right?
[05:31] <carlos> jordi, daf: what do you think about the idea of showing deleted and already imported files? should we have them for 15 o 7 days?
[05:31] <daf> LarstiQ: ah, oops
[05:31] <carlos> jordi: I guess that the answer is yes...
[05:31] <jordi> carlos: I'd like that.
[05:31] <daf> carlos: hmm, good question
[05:31] <daf> carlos: I think it would be useful, but I think the last 2 or 3 days should be enough
[05:32] <daf> carlos: reply sent to the list
[05:32] <daf> carlos: please make sure I didn't say anything dumb :)
[05:32] <carlos> jordi: do you agree?
[05:32] <carlos> daf: ok, thanks :-D
[05:32] <daf> jordi: I saw a request for an Arabic team
[05:33] <jordi> daf: I just saw it myself
[05:33] <jordi> I had no access to email duribng the weekend
[05:33] <daf> yeah, I just saw it this morning
[05:33] <jordi> a silly dhclient was running inmy server and I got an internal ip change
[05:33] <daf> oops
[05:33] <jordi> yeah man
[05:33] <daf> I was just ignoring mail over the weekend :)
[05:33] <jordi> I tried not to
[05:33] <jordi> failed miserably :)
[05:34] <daf> ha
[05:34] <jordi> next year I'm not going to even carry a laptop to fosdem
[05:34] <jordi> useless tool there
[05:34] <carlos> daf: about the status order... What do you think about: APPROVED, IMPORTED, FAILED, NEEDS_REVIEW, BLOCKED
[05:34] <carlos> jordi: ? ^^^
[05:34] <daf> don't forget DELETED
[05:34] <carlos> oh, right
[05:35] <daf> fine by me, but Jordi's going to be using it more than me
[05:35] <jordi> hmm, why is NEEDS_REVIEW after APPROVED?
[05:35] <jordi> and, how do I use these?
[05:36] <carlos> APPROVED, IMPORTED, DELETED, FAILED, NEEDS_REVIEW, BLOCKED
[05:36] <carlos> jordi: it's the way to show all the entries on the import queue
[05:36] <carlos> so we get the whole list of entries
[05:36] <carlos> sorted by date and status (the list I just gave you)
[05:37] <jordi> nod
[05:37] <jordi> ok
[05:37] <jordi> hm
[05:37] <carlos> you will only use the NEEDS_REVIEW part, as a second step, you will have a page with just the NEEDS_REVIEW entries
[05:37] <jordi> but will each status be in a different list block?
[05:37] <jordi> carlos: aha
[05:37] <jordi> ok
[05:37] <carlos> so the list will be batched on a set of entries from the final list we get
[05:37] <jordi> I guess that makes sense.
[05:38] <carlos> jordi: just one table with different visual tags to see the different status
[05:39] <jordi> shouldn't I see needs review first, as it's the one I'm supposed to work on?
[05:39] <carlos> jordi: anyway, after it's implemented, if you want to change the order will be easy to be done
[05:39] <jordi> yeah, I was thinking just that
[05:39] <jordi> I'll trust your judgement for now. My brain is fried after the travelling, I really need a nap
[05:39] <carlos> jordi: it's a one line change on the sql query
[05:39] <jordi> nod
[05:40] <carlos> jordi: ok ;-)
[05:40] <jordi> I'll answer the Arabic and Bengali stuff later on
[05:40] <jordi> laters :)
[05:40] <carlos> jordi: btw... I remember that you said something about Akan
[05:40] <carlos> but I don't remember what...
[05:40] <carlos> and I did nothing...
[05:41] <jordi> carlos: akan is currently assigned to "aka"
[05:41] <jordi> it should be "ak"
[05:41] <SteveA> carlos: replied
[05:41] <jordi> Akkasomething is our current "ak", its wrong, should be "akk"
[05:41] <jordi> hey SteveA 
[05:42] <carlos> jordi: hmmm I don't have access to change that, you need a launchpad admin
[05:42] <carlos> jordi: I have exactly the same rights you have
[05:42] <carlos> jordi: when the imports issues are fixed, I will fix that permission problem
[05:42] <carlos> SteveA: thanks
[05:43] <jordi> ok
[05:43] <jordi> carlos: so we need to ask stub?
[05:43] <jordi> or reassign to stub, or whatever
[05:43] <jordi> ther'es a bug in malone
[05:44] <carlos> jordi: or SteveA, or lifeless or anyone member of https://launchpad.net/people/admins
[05:45] <jblack> lifeless is off today.
[05:51] <jordi> carlos: so that can be done via the ui?
[05:51] <jordi> SteveA: can you have a look at this?
[05:51] <carlos> jordi: yes
[05:51] <carlos> jordi: it's a matter of edit the appointed translationteam
[05:52] <carlos> jordi: appoint a translation team for akk and remove the one for ak
[05:52] <SteveA> jordi: can i look at what?
[05:52] <jordi> SteveA: "ak" Should be Akan, not "aka"; "akk" should be Akkadian instead.
[05:54] <SteveA> jordi: i can't look at this today.
[05:55] <jordi> SteveA: ok. I can mail the list.
[06:03] <carlos> see you guys!
[06:09] <sladen> can somebody please mark 33056 as private, quickly
[06:10] <Kinnison> sladen: done
[06:10] <Kinnison> sladen: why didn't you file it as private?
[06:13] <sladen> Kinnison: because I forgot the little ticky box and there's no preview.  It was actually send to security@u.com 2 weeks ago;  but didn't get any response...
[06:14] <sladen> does Malone talk to the  flyspray  bug tracker yet
[06:15] <bradb> not yet
[06:16] <bradb> bug 28738
[06:16] <Ubugtu> malone bug 28738 in malone "malone doesn't know about the Flyspray BTS" [Minor,Confirmed]  http://launchpad.net/bugs/28738
[06:17] <sladen> bargin
[06:26] <sladen> ah, after 5 minutes of hunting  "Bug Visibility" -> Mark as private
[06:26] <sladen> could be made more discoverable
[06:28] <bradb> there should be a change link right next to the visibility setting, IMHO
[06:29] <bradb> sort of a put-an-option-where-the-user-is-likely-to-trip-over-it approach, crazy as it may sound :P
[06:30] <dilys> Merge to devel/launchpad/sourcecode/buildbot/: [trivial]  Disable noisy DeprecationWarning (r159: Stuart Bishop)
[06:44] <dooglus> I just raised a bug in malone.
[06:44] <dooglus> and then added it to the gnome BTS
[06:44] <dooglus> at around the same time, someone else linked it to the GNOME BTS too
[06:45] <dooglus> so now it has two identical links to the GNOME BTS
[06:45] <dooglus> is this a known issue?
[06:46] <bradb> dooglus: bug 4594
[06:46] <Ubugtu> malone bug 4594 in malone "Shouldn't be able to add duplicate bug watches" [Normal,Confirmed]  http://launchpad.net/bugs/4594
[06:47] <dooglus> thanks
[06:47] <bradb> no prob
[07:24] <elmo> ddaa: ping
[07:26] <ddaa> elmo: pong
[07:28] <elmo> ddaa: marambio is almost out of disk space
[07:28] <ddaa> oh, that's interesting
[07:29] <ddaa> elmo: when can I start running multi-weeks jobs again?
[07:29] <ddaa> gimp is still outstanding...
[07:31] <elmo> ddaa: sorry, you should be safe now
[07:32] <ddaa> elmo: also I know there's a ton of shit in my account on chinstrap, I'll rm it when the bzr imports are live.
[07:33] <ddaa> I had to jump through a bunch of hoops to get the bzr branches from escudero to galapagos and neumayer
[07:36] <elmo> no problem
[09:09] <JohnFlux> Hey all
[09:10] <JohnFlux> What are the chances of launchpad becoming open source?
[09:18] <sladen> can somebody with godmode mark two private bugs as duplicates, 33056 and 33070
[09:25] <bradb> sladen: if you can see those bugs, you can mark them as dupes
[09:26] <bradb> sladen: You can edit anything about a bug, if you're logged in, and it's otherwise visible to you.
[09:27] <jblack> Any launchpad devs around that happen to be ubuntu/debian devs as well? I made up launchpad packages that do dependancies and would like gobs of input
[09:34] <sladen> Kinnison: :)
[09:51] <lifeless> pqm going down for a manual merge.
[09:51] <lifeless> be ~30
[10:04] <ddaa> lifeless: be sure to run the merge test suite in production
[10:04] <lifeless> ddaa: dude, SUCK EGGS
[10:05] <lifeless> kthnxbye
[10:05] <ddaa> right I'll get lost
[10:07] <Omni|Work> There is a spam project on Launchpad.
[10:07] <Omni|Work> https://launchpad.net/products/launchpad/+bug/32990
[10:07] <Ubugtu> malone bug 32990 in launchpad "Spam project on Launchpad (fatalnetwork)" [Normal,Unconfirmed]  
[10:08] <LarstiQ> I'll mail that to launchpad-users
[10:09] <bradb> thanks LarstiQ 
[10:09] <Omni|Work> Thanks.
[10:09] <LarstiQ> bradb: is that the right approach?
[10:10] <bradb> LarstiQ: Yeah. It's a good fallback if noone seems to be around that can help in #launchpad.
[10:11] <LarstiQ> k
[12:01] <mpt__> daf, it's a centered table -- the margin on the left is the same as the margin on the right
[12:02] <tolgam> Hello ! I'm trying to report a bug for gdm (in dapper) but it seems it's not using malone. What should I do then ?
[12:02] <tolgam> please :)