[00:32] <longsleep> Anyone knows why 'snapcraft register-key' fails with 'Key registration failed: The account-key-request assertion is not valid.' for me?
[18:20] <Rillian_> hello


[03:40] <rameshh> hi
[03:40] <JoseAntonioR> hi, rameshh! :)
[03:40] <rameshh> when is ubuntu12.10 release?
[03:41] <JoseAntonioR> rameshh: in 13 days exactly, October 18
[03:42] <rameshh> ok jose
[03:42] <rameshh> thanku
[03:42] <JoseAntonioR> may be 12 days for you, depending on your time zone
[03:42] <JoseAntonioR> no problem
[03:42] <rameshh> how to update ubuntu 12.10?
[03:42] <rameshh> i am using ubuntu12.04
[03:43] <JoseAntonioR> rameshh: once it's released, you can open a terminal and issue the command 'do-release-upgrade' with no quotes ('')
[03:43] <rameshh> ohh thanku very much
[03:43] <JoseAntonioR> no problem
[03:44] <rameshh> In release i have to mention 12.10?
[03:44] <JoseAntonioR> rameshh: nope, just do-release-upgrade
[03:44] <rameshh> ok ok
[03:49] <JoseAntonioR> hey, ejat! will I see you at uds again? :)
[03:49] <ejat> JoseAntonioR: :)
[03:50] <ejat> JoseAntonioR: r u going ?
[03:50] <JoseAntonioR> yep
[03:51] <ejat> c u there ...
[03:51] <JoseAntonioR> yay
[03:54] <ejat> JoseAntonioR: did u manage to get the uds-q crew photo ?\
[03:54] <JoseAntonioR> ejat: nope, at all
[03:54] <ejat> :(
[03:54] <JoseAntonioR> let me ask cjohnston who may have it
[03:54] <ejat> ok tx
[03:54] <JoseAntonioR> np
[08:39] <locodir-u11ser> hi


[00:34] <slangasek> bkerensa: makes sense
[17:15] <albrigha> bkerensa, ping
[19:49] <MarkDude> bkerensa, ping2
[19:49]  * MarkDude wants folks to know that is not just 2- he meant ping *squared*
[19:49]  * MarkDude waits his turn....
[19:50] <blkperl> ping6


[01:50] <ubotu> New bug: #148338 in malone "Duplicate projects "kdemultimedia" and "KDE Multimedia"" [Undecided,New]  https://launchpad.net/bugs/148338
[06:46] <stdin> bugs.lp.net/~you
[06:46] <spiv> bdmurray: https://bugs.launchpad.net/people/+me/+commentedbugs?orderby=-date_last_updated  ?
[06:46] <stdin> or that longer version, yeah :p
[06:47] <spiv> (Which you can get to from the "List commented bugs" link on your bugs page, then sort by "recently changed")
[06:48] <bdmurray> Okay, I found the bug but come to find out I didn't comment on it just set the status and importance.
[06:48] <bdmurray> I found it via other means
[08:48] <carlos> morning
[08:49] <Hobbsee> morning carlos!
[09:16] <jonathan_> hi
[09:16] <jonathan_> ls
[09:16] <jonathan_> sorry
[09:17] <jonathan_> I have questions regarding gobby
[09:25] <ubotu> New bug: #148425 in rosetta "Report import warnings to uploader" [Undecided,New]  https://launchpad.net/bugs/148425
[09:25] <ubotu> New bug: #148426 in launchpad "packages should not be in dep-wait when they are superseded" [Undecided,New]  https://launchpad.net/bugs/148426
[09:40] <ubotu> New bug: #148430 in rosetta "Language pack selection must be set automatically" [High,Confirmed]  https://launchpad.net/bugs/148430
[09:40] <ubotu> New bug: #148431 in rosetta "Language pack export code should use always the start time to refer to that export" [High,Confirmed]  https://launchpad.net/bugs/148431
[09:43] <yeager> what happened with the new xubuntu-docs?
[09:45] <ubotu> New bug: #148433 in rosetta "Allow differerent language packs running at the same time" [High,Confirmed]  https://launchpad.net/bugs/148433
[09:58] <jonathan_> hi yeager sorry i don't know launchpad yet
[10:00] <mdke> yeager: in what way?
[10:01] <carlos> yeager: they are waiting to be approved, we just got them yesterday
[10:02] <carlos> mdke: do you know whether all them must be approved or there is anyone that should be ignored like in ubuntu-docs and kubuntu-docs ?
[10:02] <carlos> mdke: https://translations.edge.launchpad.net/ubuntu/gutsy/+source/xubuntu-docs/+imports
[10:02] <carlos> mdke: https://translations.launchpad.net/ubuntu/gutsy/+source/xubuntu-docs/+imports
[10:03] <mdke> yeah, I saw them. I think they are all ok to be approved
[10:06] <carlos> and the ones available today could be removed, right?
[10:06] <mdke> yeah
[10:06] <mdke> carlos: btw, for the multiple template export, do you think it's appropriate for me to ask for them to be in the format template/lang.po rather than template/template-lang.po?
[10:06] <mdke> to be consistent with the single template export
[10:07] <carlos> mdke: seb128 already asked me for it and I agree is doable
[10:07] <carlos> mdke: well, isn't single template export doing that now too?
[10:07] <carlos> mdke: please, look whether seb reported that bug already and report it if is not yet there
[10:08] <carlos> we changed recently the way exports are stored in the tarball
[10:08] <mdke> oh, I don't know if single template has changed recently; it used to do lang.po
[10:08] <carlos> yeah, but we changed all the export infrastructure recently
[10:09] <carlos> I think it was last moth
[10:09] <mdke> aha
[10:10] <mdke> ok, i'll check for a bug
[10:12] <carlos> thanks
[10:13] <carlos> mdke: about xubuntu-docs... I wonder what happens with those templates, isn't too late now for non language pack translations?
[10:17] <yeager> carlos: deadline is tomorrow so we poor translators doesn't have much time left for xubuntu-docs
[10:17] <carlos> yeah, that's my point...
[10:17] <carlos> anyway, I'm going to cheat the import queue to get this imported right now..
[10:23] <yeager> thanks carlos
[10:23] <yeager> btw.. fast-user-switch-applets is still 0 strings
[10:26] <carlos> that's due to our performance problem with imports, we are going to send an announcement about that later this week
[11:26] <Hobbsee> morning sabdfl
[11:26] <sabdfl> howdy
[11:30] <killercow> Hi,
[11:30] <killercow> would this be the correct channel to get some help on setting up the launchpad account and bazaar settings for my project?
[11:31] <killercow> I've been strugling to get my code into bazaar hosted by launchpad.net
[11:37] <Fujitsu_> killercow: This is the correct channel.
[11:37] <Fujitsu_> What issues are you having?
[11:39] <killercow> I setup my project at launchpad
[11:39] <killercow> https://www.launchpad.net/freevolution
[11:39] <killercow> and i tried to insert my code into it
[11:40] <killercow> since im new to bazaar im having dificulties  to get the source online
[11:40] <killercow> i had a key pair, and i could setup an sftp connection
[11:40] <killercow> but uploading won;t work somehow
[11:43] <killercow> Im running Ubuntu, and i'd like my code to be available online,
[11:43] <killercow> First step would be to create a public key
[11:43] <killercow> i did that, and inserted it
[11:44] <killercow> Now when i ssh into launchpad as the username i used in launchpad it works
[11:44] <killercow> That is correct right?
[11:45] <Fujitsu_> killercow: What do you mean uploading won't work? What error does it give?
[11:45] <killercow> Well, i installed the bazaar software trough synaptic
[11:45] <Fujitsu> Ah, install bzr
[11:45] <killercow> Ok, just a sec
[11:46] <killercow> ok, that was installed
[11:46] <killercow> bzr and bzr-gtk
[11:46] <killercow> i also tried olive, but that didn;t help me either
[11:47] <Fujitsu> Firstly, what's the command you're trying, and what error does it give?
[11:48] <killercow> :P
[11:48] <killercow> what command should i be giving?
[11:49] <killercow> I don;t think the launchpad software is at fault here, i think im the problem, i don't get how to work it yet
[11:49] <Fujitsu> killercow: bzr push<EMAIL_ADDRESS>[11:50] <Balaams_Miracle> Pardon my interruption, but is maintenance being done on Rosetta? I only get timeouts for pages i try to open on translations.launchpad.net
[11:50] <killercow> in the folder that contains the source code right/
[11:50] <Fujitsu> Where you should replace username with your username, userorteamname with who you want to own the branch, and branchname with a... name for the branch.
[11:50] <Fujitsu> killercow: In the bzr branch.
[11:50] <killercow> ?
[11:50] <killercow> how do i setup a bzr branch then?
[11:50] <killercow> local i asume?
[11:50] <Fujitsu> killercow: Oh, I see. Wait s ec.
[11:50] <Fujitsu> *a sec.
[11:51] <Fujitsu> killercow: http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html should help you there.
[11:51] <Balaams_Miracle> Isn't "trunk" the main branch?
[11:51] <Fujitsu> Balaams_Miracle: That seems to be the standard, but it's not required.
[11:52] <killercow> Somehow  managed to get a Trunk created in launchpad,
[11:52] <Balaams_Miracle> Fujitsu: I've just saw killercow's project, and "trunk" is present
[11:52] <Fujitsu> Balaams_Miracle: That's likely a series, not a branch.
[11:53] <Balaams_Miracle> Ah, i see
[11:53] <Balaams_Miracle> (i think)
[11:53] <killercow> seems bzr init . has allready been done once
[11:53] <killercow> allready a branch
[11:53] <killercow> so i continue with add
[11:54] <killercow> which runs a lits of al the files
[11:54] <Fujitsu> Balaams_Miracle: Rosetta is working OK for me, and I don't know of any maintenance (but I'm not one of the LP guys)
[11:54] <killercow> hmm
[11:54] <killercow> the commits spews out an error:
[11:55] <killercow> bzr commit -m "initual import"
[11:55] <killercow> bzr: ERROR: No such file: u'/home/killercow/public_html/freevolution_0.958/freevolution/.bzr/repository/knits/bc': [Errno 2]  No such file or directory: '/home/killercow/public_html/freevolution_0.958/freevolution/.bzr/repository/knits/bc'
[11:55] <Fujitsu> O_o
[11:55] <Balaams_Miracle> Fujitsu: The rest of LP (bugs, code, etc.) does work for me, only the translations yield timeouts on my end of the line
[11:55] <Fujitsu> killercow: Have you committed anything to that branch before?
[11:55] <killercow> i don't think so
[11:56] <killercow> i copy and paste the folder to a new  one
[11:56] <carlos> Balaams_Miracle: we are not doing any maintainment tasks for Launchpad Translations
[11:56] <killercow> should i try to remove the .bzr folder
[11:56] <Fujitsu> killercow: Yep, that's what I'd try.
[11:56] <carlos> Balaams_Miracle: could you give me OOPs numbers to check it?
[11:57] <Balaams_Miracle> carlos: The most recent one i got is OOPS-641F714
[11:57] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/641F714
[11:57] <killercow> Ok, did that, the init now works fine
[11:57] <killercow> so does the add
[11:57] <killercow> import running now
[11:57] <carlos> Balaams_Miracle: I need to wait a couple of minutes to have the report available
[11:58] <carlos> will read it and tell you about it
[11:58] <Balaams_Miracle> carlos: No problem, i do have a bit of spare time :-)
[12:00] <killercow> ok, commited revision 1
[12:00] <Fujitsu> killercow: Right, if you now push it, it should work.
[12:00] <killercow> push with the command you gave right
[12:01] <Balaams_Miracle> carlos: The translations page on my personal LP page does work now, but the translation i was working on still times out. So it partially works for me now
[12:01] <killercow> bzr push sftp://jan<EMAIL_ADDRESS>[12:01] <Fujitsu> killercow: Erm, that username can't be right.
[12:01] <killercow> what about the space
[12:01] <killercow> exactly
[12:01] <Fujitsu> janklopper-innerheight, I think you want.
[12:01] <killercow> hmm
[12:01] <carlos> Balaams_Miracle: did you translate using that url before and worked?
[12:01] <killercow> its probably janklopper-innerheight
[12:02] <carlos> jtv: I think you should take a look to https://devpad.canonical.com/~matsubara/oops.cgi/2007-10-03/F714
[12:02] <carlos> jtv: it's related to your recent changes to improve the performance of the +translate page
[12:02] <carlos> jtv: seems like it's not fast enough
[12:03] <killercow> hmm
[12:03] <killercow> bzr: ERROR: Parent directory of<EMAIL_ADDRESS>does not exist.
[12:04] <Fujitsu> killercow: ~janklopper-innerheight
[12:04] <killercow> so, i should supply the -create-prefix folders?
[12:04] <Fujitsu> And there's already a `trunk' branch, so you probably want to update that.
[12:04] <Balaams_Miracle> carlos: I did. I was browsing for translations to be corrected, when i suddenly got timeouts. Nothing out of the ordinary because on second (and sometimes a third) try, i was able to browse on. But this time the timeouts seem to persist
[12:04] <killercow> what would the command be then?
[12:04] <Fujitsu> killercow<EMAIL_ADDRESS>[12:05] <carlos> Balaams_Miracle: ok, let me see whether I could get jtv here to check it
[12:05] <killercow> okay, seems to be doing something
[12:05] <killercow> Fetch Phase is processing now
[12:05] <killercow> never seen that before
[12:06] <killercow> :)
[12:06] <Fujitsu> killercow: Sounds like it's working :)
[12:07] <Balaams_Miracle> carlos: Okay. But it should be noted that just before the timeouts started (a little over 30 minutes ago), translations worked pretty smoothly
[12:07] <jtv> carlos: checking...
[12:07] <carlos> jtv: thanks
[12:08] <carlos> Balaams_Miracle: it would depend on load in our server
[12:10] <killercow> Great,
[12:10] <killercow> Thanks Fujitsu
[12:10] <Balaams_Miracle> The glue that the server had stepped in, seems to have dissolved now. :-) Big thanks to Fujitsu, carlos and jtv
[12:10] <Fujitsu> killercow: No problem.
[12:11] <carlos> Balaams_Miracle: we did nothing (yet), but you are welcome ;-)
[12:11] <Balaams_Miracle> Yeah, i've cried victory a bit too soon, because it stepped in the same glue again...
[12:12] <jtv> Balaams_Miracle: as carlos said, it's basically just that there's so much data to look through!
[12:12] <Balaams_Miracle> jtv: I understand completely. OLP is so large and so full of features, it much have a lot of code in its backend.
[12:13] <killercow> So next time i update the software, i should just issue the Push command again?
[12:13] <Balaams_Miracle> much=must.
[12:13] <Fujitsu> killercow: Yep.
[12:13] <killercow> Ok, great
[12:13] <killercow> il see how it all goes
[12:13] <jtv> Balaams_Miracle: the data is especially large.  What you've been doing when this happened was the right thing.  And your translations should still get through; they do, right?
[12:14] <Fujitsu> killercow: It should have even remembered where to send it, so a simple `bzr push' should do it.
[12:14] <killercow> ah, nice
[12:15] <Balaams_Miracle> jtv: It looks like it, after my last translation, i was just scanning the code for a particular string which i feel was mistranslated by someone else.
[12:18] <Balaams_Miracle> jtv: I've just tested it, and my translations do go through. Also, the load on the server seems to have diminished. Is it anything you did this time?
[12:20] <jtv> Balaams_Miracle: It'll be worst when you haven't visited that page for a while.  We've actually improved the problem a lot with the last release, but it's not gone.  We continue to plan changes to fight it.
[12:20] <jtv> Balaams_Miracle: no, probably just caching effects.
[12:22] <Balaams_Miracle> jtv: Yeah, i've noticed that the problem is at its worst with large packages. About the caching, i have cleared my cache earlier today to solve a problem with a page that refused to refresh. So if it's a caching effect, it won't be my browser's cache :-)
[12:22] <jtv> Balaams_Miracle: the translation for Blue Type doesn't look right to melooks more likely that it should be something like "Blauwe Tekst"
[12:23] <jtv> Balaams_Miracle: no, this is purely on the server side.
[12:23] <Balaams_Miracle> jtv: On what page did you find that? I must have overlooked it
[12:23] <jtv> Balaams_Miracle: (at least I can't imagine how "a type" can have a colour :)  It's on the URL of the page that timed out that you pasted earlier
[12:23] <jtv> #6
[12:23] <Balaams_Miracle> Ah, i'll go and see
[12:27] <Balaams_Miracle> jtv: The URL of page that the timeout occurred on was https://translations.launchpad.net/ubuntu/gutsy/+source/nautilus/+pots/nautilus/nl/+translate?start=190 , but i can't find "blue type" anywhere on the page.
[12:28] <jtv> Oh, I seem to have gotten the first page.
[12:28] <Balaams_Miracle> Ah, back to the first page then :-)
[12:29] <jtv> Balaams_Miracle: ah, of course.  I got that URL from the error report on the server.  Which separates the arguments from the path.
[12:32] <Balaams_Miracle> jtv: "Blue Type" is a theme or background for Nautilus. (Bewerken => Achtergronden en emblemen...)
[12:33] <Balaams_Miracle> Oh, he's off
[12:40] <Balaams_Miracle> jtv: welcome back
[12:41] <Balaams_Miracle> jtv: I've looked into your suggestion, but "Blue Type" is a theme or background for Nautilus. (Bewerken => Achtergronden en emblemen...)
[12:42] <Balaams_Miracle> jtv: Still, some of those translations are quite ugly
[12:45] <ubotu> New bug: #148491 in malone "url entry form should add http:// where necessary" [Undecided,New]  https://launchpad.net/bugs/148491
[12:47] <carlos> Balaams_Miracle: did you try google?
[12:47] <carlos> Balaams_Miracle: we have our translation pages public so google could index us as a workaround until we get native search in place
[12:48] <carlos> I'm not sure how good is that search, but is an option that should help
[12:49] <Balaams_Miracle> carlos: Ah, haven't tried that. But i can't imagine it would work if i'd search for something like "network" or "desktop" inside package "foo"
[12:49] <jtv> Balaams_Miracle: add the package name though.  We usually end up pretty high in Google's rankings.
[12:50] <jtv> Balaams_Miracle: not perfect though, true.
[12:50] <carlos> Balaams_Miracle: also 'Translations' should filter out some unrelated pages
[12:50] <Balaams_Miracle> Hmmm... In that case, it's worth a try
[12:50] <carlos> and adding site:translations.launchpad.net would help too
[12:50] <killercow> Hmm
[12:50] <killercow> Its stil doing the fetch phase,
[12:51] <killercow> how long should this take?
[12:51] <Fujitsu> killercow: How big is the codebase?
[12:51] <killercow> its about 7meg, mostly small images
[12:51] <Fujitsu> killercow: How many files, approximately?
[12:52] <killercow> 19k
[12:52] <killercow> (19.000 files),
[12:53] <killercow> one of the first steps i want to complete is fix the scripts that generated those images to remove them from the actual codebase and have them generated at setup
[12:54] <Fujitsu> Ow, that will probably take a while.
[12:54] <Fujitsu> Erm, you might want to stop it, and use bzr+ssh instead of sftp, if you're using a recent bzr.
[01:04] <killercow> Fujitsu: how do i do that?
[01:05] <killercow> chaning the protocol in the url gives me a protocol unsupported error
[01:44] <yeager> xubuntu-docs has been importered.. sweet
[02:35] <killercow> hmm
[02:35] <killercow> push just finished:
[02:35] <killercow> bzr: ERROR: These branches have diverged.  Try using "merge" and then "push".
[02:36] <killercow> any info on how to fix that?
[02:36] <killercow> merge gives: bzr: ERROR: No location specified or remembered
[02:37] <killercow> should i run it with the entire command again, switching push for merge?
[02:38] <killercow> which results in: bzr: ERROR: Branches have no common ancestor, and no merge base revision was specified.
[02:38] <killercow> doh
[02:38] <ddaa> sounds like your are trying to push something unrelated on top of an existing branch
[02:39] <killercow> apparently the tries i made in june are comming back to haunt me now
[02:39] <killercow> What is the best way do go forward now?
[02:39] <ddaa> delete the existing branch
[02:39] <ddaa> or push --overwrite
[02:39] <ddaa> or use a different name
[02:40] <ddaa> or carry your changes on top of the existing branches (maybe using diff/patch)
[02:40] <ddaa> depends on what you really want
[02:40] <ddaa> it's not a launchpad problem
[02:40] <ddaa> it's purely a problem in how you are using bzr
[02:44] <killercow> oka, il see
[02:45] <killercow> i once tried to setup a bazaar branch and stranded
[02:45] <killercow> now im trying to do so again
[02:45] <killercow> so the branch should still be empty
[02:45] <killercow> clearly it is not
[02:45] <ddaa> hint: if you point to the specific branch on launchpad it helps
[02:45] <killercow> but ill try overwrite and see what it does
[02:45] <killercow> :)
[02:46] <killercow> https://code.launchpad.net/~janklopper-innerheight/freevolution/trunk
[02:46] <killercow> this one
[02:46] <ddaa> obviously, it's not empty
[02:46] <ddaa> I see three revisions there
[02:46] <ddaa> you can just delete it
[02:47] <ddaa> Click on "Delete branch" in the Actions box in the top-left.
[02:47] <ddaa> obviously, this branch is just scrap
[02:55] <killercow> ok
[02:55] <killercow> lets see
[02:55] <killercow> hmm, seems to have done something now
[02:55] <killercow> Pushed up to revision 1.
[02:55] <killercow> which probably means i can delete the older branch
[02:55] <killercow> ---- revision
[02:56] <ddaa> you've already done so
[02:56] <killercow> i see
[02:56] <lamont> flacoste: any word?
[02:56] <killercow> damn, stupid typo
[02:56] <ddaa> lamont: flabbergasting
[02:56] <ddaa> that's a word, right?
[02:57] <lamont> ddaa: not today, it isn't. :-)
[02:57] <killercow> overwrite clears the entire branch, and then insert the new code as the first revision
[02:57] <ddaa> lamont: satyriasis?
[02:57] <flacoste> lamont: cprov will land the branch shortly, i don't know if it will be cherry-picked or will be published with next release
[02:58] <cprov> flacoste: it's a cherrypick candidade we will see.
[03:00] <lamont> cprov: thanks.  in other news, can you drop chroot-ubuntu-gutsy-{i386,powerpc,sparc,amd64} where I can get them?  I need to do a little bootstrapping in universe.
[03:01] <lamont> and yeah, we'll need to publish those.  and once we're done bootstrapping, restore them to their former glory
[03:01] <cprov> lamont: in 5 minutes, ok ?
[03:02] <lamont> I won't be ready to play with them for at least 30 min
[03:03] <Daviey> Hey, how can i add a 'milestone'?
[03:08] <cprov> lamont: ta, ping when you are ready.
[03:38] <lamont> cprov: once the branch lands (has it?), who is my new nagging target?
[03:39] <cprov> lamont: kiko
[03:39] <lamont> and branch landed?
[03:40] <Hobbsee> oh, holy hell
[03:40] <lamont> hell not holy
[03:41] <lamont> Hobbsee: what's multiplying?
[03:41] <Hobbsee> lamont: the lp bug statuses mailing list thread
[03:42] <lamont> hehehe
[03:42] <Hobbsee> what vaguely annoys me is that the LP guys dont get that most people dont use every state - and so to have the tedium of having to set everything is just annoying
[03:42] <Hobbsee> heck, we dont usually bother to set importance most of the time.
[03:43] <lamont> lol
[03:43] <lamont> there's an importance field?
[03:43] <lamont> what's that for?
[03:43] <lamont> :-)
[03:43] <Hobbsee> and, y'know, every time i see that upstream bug section (both of them), i want to scream, and i keep hitting options until i get the familar URL box.  if i'm lucky, and have sacrificed enough goats to the gods of launchpad.
[03:44] <Hobbsee> if i'm unlucky, i never find said box, say "screw it", report it upstream separately, and subscribe to the bug there, and never link it back to ubuntu - or say "reported upstream as bug x"
[03:44] <Hobbsee> or i just give up on working with bugs for a while.
[03:46] <Hobbsee> lamont: well, seeing as most of our stuff is upstream bugs anyway, there's little point in setting an importance inside ubuntu - better to file it upstream and wait, as i dont have the tech knowledge to be able to fix it.
[03:46] <Hobbsee> lamont: so all i should do is file it upstream, or get upstream to deal with our bugs here.  but see the part about the upstream bug section.
[03:46] <killercow> Hobbsee: theres need for goat sacrificing? i was under impression sheep would also suffice?
[03:46] <lamont> Hobbsee: oh.  so you're one of _those_ people, eh? :)
[03:46] <Hobbsee> killercow: depends on the part of launchpad.
[03:47] <Hobbsee> lamont: yeah, i'm one of those crappy people who can barely code.
[03:47] <lamont> we love you anyway
[03:47] <Hobbsee> sure sure.
[03:47] <killercow> ah okey, wouldn't want to sacrifice the wrong animal to the wrong god and have the thing come tumbling down.
[03:49] <Hobbsee> (and seriously - ewww, tags!)
[03:50] <lamont> tags are lvoe
[03:50] <lamont> love, even
[03:50] <radix> loving never took so many clicks
[03:50] <lamont> radix: this is launchpad.  love the click
[03:50] <radix> ok, clicks aren't so bad, but pageloads are :)
[03:51] <Fujitsu> Does anybody here actually navigate through LP using the navigation links?
[03:51] <lamont> yeah - I have a bug or 3 to submit after I get hppa all happy
[03:51] <radix> Fujitsu: as opposed towhat?
[03:51] <Fujitsu> radix: Composing URLs manually.
[03:51] <lamont> radix: knowing magic urls
[03:51] <Hobbsee> if i cant set tags by keescook's script, or even in the same interface where i set the statuses and such, then tags are useless for my workflow.
[03:51] <radix> Fujitsu: hmm, for what kind of navigation?
[03:51] <Hobbsee> Fujitsu: oh, sometimes.
[03:51] <laga> Fujitsu: i do. because i cant remember the urls. the pain is starting to teach me, though
[03:51] <Hobbsee> Fujitsu: for some cases, yes i do.
[03:52] <Hobbsee> Fujitsu: but i have Long Pointy Stick of DOOM!!!!!!!!!!!!!!!  and lpb, which alias to launchpad source and launchpad bugs for the source package, which i use all the time.
[03:52] <Hobbsee> gah.  l p s.
[03:52] <Fujitsu> radix: Generally anything other than editing things. Moving to other contexts, etc.
[03:52] <radix> I use launchpad for my daily full-time work routine, and I pretty much only ever type as much as "http://launchpad.net/project"
[03:53] <Hobbsee> having the aliases is much better
[03:53] <radix> oh, but I do have bookmarks to particular milestones and to the "review" tag and "in progress" states in my projects.
[03:53] <Hobbsee> although being able to type lau, then go to the closest match, and keep tying is useful too
[03:53] <radix> The biggest navigation annoyance I have is when I'm in a milestone view, I can't click any of the tabs.
[03:53] <radix> and the fact that I have to pageload to edit tags.
[03:54] <radix> (the latter isn't so much navigation problem as UI design -- there shouldn't *be* navigation there)
[03:54] <Hobbsee> it's worse without the navigation bar :P
[03:55] <Hobbsee> else i cant find anything (particularly when going to a particular ubuntu version, or something)
[03:55] <Fujitsu> Page loading times, particularly on edge, are shocking at the moment :(
[03:56] <Hobbsee> yeah - i was wondering if edge has been slow, or i've been dreaming
[03:56] <Hobbsee> seeing as i switched to edge *precisely* for attempted speed gain.
[03:57] <radix> It seems to get get slow at times.
[03:57] <radix> but other times I don't notice it being slower than the main LP.
[03:57] <Hobbsee> at least it's up.
[03:57] <Hobbsee> most of the time, that is.
[03:57] <radix> :)
[03:58] <Hobbsee> usually there's planned maintenence whenever i try to do a stack fo bug triaging - it's murphy's law, i swear.
[04:01] <barry> hi everybody it's time for the eu/us launchpad reviewer's meeting.  for the next 45 minutes or less, we'll be discussing the review process for launchpad code
[04:01] <jtv> Hobbsee: murphy's law, keystroke logger, what is difference?
[04:01] <Hobbsee> jtv: good question :)
[04:01] <barry> == Agenda ==   * Roll call  * Next meeting  * Action items  * Queue status  * Proposal: add "needs-mentoring" state to PendingReviews. (proposed by AU meeting, EU/US meeting please discuss)  * Mentoring update
[04:01] <barry>  * Roll call
[04:01] <barry> who's here today for the reviewer's meeting?
[04:01] <BjornT> me
[04:02] <jtv> me
[04:02] <salgado> me
[04:02] <barry> intellectronica sends his apologies
[04:02] <bac> me
[04:03] <sinzui> me
[04:03] <flacoste> me
[04:04] <statik> me. thanks for waking me up bac :)
[04:04] <barry> kiko, SteveA: ping if you're available
[04:04] <barry> mwh: ping
[04:04] <barry> i think that's everyone
[04:05] <mwhudson> barry: hi
[04:05] <barry> mwhudson: hi!
[04:05] <mwhudson> sorry for lateness
[04:05] <barry>  * Next meeting
[04:05] <barry> no worries
[04:05] <barry> so, same time and place next week?  does anybody know they will not be able to make it?
[04:06] <barry> cool
[04:06] <barry>  * Action items
[04:06] <barry>  * intellectronica to take barry's original review script, add it to utilities, and merge his patch to CC reviewers.
[04:06] <barry> he's not here today, but i don't think this was done, so we'll just carry it forward to next week
[04:06] <mwhudson> hasn't conspicuously happened
[04:07] <barry> i think i'll make a branch with my version of the script and then intellectronica and add his patches when he gets around to it.  any objections?
[04:08] <barry> 5...4...3...2...1
[04:08] <barry>  * sinzui to help make `lint.sh` better by updating pylint.
[04:09] <barry> sinzui: did i see you had a branch for that?
[04:09] <sinzui> bug-141317-add-pylint is in review
[04:09] <barry> sinzui: rock on
[04:09] <sinzui> barry: I also ads xmllint
[04:09] <barry> sinzui: awesome.  let me know when it lands so i can remove that action item
[04:09] <sinzui> ok
[04:10] <barry> and please send a message to launchpad@ to let people know how to use it
[04:10] <barry>  * barry will try to find someone to work on [https://launchpad.net/bugs/113626 bug 113626]  to extend pending-reviews to run make lint for us.
[04:10] <ubotu> Launchpad bug 113626 in launchpad "pending-reviews should run and display the output of make lint" [Undecided,Confirmed]  https://launchpad.net/bugs/113626
[04:10] <ubotu> Launchpad bug 113626 in launchpad "pending-reviews should run and display the output of make lint" [Undecided,Confirmed]
[04:10] <bac> sinzui: how does trunk look with pylint?
[04:11] <sinzui> bac: are asking make lint-complete, or do you want to know the ugly truth>=?
[04:11] <bac> sinzui: i guess i'm asking if we'll be overwhelmed by running 'make lint'
[04:12] <sinzui> I wanted several targets that changed the strictness from make. make lint will not overwhelm, even though it is running pylint and xmlint.
[04:13] <sinzui> make lint-complete will complain about out missing docstrings, and that does overwhelm
[04:13] <barry> ideally i think, people should mostly be concerned with changes they make and not all of lp.  that's what the current make lint tried to do, but it's check wasn't correct (it only looked at uncommitted changes, not all changes in the branch)
[04:13] <sinzui> There are other differences too that I hope spiv will remark on.
[04:14] <barry> sinzui: will we be able -- over time -- to either fix those or silence the false positives through config files or #pragmas and such?
[04:14] <sinzui> lint looks for changes from the parent branch. it is ok to have commits in the branch
[04:14] <barry> sinzui: excellent
[04:15] <sinzui> We should be fix doc strings. I got tired one Friday and fixed Questions. I've fixed half of bugs.
[04:15] <mwhudson> sinzui: fix the markup of the docstrings?
[04:16] <flacoste> i assume he's talking about missing docstrings
[04:16] <barry> i'm sure we'll get false positives, so we should establish a coding guideline for addressing and resolving them
[04:16] <sinzui> We have a lot of missing docstrings. database.person is a good example
[04:17] <barry> sinzui: we'll make the next person to touch person.py fix them :)
[04:17] <sinzui> pylint does need some training, or a plugin to capture some of our style.
[04:17] <barry> or maybe: YTIYOI (you touch it you own it)
[04:18] <sinzui> barry: Person is too big. (that is another pylint warning).
[04:18] <barry> sinzui: yeah, that's a well known problem (there might even be a bug open on that)
[04:18] <barry> sinzui: will we be able to commit a config file to train pylint so all developers can benefit from that, or will they all have to add something to a ~-dot file?
[04:19] <sinzui> I added a loose and a strict config file that we can edit.
[04:19] <barry> sinzui: cool.
[04:19] <sinzui> The make targets just switch the config file.
[04:20] <barry> sinzui: thanks very much for doing this.  i'm sure we'll discuss it more on the general list.  anything else?
[04:21] <barry> sinzui: done?
[04:21] <sinzui> yes
[04:21] <barry> cool, thanks!
[04:21] <barry>  * barry will coordinate for ''reviewer's sprint'' at all-hands
[04:22] <barry>  * Queue status
[04:22] <statik> I suck
[04:22] <barry> there's 10 needs-review branches over the sla
[04:22] <barry> this is week 1 so it's a good time to sprinkle your reviews when you're tired of coding :)
[04:23] <mwhudson> mostly kiko though
[04:23] <mwhudson> :)
[04:23] <barry> mwhudson: indeed :)
[04:23] <sinzui> jtv landed his branch before it was assigned to me
[04:23] <barry> stub wins the oldest branch award tho
[04:24] <barry> sinzui: i'm confused.  how did that happen?
[04:24] <barry> sinzui: did someone else review it?
[04:24] <jtv> barry: it was reviewed by SteveA
[04:24] <jtv> Rush job
[04:24] <jtv> But hey, sinzui beat the world record with a negative review time.
[04:25] <barry> jtv: lol.  you should make sure to remove landed branches from PendingReviews.  i just want to make sure reviewers aren't wasting time duplicating work
[04:26] <barry> i know it's easy to forget but we should make sure developers know that it's their responsibility to remove landed branches from PendingReviews.  it's not the reviewer's responsibility
[04:27] <barry> anything else on the queue?
[04:27] <barry> 5
[04:27] <barry> 4
[04:27] <sinzui> I suppose I'm available to take a branch
[04:27] <barry> 3
[04:27] <sinzui> if someone feels overloaded
[04:28] <barry> sinzui: cool.  also you can always take a branch from the general queue.  you don't have to wait for it to be assigned
[04:28] <sinzui> fab
[04:28] <barry> 2
[04:28] <barry> 1
[04:28] <barry>  * Proposal: add "needs-mentoring" state to PendingReviews. (proposed by AU meeting, EU/US meeting please discuss)
[04:29] <jtv> Yes
[04:29] <barry> i think we've talked about that here in the eu/us meeting before
[04:29] <sinzui> I think that is a good status
[04:29] <barry> i'm pretty sure we know what this means.  all in favor say "aye".  all opposed say "nay".  if you think we need to discuss it say "maybe"
[04:30] <barry> aye
[04:30] <mwhudson> does it imply changes to the pending-reviews script?
[04:30] <sinzui> Aye
[04:30] <mwhudson> aye
[04:30] <flacoste> aye
[04:30] <flacoste> well, maybe
[04:30] <salgado> maybe
[04:30] <jtv> mwhudson: I think it would
[04:30] <statik> aye
[04:30] <bac> aye
[04:30] <BjornT> aye
[04:30] <flacoste> the problem i have with it is that it its semantic are not clear
[04:30] <flacoste> it looks more like a tag than a new status
[04:31] <flacoste> for example, the mentoree could have said needs-reply or merge-conditional
[04:31] <flacoste> and needs-mentoring
[04:31] <jtv> The mentoree can't say merge-conditional
[04:32] <BjornT> actually, i was going to say the same thing :) i think it's better to add a flag
[04:32] <bac> flacoste: needs-mentoring would be the active state with the other just being proviional
[04:32] <BjornT> for example, merge-conditional*
[04:32] <BjornT> that way you can see what state the reviewer thought the branch should be in, but it still needs to be mentored
[04:32] <jtv> merge-conditional means "go ahead and merge, at your own convenience, provided you fix these points."
[04:32] <salgado> I think this is something which is best conveyed in the review itself.  I doubt reviewees will look at pending-reviews to see the status of their branches
[04:33] <jtv> salgado: it's meant more for the mentors.
[04:33] <flacoste> jtv: the mentoree can say merge-conditioinal
[04:33] <salgado> jtv, well, the mentors get a copy of the reviews by email
[04:33] <flacoste> jtv: he should say "merge-conditional unless the mentor has something else to say"
[04:33] <barry> here's what the minutes of the au meeting says:
[04:33] <salgado> jtv, I, as a mentor, don't find it useful.  if other mentors want it, that's fine with me
[04:33] <BjornT> salgado: it's also good when reviewing the state of the queue; you get an indication who's blocking it
[04:34] <barry> jtv proposed a "needs-mentoring" status for branches that are waiting for a mentor's review.  This would be useful to make it plainly visible which branches are held up by mentors (and visible to a mentor what branches they need to look at), and to make it clear to developers where their branch is at.  All present agreed.  spiv will add that proposal to the .eu meeting agenda.
[04:34] <sinzui> This is like the bug status discussion
[04:35] <jtv> flacoste: if a mentored review says merge-conditional, that changes the semantics of merge-conditional from "go ahead, merge at your convenience once these things are fixed" to "fix these then wait."
[04:35] <flacoste> lol
[04:35] <sinzui> We should not mix the status of the object (branch) with the status of the person (reviewer)
[04:35] <spiv> So call it "half-reviewed" then ;)
[04:35] <flacoste> jtv: the semantic do not change, it's just that when the status is granted by a mentoree, there is an additional step
[04:36] <BjornT> jtv: it's still valuable to know what status the mentoree intended. that's why an additional flag would be better than a new status
[04:36] <jtv> But more work for all involved, no?
[04:36] <BjornT> jtv: why?
[04:37] <jtv> It needs more changes to status page script, I'd say
[04:38] <barry> it sounds to me like this discussion should move onto the mailing list before we approve or reject it
[04:38] <BjornT> jtv: not necessarily, it depends on how we implement it.
[04:38] <barry> jtv: since you proposed it, can you post to launchpad-reviews@ and see if we can gain consensus about the semantics and workflow?
[04:38] <jtv> ok
[04:39] <barry> jtv: thanks.
[04:39] <barry> moving on...
[04:39] <barry>  * Mentoring update
[04:39] <barry> any feedback from mentorees or mentors?  any problems (other than the needs-mentoring workflow)?
[04:40] <barry> i know we felt that we might be bringing on too many new reviewers.  any mentors feel overwhelmed or do you think it's going pretty well?
[04:41] <barry> also, think about possible graduations at the end of .10.  it's okay if we want to keep mentoring people for a while long too.
[04:41] <barry> er, longer
[04:42] <barry> 5
[04:42] <barry> 4
[04:42] <barry> 3
[04:42] <flacoste> let's see how hell's week goes
[04:42] <barry> flacoste: good point :)
[04:42] <barry> 2
[04:42] <flacoste> (hell's week being week 3)
[04:42] <barry> 1
[04:43] <barry> that's it for the agenda.  we have 2 more minutes.  does anybody have anything else?
[04:44] <barry> sounds like we're good then.  so we can end 1 minute early.  yay! :)
[04:44] <barry> MEETING ENDS
[04:44] <barry> thanks everyone!
[04:44] <bac> thanks barry
[04:45] <flacoste> thanks barry
[04:45] <mwhudson> thanks barry
[04:56] <kiko> Fujitsu, hmmm.
[04:56] <kiko> Fujitsu, so what should happen when you click on the Bugs tab in a milestone page?
[05:02] <killercow> anyone else got the ubuntu countdown counter on their site yet?
[05:50] <ubotu> New bug: #148595 in malone "Indicate in buglists when a bug has one or more bugtasks that are fixed in other contexts" [Undecided,New]  https://launchpad.net/bugs/148595
[06:52] <lamont> cprov-lunch: I'm heading to lunch, and then I'll be ready to play.  I'll need chroot-ubuntu-gutsy-{powerpc,sparc}.tar.bz2.  it's still maybe up in the air which of chroot-ubuntu-{gutsy,hardy}-amd64.tar.bz2 I will need.
[06:53] <lamont> (eventually)
[06:53] <cprov> lamont: hardy ?
[06:54] <cprov> lamont: i will copy them to chinstrap
[06:54] <lamont> yeah.  that'd be after gutsy releases, eh.
[06:55] <lamont> cprov: as long as you're tossing, throw in gutsy/amd64 too... they may decide to just grab sid's mlton in the end
[06:55] <cprov> lamont: okidoki
[07:35] <ubotu> New bug: #148636 in launchpad "Site requests are slow, sometimes time out" [Undecided,New]  https://launchpad.net/bugs/148636
[08:09] <mdke> carlos: the ones uploaded by me should be approved (why do they need approval?)
[08:12] <mdke> carlos: I don't know about kubuntu-docs
[08:23] <mdke> carlos: lp seems to give me the option of approving the two templates myself, but then says "There are 5 errors" when I try to save changes; without specifying what the errors are
[08:33] <carlos> mdke: that's a know bug. If you use filters it will work
[08:33] <carlos> mdke: about approve your own entries, you don't need to do that
[08:33] <carlos> mdke: I mean, if you don't use filters it will work
[08:34] <carlos> mdke: I talk about the templates you didn't upload
[08:34] <carlos> mdke: what should I do ?
[08:34] <carlos> remove? block?, approve?
[08:34] <mdke> carlos: those are to be deleted
[08:34] <mdke> i thought I emailed about those, probably I forgot :(
[08:34] <carlos> mdke: there is a request to approve the website-index one
[08:34] <carlos> let me look for it...
[08:35] <mdke> no, that can go
[08:35] <carlos> mdke: https://bugs.edge.launchpad.net/rosetta/+bug/140694
[08:35] <ubotu> Launchpad bug 140694 in rosetta "[gutsy]  Important documentation translations in "Needs review" state" [Medium,Confirmed]   - Assigned to Carlos Perell Marn (carlos)
[08:35] <mdke> i'll reply on the bug
[08:36] <carlos> thank you
[08:37] <mdke> not sure about kubuntu-docs though
[08:37] <carlos> who knows about it?
[08:38] <ScottK> nixternal is the person who knows most about it from the Kubuntu end.
[08:38] <carlos> ScottK: ok, thanks
[08:39] <ScottK> Riddell probably too if nixternal isn't around.
[08:39] <kiko-afk> ScottK, who could I find that might be interested in packaging OGMRip?
[08:39] <ScottK> What is it?
[08:39] <kiko-afk> ScottK, they are using bzr, so that might make things slightly easier to update
[08:39] <mdke> carlos: I'll check myself actually
[08:39] <kiko-afk> http://launchpad.net/ogmrip -- it's a DVD-ripping gnome app.
[08:40] <carlos> mdke: ok
[08:40] <mdke> carlos: meh, it's not clear from the package; best to ask nixternal
[08:40] <carlos> ok
[08:40] <ScottK> kiko-afk: I'd ask on #ubuntu-motu.  It sounds like something people would be interested in.
[08:40] <carlos> :-)
[08:41] <ScottK> 't use Gnome, so not me.
[08:41] <ScottK> doesn't even...
[08:42] <kiko> I use ion2
[08:43] <LaserJock> ewww
[08:43] <LaserJock> ;-)
[08:44] <kiko> LaserJock, ScottK: is there someone who usually packages gnome apps?
[08:45] <variant> It's annoying when you answer a question on answers.launchpad and then someone comes along and says something simmilar to "yes, soandso is correct" and then the poster markes it as solved and the hijacker gets the credit!!
[08:45] <variant> :)
[08:46] <LaserJock> kiko: nope
[08:46] <LaserJock> kiko: you can file a bug though
[08:47] <kiko> LaserJock, do you think I should, or should I keep begging?
[08:47] <kiko> variant, I think there's a proposal to allow marking multiple answers as credited.. flacoste_lunch?
[08:47] <LaserJock> kiko: http://tinyurl.com/2mbskn
[08:47] <pochu> kiko: you can file a RFP in BTS and wait, maybe somebody packages it and we can sync it.
[08:48] <cprov> Rinchen: ping
[08:48] <variant> kiko: that would be great..
[08:49] <Rinchen> hi cprov
[08:49] <variant> I answer quite a few questions and it's really annoying.. a thank you is the payment you get for helping someone so it's intensly annoying when somone steals it
[08:49] <cprov> Rinchen: do you have more information about bug 148651
[08:49] <ubotu> Launchpad bug 148651 in apport "apport crashes when reporting a bug in a PPA package" [Undecided,New]  https://launchpad.net/bugs/148651
[08:49] <flacoste> kiko, variant: yes, we talked about that
[08:49] <Rinchen> cprov, oh wow, that's cool
[08:49] <Rinchen> cprov, I didn't know it was there.
[08:50] <flacoste> somebody proposed a 'shared-recognition' spec
[08:50] <Rinchen> cprov, let me look since it crashed here and I handed you that oops
[08:50] <cprov> Rinchen: I've just filed it ;)
[08:50] <Rinchen> you're a wonderful man!
[08:50] <cprov> Rinchen: also, can you follow-up  kiko
[08:50] <Rinchen> cprov, gimme a few minutes to chat with barry and I'll send you the error
[08:50] <cprov> 's review for "get PPA TOS out of LP" ?
[08:51] <cprov> Rinchen: sure, thanks.
[08:59] <Rinchen> cprov, https://pastebin.canonical.com/444/
[08:59] <Rinchen> sorry about the formatting
[08:59] <Rinchen> chose the wrong option
[09:00] <cprov> Rinchen: it's ok thanks
[09:01] <Rinchen> cprov, I have no idea why it's listed google-earth though
[09:01] <Rinchen> it was smart that failed
[09:01] <cprov> Rinchen: me neither ...
[09:02] <Rinchen> I don't have an apport crash log either
[09:02] <Rinchen> what happened to me was apport sent me to a non-existent LP page. Apport itself doesn't appear to have crashed
[09:02] <Rinchen> at least, not via the logs
[09:03] <cprov> Rinchen: uhm, it just pointed you to a "not-found" page
[09:03] <Rinchen> yes
[09:03] <cprov> Rinchen: I thought it had crashed.
[09:03] <Rinchen> I thought it did too
[09:03] <Rinchen> hehe
[09:03] <Rinchen> let me make smart crash again and see what happens
[09:03] <Rinchen> I should be able to replicate it
[09:03] <cprov> Rinchen: okay
[09:09] <Rinchen> cprov, would you believe that even after I removed the smart fix (reset it to it's crashing state) it won't crash now.  arrg
[09:10] <cprov> Rinchen: well, 'not crashing' is good.
[09:10] <Rinchen> yeah but very not helpful in diagnosing this issue
[09:11] <LaserJock> Rinchen: what issue? ;-)
[09:12] <cprov> Rinchen: well, let's keep the bug on the radar for now
[09:12] <Rinchen> cprov, right...let me see if I can crash smart again
[09:12] <Rinchen> cprov, working with niemeyer on it on another channel
[09:12] <cprov> Rinchen: I'm watching ...
[09:13] <niemeyer> cprov: The issue is that Smart expects the uncompressed Packages file to be available
[09:13] <niemeyer> cprov: Which isn't currently the case with PPAs
[09:13] <niemeyer> cprov: It doesn't download the file, but it uses it's md5sum in the Releases file
[09:13] <niemeyer> s/it's/its
[09:14] <Rinchen> cprov, ok, here we go
[09:15] <cprov> niemeyer: well, the md5 for the plain indexes is already available in Release, it was a 1.1.9 task, if I'm not mistaken
[09:15] <niemeyer> cprov: Hmm
[09:15] <niemeyer> cprov: I think it wasn't, in the PPA I've looked at
[09:15] <niemeyer> cprov: Let me check that again
[09:15] <Rinchen> cprov, ok, apport doesn't crash. Instead it sends me to a not-found page.
[09:15] <Rinchen> https://edge.launchpad.net/ubuntu/+source/smartpm-core/+filebug/p4f6ULIBrVT9ALs2ULtMOIdeYBt?field.title=smart+crashed+with+KeyError+in+fetch%28%29
[09:16] <cprov> niemeyer: it possible that it needs to be regenerated
[09:16] <cprov> niemeyer: bug 134131
[09:16] <ubotu> Launchpad bug 134131 in soyuz "NoMoreAptFtpArchive generates incorrect Releases file" [High,Fix released]  https://launchpad.net/bugs/134131 - Assigned to Julian Edwards (julian-edwards)
[09:17] <niemeyer> cprov: http://ppa.launchpad.net/landscape/ubuntu/dists/dapper/Release
[09:18] <cprov> niemeyer: weird, it's from Date: Tue, 02 Oct 2007 22:00:24 UTC
[09:22] <cprov> niemeyer: you're right, the fix wasn't extended to PPAs :(
[09:27] <niemeyer> cprov: Uh oh :)
[09:27] <niemeyer> cprov: Well, it's cool that we'll see a fix for that soon
[09:27] <cprov> niemeyer: bug 148685
[09:27] <ubotu> Launchpad bug 148685 in soyuz "PPA Release files have to list plain indexes as well" [Undecided,In progress]  https://launchpad.net/bugs/148685 - Assigned to Celso Providelo (cprov)
[09:28] <niemeyer> cprov: Sweet, thanks!
[09:36] <ubotu> New bug: #148685 in soyuz "PPA Release files have to list plain indexes as well" [Undecided,In progress]  https://launchpad.net/bugs/148685
[09:38] <flacoste> barry: ping
[09:39] <barry> flacoste: pong
[09:46] <variant> flacoste: cool, think it will get implemented?
[09:46] <variant> I would also like to be able to automatically subscribe to any qeustiont that I comment or answer by default
[09:47] <flacoste> variant: to be honest, you won't see much development on the answer tracker in the coming months, but it's definitively on the list of priorities for it
[09:48] <flacoste> variant: you should file a bug for that new feature request (automatic subscription for questions you comment on)
[10:01] <variant> flacoste: will do
[10:02] <variant> flacoste: it's a really cool idea (answers.launchpad).. launchpad in general is very cool (i just wish it was all hpl :))
[10:02] <variant> gpl*
[10:02] <nixternal> and I take it that I missed the kubuntu-docs talk?
[10:11] <ScottK> nixternal: The conversation you just had with carlos on #ubuntu=devel was it.
[10:12] <nixternal> oh
[10:13] <nixternal> well then, keep on rockin' you LP phreaKz :)
[10:14] <lamont> cprov: ready to play?
[10:15] <variant> flacoste: seems that it has been requested a few times. I have updated the bug rep with my opinion too :)https://bugs.launchpad.net/malone/+bug/977
[10:15] <ubotu> Launchpad bug 977 in malone "Commenting on bug should optionally subscribe you" [High,Fix released]   - Assigned to Brad Bollenbach (bradb)
[10:15] <cprov> lamont: have you already modified the chroots ?
[10:15] <flacoste> variant: that bug is fix released and is about bugs, not questions
[10:16] <flacoste> variant: you should post your bug in https://bugs.launchpad.net/launchpad-answers
[10:18] <lamont> cprov: now that I'm awake, I'm fetching them.  sigh
[10:18] <cprov> lamont: ok, how long will it take ?
[10:19] <cprov> lamont: I have to go out a bit (30 min), it that ok ?
[10:19] <lamont> I should be ready for push 1 within 20 min, I think.
[10:20] <lamont> rsync of the tarballs looks to be on the order of 2 min per
[10:20] <variant> flacoste: doh
[10:20] <lamont> cprov: you fix's branch has landed, yes?
[10:21] <cprov> lamont: in RF, but it wasn't cherrypicked in production yet
[10:41] <lamont> cprov: I want to make sure I'm not breaking things before we push the chroots.... when will you be back?
[10:41] <cprov> lamont: 30 min ~ 1 hour
[10:42] <cprov> lamont: anyway, call me if you need anything, I will be around.
[10:43] <lamont> great - I know I'll be ready then..  (chroots are built, bootstrap archive is built, I 'm going to verify that I didn't break anything by maybe breaking primero, and then I'll know.
[10:45] <lamont> cprov: sigh.  _long_ builds going on both hppa buildds...
[10:45] <lamont> do you happen to have the exact apt-get invocation that gets used to install build-deps and upgrade the chroot?
[10:46] <cprov> lamont: no, but you can check the the build log or the usr/share/launchpad-buildd/scripts/*.sh on builders
[10:47] <lamont> oh. duh.  thanks
[10:47] <Kopfgeldjaeger> good night
[10:51] <lamont> ew.  chapt-get uses the real root's trusted.gpg.  sigh
[11:00] <ubotu> New bug: #148716 in launchpad "Add doctest documenting and enforcing the policy for name changes" [Medium,Triaged]  https://launchpad.net/bugs/148716
[11:00] <mpt> Goooooooooooooooood morning Launchpadders!
[11:14] <flacoste> Gooooooooooooooooooood morning mpt!
[11:14] <flacoste> mpt: feeling better?
[11:30] <mpt> flacoste, mostly
[11:36] <mpt> thanks :-)
[11:38] <Ng> can I move a branch from ~me to ~myteam or should I just push it to the new location?
[11:41] <Ubulette> Ng: assign "author" to your team
[11:41] <Ng> aha :)
[11:41] <Ng> thanks
[11:50] <ubotu> New bug: #148737 in launchpad-bazaar "Bzr needs a more decriptive error message when product does not exist on launchpad" [Undecided,New]  https://launchpad.net/bugs/148737
[12:14] <thumper> Ng: change the author doesn't move the branch
[12:14] <thumper> Ng: you need to reassign it, or push to the new location
[12:16] <Ng> thumper: so ~me/blah/+reassign?
[12:16] <Ubulette> i did that a dozen of time
[12:16] <Ubulette> yet the branch was already subscribed to my team too
[12:17] <thumper> Ng: ~user/project/branch-name/+reassign or select "Change registrant" from the actions
[12:18] <Ng> thumper: cool, thanks
[12:28] <cprov-out> lamont: ?
[12:28] <lamont> si
[12:29] <lamont> chinstrap:~lamont/chroot-bootstrap/*
[12:29] <cprov-out> lamont: right
[12:29] <lamont> if you want to do one first, then we can make sure I didn't horribly screw up
[12:30] <lamont> cprov-out: one other question for you
[12:30] <cprov-out> lamont: yes
[12:30] <lamont> if we start building 20061107-1 and 20070826-1 is uploaded while that build is going on, will the build results still publish?
[12:32] <lamont> (I want to bootstrap with 20061107-1 on !amd64, will need to bootstrap with 20070826-1 on amd64)
[12:34] <cprov-out> yes, for a very short period of time, ~ 2 hours
[12:34] <cprov-out> lamont: done, chroots updated
[12:34] <lamont> as long as it's fetchable... :-)
[12:36] <lamont> and builds started on ppc/sparc
[12:41] <lamont> cprov-out: looks good from here.  I think we're ok leaving the tarball alone until after we finish with amd64, which will be sometime tomorrw (mlton is not a fast builder)
[12:42] <lamont> does ppa use the same tarball as on-ppa?
[12:42] <cprov-out> lamont: okay, great
[12:42] <lamont> s/on-ppa/non-ppa/
[12:42] <cprov-out> lamont: yes :(
[12:42] <lamont> fwiw, there's a bug in chapt-get... where should I be sending a patch to?
[12:42] <cprov-out> lamont: will they fail horribly ?
[12:42] <lamont> horribly is not entirely accurate...
[12:43] <cprov-out> lamont: to me ;)
[12:43] <lamont> unless the real-root's /etc/apt/trusted.gpg has 0a0ac927 in it, then apt-get update fails, and I think we die.
[12:43] <lamont> so it's a quick death, at least.
[12:43] <lamont> that only affects promethium atm
[12:44] <lamont> prometium won't let me log in, or I'd fix it myself...
[12:45] <lamont>     -o APT::GPGV::TrustedKeyring=${chroot}/etc/apt/trusted.gpg \
[12:46] <lamont> in /usr/bin/chapt-get's final command somewhere should fix the issue
[12:46] <cprov-out> lamont: we can ping the IS guys, but I don't anyone is available right now
[12:46] <lamont> if you hand patch promethium, then we can ignore it for a while
[12:46] <lamont> right
[12:46] <elmo> what the heck are you doing on/to promethium?
[12:47] <cprov-out> elmo:  wow, wow, nothing ...
[12:48] <Daviey> elmo: would i be allowed to torrent (iso) from our canonical box?
[12:48] <lamont> cprov-out: on the bright side, it's just universe builds on prometium that are b0rked
[12:48] <Daviey> elmo: -- with a reasonable upload cap?
[12:49] <elmo> Daviey: -ECHANNEL, and hang on, phone call
[12:49] <lamont> hrm... I wonder what he highlights on :-)
[12:49] <cprov-out> lamont: users can retry it later, I guess, let's try to do it as fast as possible
[12:50] <lamont> cprov-out: go ahead and push the non-bootstrap chroot on amd64 for now
[12:50] <lamont> it'll be hours before I'm ready to sync the source that has to be there for amd64 to bootstrap
[12:51] <lamont> as in, I still need to find one more motu to bless the uvfe for mlton, or it can happen in hardy
[12:51] <cprov-out> lamont: done, amd64 chroot reverted
[12:51] <lamont> so do you want a proper diff for chapt-get?  or is the above enough?