[08:16] <eagles0513875_> hey all
[08:17] <eagles0513875_> any devs around
[09:09] <eagles0513875_> hey cfhowlett
[09:09] <cfhowlett> eagles0513875_, yep
[09:09] <eagles0513875_> cfhowlett: can you kindly confirm something for me in regards to a particular package as i dont have an ubuntu studio setup installed yet
[09:10] <cfhowlett> I'll try.
[09:10] <eagles0513875_> thanks
[09:11] <eagles0513875_> unless there is a web page which lists all packages and one can see a particular package and what release its in
[09:11] <cfhowlett> packages.ubuntu.com
[09:12] <eagles0513875_> excellent thanks ill check there
[09:13] <eagles0513875_> thanks cfhowlett that helped tremendously
[09:13] <cfhowlett> happy2help!
[18:53] <sakrecoer> hi guys!
[18:53] <sakrecoer> i'm trying to find a good place to keep the feature-tour.txt file on luanchpad, but i don't want to mess up the website repos...
[18:56] <sakrecoer> feeling a bit rusty on the branch thing... i see the new theme is in git...
[18:57] <sakrecoer> and the old (? one of them) is in bzr, but seem to have last modification date linked to the git... https://code.launchpad.net/~ubuntustudio-website/ubuntustudio-website/ubuntustudio-website


