/srv/irclogs.ubuntu.com/2006/07/07/#launchpad.txt

=== flacoste [n=francis@209.217.74.66] has left #launchpad ["Bye"]
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad
=== LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #launchpad
=== rpedro [n=rpedro@87-196-5-241.net.novis.pt] has joined #launchpad
=== mpt [n=mpt@203-173-177-223.bliink.ihug.co.nz] has joined #launchpad
=== stub [n=stub@ppp-58.8.3.131.revip2.asianet.co.th] has joined #launchpad
jamesh34.5% of launchpad.net hits are from windows?04:44
spivstub: Hello.  Can you try running http://rafb.net/paste/results/IPGxHe33.html on balleny for me?  I'm try to reproduce the bzr test failures.04:46
spivI can't reproduce it locally (even though that script does 25 commits/sec on my laptop), but perhaps there's something different about balleny (64-bit?  different fs?) that's affecting it.04:47
mptGooooooooooooooooooooooood afternoon Launchpadders!05:00
ruffneckmornin05:06
ruffneckI'd need to launch a new pack of CD's05:06
ruffneckthey even sent the CD's but the one I tried had an error, or the computer was broken or something05:07
ruffneckit was my sisters computer.. she was complaining about spyware with win dose05:07
ruffneckI could try to use the live CD05:07
ruffneckshould I Try now... but does it have pr0n-get ?05:07
jameshruffneck: if you're having trouble installing Ubuntu, you'll probably get more help on #ubuntu.05:20
ruffneckoukei05:21
ruffneckwell.. I'll be fine with it05:21
ruffneckI just gotta have a working CD05:21
ruffneckit was broken or something it complained.. even offered me a chanse to check CD integrity or something05:21
jameshruffneck: btw, with Dapper the live CD _is_ the install CD05:21
jameshthere is a non-live CD ISO that can be used for install, but last I checked it was slightly oversized05:23
ruffneckdapper?05:35
ruffneckthere were 2 CD:'s in the cardboard05:36
ruffneckthe other is the other and..05:36
ruffneckI tried the Live05:36
jameshruffneck: that's probably breezy (Ubuntu 5.10)05:36
ruffneckyeah, old05:36
jameshruffneck: the current release is dapper (Ubuntu 6.06)05:36
ruffneckhehe, they just sent me it after few cliking :D05:36
ruffneckthis is humane :)05:36
ruffneckhumane interface05:37
ruffneckJef Raskin wrote.. I guess I should read05:37
jameshif you are doing a new install, I'd recommend going with Dapper05:37
stubspiv: works fine on balleny05:58
=== sivang [i=sivan@muse.19inch.net] has joined #launchpad
spivstub: damn.  I wonder how to reproduce it then.06:30
=== mpt [n=mpt@203-173-177-223.bliink.ihug.co.nz] has joined #launchpad
=== raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad
=== BjornT [n=bjorn@213.226.190.253] has joined #launchpad
mptstub, staging is down08:06
stubmpt: It is being rebuilt, as last nights auto rebuild failed.08:06
mptok, thanks08:07
stubmpt: Should be up in about 40 mins if it keeps to the normal timings.08:08
stub(and assuming there isn't more breakage to fix)08:08
=== mpt wonders why PQM thinks his latest Launchpad PQM request is "Request for non-PQM managed branch"
jameshmpt: too many or two few slashes on the end of a branch name08:26
jameshI forget which08:26
jameshthat's just a guess though08:26
=== raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad
=== frodon_ido [n=patrick@ip-213-49-210-27.dsl.scarlet.be] has joined #launchpad
=== rpedro [n=rpedro@87-196-79-58.net.novis.pt] has joined #launchpad
=== malcc [n=malcolm@host86-135-139-100.range86-135.btcentralplus.com] has joined #launchpad
lifelessmpt: branh url is wrong09:35
lifeless(yay Hong Kong, free wifi)09:35
jsgotangconice09:37
mptwell the URL works with bzr push...09:39
=== mpt adjusts it
lifelessnoit *cannot* work with bzr push - you dont have access to push to the rocketfuel branches.09:53
mptlifeless, the branch is sitting on chinstrap and the pending-reviews script picked it up fine, so the URL *must* have worked with bzr push09:56
lifelessmpt: not *your* branch url. the branch you told PQM to merge into.09:56
lifelesssorry if I'm not being clear, I just got off an 11hour plane flight09:57
mptoh, ok09:57
mptI never tell PQM to push into any particular branch, I use a script for that09:57
=== mpt looks to see what it's doing
jameshmpt: what are you using to make your pqm submissions?09:58
mptjamesh, a script called "publish", I can't remember where it's from (somewhere on the wiki, I suspect)09:59
mptit gets the URL from .bzr/branch/parent09:59
mptwhich in this case is sftp://chinstrap.canonical.com/home/warthogs/archives/rocketfuel/launchpad/devel10:00
jameshmpt: try making that chinstrap.ubuntu.com10:00
jameshlike we always use10:00
jameshmpt: pqm works on string equality rather than path equality for the merge target10:01
mptok, that was a problem in my new-branch script10:12
mptthanks jamesh10:12
jameshmpt: when I ran into this problem last, it was because I had an extra slash on the end of the target branch name, hence my original comment10:13
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad
sivangmorning10:37
=== doko [n=doko@dslb-088-073-110-126.pools.arcor-ip.net] has joined #launchpad
=== stub [n=stub@ppp-58.8.3.131.revip2.asianet.co.th] has joined #launchpad
elmostub: can you add me back as an lpadmin please?11:08
elmostub: kiko removed me, but my removal was conditional on certain functionality (e.g. buildd shutdown/revival) working without lpadmin, and it doesn't11:08
elmoor anyone else who's a lpadmin and is awake11:09
stubk11:09
stubYou already are (?)11:09
=== erdalronahi [n=erdal@p5087664D.dip.t-dialin.net] has joined #launchpad
stubyup11:10
elmoerr, really?11:11
stubIf you can't do something, maybe you have found a task that soyuz-dev can do but launchpad-admins can't?11:11
elmostub: this task use to work though.  how confusing11:11
elmosorry for wasting your time, I should have checked11:11
stubI'll add you to launchpad-buildd-admins and see what happens11:12
elmostub: canonical sysadmins are a member of lp-buildd-admins tho, no?11:12
stubYes. So I'm out of ideas ;)11:12
=== stub wonders why the Ubuntu technical board is the administrator of the buildd-admins team
stubThat seems an abuse of an existing team...11:13
elmostub: how so?11:14
stubA team tasked with setting standards and making architectural decisions. I don't see why membership in that team should confer pretty high level rights over the buildds and other production systems.11:15
=== samyboy [n=sam@85-218-27-91.dclient.lsne.ch] has joined #launchpad
samyboyHello. Since Launchapd is not yet released, I would like to find something similar to launchpad tu use in my company. any help ?11:21
lifelessYou can use launchpad right now, just sign up for an account and login.11:22
jsgotangcomaybe he meant to install it in a machine for internal use for his company?11:27
=== WaterSevenUb [n=WaterSev@195-23-238-201.nr.ip.pt] has joined #launchpad
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad
=== mpt_ [n=mpt@203-173-177-223.bliink.ihug.co.nz] has joined #launchpad
=== lfittl [n=lfittl@83-65-242-161.dynamic.xdsl-line.inode.at] has joined #launchpad
=== jd_ [n=jd@wikipedia/Meanos] has joined #launchpad
=== mpt_ wonders why PQM is taking so long
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad
=== jd_ [n=jd@wikipedia/Meanos] has joined #launchpad
=== lincao [n=lincoln@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
=== maxPhoenix [n=root@host209-33.pool8257.interbusiness.it] has joined #launchpad
maxPhoenixsomeone from Italy?02:18
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad
=== salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
=== jd_ is now known as jd_miam
samyboylifeless, I meant what jsgotangco said earlier02:26
samyboyi need a launchpad-like for internal use.02:27
samyboyWhen i say "launchpad-like" I mean a _good_ tool :)02:28
=== Keybuk [n=scott@quest.netsplit.com] has joined #launchpad
=== raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad
=== AndreNoel [n=drenoel@201.22.95.1.static.gvt.net.br] has joined #launchpad
=== LoBoGoL [n=LoBoGoL@200.142.82.130] has joined #launchpad
kikohello hello02:36
LoBoGoLhello :)02:39
=== niemeyer [n=niemeyer@200.193.159.127] has joined #launchpad
LoBoGoLPlease...02:55
LoBoGoLCould somebody tell me if project Ubuntu has an open channel for users' packages and utilities suggestions?02:55
salgadocan I use the email interface on staging?02:56
=== lincao [n=lincoln@200-171-140-32.dsl.telesp.net.br] has joined #launchpad
LoBoGoLsalgado: sorry?02:58
=== flacoste [n=francis@modemcable207.210-200-24.mc.videotron.ca] has joined #launchpad
matsubaraLoBoGoL: #ubuntu maybe03:00
=== cprov [n=cprov@monga.dorianet.com.br] has joined #launchpad
LoBoGoLmatsubara: ok, thanks..03:04
kikoflacoste!03:04
flacostehi kiko!03:04
kikosalgado, no, I don't think you can.03:04
jameshkiko: so we're doing keywords/tags for bugs rather than product components?03:09
kikojamesh, that's the current standing, yes. what do you think?03:09
jameshkiko: it doesn't bother me much either way.03:10
=== niemeyer [n=niemeyer@200.193.159.127] has joined #launchpad
jameshkiko: I suppose the question is whether to manage a fixed set of keywords (similar to bugzilla keywords or bugzilla product components) or have them free text (like "tags")03:11
jameshthe first probably makes for easier searching but is more restrictive03:12
kikojamesh, we were leaning for the latter last we discussed the subject.03:13
flacostekiko: thanks for the spec review!03:13
jameshkiko: I know mark said that if we do keywords we should call them tags :)03:14
salgadois it possible for a person without a preferred email to use the email interface?03:14
kikosalgado, not that I know of. I think it breaks at least03:19
salgadokiko, I'm asking because I want to get rid of this: https://chinstrap.ubuntu.com/~dsilvers/paste/file9pG4cu.html03:22
kikolet's see03:22
kikosalgado, why do we accept email from users with no preferred email?03:23
=== WaterSevenUb [n=WaterSev@195-23-238-239.nr.ip.pt] has joined #launchpad
kikosalgado, is it just because of https://launchpad.net/products/launchpad/+bug/33427 ?03:24
kikosalgado, if so, just fix that bug and remove that crack03:24
salgadothe bug is fixed03:24
salgadoI'm not sure if it's only because of that bug03:25
salgadothe first XXX doesn't mention the bug03:25
=== bradb [n=bradb@209.217.74.66] has joined #launchpad
kikoyeah03:31
kikobradb, do you know of bjorn?03:31
=== jd_miam is now known as frangin
=== frangin is now known as jd_
=== bradb [n=bradb@209.217.74.66] has joined #launchpad
=== carlos [n=carlos@62.87.127.198] has joined #launchpad
carloshi03:56
kikocarlos103:57
kikobradb!03:57
bradbhey!03:57
kikohow's it going bradb 03:58
kikoso03:58
kikoI thought about our problem03:58
kikoand I think I have a plan03:58
kikobut I'd like to see what you think03:58
bradbsure03:59
kikolessee03:59
kikohttps://chinstrap.ubuntu.com/~dsilvers/paste/file2TMy90.html03:59
kikobradb, how does that sound?04:00
=== bradb ponders
kikobradb, the nice thing is that the knob is only used in one point -- filebug.04:01
bradbkiko: Do we know of any current Launchpad user other than Landscape that will want to toggle this flag?04:02
kikobradb, niemeyer made a case yesterday for this actually being useful in certain situations04:03
bradbMy main concern with this approach is it looks like a more generic solution for a problem we've only seen once and which will, AIUI, only last for about six months.04:04
niemeyerbradb: In fact, the flag is already there.. it's only a minor extension to an existing concept..04:05
bradbniemeyer: do you really mean the flag is there?04:06
niemeyerbradb: As exposed in the ticket, "only subscribers can see" currently means "unsubscribe the bug contact".04:07
niemeyerbradb: All we need is to untie these two concepts, and add a "default_is_private" flag..04:08
bradbniemeyer: It means "don't subscribe the bug contact", fwiw.04:08
niemeyerbradb: The behavior in bugs is largely unchanged.04:08
niemeyerbradb: Ok :)04:08
bradbniemeyer: So, my main concern is bloat. This looks like a generic solution for a problem we've seen once, and which, AIUI, is only a problem until LS is officially released.04:09
bradbbecause we can also solve this problem without bloat, and much more quickly.04:10
niemeyerbradb: I was looking at it as something simple.. if you belive it's not worth the effort, we can of course setup our own Roundup or something.04:10
bradbniemeyer: Another way to solve this is to model the solution after the problem: a special case.04:11
kikobradb, I wonder whether the special case will be cleaner than the fix I'm proposing, though04:11
kikobradb, are you suggesting just doing the special case in browser code?04:12
niemeyerbradb: I was quite suprirsed when I understood that the bug contact wouldn't see the bug if you click "only for subscribers". If I'm the maintainer of a product, and someone click on that button, I basically will never get notified about it. Is it the case?04:12
kikoniemeyer, yes, but that's arguably a bug.04:12
bradbniemeyer: It is. I think we're both in strong agreement that that's a nasty bug. :)04:13
bradbthere should be at least some way to file a private bug and not be the only person subscribed to it04:13
kikoright.04:13
kikoone option would be to add a text field04:13
niemeyerbradb: Ah, cool.. I wasn't getting that you agree this should be fixed.04:13
kikoanother would be to add yet another checkbox04:13
kikompt_?04:13
bradbniemeyer: I filed that bug exactly one year ago today. :)04:14
bradbbug 129404:14
UbugtuMalone bug 1294 in malone "Filing a private bug requires the ability to Cc the maintainer" [Critical,Confirmed]  http://launchpad.net/bugs/129404:14
niemeyerWow :-)04:14
kikoniemeyer, we're discussing whether we should do the special handling for bug filing.04:15
mpt_bradb, I don't think it should be *possible* to report a private bug and be the only one subscribed to it, unless you're the maintainer04:15
niemeyerbradb: So, isn't it simple to add a "bugs_default_to_private" flag in products?04:15
kikobradb, if it would be only browser code I am okay with adding the celebrity code.04:15
kikobradb, I still wonder whether it'll be more or less work than doing the product db change04:15
bradbniemeyer: "simple" is a dangerous word. :) it's a feature that needs to be discussed further, spec'd, tests written, implemented, code reviewed, etc. to solve a problem that may not even exist in six months.04:16
bradbconsider it this way:04:16
bradbthe upside is that it would solve your use case04:17
kikobradb, stop singing the spec/tested/etc song, because it's boring and not very true either!04:17
bradbthe downsides are that 1. it will take somewhat longer than a "quick hack" solution for a quick hack problem, 2. it's solving a problem that we've only seen once, and which may not even be there in six months.04:17
kikohowever04:18
kikounless you are /ignoring me04:18
kikoI still haven't seen you confirm that the hack would be browser code only04:18
bradbkiko: in browser code only, i think, yeah.04:19
kikothen I think it's cool04:19
bradbin FileBugView04:19
niemeyerbradb: If it works, I'm not really worried about how it's implemented (you're the one who should be wearing that cap :-).04:19
kikoagreed04:19
bradbI can have the FileBugView solution tested an implemented (though I can't guarantee past pqm) before lunch.04:20
kikowell04:20
kikothere's also fixing bug 1234, which will take longer because we actually have no idea of the UI04:20
kikompt_, wake up04:20
bradbyeah04:21
mpt_kiko, it's 2am!04:21
kikoand at least the impression I get is that 1234 blocks the celebrities hack04:21
niemeyermpt_: What!? And you're not working!? Absurd!04:21
niemeyer:-)04:21
bradbbug 1294, fwiw04:21
UbugtuMalone bug 1294 in malone "Filing a private bug requires the ability to Cc the maintainer" [Critical,Confirmed]  http://launchpad.net/bugs/129404:21
mpt_niemeyer, I am working, I'm fixing the Ubuntu Desktop Guide04:22
kikobecause, well, the celebrities hack, if well-done, will also auto-subscribe the maintainers.04:22
mpt_I am not, however, Launchpadding04:22
niemeyermpt_: Ah, ok then.. ;)04:22
bradbthe simplist solution i can see is to say "if the only person subscribed to this bug would be the reporter, then subscribe the .bugcontact. if there is no .bugcontact, then subscribe the .owner"04:23
bradbthere are, of course, other options04:23
mpt_bradb, that seems reasonable04:23
kikompt_, bradb: how do we make it clear to the end-user?04:24
=== bradb ponders
kikomy only concern is that this is a special-case on top of a special-case04:25
mpt_Mind-waves-over-IP04:25
mpt_[ ]  This bug report should be private04:25
mpt_    Only the bug contact or package maintainer will be notified.04:25
bradbmpt_: the problem is that won't be true if the user clicks the security cb and there is a sec contact04:26
kikomaybe use radio buttons?04:27
kikoand have security-always-be-private?04:27
mpt_    Only the bug contact, security contact (for security bugs), or package maintainer will be notified.04:27
=== samyboy [n=sam@85-218-27-91.dclient.lsne.ch] has left #launchpad ["a+"]
=== bradb ponders ponders ponders
mpt_Are there any Bugzillas that have separate private/security checkboxes?04:29
kikompt_, well, in practice yes, but..04:30
kikobugzilla permissions are way too complicated.04:30
mpt_So, can we possibly turn these from two checkboxes into one?04:32
kikowe could turn them into a radiobutton04:32
bradbRedhat's security cb is an email address :P04:32
kikoor we could turn them into a singel checkbox04:32
bradba single cb would be nice. trying to think of how we'd be able to address all three use cases (private bug, public security bug, private security bug)04:36
bradbone way to model security in launchpad is not to model it at all04:36
bradb(er, sort of)04:36
bradbso, "security" could end up being a keyword, because it's just metadata about a bug, no more special than "branding", or "i18n"04:37
bradbthe bug knob would control only visibility04:37
bradbsecurity bugs would be emailed to security contacts, done outside of Malone, like Redhat doex04:38
bradbs/doex/does/04:38
bradbto report a security bug, you'd follow a link from +filebug, explain the procedure, whom to mail, and offering a gpg key if you're feeling extra paranoid04:39
bradbs/explain/which explains/04:39
mpt_Alternatively, trust product/package/distribution maintainers to forward security bugs to the relevant person04:40
bradbmpt_: keep in mind that the bugcontact for Ubuntu is ubuntu-bugs@ :)04:42
mpt_If that's true, what's the use of reporting a private bug right now?04:43
mpt_"This bug report will be limited to only a gazillion people"04:43
bradbmpt_: they don't see private bugs04:44
kikompt_, right now? we don't CC: anybody04:44
mpt_argh04:44
mpt_hence the original problem :-)04:44
bradbthat's bug 129404:44
UbugtuMalone bug 1294 in malone "Filing a private bug requires the ability to Cc the maintainer" [Critical,Confirmed]  http://launchpad.net/bugs/129404:44
mpt_bing bing bing04:44
mpt_So, I think this is what you get for not implementing product/package/distro subscriptions04:45
mpt_ubuntu-bugs@ should be subscribed to Ubuntu04:45
mpt_but they should not be the bug contact04:45
mpt_and should not get notified about private bugs04:46
=== mdke_ [n=matt@ubuntu/member/mdke] has joined #launchpad
kikompt_, who /should/ get notified about private bugs?04:46
kikoin the ubuntu case?04:46
mpt_The bug contact or maintainer04:47
kikowho would the bug contact be for ubuntu?04:47
mpt_some smaller trusted team, Ubuntu Drivers perhaps?04:47
jameshubuntu-bugs@lists.ubuntu.com is the bug contact at the moment04:47
mpt_yes, jamesh, that's what we're discussing04:48
bradbspecifically, private security bugs should be sent only to the security team, i think. the idea being that an undisclosed vuln should be disclosed to as few people as possible04:48
kikobradb, sure. we know that, and that's what happens today.04:49
kikothe question is: if it /wasn't/ a security bug, but just private, who should we email by default?04:49
kikoI think this is a moot point04:49
kikoI am coming around to thinking that security/privacy should be a single flag for ubuntu04:49
kikoand for landscape only security might be settable via +filebug04:50
kikobut that's really icing on the cake04:50
mpt_If you're odd enough to need private non-security bugs, you can be organized enough to have enough people in your maintainer team to handle all the private bugs04:50
kikompt_, in your security team you mean?04:51
mpt_(Disclaimer: It's nearly 3am and I'm not necessarily making any sense)04:51
kikompt_, then go to sleep04:51
mpt_I'm thinking of what we used to have04:51
mpt_[ ]  This bug report should be private04:51
kikobradb, how does that sound?04:51
mpt_    For example, it's about a security vulnerability04:51
kiko[ ]  This is a security issue04:51
kikothat's the only checkbox that would appear04:51
kikothe security contact would judge whether it's a valid security issue and whether it should be private04:52
bradbkiko: you're suggesting one cb on +filebug, but still keeping two separate cb's on the bug?04:52
kikobradb, yes.04:52
kiko    [ ]  This is a security issue04:53
kiko    * For ubuntu, marking security would make it private as well.04:53
kiko    * For landscape, all bugs would be private. Marking security would04:53
kiko      only make it security-related.04:53
kikoand s/ubuntu/any other context/04:53
jameshkiko: would a set of checkboxes for each of the default bug contacts make sense for private bugs?04:53
jameshkiko: to give the user an idea of who might be worth subscribing up front?04:54
kikojamesh, like a subsidiary set of checkboxes? that sounds overcomplicated to me..04:54
kikojamesh, I get the feeling that all security bugs should be initially private and the security contact can decide whether to disclose them or not.04:54
kikosort of a "security triage"04:54
kikothis would solve the "nobody sees private bugs" problem04:54
kikosimplifying that -- possibly fixing bug 129404:55
UbugtuMalone bug 1294 in malone "Filing a private bug requires the ability to Cc the maintainer" [Critical,Confirmed]  http://launchpad.net/bugs/129404:55
kikobradb, talk to me04:55
bradbkiko: The issue still seems to remain about who to subscribe when that box is checked, if there is no sec contacct04:55
bradb(and make it clear to the user)04:55
kikobradb, the maintainer. that can be made clear using text.04:55
kikobradb, that's an easy one to answer.04:55
jameshkiko: you need to let the reporter make a security bug public: they have the ability to disclose it anyway04:55
kiko(and I thought that's how it worked today)04:55
kikojamesh, they can do it after the fact, sure04:56
jameshkiko: making security bugs private by default is a good idea though04:56
kikojamesh, I just don't think it warrants letting them do it in +filebug04:56
kikoin particular because filing private bugs makes the CC: issue complicated.04:56
bradbjamesh: that's how it works today, where "by default" means we select the privacy cb for them when they click the security cb.04:56
kikoI am arguing for not displaying the privacy cb at all in +filebug04:56
kikoand letting the security contact take care of triaging the security bugs.04:57
bradbyeah, i understand that04:57
kikodo you agree with it, though :)04:57
jameshbradb: That's the behaviour I'd expect.  So the reporter can unselect it if the security bug is for an issue that has previously been disclosed04:57
=== raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad
kikojamesh, are you arguing for making the privacy checkbox /only apply/ if security is checked?04:58
kikojamesh, I also think that it's not a lot of work to disclose it post-report, anyway.04:58
jameshkiko: no.  I think the current setup of two checkboxes is okay.04:58
jameshkiko: currently javascript is used to check the private checkbox if you check the security checkbox04:59
kiko"This security bug is by default private, and only the security contact ubuntu-security@ubuntu.com has been subscribed. You can disclose the bug <a href="">in the bug edit form</a>04:59
jameshperhaps a combo box that combines both settings would be better though04:59
kikojamesh, I don't think the current setup of two checkboxes is okay, though. A lot of end-users get confused and we still have the issue of non-security private bugs going to limbo.04:59
=== mdke [n=matt@ubuntu/member/mdke] has joined #launchpad
jameshkiko: do you think a combo box would be better?05:00
mpt_WARNING: "You can $FOO in the $BAR" detected. Try linking directly to the page instead.05:00
mpt___Disclose the bug__05:00
kikoyeah yeah05:00
kikojamesh, I think that non-security private bugs are a bad idea.05:01
=== bradb can't think of a practical use case for them, other than LS for the next six months.
jameshkiko: do you think public bugs marked as security related are a good idea?05:02
bradb(our own LP use case can be solved by putting sensitive snippets on private servers, like chinstrap)05:02
kikojamesh, I'm okay with that, though I think there's a weak case for catering specially for them in +filebug.05:02
jameshbradb: btw, if you have any comments on the PythonBugTrackerCompetition wiki page, please update the wiki page or mail the list05:04
kikobradb, wanna seal this with a phone call?05:05
bradbkiko: sure05:05
jameshbradb: I'll see if I can get a basic import ready early next week, but I think we'll need to coordinate on some malone improvements05:06
bradbjamesh: yeah, i'm subscribed to that page05:06
bradbjamesh: cool05:06
=== einheit_ [n=steve@195.182.78.95] has joined #launchpad
salgadohey kiko, would you like to review my karma-context branch?05:12
kikosalgado, I guess I could05:13
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad
=== einheit_ is now known as SteveA
=== _malcc [n=malcolm@host86-135-139-100.range86-135.btcentralplus.com] has joined #launchpad
salgadoZnarl, kiko, how about "Choose Release if this mirror contains CD images of any of the  various releases of this distribution, or choose Archive if this mirror contains packages for this distribution and is meant to be used in conjunction with apt.", as the text under the Content drop-down box, to help people choosing the right one?05:36
kikosalgado, or we could auto-detect. have you considered that?05:37
salgadono05:38
carlosIs pqm stalled?05:38
mpt_yes05:39
salgadokiko, that won't be trivial to implement. I'd prefer to do something like this and, if it doesn't work, we can do the auto-detection05:39
salgado(I was expecting that people would know the content they're mirroring)05:40
kikosalgado, I don't think text is going to be effective, but sure, give it a try.05:40
Znarlsalgado : I think it's good.05:40
ZnarlAnd agree with you on auto-detecting not really working very well.05:40
=== mdke grabs Znarl
carlosmpt_: ok, thanks for your confirmation05:41
salgadoZnarl, cool...  I'm doing some tweaks to the mirrors UI; maybe you can have a look after I finished to see if everything is okay?05:44
Znarlsalgado : Sure, ping me when you're ready.05:45
salgadowill do!05:45
=== Duro_De_Peinar [n=duro@tor/session/external/x-b8a4585fcd3386c5] has joined #launchpad
=== Alextremo [n=desarrol@150.188.12.22] has joined #launchpad
=== ploum [n=ploum@ubuntu/member/ploum] has joined #launchpad
=== ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad
=== Duro_De_Peinar [n=duro@tor/session/external/x-b8a4585fcd3386c5] has left #launchpad ["Leaving"]
=== mdz [n=mdz@studiocity-motorola-bsr1-70-36-194-85.vnnyca.adelphia.net] has joined #launchpad
=== sabdfl [n=mark@ubuntu/member/pdpc.silver.sabdfl] has joined #launchpad
sabdflkiko-fud: please ping cvd when you're back and we can have that call06:28
SteveAi'm around.06:29
SteveAsabdfl: want to do a quick pre-kiko catch up?06:29
=== bradb & # lunch
=== LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #launchpad
=== Alextremo [n=desarrol@150.188.12.22] has joined #launchpad
=== carlos_ [n=carlos@62.87.127.60] has joined #launchpad
=== mdz [n=mdz@studiocity-motorola-bsr1-70-36-194-85.vnnyca.adelphia.net] has joined #launchpad
=== niemeyer_ [n=niemeyer@200.193.159.127] has joined #launchpad
=== Alelasquez [n=desarrol@150.188.12.22] has joined #launchpad
=== loko555 [n=user@p54B8AA11.dip0.t-ipconnect.de] has joined #launchpad
loko555i have a problem with launchpad. i am not assigned to a bug nor i have subscribed to one but i still get a email-report about a bug. how can i stop this?07:41
=== raphink [n=raphink@vll06-1-82-234-166-84.fbx.proxad.net] has joined #launchpad
salgadoloko555, which bug?07:44
=== BjornT [n=bjorn@213.226.190.253] has joined #launchpad
loko555https://launchpad.net/bugs/3296307:48
UbugtuMalone bug 32963 in xserver-xorg-driver-i810 "Xv movies on 810/i945 gives horrible color, Gamma" [Unknown,Needs info]  07:48
loko555salgado: this is the bug07:49
salgadoloko555, did you report bug 42349?07:51
UbugtuMalone bug 42349 in xserver-xorg-driver-i810 "Dapper Drake - i810 - Video Color output wrong" [Medium,Fix released]  http://launchpad.net/bugs/4234907:51
loko555yes07:51
loko555but i get infos about bug 3296307:52
UbugtuMalone bug 32963 in xserver-xorg-driver-i810 "Xv movies on 810/i945 gives horrible color, Gamma" [Unknown,Needs info]  http://launchpad.net/bugs/3296307:52
loko555but why?07:52
salgadoloko555, right. you get notifications about the latter because it has the former (the one you filed) as one of its duper07:53
salgados/duper/dupes/07:53
loko555ok, but how can i cancel the notifications?07:53
salgadothere's a bug open for that, IIRC. (I'm trying to find)07:53
matsubarabug 4886007:54
UbugtuMalone bug 48860 in malone ""Also notified" makes difficult to unsubscribe" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/4886007:54
loko555oh, and this does mean that at the moment i will get the notifications until this bug is closed?07:55
flacoste/whoami07:57
flacostethis is a big question...07:57
=== BjornT_ [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad
=== cprov [n=cprov@monga.dorianet.com.br] has joined #launchpad
=== mdz [n=mdz@studiocity-motorola-bsr1-70-36-194-85.vnnyca.adelphia.net] has joined #launchpad
sabdflSteveA, kiko-fud: calling now08:13
=== edgy [n=edgy@86.60.38.116] has joined #launchpad
edgyHi, as far as I read rosetta is not free, how much is it?08:15
sabdflit's free to host your potemplates and pofiles08:15
edgysabdfl: can I e.g import other distributions' files to it?08:16
edgysabdfl: say fedora e.g specific files?08:16
edgysabdfl: I want to use it for maintaining traslation of many open source projects that may not fit well  being uploaded to ubuntu, should I buy it or go for pootle or make a deal with canonical to translate rosetta to my lang and they allow me to use it? ;)08:18
LarstiQedgy: there are upstream projects with translations in rosetta, not just ones in ubuntu.08:19
edgyLarstiQ: yes but as far as I understand all those upstream projects can be used in ubuntu like kde or gnome but I don't see any other distribution specific files in rosetta, is there?08:21
LarstiQedgy: I'm not sure what you are asking for. There are other distributions in launchpad, see https://launchpad.net/distros/08:21
edgyLarstiQ: wow! this is new to me.08:22
LarstiQedgy: launchpad is meant to make cooperation between up/down/samestreams easier. Wether that is between distros, between a given up and all their downstreams, etc.08:23
LarstiQedgy: so it has support to track the state of a bug in all places08:23
LarstiQedgy: I'd think the same is true for rosetta.08:24
edgyLarstiQ: nice. but  https://launchpad.net/distros/fedora/+translations contains no translation and saying: Translation policy: Doesnt use Rosetta08:25
LarstiQedgy: you want to translate fedora specific packaging?08:26
edgyLarstiQ: yes08:26
LarstiQedgy: I guess you would need to talk to the fedora people then08:26
LarstiQedgy: but carlos can help you more with these questions I think08:27
=== LarstiQ is just a launchpad user (and not even ubuntu at that)
LarstiQedgy: Afaik the idea is not to use rosetta if the product/distro in question doesn't want to use it itself08:27
edgyLarstiQ: so it's just a matter of  fedora people agree but ubuntu people would have no issue about importing any open source project?08:28
LarstiQnow you confuse me08:28
=== LarstiQ gets an example
edgyLarstiQ: still I am confused because kde is translated using it's cvs system and if I translate from rosetta a conflict would happen08:29
edgysome work would got thrown away in favor of the other unless an upstream update is checked daily or so08:30
edgyLarstiQ: why do I confuse you?08:30
LarstiQsorry, had to let someone in08:31
edgyLarstiQ: fedora has different teams for each language. a maintainer of one language may like to use rosetta but others may not. so would it be decided for each team alone or for the whole distro?08:31
LarstiQedgy: I think it would be possible on a per team basis, I believe gnome has something similar going on08:32
LarstiQedgy: the confusion stems from me thinking you want to do packaing bits, then thinking, oh no, upstream products, and being thrown from the one to the other08:33
=== LarstiQ will take kde as an example next, but first bzr
LarstiQedgy: see https://launchpad.net/products/bzr , that is the upstream product, no distribution bits there08:33
LarstiQedgy: bzr doesn't use rosetta simply because there is nothing to translate08:34
LarstiQhttps://launchpad.net/products/bzr/+distributions lists the packages of bzr in distributions08:35
edgyLarstiQ: ok this is clear now08:35
LarstiQedgy: so if there is an upstream products you want to translate, but not necessarily bound to a distro, you can do that 08:37
edgyLarstiQ: understood. thx for the clarification08:38
=== LarstiQ wants to clarify more, but I have to leave the house for a while, sorry
LarstiQciao08:41
=== niemeyer_ [n=niemeyer@201.11.38.227] has joined #launchpad
=== edgy [n=edgy@86.60.38.116] has left #launchpad ["Konversation]
LarstiQhmm, he left already.09:23
=== lfittl [n=lfittl@83-65-242-161.dynamic.xdsl-line.inode.at] has joined #launchpad
=== ploum [n=ploum@ubuntu/member/ploum] has joined #launchpad
kiko-fudbradb, note mdz's emails on the subject of our discussing this morning, but both mark and I have now green-lighted the project so it is blessed from Above :)09:54
kiko-fudBjornT_!09:54
bradbkiko-fud: I already made the change to vulnerability here.09:55
bradbSo I'm on the road, speeding through the green light, creating a breeze for the pedestrians.09:55
mdzbradb: could we require that they type into a text entry box "I am not fucking around" before it will let them file a security bug?09:55
kiko-fudmdz, the current plan is moving that control to a separate page anyway09:57
bradbmdz: that might be useful, though i'd rather proceed with what kiko/mark/etc. already blessed before changing it09:57
kiko-fudfucking around might look bad on LP UI09:58
bradbcussing is for portlets09:58
=== bradb discovered the agony of doing .getControl(name="some-checkbox") vs. .getControl("the checkbox label"). you can do .selected = True on one and not the other!
LarstiQfor some reason autotools-dev is listed as a distro package for bzr. Anything I can do about that?10:13
=== jd_ [n=jd@wikipedia/Meanos] has joined #launchpad
=== bradb [n=bradb@209.217.74.66] has joined #launchpad
Alextremoviva PAPASHANTY SOUND SYSTEM... !!!! Chao mis panas... Nos leemos el Lunes....5 4 3 2 1 010:49
kiko-fudwtf10:49
kiko-fudPAPASHANTY SOUND SYSTEM?10:49
Alextremoyeah  escuchalo10:50
kiko-fudI'll give it a spin later10:50
AlextremoPAPASHANTY = Father of the peace10:51
AlextremoPAZ10:51
Alextremobuy the cd10:52
Alextremois very nice10:52
Alextremosorry not speak so much english10:52
AlextremoBueno, Feliz  Fin de Semana...10:54
AlextremoChao10:55
=== Alextremo [n=desarrol@150.188.12.22] has left #launchpad ["Konversation]
kiko-fudlol10:56
=== andyp [n=andydpar@83.104.143.93] has joined #launchpad
=== raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad
matsubarabradb, BjornT_, SteveA, anyone: Datetime field returns an not naive datetime object. Do you know from where it takes that timezone information?11:55
=== lbm [n=lbm@82.192.173.92] has joined #launchpad

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