=== avoine [n=avoine@modemcable197.196-131-66.mc.videotron.ca] has joined #launchpad [02:13] why its not all the package that are in the product list of launchpad? [02:13] Because i want to report a bug on the new combiz package but the software is not register should i create it? === stub [n=stub@gb.ja.95.210.revip.asianet.co.th] has joined #launchpad [02:16] sorry, my mistake the software was there . === mpt [n=mpt@219-89-137-47.jetstart.xtra.co.nz] has joined #launchpad [02:59] Gooooooooooooooooooood afternoon Launchpadders! [03:16] Merge to devel/launchpad/sourcecode/buildbot/: [trivial] Fix or skip buildbot tests to be compatible with Twisted 2. (r158: Andrew Bennetts) [03:18] lifeless: we have a winner! :) [03:18] lifeless: Thanks for sorting that buildbot merge out. [03:25] stub: could you delete bugtracker ID 33 (name = auto-bugs.gnome.org)? [03:25] stub: it shouldn't have any bug watches on it now [03:26] jamesh: Done [03:26] thanks === jsgotangco [n=jsg@ubuntu/member/jsgotangco] has joined #launchpad === tambaqui [n=patricia@200-183-97-99-mns.cpe.vivax.com.br] has joined #launchpad === tambaqui [n=patricia@200-183-97-99-mns.cpe.vivax.com.br] has left #launchpad ["Fui] === mpt [n=mpt@219-89-137-47.jetstart.xtra.co.nz] has joined #launchpad [04:40] stub: I'd like to make the librarian's Database-Name check compulsory, but that means updating remoteAddFile to send it. [04:41] Yup [04:41] How do I get gpgme into my tree? [04:41] spiv: Is that problematic? [04:41] stub: Which probably means updating logger.LibrarianFormatter... [04:41] Basically, I'm not sure that I can automatically figure out the right value to send. [04:42] LibrarianFormatter just uses the api - only changes needed should be client.py [04:43] stub: I guess what I'm really asking is it safe to assume that all users of remoteAddFile (which I think is just the LibrarianFormatter) actually have database access? [04:43] So the issue is that we might not be able to retrieve the database name at the point of sending [04:43] So we need to retrieve the database name on connection and cache it [04:44] It probably isn't an urgent fix - there has been no case where such a misconfiguration has actually occured. [04:45] Yeah. If it was a near-trivial change, it would be worth doing, but this is requiring more thought and effort than I'd anticipated... [04:45] spiv: Actually - it is trivial [04:45] spiv: Just pull config.dbname [04:46] Ah, cool. [04:46] That will have the right value always? [04:46] Unless someone has manually opened a database connection, yes. [04:46] (with their own connection string and everything) === tambaqui [n=patricia@200-183-97-99-mns.cpe.vivax.com.br] has joined #launchpad [04:47] Yeah, in that case they're on their own :) [04:47] client.py likely wouldn't work anyway [04:47] It would take a lot of work to break it all that badly anyway ;) [04:50] Well, tests seem to pass with that, so that'll do :) [04:50] spiv? [04:51] mpt: You mean sourcecode/pygpgme? [04:52] I mean whatever's absence is causing the error "Couldn't import canonical.launchpad.utilities, No module named gpgme" [04:52] after updating rocketfuel I have no sourcecode/gpgme directory [04:52] Hmm, I just rsynced rocketfuel-built as usual and I'm not getting that problem. [04:53] rsync -aP --delete chinstrap:/home/warthogs/archives/rocketfuel-built/ ~/hacking/lp/rocketfuel [04:53] that look correct? [04:54] mpt: lib/gpgme should be a symlink to ../sourcecode/pygpgme/gpgme [04:54] Looks ok to me. [04:54] lrwxrwxrwx 1 mpt mpt 27 2006-02-20 16:24 gpgme -> ../sourcecode/pygpgme/gpgme [04:55] mpt: copy sourcecode/pygpgme from rocketfuel-built to the same location in your tree [04:55] Does sourcecode/pygpgme exist? [04:55] no [04:55] pyme does [04:55] but pygpgme does not [04:56] sourcecode/pygpgme should be in your rsynced copy of rocketfuel-built, copy it into the tree you're working on. [04:56] ok [04:57] You might need to "make build" again. [04:57] hmmm, now that directory's there and all the other's are symlinks [04:57] aha, I think I know what to do from here [04:57] others, rather [04:58] Yeah, you can probably symlink it to your rocketfuel-built copy, if you're doing that with the others. Just so long as it's there in your tree, one way or another :) [04:59] ok, it's working [04:59] thanks spiv and jamesh === mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #launchpad [06:38] good morning [06:38] lifeless: ping [06:42] pong [06:44] Merge to devel/launchpad/: [trivial] Make foaf-update-karma-cache friendlier and less likely to trigger deadlocks (r3162) [06:44] dreadlocks? [06:48] SteveA: ping [06:48] nm [07:08] I don't think rastas do karma [07:32] spiv: hello === mpt_ [n=mpt@219-89-158-15.jetstart.xtra.co.nz] has joined #launchpad === Protocol1 [i=Protocol@ACC0AC2B.ipt.aol.com] has joined #launchpad [07:38] SteveA: Hi. [07:39] jamesh: Do you mind if I shift bjorn/launchpad/distro-launchpad-usage into my review queue? It's merged into another branch in my queue. [07:39] spiv: go ahead. [07:39] jamesh: Thanks [07:40] Merge to devel/launchpad/: [r=BjornT] Fixes the error pages to suggest support requests rather than bug reports (bug 3578). Shortens text fields across Launchpad so they're not overlapping the right column (bug 28740). Finishes the GPG -> OpenPGP fixes (bug 30212). (r3163: Matthew Paul Thomas) [07:43] spiv: voip call ? === mpt [n=mpt@219-89-158-15.jetstart.xtra.co.nz] has joined #launchpad [07:46] SteveA: I haven't tried setting up voip on this laptop yet, because of the likely echo (the bug where I can't turn built-in speakers off) [07:46] spiv: a USB headset avoids that sort of problem :) [07:47] jamesh: by being a seperate sound device? I'd rather just have a fixed kernel ;) [07:47] yeah [07:48] I'll try out dapper soon, apparently a new enough kernel should have the fix for this. [07:49] spiv: nail scissors... [07:49] you should be able to disable the speakers with those [07:50] SteveA: That's an option I suppose... [07:51] or a large pillow to cover the speakers [07:51] anyway, let's have a phone call === Protocol1 [i=Protocol@ACC0AC2B.ipt.aol.com] has left #launchpad ["Leaving"] [07:51] Let's. [07:51] My landline is preferred. === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad [08:00] ddaa: hello === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad [08:34] coffee pot, check [08:34] cigarette, check [08:34] SteveA: hello [08:35] nice to see i'm next in line to your addictions [08:35] we've a meeting in 1h25, is that right? [08:35] Uh, well, I like you, but I did not actually mean it that way ;) [08:36] SteveA: yes, though I think that one is going to have a pretty simple agenda. [08:36] One item: "do everyone like the plan? yes? shall we start now?" [08:36] i guess i should get up to date with the plan [08:37] That would be nice. [08:38] everything should be in your inbox [08:41] that's the problem. *Everything* is in my inbox! [08:43] for the record, the hyperlinked version is there https://chinstrap.warthogs.hbd.com/~david/importd-bzr-plan/importd-bzr-plan.html#implementation-plan === Lorenzod [n=lorenzod@63.218.103.162] has joined #launchpad [08:43] The mail version contains the source of the "implementation plan" section for easy commenting. [08:44] Merge to devel/launchpad/: [trivial] Staging config updates (r3164: Stuart Bishop) [08:44] ddaa: okay. i'll read through the https version === mpt_ [n=mpt@219-89-158-216.jetstart.xtra.co.nz] has joined #launchpad === carlos [n=carlos@84.76.255.40] has joined #launchpad [08:56] morning [09:03] hi carlos [09:03] spiv has been adding an API to do more diagnostics with the librarian [09:04] the patch is in the review queue, but it will be in production soon [09:04] so, you should look at how to use this for rosetta. [09:04] carlos: The basic change is that you can do client.addFile(..., debugID='foo') [09:05] ok [09:05] carlos: And that will cause the server to log a bunch of debugging stuff for that request, and mark it with 'foo' [09:05] I will use the 'poexport' tag as that's what triggers the error [09:05] spiv: thanks! [09:05] so the 'foo' should in fact be something unique to that particular request [09:05] carlos: You can even use a different tag for each request, if you like. [09:05] so 'poexport-xxxx' [09:06] It will already have datestamps, but more information won't hurt. [09:06] carlos: can more than one poexport run at once? [09:06] SteveA: no, the export is done by a script so it's a serial process [09:07] carlos: how about if you get int(time.time()) at the script's start up [09:07] and put that into a global called script_invokation_id [09:07] and use that as part of the ID [09:08] then we'll be sure about this [09:08] The infomration logged will include a timestamp, and the name and size of the file uploaded. [09:08] spiv: hmm, what about the fetch function? [09:08] spiv: did you update it? [09:08] to have the debugID argument [09:09] No; that already logs some basic information, and by the time the fetch occurs, it seems the damage has been done. [09:10] spiv: my point is to group the actions from a single script invokation [09:11] ok [09:11] SteveA: the addFile can be executed more than once per time [09:11] I was thinking on the fetch method [09:11] SteveA: It's pretty clear already; aside from occuring shortly after the upload, the download includes the same IDs. [09:12] ok [09:12] spiv: yay! your buildbot patch is merged! [09:12] ddaa: Thank lifeless, all I had to do was hit the "submit" button repeatedly ;) [09:12] spiv: as promised, I tentatively assigned a couple of items to you in the importd-bzr plan. You might want to check about that: https://chinstrap.warthogs.hbd.com/~david/importd-bzr-plan/importd-bzr-plan.html#implementation-plan [09:13] ddaa: Heh, ok. === spiv looks [09:13] spiv: that's still a proposal, SteveA and lifeless have not approved it yet [09:13] spiv: do you think that with that tag we will be able to trace the problem? (we only see it when we try to fetch the files) [09:13] ddaa: I'm happy to be responsible for those tasks. [09:14] carlos: I think so. The important part is to log more about those uploads, I think. [09:14] spiv: that's cool, will keep you posted. Unless mgmt has objection with the plan, you should be able to start the first one RSN. [09:15] ddaa: No rush, I have plenty to keep me busy ;) [09:15] (actually, It would be nice to start it soon because other tasks depend on the celebrity being available) [09:15] ok [09:15] spiv: will keep you posted :) [09:16] spiv, ddaa: these tasks are fine for spiv to do. [09:16] ddaa: Actually, one question [09:16] ddaa: does anything need to be done before spiv could start on these? [09:16] SteveA: I do not think anything blocks the first one [09:16] ddaa: I don't know much about baz2bzr [09:16] spiv: don't be so tight, you have unlimited questions credit [09:17] spiv: can you put the first one on your todo list, above the authserver cacheing work? (that's "Add ``importd`` Celebrity to Launchpad and modify ``supermirror-pull-list.txt``") [09:17] spiv: well, the baz2bzr thing this doc is talking about does not exist yet, it's the big piece that we will have to implement. [09:17] SteveA: Ok. [09:17] thanks [09:18] ddaa: for the second one, i think it will need a bit more explanation [09:19] spiv: most of the document is about deciding how to implement it and why. Basicilly what the second task means is "modify all the bits that register new branches to set Branch.origin appropriately". [09:19] ddaa: Ah. I understand what's required for Branch.origin with AuthServer and Launchpad. [09:19] Right. [09:19] It should be usually trivial, it's just nasty to deploy. [09:20] And "baz2bzr" in this context means "whatever converts our exist baz imports to bzr"? [09:20] specifically it means "the script we will run in buildbot to convert, register and internall publish bzr branches for rcs imports" === AlinuxOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad [09:20] where convert means "convert from baz" [09:21] Right. [09:21] Well, I won't worry about that bit until that script exists :) [09:21] spiv: exactly :) === AlinuxSOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad [09:21] it's just a cleanup anyway, it's not critical to delivering === AlinuxOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad === AlinuxOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad === AlinuxSOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad [09:32] ddaa: the importd celebrity [09:32] what kind of object do you imagine this will be? [09:33] SteveA: TBH I was a bit handwaving here... [09:33] it needs to be an owner of some stuff [09:33] so it needs to be from the Person table [09:33] so it can be a Person or a Team [09:34] I guess it could be a plain "dummy" person, or a team with buttsource as its admin. [09:35] we really should change the name "buttsource" sometime [09:35] seeing is there is no "buttress" any more [09:35] Thinking of it, the main purpose of having something separate from buttsource is to avoid advertising the "buttsource" name in public URL. [09:35] ok === AlinuxOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad [09:35] let's change it to rename "buttsource" to importd [09:35] because it makes people giggle? [09:35] then spiv need not do so much work? [09:36] some people claim that it is simply not possible to say the word "butt" too often [09:37] I'm happy with renaming buttsource to importd and using that as the owner of import branches. I'd like to hear lifeless about it. [09:37] He might be aware of some nasty corner case were that would be problematic. [09:37] to rename the 'buttsource' team, we'd need to have a change to the celebrities, and a database patch [09:37] okay, so item for the meeting in 20 mins [09:37] ddaa, SteveA: Let me know what you decide, so I know what to implement :) [09:38] anyway, the buttsource emblem sucks, dunno how I'm going to draw importd though :) [09:39] A big vacuum cleaner. [09:39] Because it sucks ;) [09:39] spiv: that's a great idea! [09:40] it's all about vacuum cleaners, Hoover, Roomba... [09:40] CVS, SVN... [09:40] Thinking of which, when do I get a Twisted import? ;) [09:40] spiv: though it's hard to make something look big in 16x16 [09:41] spiv: there will be a bug filed on you for it [09:41] spiv: interesting question, after we are publishing bzr branches, there should probably be a balance between fixing bugs and cleaning up the code... === mpt__ [n=mpt@219-89-136-194.jetstart.xtra.co.nz] has joined #launchpad [09:42] there a very large amount of work to do on both fronts, and I do not think it would be wise to just serialise them. [09:43] ddaa: Ideally you fix bugs by cleaning up the code ;) [09:43] (mostly because each task is basically a "can take forever" sort of task) === ddaa hands a cup of XP kool-aid to spiv [09:43] spiv: either do functional changes, or refactoring, not both at the same time [09:45] ddaa: I was imagining a magical world where all bugs are simply the result of ugly code. The sort of wishful thinking that comes from being a reviewer, maybe ;) [09:45] spiv: well, maybe but you know, fixing deployed SVN and CVS out there is not really an option [09:46] so we have to add ugliness in our code to match this external ugliness [09:46] But as far as cleaning vs. bug fixing, I guess it's just a matter of balancing priorities. === AlinuxOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad [09:47] spiv: yes, and that's a tricky problem, because most problems there are firmly in the "urgent and important" corner... === papa_lic [n=cissa_li@88-196-34-187-dsl.noe.estpak.ee] has joined #launchpad [09:48] I guess I should sit down again for a week and think about it after we have done phase 1 transition... === mpt__ is now known as mpt [09:49] "Urgent and important corner"? Someone's been Covey-ing :-) === mpt wonders what the point of a distribution members team is [09:51] what do you mean "what the point is" [09:51] Why does it exist? [09:51] What can members of that team do that other people can't? [09:51] you are talking about a specific team? [09:51] or the concept in general? [09:51] The concept in general [09:51] i can't say about that [09:51] (hence "a", not "the") [09:52] ubuntu members can [09:52] - get an ubuntu.com email address [09:52] - have signed the CoC [09:52] - can get business cards [09:52] - have been voted in as members by the CC [09:52] - are identifiable in launchpad by having the ubuntu members team emblem === ddaa suggest that the CC emblem should be a small cone of white powder === AlinuxOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad [09:53] Pillars of Launchpad and pillars of salt? [09:54] enough of this pillar-talk [09:54] SteveA, I was trying to come up with a sensible blurb for the +selectmemberteam page [09:54] At the moment it says "Select the Launchpad team that defines the members of " [09:54] it doesn't say *why* [09:55] different distros will have their own concept of "membership" [09:56] hummm [09:56] the other thing that ubuntu members get to do is to vote [09:56] so maybe that's the defining thing for ubuntu members in launchpad [09:57] All those things could be done if "distribution members team" wasn't a special kind of team in Launchpad [09:57] how do you mean "special kind of team" ? [09:58] a team that fills a special slot in a distro entity [09:58] as a side note, people don't create distros all that often in launchpad. so there are probably things you could work on that have a greater benefit. [09:58] distribution.members [09:59] launchpad has a model of what makes up a distribution [09:59] Yeah, I know, I was just passing through that template [09:59] this is modeled along the lines that ubuntu uses [09:59] ubuntu has "ubuntu community members" [09:59] there are reasons to want to be able to, in code, get to the "community members" team of a distro [10:00] so that is why it is a special kind of team [10:00] although, i wouldn't say "special kind of team" [10:00] because that implies it works differently to other teams [10:00] it is a team that is in a special relationship to a distro [10:00] I was wondering what those reasons were === jsgotangco [n=jsg@125.212.123.165] has joined #launchpad [10:01] I'll just XXX it [10:02] for example, be able to display on a page "This distro's members are _The Ubuntu Members Team_." [10:02] to say "in launchpad, Ubuntu has 6000000 members. Impi has 50000 members" [10:02] or whatever numbers [10:03] That would be useful if it meant anything *else* -- but if it can mean "contributors" for one distro and "users" for another, not so much. === mpt discovers http://launchpad.net/distros/ubuntu/+members [10:05] cf. https://launchpad.net/people/ubuntumembers [10:09] stub: can you point staging's email to the imap box? [10:09] morning [10:17] daf: morning === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === thisfred [n=thisfred@a80-127-80-154.adsl.xs4all.nl] has joined #launchpad === Keybuk [n=scott@213-78-32-60.ppp.onetel.net.uk] has joined #launchpad === irvin [n=irvin@ubuntu/member/irvin] has joined #launchpad [10:37] daf: ddaa will shortly be filing an oops bug on an oops produced by a page related to bzr imports [10:37] would you be able to look at it? [10:37] yes [10:38] though Launchpad is not responding for me right now [10:39] works for me [10:39] ddaa will assign the bug to you, when it is filed [10:40] SteveA: Yup. config changes should have landed now. [10:40] stub: cool, thanks [10:41] it's odd; the HTTP service redirects me to the HTTPS one, but then the HTTPS one doesn't give me a response [10:41] maybe you have a certificate-related window open somewhere? [10:42] I don't think so, no [10:42] I can access chinstrap https fine [10:42] I'll try restarting Epiphany [10:45] that didn't work === jsgotangco [n=jsg@ubuntu/member/jsgotangco] has joined #launchpad [10:46] using openssl -connect launchpad.net:https and issuing a GET request by hand works [10:46] so it's Epiphany [10:48] hmm, same happens with Firefox [10:49] so it's Necko [10:49] is that like Gecko? [10:49] It's the networking library [10:49] Gecko's the layout engine [10:49] I see === pingu64 [n=jsg@125.212.123.165] has joined #launchpad === ajmitch_ [n=ajmitch@203.89.166.100] has joined #launchpad === ippfx [n=irvin@203.213.196.252] has joined #launchpad [11:04] SteveA: Should be running now [11:24] Kinnison: ping [11:26] stub: pong [11:26] stub: what can I do for you sir? [11:27] Kinnison: Are you still handling soyuz rollouts or has that been handed off to someone else (me?). There will be a rollout tomorrow. [11:28] stub: I can assist, or cprov can [11:28] stub: or, if you have permission, you can do it and I'll be here in case you get stuck [11:29] ok. [11:29] stub: can you log into drescher? [11:29] hello nerds ;) [11:29] question [11:29] does anyone know about problems using live-cd? [11:30] I wanted to use live cd in estonian but got stuck in the login screen [11:30] papa_lic: most likely, guys in #ubuntu would know [11:30] id wont log in under any circumstances [11:30] Kinnison: Yes. I think I have access. It is more should code be updated, what branch needs to be rolled out, and all that stuff. I'm happy to leave the details to you and/or cprov [11:30] ok [11:30] papa_lic: this channel is about the launchpad.net website [11:30] stub: I'd say you need to coordinate with cprov since he know the codeline more than I [11:31] ok. [11:31] stub: I've been away from it for a week now === beyond [n=beyond@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === fabbione [i=fabbione@gordian.fabbione.net] has joined #launchpad [11:42] stub: could you please run pending/reduce-support-tracker-statuses.sql on staging? [11:42] Merge to devel/launchpad/: [r=spiv] add 'launchpad usage' flags to distributions, in the same way it's done for products. (r3165: Bjorn Tillenius) === fabbione [i=fabbione@gordian.fabbione.net] has joined #launchpad [12:05] hi carlos [12:05] SteveA: hi === cprov [n=cprov@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [12:13] good morning [12:13] hi cprov [12:14] SteveA: hi, how was the weekend ? [12:14] it was good. i got my guitar out for the first time in months. [12:16] SteveA: hey, good Mr rock'n roll ) [12:16] mr scottish-folk-played-poorly in this case, but thanks :-) === SteveA pings BjornT === Kamion [n=cjwatson@83-216-156-196.colinw664.adsl.metronet.co.uk] has joined #launchpad [12:18] SteveA: pong [12:18] thanks [12:23] cprov: hi [12:23] cprov: how was the testing? [12:24] carlos: hi, bad, lot of issues raised, from you part, still missing proper changesfiles (md5 collisions from the last) [12:24] carlos: haven't time to fix it myself, yet [12:24] cprov: ok, I will provide you with fixed packages [12:25] carlos: thanks dude [12:27] SteveA: spiv: bug 32105, bug 32106 [12:27] malone bug 32105 in launchpad "Rename importd" [Normal,Confirmed] http://launchpad.net/bugs/32105 [12:27] malone bug 32106 in launchpad "Extend supermirror-pull-list.txt for vcs-imports" [Normal,Confirmed] http://launchpad.net/bugs/32106 [12:34] is there a guide somewhere as to what the different 'status' values mean in malone? === pkunk_ [n=pkunk@a84-231-5-36.elisa-laajakaista.fi] has joined #launchpad [12:40] particular 'fix released' and 'fix committed', and how either of those relates to users being able to check that the bug really is fixed, so the fix doesn't get lost. === avoine [n=avoine@modemcable197.196-131-66.mc.videotron.ca] has left #launchpad ["Ex-Chat"] [12:41] dooglus: the difference is between released versions, and fixes in the version control system [12:42] dooglus: whilst some users might be able to checkout the most recent version from cvs (or whatever), most will not [12:42] dooglus: but the actual work has been done at that point, other than waiting for a release to happen === AlinuxOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad [12:48] LarstiQ: sometimes I report a bug, it gets marked as "fix released" and then the bug hangs around for another few months with no visible change, other than that the bug no longer appears in malone when I search for it. [12:49] LarstiQ: it's as if I had never reported the bug - it's not shown in search results, and isn't fixed, although it's marked as such. [12:49] dooglus: do you have an example of such a bug? [12:49] LarstiQ: there seems to be no way of distinguishing between "fix released" and "fix available on archive.ubuntu.com and available for installation" === Panda^ [n=giampaol@217.201.205.211] has joined #launchpad [12:50] LarstiQ: I'm trying to find one. Just a moment. [12:50] dooglus: now you're entering into areas where my knowledge as a launchpad user falls short [12:51] Merge to devel/launchpad/: [r=salgado] fix bug 6667, update more than one bug watch in a single request to a remote bugzilla instance. (r3166: Bjorn Tillenius) [12:52] LarstiQ: https://launchpad.net/distros/ubuntu/+source/update-notifier/+bug/28672 [12:52] malone bug 28672 in update-notifier "text in pop-up bubble has odd capital 'U'" [Normal,Fix committed] [12:53] LarstiQ: that's "fix committed", not "fix released", but the patch hasn't made its way to the archives and it's had over a month to do so. [12:55] dooglus: this looks to me as exactly what fix committed is for. I don't know why there hasn't bee a new upload yet, perhaps Michael has other changes he wants to roll in [12:55] dooglus: you're running dapper? [01:00] LarstiQ: yes. [01:00] LarstiQ: Michael has made many uploads since marking that one "fix committed" [01:00] LarstiQ: many uploads of update-notifier, that is [01:01] LarstiQ: ten releases: 0.41.1, 0.41.2, 0.41.3, 0.41.4, 0.41.5, 0.41.6, 0.41.6, 0.41.6, 0.41.7, and 0.41.7.cln, were all uploaded *after* that bug was 'fix-committed'. [01:02] LarstiQ: so I don't know whether the patch has got lost, or whether it's being held back for a different reason [01:02] LarstiQ: now, this is just a typo bug, so I don't really care, but the same applies to any other bug. shouldn't there be a 'status' value for "patch available in the archives", so that I can check that the bug really is fixed? [01:02] dooglus: hmm, I don't know enough about update-notifier, I would need to look at the repository to see what is going on [01:03] dooglus: afaiui, fix released would work for that [01:03] dooglus: update-notifier seems to me a native package, so you have no problem with upstream interaction? === seb128 [n=seb128@ubuntu/member/seb128] has joined #launchpad [01:04] hi [01:04] LarstiQ: that's right === salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [01:04] LarstiQ: "fix released" isn't the same. https://launchpad.net/distros/ubuntu/+source/vnc/+bug/31296 is "fix released" [01:04] malone bug 31296 in vnc vncserver "vncserver isn't installable" [Normal,Fix released] [01:05] LarstiQ: however, "The following packages have unmet dependencies. vncserver: Depends: xserver-common but it is not installable" [01:06] hi seb [01:06] daf: interested by some oops today? [01:06] dooglus: Fabio said he has uploaded the packages though [01:06] I'm trying to triage some of my bugs, but launchpad is still far to behave correctly [01:06] dooglus: there is a delay between upload and being available on package mirrors, perhaps that is biting you? [01:06] LarstiQ: that's right. so maybe the status should be "fix uploaded" or something? [01:07] dooglus: ah hmm, to me, upload == release in these cases. But I'm not an lp dev, so you could try asking for that (wiki, malone? not sure) [01:07] dooglus: I do know there has been discussion on these 'fix something', so there must be documentation somewhere [01:08] BjornT: Done [01:08] dooglus: for your update-notifier, the communication with mvo seems the bottleneck to me === ippfx [n=irvin@203.213.196.252] has joined #launchpad [01:09] LarstiQ: is malone the proper place to attempt communication about bugs? Or should I hunt him down on IRC or email? === pingu64 [n=jsg@125.212.126.231] has joined #launchpad [01:10] dooglus: you have pinged the bug twice, in my eyes, communication there is proper, but irc/email looks more effective for this bug [01:10] dooglus: I'll help hunt if needed ;) === doko [n=doko@dslb-084-059-103-022.pools.arcor-ip.net] has joined #launchpad [01:13] LarstiQ: the hunt isn't a very difficult one ( https://launchpad.net/people/mvo ) [01:14] ah no, that should be easy [01:15] daf: bug 32117 [01:15] malone bug 32117 in launchpad "ProductSeries.branch OOPS" [Normal,Confirmed] http://launchpad.net/bugs/32117 === AlinuxOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #launchpad [01:43] Is it worth reporting source package timeout errors? If there's already fixes in the queue, I'd hate to just be adding noise to your database. (It's looking up source packages in Ubuntu) [01:44] there are bugs already, yes [01:44] jbailey: you can search for 'oops' milestone bugs [01:44] if you want to be subscribed to them or whatever === irvin [n=irvin@ubuntu/member/irvin] has joined #launchpad [01:45] SteveA: I'm not fussed about subscribing - I just don't want to create unnecessary work if there's already a bunch of optimisation stuff scheduled for tomorrow's rollout. [01:45] I've gotten good at hitting the reload button until the page comes up [01:49] How do I search for "9600" as text within a bug, rather than looking for a bug number? [01:50] kiko: hi [01:50] hey carlos, what's up? [01:50] I'm filing a bug against X and am search for the card model number to check for dupes [01:50] kiko: I found the problem, I was too tired O:-) [01:50] aha [01:50] that's better [01:50] kiko: the error was a broken check [01:50] kiko: the tests are passing now [01:51] kiko: do you have time to take another look and approve it? [01:51] carlos, can you show the code to SteveA? [01:51] I'd rather he had a look [01:51] sure [01:51] let me prepare a new diff === AlinuxOS [n=Ubuntu@d83-176-120-2.cust.tele2.it] has joined #launchpad [01:57] SteveA: hi [01:57] kiko: who should I ping about launchpad oopsing all the time? [01:58] seb128, me :) [01:58] what is bothering you today? [01:58] OOPS-51C130 OOPS-51C155 OOPS-51A147 OOPS-51D142 OOPS-51A157 OOPS-51D162 OOPS-51C188 OOPS-51A187 OOPS-51B195 OOPS-51B194 OOPS-51A194 OOPS-51D199 OOPS-51A218 OOPS-51A223 OOPS-51C235 OOPS-51B236 OOPS-51B237 OOPS-51C240 OOPS-51B247 OOPS-51A236 OOPS-51D238 [01:58] https://chinstrap.ubuntu.com/~jamesh/oops.cgi/51C130 [01:58] https://chinstrap.ubuntu.com/~jamesh/oops.cgi/51C155 [01:58] https://chinstrap.ubuntu.com/~jamesh/oops.cgi/51A147 [01:58] https://chinstrap.ubuntu.com/~jamesh/oops.cgi/51D142 [01:58] https://chinstrap.ubuntu.com/~jamesh/oops.cgi/51A157 [01:58] https://chinstrap.ubuntu.com/~jamesh/oops.cgi/51D162 [01:58] https://chinstrap.ubuntu.com/~jamesh/oops.cgi/51C188 [01:58]