[12:58] <thumper> yml: when the branch is pushed, it is signalled to be refreshed
[12:58] <thumper> yml: but it isn't instantaneous (as much as I'd like it to be)
[01:30] <ubotu> New bug: #138775 in malone "Notification subject included bug number but no summary" [Undecided,New]  https://launchpad.net/bugs/138775
[04:55] <poolie> i thought the 'most recently reported bugs' list used to show their state
[04:55] <poolie> but this no longer seems to be true on edge?
[04:55] <poolie> did it regress?
[05:33] <mpt> poolie, on which page?
[05:46] <ubotu> New bug: #138805 in launchpad-bazaar "Permissions for editing bug branch links is too permissive" [Undecided,New]  https://launchpad.net/bugs/138805
[06:47] <poolie> mpt, https://bugs.edge.launchpad.net/bzr/+filebug
[06:54] <mpt> poolie, the "Is the bug youre reporting one of these?" list does show the state of each bug
[06:55] <mpt> I think the "Most frequently reported bugs" list includes only open bugs now, but don't quote me on that
[06:55] <mpt> If so, there wouldn't be *much* point including their status
[06:55] <poolie> mpt, it does not, the top one in the list on https://bugs.edge.launchpad.net/bzr/+filebug is fix released
[06:56] <poolie> i can see how users might still be encountering it in older versions s
[06:56] <poolie> so i think it's ok to  have it there
[06:56] <poolie> but it is a bit annoying for advanced  users
[06:56] <poolie> also, wasn't there once a link from a bug page to file a new bug? has that gone entirely?
[06:57] <mpt> That's now in the "What next?" section at the bottom
[06:57] <poolie> huh
[06:57] <poolie> ok
[06:57] <poolie> also it seems odd to me that the 'offer to mentor' is given so much prominence compared to other actions
[06:58] <mpt> I agree
[07:02] <poolie> i guess it makes sense for new features to be a bit more obvious
[07:18] <mpt> poolie, reported bug 138813
[07:18] <ubotu> Launchpad bug 138813 in malone ""Most Frequently Reported Bugs" list includes closed bug reports but doesn't distinguish them" [Undecided,New]  https://launchpad.net/bugs/138813
[07:25] <ubotu> New bug: #138813 in malone ""Most Frequently Reported Bugs" list includes closed bug reports but doesn't distinguish them" [Undecided,New]  https://launchpad.net/bugs/138813
[07:26] <mpt> ubotu, you could be smarter about that
[08:00] <thumper> jamesh: reviewer meeting?
[08:00] <thumper> lifeless: meeting?
[08:00] <jtv> thumper: coffee?
[08:00] <thumper> jtv: yes please
[08:01] <jtv> thumper: we're just making it, if you can be here in 5 mins?
[08:01] <thumper> jtv: sure, I'll just pop over
[08:01] <jamesh> hi
[08:01] <jtv> hi
[08:04] <thumper> I have a dinner appt at 07:00UTC for the wife's birthday
[08:04] <thumper> so I can't hang around forever :)
[08:05] <jtv> congrats.  Have a cookie with the coffee!
[08:05] <tonyyarusso> thumper: Mine too - wish her a happy co-birthday for me :P
[08:06] <jml> hello hello
[08:06] <thumper> tonyyarusso: she doesn't want her birthday any more and is considering having mine instead
[08:06] <tonyyarusso> thumper: lol
[08:08] <jamesh> should we start in a few minutes then?  (with or without lifeless, spiv or BjornT)
[08:08] <BjornT> i'm here
[08:09] <spiv> I'm here.
[08:09] <thumper> I'm here
[08:09] <jml> I'm here.
[08:11] <jamesh> given that lifeless is not about, who is charing?
[08:12] <jamesh> chairing, even
[08:12] <jamesh> guess I'll do it then :)
[08:13] <jamesh> == Agenda ==
[08:13] <jamesh>  * Roll call
[08:13] <jamesh>  * Next meeting
[08:13] <jamesh>  * Queue status
[08:13] <jamesh>  * Barry has been slack with last EU/US meeting minutes
[08:13] <jamesh>  * Mentors wanted
[08:13] <jamesh> is everyone happy with the same time next week for the meeting?
[08:13] <jml> yes
[08:13] <thumper> yes
[08:13] <jamesh> that is 18th September at 06:00 UTC
[08:13] <jtv> yes
[08:14] <spiv> yes
[08:14] <jamesh> good.
[08:14] <jamesh> * Queue status
[08:14] <thumper> longish
[08:14] <jamesh> 36 branches, 11 past the due date
[08:15] <spiv> One's mine; I'll get that done today.
[08:15] <jamesh> two of the overdue ones are mine (one of them in followup)
[08:15] <spiv> kiko has 5 overdue branches!
[08:15] <jamesh> I'll get them finished today
[08:15] <thumper> I've done all mine
[08:16] <thumper> . o O (they were small though)
[08:16] <jamesh> given the size of the development team and review team, I guess the review queue isn't too huge
[08:16] <jamesh> although it'd be worth bringing up kiko's branches at the EU meeting if they're still not done
[08:16] <jml> Mine's got 2 more that need review.
[08:17] <jml> well in hand, I think.
[08:17] <jamesh> the next item doesn't seem applicable
[08:17] <jamesh>  * Mentors wanted
[08:17] <jamesh> according to Barry's email, we've got all the review mentors sorted out now
[08:18] <spiv> That's my understanding too.
[08:18] <jamesh> for the people at this meeting, spiv is mentoring jml and I'm mentoring jtv
[08:18] <jamesh> * Other business
[08:19] <thumper> none from me
[08:19] <jamesh> if no one has anything else to add, we can finish the meeting.
[08:19] <jamesh> 5
[08:19] <jamesh> 4
[08:19] <jamesh> 3
[08:19] <jamesh> 2
[08:20] <jamesh> 1
[08:20] <jamesh> meeting ends.
[08:20] <jtv> liftoff!
[08:20] <jml> jamesh: thanks.
[08:20] <thumper> thanks jamesh
[08:20] <jamesh> than's for coming
[08:25] <lifeless> bleh, was on fphone with poolie
[08:25] <lifeless> very sorry
[08:47] <carlos> morning
[10:20] <mrevell> Morning Launchpadders!
[10:20] <Fujitsu> Hi mrevell.
[10:20] <mrevell> how Fujitsu
[10:21] <Hobbsee> mrevell!
[10:21] <mrevell> Hobbsee: Morning drongo :-D
[10:21] <mrevell> sorry, drongobrain
[10:22] <Hobbsee> hah
[10:22] <mrevell> Hobbsee: Or is that a terrible insult and I've made a cultural faux-pas?
[10:22] <Hobbsee> mrevell: it is an insult, yes.
[10:22] <mrevell> Hobbsee: In which case, erm, errr...
[10:22] <Fujitsu> That's the one.
[10:22] <mrevell> Hobbsee: Phew, thanks for the attack, the universe is back in balance.
[10:22] <mrevell> Fujitsu: Rocketfuel
[10:23] <mrevell> Fujitsu: Not sure on that. Don't think so. let me check.
[10:23] <Hobbsee> heh
[10:23] <Fujitsu> mrevell: I know it isn't now, but I think it might be nice if it was.
[10:23] <mrevell> Fujitsu: Right, got you.  It'll make more sense for you to file it.
[10:31] <Le-Chuck_ITA> Hi all
[10:31] <Le-Chuck_ITA> somebody going to join me to the lp beta testers team?
[10:31] <Le-Chuck_ITA> I would like to provide a bugfix via PPA
[10:31] <Le-Chuck_ITA> I already sent e-mails, subscribed to the mailing list and all the rest
[10:32] <Fujitsu> Le-Chuck_ITA: Why not provide a bugfix through proper channels?
[10:32] <Le-Chuck_ITA> I want to provide the package for testing
[10:32] <Le-Chuck_ITA> it's a new upstream release
[10:33] <Le-Chuck_ITA> and if I am not wrong the way to sponsored uploads should become PPA soon
[10:33] <Le-Chuck_ITA> ?
[10:34] <Hobbsee> Fujitsu: if it's a new upstraem release, it will need testing elsewhere, yes.
[10:34] <Hobbsee> Le-Chuck_ITA: you know, you got answered a few minutes after you left, last time
[10:35] <Le-Chuck_ITA> what time :)?
[10:35] <Le-Chuck_ITA> you mean today?
[10:35] <Hobbsee> whenever i last saw you ask about ppa's.  not today, on any timezone, iirc.
[10:35] <Le-Chuck_ITA> ok
[10:35] <Le-Chuck_ITA> I have to find a way
[10:36] <Le-Chuck_ITA> to leave chat windows closed
[10:36] <Le-Chuck_ITA> in gaim and get warned for certain keywords
[10:36] <Le-Chuck_ITA> or just to close IRC windows without leaving the channel
[10:36] <Le-Chuck_ITA> sorry for that, Hobbsee
[10:37] <Le-Chuck_ITA> however I am now reading the reply in the channel log
[10:39] <mrevell> Le-Chuck_ITA: Hi!
[10:40] <Le-Chuck_ITA> Hi mrevell: I have just read your reply!
[10:40] <mrevell> Le-Chuck_ITA: Ah, great :)
[10:40] <Le-Chuck_ITA> Ok I'll wait
[10:40] <mrevell> Le-Chuck_ITA: I'm just working my way through applicants to the beta team, so you should be in it this morning.
[10:40] <Le-Chuck_ITA> I hate to leave windows opened, that's the only reason why I leave channels :)
[10:40] <mrevell> right :)
[10:40] <Le-Chuck_ITA> ok, that's wonderful
[10:42] <Le-Chuck_ITA> yeah
[10:42] <Le-Chuck_ITA> I used xchat for a long time
[10:42] <Le-Chuck_ITA> gaim is just comfortable but I see it lacks some feature
[10:50] <ubotu> New bug: #138828 in launchpad "LP bzr revision number largely useless with rocketfuel mapping" [Undecided,New]  https://launchpad.net/bugs/138828
[11:10] <Le-Chuck_ITA> bye all, time to close this window :)
[11:47] <proppy> hi
[11:48] <proppy> Is there an rss feed associated to each bug report ?
[11:48] <pochu> There isn't, but if you subscribe it, you'll be notified by mail with every change.
[11:48] <pochu> (there isn't *yet*)
[11:49] <proppy> Ok, thanks :)
[11:49] <proppy> there is not +rdf tricks either ?
[11:50] <proppy> like https://launchpad.net/%7Eproppy/+rdf
[11:52] <mpt> proppy, do you have any reason for preferring RDF for bug reports, rather than Atom or RSS?
[11:54] <mpt> (to answer your question, we don't have RDF for bug reports either)
[11:55] <ubotu> New bug: #138844 in launchpad-bazaar "bazaar-portlet-importstats is cruft" [Undecided,New]  https://launchpad.net/bugs/138844
[12:02] <proppy> mpt: no, I was just asking if rdf was available because I know it is from other launchpad pages, like groups or peoples
[12:02] <proppy> Is there a way I can help to implement rss support ?
[12:02] <proppy> (or rdf)
[12:03] <Fujitsu> Machine parsable bug pages with more than the absolute basics... hahahaha.
[12:04] <mpt> proppy, I'll get back to you on that
[12:04] <proppy> np, I believe the necessary info are on my launchpad page linked above
[12:05] <mpt> ok
[02:13] <Hobbsee> mpt: ping
[02:14] <Hobbsee> just checking, is mainline r4831 currently on edge?
[02:14] <Hobbsee> (https://bugs.edge.launchpad.net/malone/+bug/134220)
[02:14] <ubotu> Launchpad bug 134220 in malone "Bug page has no information about current package version" [High,Fix committed]   - Assigned to Matthew Paul Thomas (mpt)
[02:16] <Fujitsu> Hobbsee: I don't believe so.
[02:16] <Hobbsee> darn
[02:17] <Hobbsee> oh, does it go on staging instead?
[02:17] <Fujitsu> It's hard to tell, because the revision numbers don't match, and there's no way for mortals to tell between them (I filed that bug earlier..)
[02:17] <Fujitsu> No, it'll go to edge first, AFAIK.
[02:18] <Hobbsee> either i'm blind, or it hasnt appeared on staging yet
[02:18] <Hobbsee> er, edge
[02:18] <Hobbsee> nope.  no dice
[02:18] <mrevell> hi Hobbsee
[02:19] <Hobbsee> mrevell: greetings!  what's the purpose of edge, if not to show all the currently committed code?
[02:19] <mrevell> Hobbsee: Howdy. Its purpose is to allow the code to be used in-situ, before release. Is that what you mean by "showing" code?
[02:20] <Hobbsee> mrevell: in-situ?
[02:20] <Hobbsee> oh, in situation
[02:21] <mrevell> Hobbsee: In place.
[02:21] <Hobbsee> mrevell: why, then, is the above feature not implemented again on edge?
[02:22] <mrevell> bug 134220?
[02:22] <ubotu> Launchpad bug 134220 in malone "Bug page has no information about current package version" [High,Fix committed]  https://launchpad.net/bugs/134220 - Assigned to Matthew Paul Thomas (mpt)
[02:22] <Hobbsee> mrevell: yep
[02:22] <mrevell> let me take a look
[02:24] <pochu> Hobbsee, mrevell: mpt said it's fixed in r4831, but edge is running build 4826
[02:24] <pochu> I guess that's the cause :)
[02:24] <Hobbsee> pochu: ahh.  how can i find what build it's running?
[02:25] <mrevell> pochu: That's a cause but not a reason :)
[02:25] <Hobbsee> oh, i see
[02:25] <pochu> Hobbsee: left down corner
[02:25] <Hobbsee> right, actually
[02:25] <Hobbsee> but thanks :)
[02:25] <pochu> hehe
[02:26] <mrevell> Hobbsee: Updates to edge are suspended at this stage of the LP dev cycle.
[02:26] <mrevell> Hobbsee: Let me check when updates will resume.
[02:27] <Hobbsee> mrevell: then the next question is...if staging is at 4845, why is it not there either?  or is this to do with the revision numbers not matching?
[02:29] <Fujitsu> Hobbsee: Cherry-pickings and the like stuff build numbers up.
[02:29] <Hobbsee> Fujitsu: right
[02:30] <Hobbsee> this all makes soyuz look simple.
[02:32] <mrevell> Hobbsee: I'm on the case to get a good answer.
[02:32] <Hobbsee> mrevell: cool, thanks
[02:32] <matsubara> hi, what rev specifically you're looking for Hobbsee?
[02:35] <Hobbsee> matsubara: heya!   r4831
[02:39] <matsubara> Hobbsee: take bug https://bugs.staging.launchpad.net/ubuntu/+source/firefox/+bug/44062 as an example. if you expand the firefox (ubuntu) bugtask you'll see there's a Latest release: in the table.
[02:39] <ubotu> Launchpad bug 44062 in firefox "Firefox allows cookies to be set for second-level domain hierarchies" [High,Confirmed]   - Assigned to Mozilla Bugs (mozilla-bugs)
[02:42] <matsubara> Hobbsee: we've stopped updating edge because this week we had to land DB patches. Since edge uses the same DB as lpnet, we can't update the code, until we update the DB.
[02:43] <Hobbsee> matsubara: ohh...i see.
[02:43] <Hobbsee> yep
[02:43] <Hobbsee> meh.  that doesnt fix the bug in the way that is actually useful
[02:45] <Fujitsu> Hm, that's really out of place and hidden.
[02:48] <matsubara> Hobbsee, Fujitsu: if that UI isn't working for you, please leave a comment in the bug report telling mpt why not and explaining your use case.
[02:49] <Hobbsee> matsubara: will do.  might poke him over irc first, then take that to the bug report - as we do need this fixed.
[02:49] <Hobbsee> (reasonably quickly)
[02:51] <matsubara> thanks Hobbsee
[03:18] <evadave> This is probably a silly question, and I have read help.launchpad.net, but, how does a project admin create a list of FAQs? (so that it appears under "List all FAQs". Thanks in advance.
[03:21] <kiko> evadave, you create them based on questions, I believe
[03:22] <evadave> Yeah, I created one but I couldn't see how to make it a FaQ
[03:22] <evadave> s/FaQ/FAQ/
[03:29] <kiko> evadave, based on answered questions, though
[03:29] <kiko> evadave, I'll see to adding a new blog post about this once I find out
[03:35] <evadave> I answered it too :/
[03:36] <evadave> Does somebody else have to answer it? ;)
[03:37] <evadave> Oh I see, it has to be set answered, not solved, and then you can make it a FAQ!
[03:38] <Farranco> Can one use LaunchPad to translate a project that is not open source? Or does LaunchPad require as part of its term of use that all projects be open source?
[03:39] <kiko> Farranco, it's for open source. contact statik if you'd like to use it for a non-OSS project.
[03:40] <radix> Farranco: you probably want to talk to statik about our comme...
[03:40] <radix> yeah
[03:40] <mrevell> Farranco: Ah, kiko beat me to it :)
[03:40] <statik> hi Farranco, I'm on the phone now, but you can mail me at elliot at canonical and I'll do my best to help
[03:41] <Farranco> Thank you. I have an OS-X project and I make my own shareware and LaunchPad looks nice to help me coordinate with my users as they do the translations out of their own time. Thank you for the answers. I'll drop you an email.
[04:37] <mvo> is there a way to disable using edge.lp.net temporarly? I seem to be unable to reassign bug #137324 with it (got OOPS-619EC59)
[04:37] <ubotu> Launchpad bug 137324 in update-manager "Upgrade from 6.10 to 7.04 failed on mysql-server" [Undecided,New]  https://launchpad.net/bugs/137324
[04:38] <Ng> mvo: if you go to https://launchpad.net/ you can disable it for 2 hours
[04:38] <Ng> I asked the same thing yesterday ;)
[04:42] <mvo> aha, thanks! I went to edge.launchpad.net and was expecting the option there. silly me
[04:42] <Ng> I did precisely the same thing ;)
[04:43] <Nafallo> haha
[04:43] <Nafallo> file a bug
[04:43] <mvo> heh :)
[04:43] <mvo> hrm, looks like I get the same error on the regular launchpad :/ (OOPS-619D1104)
[04:43] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/619D1104
[04:44] <Nafallo> will any sysadmin go to the releaseparty for gutsy, and will they have a car with a space for a tiny ISP-person if something goes wrong? ;-)
[04:45] <Nafallo> mvo: disable it! ;-)
[04:46] <Nafallo> ehrm... I'm not in the channel I thought I was in :-P
[04:51] <kiko> mvo, let me check.
[04:52] <mvo> kiko: and don't tell me its because I have too many bugs assigned to me :P I know that already
[05:46] <ubotu> New bug: #138916 in launchpad "The number of translations is wrong" [Undecided,New]  https://launchpad.net/bugs/138916
[05:46] <kiko> mvo, that's not an error. it's a timeout.
[05:47] <kiko> :)
[06:13] <mvo> kiko: anything I can do to reassign this bug or to workaorund the timeout? I seem to always get it when trying to reassign the bug
[06:15] <kiko> mvo, keep trying? unfortunately I still need to get this bug fixed meanwhile
[06:30] <ubotu> New bug: #138928 in launchpad-answers "There is no way to create a FAQ without a question" [Undecided,New]  https://launchpad.net/bugs/138928
[06:35] <ubotu> New bug: #138929 in launchpad-answers "When no FAQs exist, the link to FAQ page is really weird" [Undecided,New]  https://launchpad.net/bugs/138929
[06:54] <infwonder> hi all! is there any Launchpad admin here?
[06:55] <Odd_Bloke> infwonder: There probably is, but it's best to ask your question and see if anyone answers.
[06:55] <infwonder> I have some questions about the auto-generated user info pages on Launchpad
[06:56] <Odd_Bloke> infwonder: Try asking them here and, if you don't get the answers you're looking for, try the launchpad-users mailing list.
[06:58] <infwonder> ok, thanks! A friend of mine did some translation for an open-source project, so Lauchpad created a webpage about him, but he is not confortable about it and want to remove the page, is it doable ?
[07:07] <infwonder> anyone ?
[07:08] <mrevell> infwonder: Hi
[07:08] <infwonder> hi !
[07:08] <mrevell> infwonder: I work on the Launchpad team so I may be able to help.
[07:08] <infwonder> thank you!
[07:08] <infwonder> did you see my question?
[07:09] <infwonder> or should I post them again?
[07:09] <mrevell> infwonder: yes, just writing an answer :)
[07:09] <infwonder> thank you
[07:10] <mrevell> infwonder: What information makes your friend uncomfortable?
[07:11] <infwonder> they use his name (real English name ) in the webpage, I think Launchpad got the name from the "about" page of the software he translated
[07:12] <mrevell> infwonder: I see. Do you have a link to the page? It's okay, you can send it to me in a private message if you don't want to do it publicly.
[07:14] <infwonder> ok I sent it :)
[07:15] <mrevell> infwonder: Thanks :)
[07:15] <infwonder> can you disable the page  for him ?
[07:16] <mrevell> infwonder: Your friend should visit that page and click "Hey I'm xxxxxxxxx". Doing that he can claim that Launchpad account. Once he's claimed the account, he can then change the display name to something that isn't his real name. It should take no more than 5 minutes.
[07:17] <ddaa> ...
[07:17] <ddaa> sorry, wrong window
[07:18] <mrevell> infwonder: I have to go afk for a while but if your friend has any problems, he or you can email me. use<EMAIL_ADDRESS>[07:19] <infwonder> well, he was upset because he wasn't noticed about this page , you should have notice every user when you want to make a public pages like that, he think his privacy is offended
[08:25] <ubotu> New bug: #138949 in malone "There should be a means by which bugtrackers whose bugs have been migrated to launchpad can be identified." [Undecided,New]  https://launchpad.net/bugs/138949
[08:33] <LaserJock> cprov: can we get some sort of PPA feature overview and roadmapish items on the agenda?
[08:33] <LaserJock> it seems to me that there are a few things that PPA already does but people don't know about
[08:33] <LaserJock> i.e. being able to restart a build
[08:34] <laga> right
[08:34] <laga> i didn't know that.
[08:36] <cprov> LaserJock: sure, good point, add it to the wiki page
[08:37] <kiko> cprov, LaserJock: I think cprov's comment on the ogre model is spot on
[08:42] <LaserJock> the big things is going to be what things are different from PPA than the Debian/Ubuntu archives
[08:42] <LaserJock> and how to actually use the UI
[08:43] <LaserJock> we can give people pointers on .dput.cf and stuff
[08:43] <LaserJock> but we really need to document the diff between PPA and all the "Packaging for Debian/Ubuntu"  guides out there
[08:44] <kiko> carlos, danilos: the current rosetta UI is very slick. nice work.
[08:45] <kiko> carlos, danilos:the only remaining cruft is the "someone should review" and the "add more lines"  button
[08:45] <LaserJock> kiko: what are the chances of getting some info on "future of PPA" like upcoming features, etc. ?
[08:46] <LaserJock> cprov: is it ok if I take out the "What's wrong with REVU" agenda item. It's gonna cause us a lot of grief right now
[08:46] <carlos> kiko: indeed, 'someone should review' should be our next big target once db changes phase2 is completed
[08:47] <cprov> LaserJock: yes, remove it for now, as agreed on email.
[08:48] <kiko> "What's wrong" is a very negative way of putting /anything/
[08:52] <LaserJock> well, I think he said "what's missing"
[08:52] <LaserJock> I was paraphrasing ;-)
[08:52] <LaserJock> man, the wiki preview on help.lp.net is really bad
[08:52] <LaserJock> the "Draft" watermark is not a watermark at all. I can't read anything
[08:53] <LaserJock> kiko, cprov: https://help.launchpad.net/PPA101 look ok?
[08:56] <cprov> LaserJock: yes, it does, thanks. I will try to add more comments this evening.
[09:03] <kiko> look cool!
[09:03] <kiko> err
[09:03] <kiko> looks cool!
[09:18] <fl33tingtime> is this the place to start a new ubuntu-related project?
[09:18] <fl33tingtime> or ask about it
[09:29] <fl33tingtime> hello....
[09:29] <fl33tingtime> anyone there?
[09:29] <fl33tingtime> as in listening....
[09:30] <fl33tingtime> ping
[09:31] <laga> ?
[09:31] <fl33tingtime> thnx.
[09:31] <fl33tingtime> a new ubuntu related project is on my mind
[09:31] <fl33tingtime> is it to be discussed here?
[09:32] <fl33tingtime> ubuntu-love seems to be inactive
[09:32] <laga> not sure if this is the right channels
[09:32] <laga> channel*
[09:34] <ddaa> That's not the right channel
[09:34] <ddaa> I think the folks in #motu would be able to guide you.
[09:35] <fl33tingtime> ddaa : thnx!
[09:43] <ddaa> mrevell: do we have some documentation about where to redirect various ubuntu-related requests?
[09:43] <mrevell> ddaa:  brb phone
[09:44] <mrevell> sorry ddaa
[09:44] <mrevell> back now
[09:44] <mrevell> ddaa: Do you for things similar to that above?
[09:44] <ddaa> I do mean for things similar to that above, if "mean" was indeed the missing word in your sentence
[09:45] <ddaa> Or for example when we got people asking generic packaging questions, at first we said #ubuntu-devel, then a MOTU told us that #motu was better.
[09:46] <ddaa> My problem is that we are embarrassingly ignorant of the structure of the Ubuntu community...
[09:48] <mrevell> ddaa: Yes, sorry, I did mean to write "mean". I'll poke Jono about this, see what he thinks.
[09:48] <ddaa> Thank you.
[09:52] <LaserJock> we could do that pretty easily
[09:53] <LaserJock> mrevell, ddaa: there is https://help.ubuntu.com/community/InternetRelayChat
[09:54] <kiko> ddaa, who's "we"? I claim to know something about the community structure, personally!
[09:54] <LaserJock> but generally you want #ubuntu-motu for packaging/Universe, #ubuntu-devel for general development (not support), and #ubuntu for support
[09:54] <ddaa> it is my impression that "we", as a team, do not know enough about it.
[09:55] <ddaa> we = launchpad developers, collectively
[09:55] <ddaa> maybe the issue is more that I do not know who is knowledgeable in the team.
[09:55] <kiko> I dislike blanket statements that seem to suggest that we're disconnected from our users
[09:56] <kiko> and I'm in a terrible mood today
[09:56] <kiko> so beware!
[09:57] <ddaa> LaserJock: I find this page somewhat scary
[09:58] <kiko> El Phantasmo and the Chicken-run Blast - Wine, Women and Song Mix by White Zombie from Supersexy Swingin' Sounds
[09:58] <kiko> !
[09:58] <LaserJock> ddaa: yeah, you guys might want to have a LP-specific version on your wiki
[10:00] <LaserJock> the big thing is to not send people to #ubuntu-devel for support or packaging questions
[10:00] <LaserJock> and to not send people to #ubuntu-motu for generic Ubuntu questions
[10:00] <mpt> Gooooooooooooooooooooood morning Launchpadders!
[10:01] <ddaa> LaserJock: by "generic ubuntu questions" you mean "generic ubuntu user questions"?
[10:01] <ddaa> I have some idea of the scope and purpose of #ubuntu.
[10:02] <LaserJock> ddaa: well, generic development questions perhaps as well
[10:03] <ddaa> where should these go, then?
[10:03] <LaserJock> like the question you got earlier
[10:03] <ddaa> BTW, I am not sure what qualifies as "generic development question"...
[10:03] <LaserJock> well, most likely #ubuntu-devel
[10:03] <LaserJock> well, MOTU is Universe
[10:03] <LaserJock> so if somebody is asking about something in Main then it should go to #ubuntu-devel
[10:04] <LaserJock>  generally, #ubuntu-motu is Universe+packaging
[10:04] <ddaa> okay, so we can use #ubuntu-devel as our main hub, except for users requesting help about ubuntu usage and generic packaging?
[10:04] <LaserJock> that'll probably work
[10:04] <LaserJock> the problem is that generally #ubuntu-motu is a bit ... softer than #ubuntu-devel
[10:05] <ddaa> what sort of "softer"?
[10:05] <LaserJock> not so harsh
[10:06] <LaserJock> but really #ubuntu-motu shouldn't have to field all questions
[10:06] <ddaa> right, I am a bit hesitant to send to send enthusiastic yet probably inexperienced people there
[10:06] <LaserJock> yeah, I know what you mean
[10:07] <LaserJock> it's also not great for people to get bounced around IRC channels :-)
[10:08] <LaserJock> wow, already 70 PPAs
[10:08] <ddaa> that's why I asked mrevell. But seen we will have the Word From The Chin.
[10:08] <ddaa> s/seen/soon/
[10:08] <LaserJock> shesh, geser's got 302 binaries
[10:08] <laga> LaserJock: i'm wondering, what's the biggest ppa?
[10:09] <LaserJock> depends on what you are measuring
[10:09] <laga> size in bytes? ;)
[10:09] <LaserJock> hmm, don't know that
[10:10] <laga> ah, k
[10:10] <LaserJock> geser's got the most binaries
[10:10] <laga> mine is around 2 GiB right now because old stuff is not automatically purged yet
[10:10] <LaserJock> ~kubuntu-members has got the most source packages
[10:10] <LaserJock> I could totally bloat mine up
[10:11] <LaserJock> I was going to do some TeX stuff
[10:11] <LaserJock> that's around ~700MB per upload
[10:11] <ddaa> Maybe we should not have this sort of "mine is bigger than yours" contest?
[10:11] <LaserJock> what? no karma for PPA uploads? :-)
[10:12] <kiko> no karma for any uploads, period!
[10:12] <LaserJock> I know, it's been on my Top 5 forever
[10:13] <kiko> let's get PPAs and gutsy out and fix that
[10:16] <geser> LaserJock: http://ubuntu.joejaxx.org/ must be sufficient till we get karma for uploads
[10:19] <joejaxx> geser: btw updating that now :D
[10:21] <LaserJock> geser: works fine for you, you're on the list
[10:21] <LaserJock> geser: it's just depressing for me ;-)
[10:22] <geser> joejaxx: iirc you parse the +packages list from LP? is it also counting the ppa uploads which appear also on those pages?
[10:22] <geser> LaserJock: :) upload more
[10:46] <tormod> I made a successful upload to my new PPA, no e-mails, but also no builds in any state. How long should it take?
[10:49] <kiko> tormod, it usually takes a while, depending on how busy the builders are
[10:50] <tormod> kiko: thanks. like 20min or hours?
[10:50] <tormod> is there a way to what the builders are doing, like for the normal ubuntu builders?
[10:51] <tormod> *to see
[10:54] <geser> tormod: yes
[10:54] <LaserJock> tormod: https://edge.launchpad.net/+builds/samarium and https://edge.launchpad.net/+builds/promethium
[10:54] <LaserJock> bah, you might need to take the edge. off of that URL
[10:55] <tormod> LaserJock: it redirects to edge anyway
[10:55] <tormod> they seem to be idle ?!
[11:00] <tormod> the build history seems busy. so I guess my upload is not going anywhere?
[11:02] <tormod> I got the "accepted" e-mail now.
[11:08] <LaserJock> tormod: it just takes a while for everything to get processed
[11:10] <tormod> LaserJock: ok no problem. just got worried when I had no feedback and the build servers seemed idle.
[11:29] <kiko> LaserJock, the .changes file is created automatically by dput, right?
[11:29] <LaserJock> not by dput
[11:29] <LaserJock> by debuild
[11:29] <kiko> oh
[11:29] <kiko> thanks.
[11:29] <LaserJock> dput spits out a .upload file
[11:30] <LaserJock> and you gotta either remove it or use dput -f if you want to reupload the same package
[11:33] <LaserJock> is there a particular reason that PPAs can only have FLOSS software?
[11:33] <lifeless> LaserJock: dpkg-buildpackage in fact
[11:33] <lifeless> IIRC :)
[11:33] <LaserJock> lifeless: well yes, I just didn't want to type that much ;-)
[11:33] <lifeless> :)
[11:47] <mdke> anyone know what directory structure is needed for pot/po files to be automatically imported from a package
[11:48] <mdke> ?
[11:48] <LaserJock> I don't think it has to be a specific structure
[11:49] <LaserJock> could be totally wrong though
[11:50] <mdke> LaserJock: I believe so, but I'm not sure; haven't found details in the wiki
[11:51] <LaserJock> yeah, it's quite difficult to find documentation on the packaging part of translations
[11:53] <LaserJock> yeah, they're killing off all the cool names ;-)
[11:56] <mdke> bah, search is still screwed on the wiki
[11:57] <kiko> mdke, we need to blame newz2000!
[11:57] <kiko> I gave him a #@@!# fix about a month ago!!
[11:57] <mdke> kiko: harsh, the bug says he's pushed a fix and is assigned to the sysadmins
[11:58] <mdke> (bug 110181)
[11:58] <Ubotu> Launchpad bug 110181 in launchpad "search box in help.launchpad.net wiki template is broken" [High,Fix committed]  https://launchpad.net/bugs/110181 - Assigned to The Canonical Sysadmins (canonical-sysadmins)
[11:58] <kiko> Rinchen, is there an RT for the above?
[11:58] <kiko> mdke, harsh is my middle name!!!!
[11:59] <Rinchen> kiko, yes indeed
[11:59] <mdke> kiko: we knew that
[12:00] <kiko> my eyes water
[12:00] <kiko> and yet I drill on through millions of LOC
[12:00] <mdke> hmm, LOC, *googles*
[12:00] <mdke> letter of credits?
[12:01] <mdke> London Oncology Clinics?
[12:01] <Ubotu> New bug: #138991 in rosetta "Use TranslatableLanguageVocabulary wherever "translatable languages" are checked/listed/chosen" [Undecided,New]  https://launchpad.net/bugs/138991
[12:01] <Ubotu> New bug: #138992 in launchpad "Bug suggestions when reporting a bug should include bug assignee" [Undecided,New]  https://launchpad.net/bugs/138992
[12:01] <kiko> lines of code!!!!!
[12:01] <mdke> shame
[12:06] <Ubotu> New bug: #138993 in launchpad "All bug listings should include an assignee column" [Low,New]  https://launchpad.net/bugs/138993
[12:11] <Ubotu> New bug: #138994 in launchpad "It would be nice if a projects had a default milestone" [Low,New]  https://launchpad.net/bugs/138994
[12:13] <mdke> damn screen. Don't suppose I missed someone answering my question about rosetta?
[12:13] <radix> doesn't look like anyone said anything interesting since you said "shame"
[12:14] <kiko> mdke, which question?
[12:14] <mdke> kiko: about what directory format is required for automatic importing of translation templates/translations from a package
[12:15] <kiko> mdke, it only works for packages in main -- you know that, right?
[12:15] <mdke> yes
[12:15] <kiko> so a few different formats are supported
[12:15] <kiko> I could swear this was documented somewhere
[12:15] <mdke> by format, I should have said layout
[12:16] <kiko> yeah
[12:16] <mdke> would this be acceptable:
[12:16] <mdke> packagename/template/template.pot ; packagename/template/cc/cc.po
[12:16] <mdke> rather than having all the po files in a single "po" directory
[12:18] <kiko> yes
[12:18] <kiko> I believe that's supported
[12:18] <mdke> rock
[12:18] <kiko> I can't seem to find the code to actually confirm that though
[12:20] <mdke> no worries, thanks for the help
[12:20] <Ubotu> New bug: #138996 in launchpad-bazaar "Please provide server-side Bazaar repositories" [Undecided,New]  https://launchpad.net/bugs/138996
[12:25] <Ubotu> New bug: #138997 in launchpad "Please allow editing of releases" [Medium,New]  https://launchpad.net/bugs/138997
[12:30] <Ubotu> New bug: #138999 in malone "Please allow for bugs to be proposed to a milestone and a series" [Medium,New]  https://launchpad.net/bugs/138999
[12:45] <Ubotu> New bug: #139002 in launchpad "Please create a release overview page similar to the milestone overview" [Medium,New]  https://launchpad.net/bugs/139002


[05:05] <lpotter> hate that.
[12:39] <ginggs> hi - are there any reasons why i should not rebuild cmake against the new libjsoncpp?
[12:47] <marlinc> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1542629
[14:15] <damascene> Hi, If I report a bug upstream and find that it's in Ubuntu too, should I report it on launchpad too?
[17:04] <marlinc> Who are the people who get packages from Debian and put them in Ubuntu?
[17:04] <marlinc> Is there a wiki page for that?
[17:04] <cjwatson> marlinc: Ubuntu developers in general, though in the majority of cases it's automatic
[17:05] <marlinc> Ah okay, because if this package https://launchpad.net/debian/+source/phpmyadmin/4:<IP_ADDRESS>-1 :)
[17:06] <cjwatson> marlinc: We don't automatically sync from experimental
[17:06] <marlinc> It fixes the following bug: https://bugs.launchpad.net/debian/+source/phpmyadmin/+bug/1542665
[17:06] <cjwatson> marlinc: Usually Debian developers upload to experimental when they're not comfortable with it having a wide audience yet
[17:06] <marlinc> Ah, that's something different then
[17:06] <marlinc> That explains why I'm not getting the package in a Debian sid chroot
[17:07] <cjwatson> I expect we'll get that once it hits unstable (assuming we aren't in import freeze by then)
[17:07] <marlinc> I do hope it gets released before any of the Ubuntu freezes because the phpmyadmin package is completely broken at the moment
[17:07] <marlinc> Thanks for the explanation cjwatson
[18:27] <damascene> Hi, If I report a bug upstream and find that it's in Ubuntu too, should I report it on launchpad too?
[18:31] <rbasak> damascene: if you want some action taken in Ubuntu or want to communicate with other affected Ubuntu users, then sure. Otherwise, no need, since any fix will get to Ubuntu eventually anyway.
[18:35] <damascene> I see, do Ubuntu developers apply some patches to an older version of a package if the upstream did not make a patch for it?
[18:37] <rbasak> For an existing Ubuntu stable release? To fix bugs, yes: https://wiki.ubuntu.com/StableReleaseUpdates
[18:37] <rbasak> This assumes a patch is available of course.
[18:38] <rbasak> (and thtat I've understood your question - you didn't provide any specifics)
[18:39] <damascene> for example lxde-panel for RTL languages is broken, if the upstream make a fix they probably will not port it back to the version in 16.04
[18:39] <damascene> this is one example
[18:42] <rbasak> If no fix is available, then it can't be fixed by definition, unless someone makes a fix, at which point it might be a candidate for an SRU depending on the nature of the fix.
[18:43] <damascene> thank for explaining it
[18:43] <rbasak> No problem.


[00:08] <thumper> how warm / cold is it in Dallas?
[00:08] <thumper> should I pack warm clothing?
[00:11] <jelmer> thumper: I'd recommend a winter coat
[00:11] <jelmer> It's 2 or 3 degrees (Celcius) at the moment I think
[00:15] <thumper> crap
[00:15] <thumper> jelmer: I take it the hotel is warm enough?
[00:15] <wgrant> thumper: It's going to vary.
[00:15] <wgrant> thumper: It looks like 16-17 early next week.
[00:15] <wgrant> But 1 tomorrow.
[00:15] <wgrant> And 4 later next week.
[00:15] <thumper> hmm...
[00:15] <wgrant> You'll need to take roughly everything.
[00:16] <jelmer> thumper: the hotel is nicely warm. At least they don't have the airco on "freeze" mode like in some places.
[00:16] <thumper> wgrant: when are you heading out?
[00:17] <wgrant> thumper: Sunday.
[00:18] <wgrant> You?
[00:20] <thumper> same
[00:27] <lavid> hello! i'm trying to fix https://bugs.launchpad.net/bzr-hg/+bug/518510 (since it's blocking something else i'm working on) and i'm trying to get my launchpad instance to import a mercurial repository so i can reproduce the bug locally. i don't think that functionality works on dev instances of launchpad. does anyone have any tips on either: how to better debug this issue or how to get my dev instance of launchpad to also support runn
[00:27] <_mup_> Bug #518510: assertionerror in _find_most_recent_ancestor  <Bazaar Hg Plugin:Triaged> < https://launchpad.net/bugs/518510 >
[00:28] <wgrant> lavid: You shouldn't need to run a local Launchpad instance to test that.
[00:29] <jml> huwshimi: hello & welcome!
[00:30] <lavid> wgrant: fair enough. i guess i was hoping to get a better idea as to what's happening further up the stack trace. how'd you recommend tackling this?
[00:39] <jelmer> lavid: install bzr-hg as a plugin in bzr
[00:39] <jelmer> lavid: then try to clone a mercurial branch and doign incremental pulls into it
[00:40] <wgrant> I am trying to provide a precise recipe, but my machine is being objectionable.
[00:40] <jelmer> One of the key things to the bug appears to be that it only happens on incremental pulls that import new revisions.
[00:41] <lavid> jelmer: cool. thanks. any tips for running the bzr-hg plugin via eclipse or some other visual debugger?
[00:41] <jelmer> lavid: Setting BZR_PDB=1 will open a pdb interactive debugger for you when an exception occurs in bzr
[00:42] <jelmer> I don't have any experience with Python in Eclipse, sorry
[00:42] <poolie> hi jelmer, wgrant
[00:42] <lavid> jelmer: ooh, tasty! thank you!
[00:42] <jelmer> 'evening poolie
[00:43] <wgrant> Morning poolie.
[00:43] <wgrant> Or evening, I guess.
[01:00] <jml> see you all in a bit.
[01:01]  * jml is off for stuff.
[02:23] <thumper> oh FSF
[02:23] <thumper> FFS
[02:23] <thumper> make build dying on OSError: [Errno 4] Interrupted system call
[02:23] <thumper> still
[02:25] <wgrant> thumper: Didn't it work on Friday? :/
[03:10] <thumper> wgrant: it did
[03:11] <thumper> wgrant: so it seems to be temperamental
[03:12] <wgrant> thumper: Yay.
[03:12] <wgrant> thumper: It wasn't a parallel make?
[03:13] <thumper> I don't think so
[03:16] <wgrant> thumper: Does it die on the .join()?
[03:16] <thumper> wgrant: no, times out
[03:17] <thumper> wgrant: actually, yes
[03:17] <thumper> File "./utilities/create-lp-wadl-and-apidoc.py", line 86, in main
[03:18] <thumper> sorry, didn't look enough up the stack
[04:37] <thumper> wgrant: any idea how to get around the make problem?
[04:37] <thumper> I can't make run
[04:37] <thumper> :(
[04:37] <thumper> which makes it hard for me to test this thing
[04:41] <wgrant> thumper: You could hack it to not use multiprocessing. Or use multiprocessing, but serially.
[04:41] <wgrant> It is tempting to debug, except for the whole POSIX signal fuckedness.
[04:43]  * thumper loses the will to fix it on a Monday afternoon and calls it a day
[06:06] <lifeless> [06:06] <lifeless>     Hard / Soft  Page ID
[06:06] <lifeless>       63 /  293  BugTask:+index
[06:06] <lifeless>       36 / 4408  Archive:+index
[06:06] <lifeless>       21 /  294  Distribution:+bugs
[06:06] <lifeless>       13 /  112  ProjectGroupSet:CollectionResource:#project_groups
[06:06] <lifeless>       12 /  177  POFile:+translate
[06:06] <lifeless>       12 /    0  ProjectGroup:+milestones
[06:06] <lifeless>        8 /   12  NullBugTask:+index
[06:06] <lifeless>        7 /  201  Question:+index
[06:06] <lifeless>        6 /   13  Branch:+index
[06:06] <lifeless>        5 /    4  Cve:+index
[06:08] <wgrant> Does anyone happen to know why Storm would be doing lots of 'SELECT 1 FROM foo WHERE foo.id=bar' in a test after invalidating the store?
[06:08] <wgrant> It doesn't seem to do that in production.
[08:48] <adeuring> good morning
[09:06] <al-maisan> Good morning !
[14:09] <bigjools> benji: good morning
[14:10] <benji> morning, julius maximus
[14:10] <bigjools> heh, never been called that before
[14:10] <bigjools> I'm still struggling to get my dev environment fixed :(
[14:11] <bigjools> I downgraded launchpadlib to 1.6.5 (which is the last version I had an egg for)
[14:11] <bigjools> and the librarian won't start up in tests still, I  get loads of "No handlers could be found for logger "librarian""
[14:12] <benji> hmm, that doesn't sound related to launchpadlib; I can't imagine why it'd be screwing with the librarian's logger
[14:13] <bigjools> me neither
[14:16] <jcsackett> benji: can you do qa for bug 686690?
[14:16] <_mup_> Bug #686690: 1.8.0 breaks login_with() API compat with existing credentials files, and forces keyrings <desktop-integration> <qa-needstesting> <regression> <launchpadlib :Fix Committed by benji> < https://launchpad.net/bugs/686690 >
[14:18] <leonardr> jcsackett: martin has confirmed the behavior, so i think we are ok
[14:18] <jcsackett> leonardr: ok, so i can mark that as qa-ok then?
[14:19] <leonardr> jcsackett: i'm about to upgrade launchpadlib in launchpad again. let's mark it qa-ok after i test that
[14:19] <jcsackett> leonardr: sounds good. thanks.
[14:22] <jcsackett> gmb: can you do qa for bug 686690?
[14:22] <_mup_> Bug #686690: 1.8.0 breaks login_with() API compat with existing credentials files, and forces keyrings <desktop-integration> <qa-needstesting> <regression> <launchpadlib :Fix Committed by leonardr> < https://launchpad.net/bugs/686690 >
[14:22] <jcsackett> sorry, gmb, bad copy paste. i meant bug 683672
[14:22] <_mup_> Bug #683672: Bug description in verbose footer should be indented by 2 spaces <lp-bugs> <qa-needstesting> <story-better-bug-notification> <trivial> <Launchpad itself:Fix Committed by gmb> < https://launchpad.net/bugs/683672 >
[14:26] <gmb> jcsackett: I will be doing so shortly; just waiting for deryck to get up-and-running with the staging mailbox.
[14:26] <jcsackett> gmb: cool, thanks.
[14:50] <bigjools> benji: at what point is the keyring doing stuff it should not at import time?  When it loads the backend, or something else?
[14:50] <bigjools> I made a keyringrc.cfg to force an alternative backend and it still goes bang
[14:52] <benji> bigjools: it's certainly doing backend selection at import time, but it may well be doing other things; did your bang look related to the SIGCHLD stealing or something else?
[14:52] <bigjools> benji: yeah, same EINTR stuff
[14:52] <benji> let me look at the keyring code and see where it's doing that registration
[14:53] <bigjools> I forced anUncryptedFileKeyring backend
[14:53] <bigjools> benji: I'm just trying to hack anything in to get me unblocked :(
[14:55] <benji> bigjools: hmm, I don't see anywhere that it explicitly registers a SIGCHLD handler; wait, didn't you say you downgraded to a pre-keyring launchpadlib?  if so, keyring shouldn't ever be imported
[14:57] <bigjools> benji: I've gone back to the latest lplib since the other once had that logger problem
[14:57] <bigjools> well, the librarian problem
[14:57] <benji> ah, ok
[14:57] <bigjools> the sigchld is registered somewhere in PyQt4
[14:57] <benji> I figured. :(
[14:57] <bigjools> according to my strace anyway
[14:58] <bigjools> it's all so frustrating :/
[14:59] <benji> bigjools: I think you can hack your launchpadlib to never import the keyring module (just comment out the import) and your LP will work (some tests will fail)
[14:59] <bigjools> ok, never thought of the obvious :)
[15:01] <bigjools> benji: ok, that reduces me back to the No handlers could be found for logger "librarian"
[15:01] <bigjools> maybe if I bang my head up the wall a bit more....!
[15:09] <lifeless> gary_poster: around?
[15:09] <mwhudson> who is release manager this time?
[15:09] <mwhudson> i ought to know this
[15:09] <gary_poster> lifeless: I am
[15:09] <gary_poster> mwhudson: jcsackett
[15:09] <lifeless> jc I thought
[15:09] <mwhudson> gary_poster: thanks
[15:09] <lifeless> gary_poster: hi; thanks for fast tracking the oops prefix updates
[15:10] <gary_poster> lifeless: hi, np.
[15:10] <mwhudson> jcsackett: which revno is being released today?
[15:10] <lifeless> gary_poster: I'm wondering when that goes live (and if it will mean that the oops reports mailed to the list change accordingly)
[15:10] <mwhudson> ah, db-stable 10119
[15:11] <gary_poster> lifeless, the intent is today, and yes.
[15:11] <lifeless> mwhudson: huh no
[15:11] <lifeless> we deploy from stable
[15:11] <lifeless> https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
[15:11] <lifeless> mwhudson: rev 12177
[15:11] <lifeless> mwhudson: and we're blocked on rev 12167
[15:11] <lifeless> jcsackett: ^
[15:11] <mwhudson> ah cool
[15:12] <mwhudson> well, not the being blocked part
[15:12] <mwhudson> but that means the fix i care about (and just qa-ed) is going to be released
[15:13] <jcsackett> mwhudson: we're deploying on the 12th, not the 10th. did i say the 10th in an email?
[15:13] <mwhudson> errr
[15:13] <mwhudson> no,
[15:13]  * jcsackett has written a lot of emails lately, very well could have goofed.
[15:13] <mwhudson> can i blame jetlag?
[15:13] <mwhudson> :-)
[15:13] <jcsackett> mwhudson: yes you can. :-)
[15:13] <lifeless> jcsackett: we ar edeploying from stable, right ?
[15:13] <lifeless> gary_poster: sweet, thanks.
[15:13] <gary_poster> np
[15:14] <jcsackett> lifeless: correct.
[15:14] <lifeless> jcsackett: great, my heart can start beating again
[15:14] <jcsackett> we need to deploy at least through r12177 on stable.
[15:15] <jcsackett> 10119 was the db revision we qa-ed and merged on friday, lifeless.
[15:15] <lifeless> jcsackett: thanks
[15:15] <jcsackett> np.
[15:16] <bigjools> gary_poster: can you spare me a moment please?  I've worked around the keyring problem for now, but still have a problem with the librarian in tests :(   http://pastebin.ubuntu.com/552492/
[15:16] <gary_poster> benji, leonardr, can either of you help bigjools ?
[15:18] <benji> gary_poster: I can take a look; not done much with the librarian yet though
[15:18] <lifeless> bigjools: thats weird
[15:18] <gary_poster> benji: ack.  Lemme check in with the other pending pings and I'll see what needs to be handled
[15:18] <bigjools> benji: I would have asked you but you were busy fixing the keyring :)
[15:18] <lifeless> bigjools: when did this start?
[15:19] <bigjools> lifeless: once I worked around the keyring problems just now
[15:19] <lifeless> also I hate python logging, I truely do
[15:19] <bigjools> I've not had a working dev environment since Thursday last week
[15:19] <lifeless> 2011-01-10 20:30:34+0530 [-] No handlers could be found for logger "librarian"
[15:19] <benji> bigjools: it's nice to be loved
[15:19] <bigjools> lifeless: I share your hate
[15:19] <lifeless> -not- a sane failur emode
[15:20] <lifeless> bigjools: do you have a /var/tmp/fatsam.test/librarian.pid ?
[15:21] <bigjools> lifeless: ignore that, it's a relic of the earlier failure
[15:21] <lifeless> ok
[15:21] <bigjools> I delete fatsam each run
[15:21] <lifeless> ok
[15:21] <lifeless> so its leaving the pid file when it fails to start? Could you file a bug on that - we should fix that too
[15:21]  * bigjools tries again
[15:22] <bigjools> didn't we discuss that some time ago and it was hard to fix for some reason?
[15:22] <bigjools> ARGHHHHH
[15:22] <bigjools> it's working now
[15:22] <lifeless> dunno; the code is a lot cleaner than it was it should be fixable.
[15:23] <bigjools> there was a librarian left running
[15:23] <lifeless> deleting old ones on start is problematic; dealing with a failed start is simpler
[15:23] <bigjools> thought I'd killed it
[15:23] <lifeless> however it sounds like it was behaving correctly ;)
[15:23] <bigjools> define correctly :)
[15:23] <lifeless> not connecting you to an existing librarian on the statically defined port
[15:24] <lifeless> however the diagnostics are terrible - please do file a bug that it didn't manage to tell you
[15:24] <bigjools> roger
[15:24] <gary_poster> bigjools, benji, sorry, I misunderstood thought the librarian thing was a webservice/keyring thing
[15:25] <gary_poster> but so anyway, that's "resolved" enough for benji to get back to what he was doing before, bigjools
[15:25] <gary_poster> ?
[15:25] <lifeless> it might have been :)
[15:25] <bigjools> gary_poster: in all fairness, it might have been!  I had no idea what was up.
[15:25] <gary_poster> heh
[15:25] <bigjools> gary_poster: yes, thanks, I've commented out the keyring import for now
[15:27] <bigjools> lifeless: to confirm, what did you expect it to do that it was not doing?  Telling you about an existing librarian, or something else?
[15:27] <gary_poster> bigjools: ack, and that solved it, or...something solved and you are moving on?
[15:28] <bigjools> gary_poster: "worked around" would be the right phrase :)  benji is fixing the keyring code to not do stuff when it's imported
[15:28] <lifeless> hi flacoste
[15:28] <gary_poster> bigjools: lol, ack, right.  thanks
[15:29] <bigjools> gary_poster: I'm gonna have to do some work now it's fixed.  Darn.
[15:30] <gary_poster> bigjools: lol, sorry :-)
[15:30] <bigjools> :)
[15:45] <flacoste> hi lifeless
[15:47] <bigjools> sinzui: around?
[15:56] <sinzui> bigjools: yes
[15:57] <bigjools> sinzui: when you have a moment, it's not urgent, but I'd appreciate your feedback on the mockups for the new +addseries page and its new +initseries, see https://dev.launchpad.net/LEP/DerivativeDistributions#Mockups
[15:58] <sinzui> bigjools: thanks
[15:58] <bigjools> sinzui: thank *you*
[16:05] <jcsackett> benji: are bugs 651852 and 669701 qa-able?
[16:06] <benji> jcsackett: looking
[16:06] <jcsackett> thanks.
[16:07] <lifeless>  /win 70
[16:08] <benji> jcsackett: both are; 651852 is now marked qa-ok, but 669701 will have to be QAed by someone that has write permission for feature flag rules, a LOSA perhaps
[16:09] <jcsackett> benji: dig.
[16:09] <jcsackett> thanks.
[16:18] <lifeless>  /win 70
[16:18] <lifeless> bah
[16:29] <lifeless> wgrant: *all* oops/timeout are 'high'
[16:29] <lifeless> wgrant: per ZeroOopsPolicy
[16:54] <gmb> jcsackett: Bug 683672 is now qa-ok.
[16:54] <_mup_> Bug #683672: Bug description in verbose footer should be indented by 2 spaces <lp-bugs> <qa-ok> <story-better-bug-notification> <trivial> <Launchpad itself:Fix Committed by gmb> < https://launchpad.net/bugs/683672 >
[16:54] <jcsackett> gmb: thanks!
[16:55] <flacoste> lifeless: we have a problem, project can only be part of one project group
[16:56] <flacoste> which means that lazr projects cannot be part of both lazr and launchpad
[16:56] <flacoste> we could make them all part of launchpad
[16:56] <flacoste> maybe except lazr-js
[16:56] <flacoste> and even then
[17:00] <lifeless> flacoste: ah, yes we should fix that ;)
[17:00] <flacoste> lifeless: i'm moving all of them to launchpad, leaving a URL to the other lazr project
[17:00] <flacoste> anything lazr is vapourware
[17:00] <flacoste> so not really worth separating out
[17:03] <lifeless> flacoste: ah
[17:04] <lifeless> flacoste: I fear that if we don't have a brain-dead-simple way of querying all the bugs that lp interrupt squads should care about, that ones outside the default-set will get starved
[17:04] <flacoste> lifeless: i agree
[17:04] <flacoste> that's why i'm moving all the projects which we maintain to launchpad-project
[17:04] <lifeless> \o/
[17:05] <flacoste> except storm
[17:05] <lifeless> which we don't maintain :)
[17:05] <flacoste> right
[17:05] <flacoste> and when it affects us
[17:05] <flacoste> we usually have a bugtask on launchpad for it
[17:09] <flacoste> lifeless: all done
[17:12] <lifeless> gaaarh
[17:12] <lifeless> the list of projects is cached I guess
[17:12] <bigjools> flacoste: what about launchpad-buildd?
[17:12] <flacoste> lifeless: it is
[17:12] <lifeless> :(
[17:12] <flacoste> bigjools: already there i think
[17:12]  * lifeless embugginates
[17:12] <lifeless> 'launchpad auto build system'
[17:13] <bigjools> flacoste: well generally I mean, it wasn't folded into launchpad like the others, do we intend to keep it separate?
[17:13] <bigjools> (given the bug about splitting out the code from the tree)
[17:13] <flacoste> bigjools: being part of Launchpad project is orthogonal to having a separate tree
[17:14] <flacoste> bigjools: wait a moment
[17:14] <flacoste> a) yes, it should be a separate project
[17:14] <flacoste> b) it should be part of the launchpad-project so that its bugs are part of the overall bugs we need to fix
[17:14] <flacoste> list
[17:14] <bigjools> ok
[17:14] <flacoste> c) we should move it out in a separate code tree
[17:14] <bigjools> sounds reasonable to me
[17:14] <flacoste> like lazr.restful or wadllib
[17:15]  * flacoste goes to lunch
[17:35] <lifeless> flacoste: so, I can bug triage now
[17:35] <lifeless> ?
[18:27] <flacoste> lifeless: yep
[19:27] <sinzui> matsubara: Ursinha: I am looking a bug 687465. The code thinks it is reporting oopses, but I never see them in oops reports. Can you confirm that production mailman is generating oopses and we rsync them
[19:27] <_mup_> Bug #687465: add oops reporting to the xmlrpc queue runner <lp-registry> <mailing-lists> <Launchpad itself:Triaged> < https://launchpad.net/bugs/687465 >
[19:27] <matsubara> sinzui, /me looks
[19:32] <matsubara> sinzui, which machine does production mailman runs one?
[19:33] <sinzui> matsubara: I do not know. Chex do you know ^
[19:37] <Chex> matsubara: forster
[19:42] <matsubara> sinzui, there's a /srv/launchpad.net-logs/scripts/forster/mailman-xmlrpc dir in devpad and the last oops dir there is 2009-10-06. I'm trying to find a newer mailman-xmlrpc dir in devpad
[19:42] <matsubara> Chex, thanks
[19:50] <matsubara> sinzui, ./staging/asuka/mailman-xmlrpc
[19:50] <matsubara> ./scripts/forster/mailman-xmlrpc
[19:50] <matsubara> ./qastaging/asuka/mailman-xmlrpc
[19:50] <matsubara> those are the dirs where I'd expect mailman oopses to show up
[19:51] <matsubara> and by mailman oopses I mean those with MMX prefix
[19:51] <matsubara> or QSMMX for qastaging nad SMMX for staging
[19:51] <sinzui> matsubara: I think the product config says the oopses start with a c
[19:52] <sinzui> matsubara: as I noted in the bug, I found bugs in the database there were never in the daily reports
[19:55] <pcjc2> sinzui?
[20:02] <matsubara> sinzui, the reason OOPS-1795C1521 doesn't appear in the report (https://devpad.canonical.com/~lpqateam/oops-summaries/lpnet-2010-11-30.html#informational-only-errors) is because it's hidden amongst the 2858 error of the same kind. the report just show a sample of 10
[20:02] <matsubara> it's very likely OOPS-1795D3104 doesn't show up for the same reason
[20:02] <sinzui> :(
[20:03] <pcjc2> hi Sinzui, I've provided updated information on the my LP bugs you triaged earlier
[20:03] <sinzui> matsubara: what can we do to ensure mailman oopses are not information-only-errors
[20:04] <sinzui> pcjc2: I dedupped the bug
[20:04] <sinzui> well I undid regardless of that word I just mad up
[20:04] <sinzui> made
[20:04]  * sinzui gives up
[20:05] <pcjc2> cool - was a little frustrating to see them closed down so quickly given a LP dev had asked me to file them
[20:05] <matsubara> sinzui, why do you think OOPS-1795C1521 is a mailman oops?
[20:06] <pcjc2> Is the canonical-identity-provider code available to take a poke at?
[20:06] <pcjc2> or is that a closed-source part of LP?
[20:07] <sinzui> matsubara: the TB: Module lp.registry.xmlrpc.mailinglist, line 200, in getMembershipInformation
[20:08] <matsubara> sinzui, OOPS-1795C1521 has no traceback information and is the informational only oops
[20:08] <sinzui> matsubara: since mailman is an antonymous system, most of its issues will appear  related to MailingListAPIView
[20:08] <matsubara> sinzui, OOPS-1795D3104 is not an informational only oops
[20:08] <sinzui> https://lp-oops.canonical.com/oops.py/?oopsid=1795D3104
[20:08] <sinzui> has a tb
[20:09] <matsubara> yep, and that one is not informational only
[20:09]  * pcjc2 found the identity-provider branch
[20:09] <sinzui> matsubara: as for https://lp-oops.canonical.com/oops.py/?oopsid=1795D3104, Chex saw it in mailman's log we know the runner reported it
[20:13] <sinzui> matsubara: I have the death trail of Mailman's failure in November. There are a lot of oopses it reported hours before it's death http://pastebin.ubuntu.com/552570/
[20:15] <matsubara> sinzui, OOPS-1795D3104 is a timeout. it didn't show up in the report because there were a total of 218 unique timeouts on that day and only 15 showed up in the report https://devpad.canonical.com/~lpqateam/oops-summaries/lpnet-2010-11-30.html#time-outs
[20:18] <sinzui> matsubara: okay. We may need to think about that because mailman thinks it is being DoSed
[20:18] <matsubara> sinzui, so the runner tried to get_subscriptions but LP was timing out on that call and recording each oops correctly
[20:18] <pcjc2> I'm trying to login to the staging server, but it won't auth with the API provider
[20:18] <pcjc2> Sorry - OpenID provider...
[20:19] <pcjc2> Does the staging server sync the user database for production regularly? The user I'm trying to use is for a robot, and I created the account only a couple of days ago
[20:19] <sinzui> matsubara: since we are getting the oopses. I will change mailman to send the 503 and 504 information as oopses so we see mailmans conclusion that life has no meaning and kills itself
[20:20] <sinzui> pcjc2: I do not have an answer. SSO is not launchpad and we do not control it. Canonical's ISD group does and they can set Lp staging to use their staging version of SSO. We do not know the state of their DB
[20:21] <pcjc2> ok I hadn't appreciated the division there
[20:21] <sinzui> pcjc2: try qastaging. The DB is many weeks old, but it does using production SSO (login.ubuntu.com)
[20:22] <pcjc2> is that LP database ok to screw with arbitrarily?
[20:22] <pcjc2> (I'm writing a robot, and don't want to mess things up where I shouldn't!)
[20:22] <sinzui> pcjc2: as long as there is a login.launchpad.net, no one will know there that they have two separate systems
[20:22] <sinzui> pcjc2: you can do what ever you need. The DB will be restored in a week or two
[20:22] <pcjc2> Is there a political divide?
[20:23] <StevenK> Awww, mwhudson's cloak changed :-(
[20:23] <pcjc2> ok - will create some bugs against our project and play with them
[20:23] <mwhudson> only 8 months later or whatever
[20:24] <matsubara> sinzui, sounds sensible. at least that way we'll see those reported as XMLP kind of oopses, right?
[20:24] <lifeless> pcjc2: there are different teams
[20:24] <pcjc2> ValueError: qastaging is not a valid URL or an alias for any Launchpad server
[20:24] <lifeless> pcjc2: we see eye to eye but we (effectively) cannot change stuff in that code
[20:24] <sinzui> pcjc2: No. We do not want to be in the OpenID biz. Users want more from it than we do. So gave it to Ubuntu. We want to allow users to login using any OpenID service. The problem is that setting up a domain that looks like launchpad, bug does not work like Launchpad was a mistake
[20:25] <pcjc2> credentials.get_request_token(web_root="qastaging") <-- is there a URL I can use there instead?
[20:25] <pcjc2> sinzui: I'm glad you want to let logins from any OpenID service
[20:25] <pcjc2> We just migrated our bugs and stuff to LP, and some of our users wanted to use existing OpenID logins etc..
[20:29] <sinzui> pcjc2: I use launchpadlib.launchpad.Launchpad.login_with('testing', 'https://api.qastaging.launchpad.net/')
[20:40] <pcjc2> needed to drop the "api." for the credentials.get_request_token(web_root="https://qastaging.launchpad.net"). but it worked
[20:40] <pcjc2> Thanks
[20:43]  * pcjc2 does find the distinction between loging on to LP and loging on at login.launchpad.net a little amusing
[20:43] <pcjc2> but it seems less strange to me as I know vaguely how it works ;)
[20:44] <pcjc2> I wish LP had an option to let me masquerade as another user
[20:44] <pcjc2> (my robot), rather than forcing me to log off all the way
[20:45] <pcjc2> https://launchpad.net/~gpleda-launchpad-robot
[20:45] <pcjc2> Would also be nice to have somewhere that I (or the developer team) "own" that user account
[20:45] <sinzui> There is a very old bug suggesting that we provide I way to become another user or change privileges temporarily. I do not think we plan to work on it any time soon.
[20:46] <pcjc2> sounds like many of the feature requests for our project.. nice idea.. no time ;)
[20:46] <pcjc2> (or other priorities)
[20:55] <pcjc2> Is there a schedule for when DB updates to staging / qastaging get made?
[21:04] <pcjc2> OOPS-1836QS24
[21:04] <pcjc2> Can someone check that for me?
[21:05] <pcjc2> Getting a HTTP Error 404: Not Found for bug.bug_tasks on this bug:
[21:05] <pcjc2> https://bugs.staging.launchpad.net/geda/+bug/693991
[21:05] <_mup_> Bug #693991: compiz crashed with SIGSEGV in nux::IOpenGLSurface::UnlockRect() <amd64> <apport-crash> <apport-failed-retrace> <decorations> <gnome> <metacity> <natty> <window> <compiz (Ubuntu):New> < https://launchpad.net/bugs/693991 >
[21:06] <jcsackett> is there an easy way to run ec2 tests with a different version of dependencies? say if i'm working on changes to a lazr lib? i can't find anything in the wiki.
[21:07] <lifeless> pcjc2: hasn't mirrored yet
[21:07] <lifeless> jcsackett: edit your versions.cfg
[21:08] <lifeless> and setup.py
[21:08] <lifeless> ec2 test is meant to propogate that
[21:11] <jcsackett> lifeless: i may be (read: probably am) wrong, but it looks like that requires existing version numbers. is there a way to use something that only exists as a branch i'm working on?
[21:11] <jcsackett> i see my earlier question wasn't clear. my apologies.
[21:11] <lifeless> jcsackett: once you've added it to the download cache, its fine
[21:12] <jcsackett> lifeless: ah! so i add the tarball or what have you to that, and ec2 pulls info from there? i didn't realize. that's cool.
[21:12] <lifeless> its documented on ze wiki I think
[21:12] <lifeless> you add the tarball, bzr add, bzr commit
[21:12] <pcjc2> OOPS-1836QS42  ?
[21:13] <lifeless> pcjc2: also won't have syncted yet :)
[21:13] <jcsackett> lifeless: dig. thanks!
[21:13] <pcjc2> what is the timeframe?
[21:13] <lifeless> pcjc2: generally 15 minutes IIRC
[21:13] <pcjc2> gah, I'm being a tool...
[21:13] <pcjc2> I filed the bug on staging, not qastaging
[21:31] <mwhudson> wgrant: are you awake yet?
[21:36] <lifeless> pcjc2: hmm, so
[21:36] <lifeless> oops 1836QS24
[21:36] <lifeless> how did you generate that oops ?
[21:36] <pcjc2> from the API, accessing a non-existant bug
[21:36] <lifeless> hmm
[21:36] <lifeless> shouldn't OOPS
[21:36] <pcjc2> Here is a real one which is annoying me: 1836O1543
[21:37] <lifeless> what was the API call you made ?
[21:37] <pcjc2> OOPS-1836O1543 (this was jut now, so need to wait a bit) It is a bug search timing out
[21:37] <lifeless> sure
[21:37] <lifeless> so, QS24
[21:37] <lifeless> what does the code look like that triggered it ?
[21:38] <jml> lifeless: hello. where are you?
[21:38] <lifeless> B
[21:38] <pcjc2> >>> from launchpadlib.launchpad import Launchpad
[21:38] <pcjc2> >>> from launchpadlib.credentials import Credentials
[21:38] <pcjc2> >>> credentials = Credentials.load_from_path ("commit_robot_qastaging.credentials")
[21:38] <pcjc2> >>> launchpad = Launchpad(credentials, service_root="https://api.qastaging.launchpad.net")
[21:38] <pcjc2> >>> bug=launchpad.bugs[123456789]
[21:38] <pcjc2> >>> print bug
[21:38] <lifeless> linaro room
[21:39] <pcjc2> In the response, there was: x-lazr-oopsid: OOPS-1836QS46
[21:39] <lifeless> yeah
[21:39] <jml> lifeless: do you want to grind more on persistence layer stuff?
[21:39] <lifeless> sure
[21:40] <pcjc2> The search oops I'm hitting is via the normal web interface - was looking to find all open bugs in the project with no tags
[21:40] <lifeless> jml: can yo ucome here first ?
[21:40] <lifeless> pcjc2: yeah, hang on
[21:40] <lifeless> pcjc2: need to wait for it to sync
[21:42] <jml> lifeless: sure.
[21:43] <jml> lifeless: omw
[21:43] <lifeless> pcjc2: O1543 is still pending rsync
[21:44] <jml> lifeless: which linaro room?
[21:44] <lifeless> ballroom B
[21:44] <jml> lifeless: I'll try again.
[21:45] <lifeless> back right
[21:45] <lifeless> right of main desk
[21:53] <jml> huwshimi: hello
[21:53] <huwshimi> jml: Morning
[21:54] <jml> huwshimi: how'd it go yesterday?
[21:54] <lifeless> pcjc2: ok
[21:54] <lifeless> pcjc2: slow sql
[21:54] <huwshimi> jml: Good thanks. Just getting Launchpad set up locally
[21:55] <lifeless> pcjc2: what did you search for ?
[21:55] <jml> huwshimi: all set up w/ wiki access?
[21:55] <huwshimi> jml: Yup
[21:57] <wgrant> mwhudson: Hi.
[21:58] <wgrant> lifeless: It's only a soft timeout so far.
[21:58] <lifeless> wgrant: ah; well it can be real anytime you like :>
[21:58] <mwhudson> wgrant: hi, i wanted to ask you about openid identifier/account merge crazyness
[21:58] <mwhudson> wgrant: but we found mbarnett instead
[21:59] <lifeless> pcjc2: https://bugs.launchpad.net/launchpad/+bug/701250
[21:59] <_mup_> Bug #701250: Product:+bugs timeout with search  <timeout> <Launchpad itself:Triaged> < https://launchpad.net/bugs/701250 >
[21:59] <wgrant> mwhudson: It should all be pretty much fixed soon, after the next SSO deployment.
[22:00] <mbarnett> woot
[22:00] <wgrant> But who knows when that will be.
[22:02] <lifeless> matsubara-afk: \o/ codebrowse oopses are visible
[22:39] <pcjc2> lifeless: 17 seconds is a long SQL query...
[22:39] <pcjc2> Bad DB index?
[22:43] <sinzui> pcjc2: Most long queries are because the there to too much data being collected, most of which will not be used
[22:43] <pcjc2> in terms of row count, or data join'd from other tables?
[22:44] <sinzui> data in other tables and columns. Bug queries are undermined by the ORM in a way
[22:50] <flacoste> hi huwshimi! welcome aboard!
[22:53] <lifeless> pcjc2: indeed
[22:53] <lifeless> pcjc2: we need to debug this a little against staging
[22:53] <pcjc2> we? as in me you and me?
[22:59] <flacoste> huwshimi: subscription to canonical-launchpad approved
[22:59] <jml> huwshimi: btw, give us a holler if there are issues with getting a dev env set up
[23:01] <huwshimi> jml: Thank you. It's taking a while to pull everything down, but it is working.
[23:02] <StevenK> *Another* Sydney-sider?
[23:02] <wgrant> Too many.
[23:02] <StevenK> Oh, so clearly I need to move to Melbourne?
[23:02] <wgrant> Yes.
[23:02] <wgrant> Or follow the others' lead, and move to another country!
[23:02] <mwhudson> i guess QLD is not looking such a good option currently
[23:03] <StevenK> Queensland has other problems.
[23:03] <StevenK> Such as being full of Queenslanders.
[23:03] <jml> StevenK: now now.
[23:10] <huwshimi> flacoste: Thanks you! Sorry only just noticed your message.
[23:16] <mkanat> What does it take to get ~/launchpad-pqm/loggerhead to be set up on qastaging as codebrowse, and then pushed to production?
[23:16] <mkanat> ~launchpad-pqm/ that is.
[23:17] <mkanat> Okay, I guess I need to update sourcedeps first.
[23:29] <mkanat> Do I propose merges against edge and then those go into stable...?
[23:30] <StevenK> mkanat: No, propose merges against lp:launchpad, which is the right place
[23:30] <mkanat> Okay.
[23:32] <lifeless> there is no edge
[23:32] <mkanat> lifeless: There's lp:launchpad/edge
[23:32] <jml> lifeless: hello
[23:33] <lifeless> let me just delete that
[23:33] <mkanat> lifeless: Okay.


[10:36] <mlankhorst> morning
[11:24] <mlankhorst> Laney: got sig, thanks!
[11:32] <TheMuso> mlankhorst: Don't rub it in. :p I still have one 8 hour flight left yet. :p
[11:49] <mlankhorst> yikes


[05:03] <davyboy04> can somebody please tell me how to change my video card driver and how to decide which one i neeD?
[05:06] <danage> davyboy04: go to #ubuntu (but try from bash displayconfig-gtk)
[05:07] <ethana2> I don't think he's identified
[05:08] <davyboy04> ok
[09:56] <KingOfDos> I've got a problem with zabbix-server-mysql. After a couple of upgrades of Ubuntu 6.10 to 8.04 (version after version) my zabbix-server does nothing anymore.
[09:56] <KingOfDos> While upgrading from 7.04 to 7.10 (i beleave) it wanted to convert the database format while upgrading. That faild.
[09:57] <KingOfDos> So is there a way to manually convert a zabbix-server database format from version 1.1 to 1.4
[12:25] <tarzeau> is there a user of requestsync in here?
[12:25] <tarzeau> is there a log file and the dates when the next automatic syncs (from debian unstable to ubuntu) will be?
[12:33] <RussellGee> tarzeau: i was wondering the same thing
[12:34] <RussellGee> there were updates 2 days ago but apart from that theres been nothing else
[12:34] <tarzeau> RussellGee: is that stuff not public maybe?
[12:35] <tarzeau> RussellGee: and is there a webgui for requestsync? can non-ubuntu users run it somehow? (i have friends who run ubuntu, but i don't have access on their machines from not local)
[12:35] <tarzeau> and they do want some software updates that is in debian sid, but not ubuntu
[12:36] <RussellGee> https://wiki.ubuntu.com/SyncRequestProcess
[12:36] <RussellGee> ?
[12:37] <tarzeau> RussellGee: you can't file bugs on launchpad without account
[12:38] <tarzeau> RussellGee: i got three accounts on there, but don't remember the password and my email changed and they can't send the reminders onto another mail address on the keyring :(
[12:38] <tarzeau> i don't want to create another 10 accounts on launchpad
[12:38] <tarzeau> i'd just like someone on irc that i can ping from time to time to sync package a , b, and c
[12:39] <RussellGee> sync requests normally dont happen untill after the debian import freeze
[12:39] <tarzeau> ah i see, and no automatic syncs either?
[12:40] <RussellGee> they should star soon on a regular basis
[12:40] <RussellGee> start*
[12:40] <RussellGee> you could go fetch the source your self from sid and build the packages
[12:41] <tarzeau> i know about that
[12:41] <tarzeau> so it's not known when soon is?
[12:43] <RussellGee> theres still a few things to get sorted with the toolchain
[12:43] <RussellGee> perl is in a right mess atm
[12:44] <RussellGee> things should start moving along in a few days
[12:45] <RussellGee> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-May/000424.html
[14:44] <Skiessi> does anyone know when x is going to work again?
[14:48] <Amaranth> Skiessi: just before alpha1
[14:48] <Amaranth> Skiessi: See you in June
[14:50] <Skiessi> \o/ irssi and lynx until then
[14:51] <Skiessi> and aaxine of course, I need a media player
[14:51] <Amaranth> or downgrade libxfont1
[14:51] <Skiessi> to what version?
[14:52] <Skiessi> I'll downgrade to hardy one
[14:58] <Skiessi> :| yeah it works now...
[15:12] <MonTree> ubuntu live cd comes with md5sum?
[16:39] <hwilde> is there any way I can make ubuntu call a phone number and play a pre-recorded message?
[16:39] <hydrogen> not particullarly on topic
[16:40] <hwilde> I don't even know what to search for -  it doesn't seem to exist
[16:45] <gnomefreak> hwilde: please ask in ubuntu-offtopic or #ubuntu as you were. there might not be an easy way or a known way at this time so getting an answer might not be easy
[16:45] <gnomefreak> hwilde: maybe try recording your voice and than worry about setting it up
[16:45] <hwilde> I have the recordings
[16:46] <hwilde> not sure how to initiate a voice phone call
[16:46] <hwilde> automatedly speaking
[16:47] <gnomefreak> hwilde: you need to write your own program or search for one on net . I highly doubt we have one and this is really the wrong channel to be asking in
[16:47] <gnomefreak> hwilde: please ask in ubuntu or ubuntu-offtopic
[17:48] <frenzy> hello
[17:49] <frenzy> i'm comming here with a heads up to a major problem with Ubuntu 8.04LTS
[17:49] <AtomicSpark> wrong channel :P
[17:50] <frenzy> well not really
[17:50] <frenzy> becasue this needs an update to fix
[17:50] <AtomicSpark> and what is this little problem of yours?
[17:50] <frenzy> basicly, with every program and i mean every program that creates documents you can save, the program crashes when you try to save
[17:51] <frenzy> and i think the problem is with the window mananger
[17:51] <frenzy> and no one in the support forums or the IRC can help
[17:51] <AtomicSpark> i don't appear to have this problem. did you do a fresh install?
[17:51] <frenzy> no, an update
[17:52] <frenzy> and the bug is registered, i'm not the only one having the problem
[17:53] <mnemo> frenzy: paste the URL to the bug report in launchpad
[17:53] <frenzy> ok
[17:54] <AtomicSpark> upgrades are never reliable. especially if you add stuff from the original install.
[17:54] <frenzy> https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/225355
[17:55] <frenzy>  yea i know, i had major problems with xubuntu after the last install, the ethernet card wouldn't work
[17:56] <mnemo> frenzy: that bug doesn't repro on my machine either (I tried both open office writer and "text editor")
[17:56] <frenzy> bleh
[17:56] <AtomicSpark> i tried gimp too
[17:57] <AtomicSpark> you didn't try to manually install open office at any point in the past did you?
[17:57] <frenzy> and you both did fresh installs?
[17:57] <frenzy> no, never
[17:57] <mnemo> frenzy: no, I install a beta version of gutsy and then just kept pressing "upgrade"
[17:57] <frenzy> but given that it effects all document programs, i think the issue is with window manangers
[17:58] <AtomicSpark> it would be an issue with saving so maybe nautilis or something.
[17:58] <mnemo> frenzy: on your machine, does "gedit" crash when you save a text file?
[17:58] <AtomicSpark> i upgraded from the beta. it was pretty crappy. only had a major issue with flash though.
[17:59] <frenzy> sorry i'm still ubuntuillerate, what is the gedit?
[17:59] <frenzy> aaa
[17:59] <frenzy> nvm
[17:59] <AtomicSpark> gedit is the default text editor
[18:00] <frenzy> sorry i'm used to just calling it text editor, yes it crashes
[18:00] <mnemo> ok hmm
[18:00] <AtomicSpark> hmm. what about nano? from a terminal?
[18:01] <frenzy> nano seems to load in the terminal,
[18:01] <frenzy> let me try to save
[18:01] <mnemo> frenzy: to find the cause of a crash you need to run the application inside GDB and retrive a stacktrace at the point the crash happens... but to do that you need to run an application which has debug symbols available
[18:01] <mnemo> frenzy: press CTRL-O to save stuff in nano
[18:01] <frenzy> ok
[18:02] <frenzy> well i would like to find the cause of the crash
[18:02] <BunnyRevolution> wouldn't
[18:02] <BunnyRevolution> "strace appname" work?
[18:03] <frenzy> alright so nano saved just fine
[18:03] <frenzy> in the terminal
[18:03] <AtomicSpark> might be a nautilus thing.
[18:04] <frenzy> i just reinstalled nautilus, should i restart and see if that helped?
[18:04] <AtomicSpark> scary. but sure.
[18:05] <mnemo> frenzy: there is no easy to install debug symbols for gedit as far as I know... but there is debug symbols for evince so maybe you can try that... just download any PDF file to your desktop, double click it to open it in "evince", then select "Save a copy" from the file menu and see if that crashes
[18:05] <frenzy> let me try that first
[18:06] <mnemo> frenzy: yeah try the restart first for sure
[18:06] <AtomicSpark> i thought inkscape was the pdf viewer now?
[18:06] <frenzy> no evince still is there
[18:06] <frenzy> and the program just crashed with the PDF but i'll be right back with a restart.
[18:07] <AtomicSpark> not for me lol but he did an upgrade
[18:07] <AtomicSpark> maybe document viewer is evince?
[18:08] <AtomicSpark> ah it is!
[18:10] <AtomicSpark> heh the show about human hobbits is on
[18:10] <frenzy> nope!
[18:11] <frenzy> still crashes
[18:11] <frenzy> so what were you saying about the PDF
[18:11] <mnemo> okay frenzy, run this command "sudo apt-get install evince-dbg"
[18:11] <frenzy> ok
[18:12] <mnemo> start evince without opening any PDF
[18:12] <mnemo> also start a terminal
[18:12] <mnemo> in the terminal type "gdb --pid=`pidof evince`"
[18:12] <frenzy> ok
[18:12] <mnemo> make sure you get backticks and not ' chars etc
[18:13] <mnemo> at this point evince should become unresponsive (and gray out), this is normal
[18:13] <frenzy> weird evince seems not to be in my applications menu
[18:13] <mnemo> and you should have a gdb prompt available where you can type stuff
[18:14] <mnemo> you can just launch evince from the terminal, type "evince &"
[18:14] <frenzy> ok
[18:15] <frenzy> ok i have the prompt
[18:15] <mnemo> type "c" in the gdb prompt to start evince again
[18:16] <frenzy> ok
[18:16] <mnemo> evince should not stop being gray and you should be able to use evince menus normally
[18:16] <frenzy> yes
[18:16] <mnemo> okay, repro the bug now
[18:16] <mnemo> i.e. use the "save copy" function in evince
[18:16] <mnemo> to make it crash
[18:17] <frenzy> it froze and greyed out
[18:17] <frenzy> i did open
[18:17] <mnemo> okay good
[18:17] <mnemo> switch back to gdb
[18:17] <frenzy> alright
[18:17] <mnemo> and look what it printed
[18:17] <frenzy> Program received signal SIGSEGV, Segmentation fault.
[18:17] <frenzy> [Switching to Thread 0xb6bad720 (LWP 6316)]
[18:17] <frenzy> 0xb7245bc7 in strchr () from /lib/tls/i686/cmov/libc.so.6
[18:18] <mnemo> perfect
[18:18] <mnemo> now type "backtrace full"
[18:18] <mnemo> and copy everything gdb prints into the launchpad bug :)
[18:18] <frenzy> haha ok!
[18:18] <mnemo> this information is very useful to developers
[18:19] <frenzy> alright
[18:19] <frenzy> should i just post it as a comment in the current bug?
[18:20] <mnemo> yeah, or attach it as a file is even better in case it's very long
[18:20] <frenzy> but i can't save files :-P
[18:20] <mnemo> use nano or something ;>
[18:20] <frenzy> unless i use nano
[18:20] <frenzy> yea
[18:20] <mnemo> you can also paste it into here: http://rafb.net/paste/
[18:20] <mnemo> so I can look at it
[18:21] <AtomicSpark> shift-control-v for pasting into nano
[18:21] <frenzy> should i only copy from backtrace
[18:21] <mnemo> copy the part that says SIGSEGV as well
[18:21] <mnemo> plus some lines before and after that
[18:23] <frenzy> http://rafb.net/p/B2BVWf76.html
[18:23] <frenzy> is that good?
[18:24] <mnemo> hmm
[18:24] <frenzy> hmm?
[18:25] <mnemo> two problems
[18:25] <frenzy> shoot
[18:25] <mnemo> first, you're missing symbols for some pretty important libraries... this is why it says "No symbol table info available.
[18:25] <mnemo> secondly, the backtrace is not complete... or at least I don't think it is
[18:26] <mnemo> hold on
[18:26] <frenzy> ok
[18:26] <frenzy> well it took me back to gdb
[18:27] <mnemo> yeah, maybe things will become more clear if we manage to get the symbols for glib and gtk into place
[18:27] <frenzy> well how do we do that?
[18:28] <mnemo> now i'm sort of guessing here but, try running "sudo apt-get install libgtk2.0-0-dbg"
[18:29] <mnemo> and then also run "sudo apt-get install libglib2.0-0-dbg"
[18:29] <frenzy> ok
[18:30] <mnemo> frenzy: and just to be sure, run this as well "sudo apt-get install libgtkextra-x11-2.0-dbg"
[18:30] <frenzy> ok, it's working
[18:30] <mnemo> and then grab another backtrace
[18:30] <frenzy> alright
[18:31] <frenzy> on the bug report, someone posted dependences, what's that for
[18:31] <frenzy> https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/225355
[18:32] <mnemo> the dependencies.txt file is attached automatically when you file bugs using the "help :: report a problem" functionality
[18:32] <frenzy> gottcha
[18:33] <mnemo> frenzy: did you manage to get another backtrace?
[18:33] <frenzy> still installing the last one
[18:33] <mnemo> mmkay, I see
[18:36] <frenzy> #15 0xb77f7e4f in ?? () from /usr/lib/libgtk-x11-2.0.so.0
[18:36] <frenzy> No symbol table info available.
[18:36] <frenzy> #16 0x00000000 in ?? ()
[18:36] <frenzy> No symbol table info available.
[18:36] <frenzy> same thing
[18:36] <mnemo> can you paste the whole thing again into ttp://rafb.net/paste
[18:37] <frenzy> ok
[18:37] <frenzy> http://rafb.net/p/h7Hn5M75.html
[18:39] <frenzy> is that good?
[18:39] <mnemo> okay, this is sort of where my knowledge ends... I don't know how to make the backtrace more readable unfortunatly
[18:39] <mnemo> this is still useful
[18:39] <mnemo> but it's not perfect
[18:40] <Amaranth> it is not useful at all
[18:40] <frenzy> ha
[18:40] <mnemo> :/
[18:40] <mnemo> Amaranth: so how can it be improved then?
[18:40] <Amaranth> install libgtk2.0-0-dbg and libglib2.0-0-dbg
[18:40] <Amaranth> then generate the crash report again
[18:41] <frenzy> i did
[18:41] <mnemo> yea I just asked him to do that
[18:41] <Amaranth> you crashed it _after_ you installed those?
[18:41] <frenzy> yes
[18:41] <Amaranth> then you're screwed
[18:41] <frenzy> let me restart terminal and start fresh
[18:41] <Amaranth> bad backtrace == bug not getting fixed
[18:42] <frenzy> i'm getting the same thing
[18:43] <frenzy> no symbol table info avaiable
[18:44] <frenzy> http://rafb.net/p/odsnZw54.html
[18:44] <frenzy> then should i just do a fresh install?
[18:45] <frenzy> i'm guessing the silence means i'm still screwed
[18:47] <mnemo> frenzy: i don't know how to help you at least... i wish there was better automatic crash reports in ubuntu (like windows has)... it's not reasonable to expect end-users to analyze bugs like this
[18:48] <frenzy> well at least i tried, i can do a fresh install without wiping the drive right?
[18:49] <mnemo> the installer can delete and format partitions, yea
[18:49] <frenzy> but i still should back up
[18:49] <mnemo> yes
[18:50] <frenzy> well thanks, i posted what i had to the bug report, it might do something
[18:50] <frenzy> but if not oh well
[18:50] <frenzy> i need food
[18:50] <frenzy> see you later
[18:51] <mnemo> :)
[18:51] <mnemo> see you
[21:04] <Viden> can anyone help me ... after a dist upgrade i have no background image and everything seems to be crawling along
[21:06] <Viden> i also have no right click menu on the desktop
[21:07] <Viden> anyone?  please
[21:09] <Nicke> Viden: This on Hardy/8.04? I suppose you will be better of in #ubuntu then
[21:10] <Viden> yeah ... 804, that channel is never very helpful, most of the good people hang out here.  I will wait my turn there i suppose
[21:11] <Nicke> yeah, or try the forums.. but I have never tested those myself.. : )
[21:11] <Viden> :-d
[21:36] <llin-ubuntu> is anyone else experiencing slow speeds on downloading 8.04 updates?
[21:43] <gavintlgold> so, ibex will have a new theme, correct?
[21:49] <hwilde> what replaced /etc/acpi/powerbtn.sh ?  in fact all of /etc/acpi   ?
[23:08] <gnomefreak> who was the X person that had issues with X
[23:09] <gnomefreak> didnt make much sense but you know who you are
[23:09] <gnomefreak> hes not here
[23:10] <gnomefreak> anyone watching DO NOT UPDATE YOU SYSTEM if your on intrepid or if your thinking about it
[23:14] <IdleOne> gnomefreak: no kidding. it wants to uninstall everything heh
[23:14] <gnomefreak> oh i havent been affected but one of the devels i work with did have it happen
[23:15] <gnomefreak> IdleOne: what package do you know?
[23:15] <IdleOne> lemme check
[23:17] <gnomefreak> IdleOne: thanks
[23:17] <IdleOne> http://pastebin.ca/1008740
[23:17] <IdleOne> there ya go
[23:17] <gnomefreak> thanks
[23:18] <IdleOne> np that is what i get don't know what other people are getting
[23:20] <gnomefreak> IdleOne: ill have it checked with fta
[23:20] <IdleOne> gnomefreak: is that helpful or do you need more info from me?
[23:20] <IdleOne> gnomefreak: ok cool
[23:21] <gnomefreak> IdleOne: for now its helpful
[23:21] <IdleOne> ok glad I can help
[23:22] <IdleOne> need anything more let me know
[23:22]  * IdleOne is planning a backup of /home so if I need to do a fresh install I'll be ok
[23:27] <gnomefreak> ok now ill look more into this X bug to see what caused it
[23:27] <gnomefreak> IdleOne: what version is your libffi4
[23:28] <gnomefreak> 4.2.3-2ubuntu7??
[23:30] <gnomefreak> IdleOne: extreamly helpful but not gonna fix it\
[23:31] <gnomefreak> its because of gcc-4.3 everything needs to be built on that version before you get working anything this takes time
[23:31] <gnomefreak> :)
[23:36] <IdleOne> gnomefreak: yeah I read it in the email
[23:36] <gnomefreak> IdleOne: dont ever do aptitude or dist-upgrade in devel
[23:36] <IdleOne> gnomefreak: I did it all through Hardy without issue
[23:36] <gnomefreak> if you simply do upgrade it doesnt do anything bad most of time http://pastebin.ca/1008753
[23:36] <gnomefreak> IdleOne: but you "shouldnt" is what the devels will tell you
[23:37] <gnomefreak> ad never before toolchain is done
[23:37] <gnomefreak> /ad/and
[23:37] <IdleOne> yeah yeah but they are always to careful lol
[23:37] <IdleOne> but! now that you have told me I wont
[23:37] <gnomefreak> IdleOne: we have to be since we need system or chroot to build packages for intrepid
[23:38] <gnomefreak> i havent set up my chroot yet
[23:38] <IdleOne> I had a system die on me at hardy 2 and got back online at hardy4 did religious dist-upgrade every morning with no probs
[23:39] <IdleOne> hardware failure nothing to do with ubuntu
[23:42] <gnomefreak> that late its less likely to bork your system but toolchain uploads will kill everything
[23:43] <IdleOne> yeah well this is the first time I have upgraded so early
[23:43] <IdleOne> I changed my sources.list the day after hardy release
[23:44] <IdleOne> so I am really hoping I dont break everything but hey I enjoy fresh installs :)
[23:45] <IdleOne> gnomefreak: maybe you can pass this on. nm-applet needs a disconnect from network option
[23:45] <gnomefreak> oh tell me your kidding
[23:46] <IdleOne> no not at all
[23:46] <gnomefreak> brb ill let him know
[23:46] <IdleOne> haha
[23:46] <IdleOne> ok
[23:47] <IdleOne> I mean if I want to switch from wifi to w2ing at once connections gored it connects to both so I have t
[23:47] <gnomefreak> i told him hes doing something for me atm but when he gets back hell ask me all kinds of shit, please file bug so i can point him there?
[23:47] <IdleOne> @ohmy dude
[23:47] <IdleOne> :P
[23:47] <IdleOne> sure thing
[23:47] <gnomefreak> all done smoke time now
[23:51]  * gnomefreak wonders if he set up intrepid yet
[23:56] <IdleOne> https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/227104
[23:59] <polit> why ubuntu don't release fluxbunut?