jono_well python-snippets is not for docs, it is just a library that aggregates examples00:00
lifelessjono_: the second link is probably more the sort of thing you're looking f or00:00
lifelessthat page is full of examples00:00
jono_so if you are a developer you have a regularly growing library of examples to lean on00:00
jono_sure, and it would be great to put those examples in python-snippets00:00
lifelessjono_: I think it would be better to have acire pull them in automatically.00:01
lifelessjono_: rather than duplicating content, which can then go stale.00:01
lifelessjono_: I can file a bug for you, if you like.00:01
jono_lifeless, how could that work for any project?00:01
jono_lifeless, write a patch, that would be better ;-)00:01
lifelessjono_: I don't know, I'm not an Acire developer ;)00:01
jono_I don't think it would be possible in a generic00:01
jono_if you don't want to contribute the examples, thats fine00:02
jono_I just think it will help people get started quicker00:02
lifelessjono_: uhm, I don't think we're communicating effectively00:02
lifelessI know of the acire project - its a nice idea.00:02
lifelessand you're welcome to take the examples we've written already. I think that that creates a problem for acire though00:03
lifelessthe problem is that you have to sync on an ongoing basis00:03
lifelessor the examples will stop working00:03
lifelessit also means that patches to the bzrlib docs to improve this may end up going to acire instead00:03
lifelessI don't think either of those things are desirable.00:03
jono_lifeless, I agree with the problem, I just don't know what the solution is :)00:04
jono_I suspect that if python-snippets gains momentum, people will fix the examples00:04
jono_that has happened so far00:04
lifelessso, if you agree with the problem, I can file a bug. That records the problem and perhaps someone with an interest can implement a solution.00:04
jono_I would love a way to pull in snippets automatically tbh00:04
jono_sure :)00:04
lifelessI can suggest techniques to do pull-ins for you00:04
lifelessits not conceptually hard00:05
lifelesslp:acire ?00:05
jono_lifeless, are there docs for the UI bzrlib API?00:16
lifelessthey're not perfect, but pretty good we think00:18
lifelessplease do let use know (by bugs) of any questions that aren't answered by the docstrings00:18
jono_lifeless, I am still not entirely clear what this does00:19
jono_as a bzr n00b00:20
jono_bzrlib n00b, that is00:20
lifelessok, so thats bug one00:20
lifelessI'll file it00:20
lifelessok filed00:23
lifelessbzrlib.ui.ui_factory is an instance of UIFactory (a subclass thereof)00:23
lifelessit is used to get hold of progress bars00:23
lifelessto prompt for passwords00:24
lifelessto geta file-like object that diffs and other things can be written to00:24
jono_lifeless, right, so could I use that to branch async so it doesnt block my GUI?00:31
lifelessjono_: you would run the bzr commands in a thread (pick one thread, don't move objects between threads). And then your UI factory can feed events back to your UI, yes.00:32
PabloRubianeshi i am having some troubles with Launchpad00:36
PabloRubianesI am trying to find someone to give me a hand00:36
jono_lifeless, cool00:37
thumperPabloRubianes: what type of troubles?00:40
PabloRubianesI am trying to add an email account and give me oops...00:40
thumperPabloRubianes: which account, which email and can you give me the oops number?00:41
thumperPabloRubianes: priv msg is fine00:41
PabloRubianesyes a sec00:41
thumperPabloRubianes: the tool that we use to look at the oopses is having issues of its own00:47
thumperPabloRubianes: have you asked a question on answers.launchpad.net/launchpad ?00:47
thumperPabloRubianes: that will probably be the best place to track it00:47
thumperand I can make sure someone looks at it as soon as they can00:47
thumpermost of the devs in this area are in UTC-5 .. UTC-800:48
PabloRubianesno. I just got that and the came here. But I will ask there if you say so.00:48
thumperPabloRubianes: probably best right now as I can't do anything00:48
PabloRubianesthumper: Thanks for your time00:48
thumperPabloRubianes: did you try the work around?00:49
ubottuLaunchpad bug 431845 in launchpad-foundations "Unable to add email address" [High,Triaged]00:49
PabloRubianesthe thing is that the email address has 30 minutes till i made it...00:51
PabloRubianesbut i will try that00:51
thumperPabloRubianes: ah00:52
thumperPabloRubianes: so you've not used it before?00:52
lifelesswgrant: jono_: bzrlib.branch.Branch.open does directory service lookup, I think.00:56
lifelessI suspect the problem was not loading plugins at all00:56
thumperPabloRubianes: probably a different bug then00:56
thumperPabloRubianes: make sure you say that in the question (or add a comment saying that the email address is new and unused with LP or ubuntu in any way)00:57
PabloRubianesi think the work around gave me another empthy account00:57
PabloRubianesI think someone had that mail...00:58
thumperPabloRubianes: what account did it give you?00:58
PabloRubianesnow i have it or something weird00:58
thumperPabloRubianes: did you use the email address for ubuntu forums?00:58
thumperPabloRubianes: or shipit?00:58
PabloRubianesno i use openID for thouse00:59
thumperopen id from where?00:59
PabloRubianesfrom my lauchpad account01:01
PabloRubianesI will merge two and that's it..01:03
wgrantlifeless: Ah, true.01:05
fmarieri'm a little confused by the team "reported bugs" page. i would expect that page to list all of the bugs that were reported by team members, but it doesn't seem to do that...01:06
wgrantfmarier: That probably isn't meant to exist, but your expectation makes sense.01:06
fmarieryou mean the page isn't meant to be there at all?01:07
wgrantI suspect that is the case.01:07
wgrant(teams are really people in Launchpad, so they inherit stuff)01:07
fmarierah bummer... i was hoping i'd be able to use that to find out what bugs a certain group of people had reported01:07
wgrantIf you report a bug, you probably will be able to :)01:08
wgrantIt's not hard to make that work.01:08
fmariercool, i'll do that right now :)01:08
fmarierare there really just 3 open bugs on launchpad itself?01:09
PabloRubianesthumper: done... thanks again... I will comment the bug report01:09
wgrantfmarier: Launchpad's current usage of Launchpad projects is a bit strange. There are lots of separate projects, all the launchpad-project project group.01:10
wgrantfmarier: malone is the name of the bugs component.01:10
fmarierah so i should be filing a bugs against that then01:10
wgrant'launchpad' is the bugs that haven't yet been assigned to the appropriate component.01:10
fmarieror should i let the bug triager assign it to the right component?01:11
wgrantIt's fine to file against 'launchpad' -- somebody will reassign it later on. But it'll probably be quicker if you file against the specific project to start with, yes.01:11
fmarierah just found an existing bug for it from 2008 (#307572)01:16
wgrantBug #30757201:18
ubottuLaunchpad bug 307572 in malone "Team related bugs page doesn't show bugs related to the members of the team" [Medium,Triaged] https://launchpad.net/bugs/30757201:18
wgrantfmarier: You might want to click the "Does this bug affect you?" thingy.01:19
fmarierwgrant, good point. done.01:20
yofelhi, where can I someone that can kill  a ppa build? My build on thorium seems to be stuck in an endless loop https://edge.launchpad.net/builders/thorium01:35
yofel*I find someone01:35
yofel(how about adding an 'abort' button somewhere?)01:36
wgrantyofel: Is it actually in an infinite loop, or is it not doing anything at all?01:38
persiayofel: For the abort button, file a bug.  That's likely tricky, but potentially possible.01:39
wgrantIt's likely that the builder has died somehow.01:39
wgrantI have an abort backend mostly working.01:39
wgrantBut it's unclear if it would work in this particular circumstance.01:39
wgrant(it depends on how badly the builder is wedged)01:39
yofelpersia: will do01:40
yofelwgrant: I *think* the buildlog still gets updated but as the only thing it shows are inkscape warnings I can't really tell01:41
wgrantyofel: Ah, you're right, it is updating.01:44
wgrantSo the builder is still alive.01:44
thumperfmarier: hi01:46
thumperfmarier: how are you enjoying launchpad?01:47
thumperfmarier: notice the subtle positive slant on that question :)01:47
yofelwgrant: can you kill it then, the build shouldn't take 8h...01:55
wgrantyofel: I'm just a user.01:55
yofelok, should I post a question on launchpad or do you think someone will kill the build at some point?01:56
wgrantSomebody should kill it at some point.01:59
yofelok, thx :)02:01
fmarierthumper, nice marketing work there :)02:13
fmarieractually launchpad is great for us, it's the most usable bug tracker i've ever seen02:14
fmarier or used02:14
fmariernow if we could get our old bugs imported (Question #93120), we could finalise the move to Launchpad and decommission our old tracker02:17
fmarierthumper, notice the subtle prod on that last comment ;-)02:17
* thumper looks at the question02:18
fmarierone thing that would be nice with these imports is if there was a testing script we could use to "validate" our XML export before we send it to you guys02:18
fmarierbut i'm guessing that perhaps the "testing script" currently involves trying to import it into launchpad staging...02:19
mwhudsonfmarier: launchpad running in ec2, i think, but yes02:19
thumperfmarier: I'll forward that request on to the right person :)02:24
wgrantIt first gets tested on EC2 (or you can run it locally, if you want).02:25
wgrantThen it gets tested on staging, to ensure that it doesn't conflict with production data.02:25
thumperfmarier: request passed on, should get some form of response within a day or so02:26
fmarierthumper, cool, thanks!02:26
thumperfmarier: np02:26
doctormoOOPS-1521S65 - Looks like logging in on staging is broken.06:31
doctormoI was wondering how login.launchpad.net was being translated.06:31
wgrantdoctormo: A warning about the OpenID stuff: Launchpad will probably start using login.ubuntu.com soon, so your code will probably break.06:33
doctormowgrant: Already does break, is broken, uses edge by default.06:35
wgrantdoctormo: login.ubuntu.com != login.launchpad.net06:38
wgrantThe latter is used at the moment.06:38
doctormowgrant: Will you still be sending the html form when you go to https://launchpad.net/+login ?06:40
doctormowgrant: Because my code is moving towards detecting that form and sending it on.06:40
doctormoWhere ever it points to06:40
wgrantdoctormo: The edge behaviour is what will be on production in a few days.06:41
doctormowgrant: Is openid being phaised out in favour of SSO?06:41
wgrantSSO uses OpenID.06:42
wgrantLP is becoming an OpenID consumer.06:42
wgrant(at the moment restricted to one provider -- now login.launchpad.net, but soon login.ubuntu.com, and hopefully eventually anything at all)06:42
doctormoI see06:42
doctormoSounds like a good way forward06:43
doctormoAnd makes it fairly imperative that the oauth stuff has a desktop client.06:43
wgrantOpenID makes a desktop client a little more difficult.06:45
wgrantI don't really see why requiring a browser to authorize access to a webapp is a huge problem.06:45
persiaBecause one may not need a browser to use the LP API06:47
doctormowgrant: Really bad security, terrible workflow and it doesn't work on machines without a gui.06:47
persiadoctormo: Why bad security?06:47
doctormopersia: Web browsers can display anything, from anywhere, made to look like it's authentic, it's code base is large and hard to protect from all attacks.06:48
doctormoBetter to have smaller, dedicated authentication tools06:48
wgrantA generic OpenID authentication solution without a browser borders on impossibility.06:49
doctormowgrant: It does, we may just have to assume the authentication service and let the user configure it directly in a conf file if they're using something different06:50
persiaIs there a reason that one can't use some http client library to do it?06:51
wgrantpersia: There is no common interface for authentication to OpenID providers.06:51
doctormopersia: That's what I am doing with ground control, but it's not lp policy to allow such things.06:51
wgrantAgainst, but not to.06:51
persiawgrant: Aha.  That makes sense now.06:52
doctormopersia: I figured I could make it more robust by using a find a form and find fields logic that could make educated guesses.06:52
persiaBut I'd still like to see a liboath-authenticate: perhaps that needs work with the various providers (and the spec).06:52
persiadoctormo: I think that's the wrong way to go about it, personally.06:53
doctormopersia: I'm happy to do something different06:53
wgrantpersia: OAuth, or OpenID? They're separate things.06:54
persiadoctormo: The path I'd recommend is a long one: to work with the spec to create a defined interface for authentication *to* providers, and work with the providers to implement it.06:54
doctormopersia: Of course, that's the right way to do outh as a desktop service.06:54
wgrantThat's very difficult, as providers can choose whatever authentication mechanism they wish: SSL certificates, usernames and passwords, physical key generators, that sort of thing.06:55
doctormowgrant: That's why you nail down a spec for defining such things.06:55
persiaNo, nailing it down would be bad.06:55
wgrantVery bad.06:55
wgrantConsumers aren't meant to care.06:56
wgrantAnd nailing it down would remove the abstraction that OpenID provides.06:56
wgrantAlso, you're only meant to give your credentials to your provider through an application that you trust.06:56
wgrantProxying that is a phishing attempt.06:56
doctormowgrant: Only the abstract of method, not the abstract of authorisation as a seperated service.06:56
doctormowgrant: That... gives me an idea.06:57
doctormowgrant: Will launchpad accounts be able to be logged in via multiple openid logins or just the one?06:58
wgrantdoctormo: That is undecided, TTBOMK.06:58
persiaJust to make sure I'm reading the right specs, is it correct to say that LP API clients use oauth to connect to LP, and LP will use OpenID to authorise accounts?06:58
wgrantI would hope the former, though.06:58
wgrantpersia: Correct.06:58
wgrantWhen you start an API client for the first time, it will request an OAuth token from LP.06:58
wgrantLP will give it a URL that the user must visit to authorise the token.06:59
persiaOK.  So the client (e.g. groundcontrol) uses oauth, and if it gets a failure, needs to request that the user log into launchpad.06:59
wgrantThis is normally in a browser, which has an existing user session with LP.06:59
persiawgrant: But presumably that's a bug in LP, as it cannot know in advance how the OpenID provider authenticates, no?06:59
doctormowgrant: If the former, then there is nothing to stop us having our own desktop openid authentication service. Something with a well defined spec, even using ssh or gpg keys instead of passwords.07:00
persiadoctormo: The main limiting factor there is in having a server to handle the requests (infrastructure).07:00
wgrantpersia: An OpenID consumer redirects to the provider.07:00
* persia reads specs harder07:01
wgrantpersia: It makes no assumptions about the provider's authentication mechanisms; it just redirects there with a token, and the consumer redirects back with a sort of signed copy of the token.07:01
doctormopersia: nothing to stop us hooking that to ubuntu-one07:01
wgrantdoctormo: That could be what login.ubuntu.com is.07:01
wgrant(I personally would want to unlink the login.ubuntu.com ID from my Launchpad account, because I do not trust it, so I wouldn't want applications locked to it, but that's another story)07:02
doctormoYou don't trust the canonical sso?07:02
doctormoThe why are we moving towards using it by default?07:03
wgrantI personally do not trust it. I am no Canonical person.07:03
persiadoctormo: Consider that the move to make LP an openID consumer doesn't change the authentication path.  That LP logins happen to currently be insecure is entirely separate.07:04
persiaErr..  well, it does change the path, but not the custodian of the path.07:04
doctormowgrant: Right, but surely your opinion on the matter has some weight in the discussion07:05
* doctormo feels that ground control is a project before it's time... ready to go but failed by it's cloud counterpart.07:07
persiaWell, no.07:08
persiaThe trick is making authentication work generally.07:09
doctormopersia: I have no great confidence in the future design of it, made as it is to be elegant but missing some key considerations.07:11
persiadoctormo: Hrm?  It's just code.  We can make it do anything.  The hard part is figuring out what it should do.07:12
doctormopersia: The openid stuff is closed source07:13
persia*which* "openid stuff"?07:14
doctormopersia: login.ubuntu.com and login.launchpad.net07:15
doctormohttp://divajutta.com/doctormo/gcweb/ <- This is a website Bret Alton is putting together, what do you two think?07:16
persiadoctormo: That a specific implementation is closed source is irrelevant.07:16
doctormopersia: Isn't not so long as launchpad is tied directly into it.07:18
persiadoctormo: So, the problem is that one wants to have a client that authenticates to LP in a sane way.07:19
persiaOAuth already provides useful information about authentication failures.07:19
persiaI'm sill reading the OpenID spec, but I expect to find something useful there.07:19
persiaBased on that spec, it should be possible to identify the correct behaviour for the client application.07:20
persiaAnd any way in which LP doesn't meet that behaviour is likely a bug in LP.07:20
doctormopersia: With a tie to openid, the desktop would have to have a way of getting an oauth token by using some other method of authentication.07:30
doctormoOr would have to be tied to a specific openid system, not optional07:31
persiaThe desktop client needs to have some way to richly inform the user that they need to authenticate, and help them to do so.07:31
persiaThis depends on the volume of information available when the authentication failure is received.07:31
doctormopersia: Yes, they call that the web browser07:31
persiaNot if my OpenID provider uses some other authentication method.07:32
doctormopersia: True, but there is not the tech for it currently, for most websites consuming that openid will fail.07:37
wgrantdoctormo: Why would they?07:38
wgrantdoctormo: Websites don't care -- they redirect to the provider.07:38
* persia can't imagine why07:38
wgrantThe provider is free to do whatever they want.07:38
doctormowgrant: How do you redirect, if your not using a brwoser int he first place?07:39
lifelesswasn't openid/oauth was designed with the idea that the browser was the 'trusted computing base' for the user07:39
lifelessso users won't put their password into a strange app ?07:40
wgrantOAuth not so much, but OpenID was.07:40
wgrantAnd Launchpad's OAuth authorisation implementation was07:40
lifelessdoctormo: HTTP != a browser.07:40
doctormolifeless: OAuth might have been, but the OAuth developers backtracked after security failures.07:40
doctormoShame we can't just grab webkit, rewrite the cookie implimentation and forge a system wide auth service. But it's too late for that, we got a bunch of legacy to deal with.07:43
persiaOK.  So OpenID returns openid.user_setup_url when it fails.  That should be passed to the oauth failure.07:47
persiaThere is no documentation that indicates what that URL should contain.07:47
=== poolie1 is now known as poolie
persiaSo, the next step is to work with the OpenID folk to make sure that openid.user_setup_url is guaranteed to be machine-readable.  Desktop clients can then pull and use this to provide rich information to users.07:48
thumperwhat's that damn command to list processes listening on ports?08:44
lifelessamongst other things08:46
thumperlifeless: any idea what kicks off /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service ?08:51
lifelessthumper: dbus activation08:53
persiathumper: Have you looked in /etc/init and /etc/init.d/ ?08:53
lifelessthumper: gwibber will do it08:53
lifelessthumper: as will ubuntu one08:53
thumperit was listening on 5800008:53
lifelessand potentially other things08:53
thumperas does the test librarian08:53
lifelessthumper: ahhahah08:53
persiaIf I know the URL for an bug in a bugtracker known to launchpad, is there a way to see if the bug is already registered in launchpad?08:59
wgrantpersia: Find the Launchpad bug tracker URL on https://edge.launchpad.net/bugs/bugtrackers09:03
wgrantThen add the bug number to the end of that URL.09:03
wgrantNo, this is not documented.09:03
persiaThat's fine.  Being able to do it solves my immediate problem, and if I end up doing it several times, I'll be able to tell folk here.09:03
wgrantIt comes up once or twice a year.09:05
persiaHrm.  Seems like my bug isn't there, but that's a good url to remember for lots of things, after exploring.09:06
Zushave a question abour pgp. and signing code of conduct. do i get one from a LoCo team or do i get one personaly09:59
persiaGet which?10:02
nigelbZus: you want to sign the ubuntu code of conduct?10:05
nigelbI believe the instructions are given there, how to generate key and how to upload your key10:05
Zusnigelb,  yeah i read it and downloaded it but  i need a pgp to sign it10:05
Zusi am reading  on how to make it now. but i wasnt sure if you need one per team..bugsquad or a LoCo team.. or  if i can make one on my  own10:07
ZusPgP sorry10:07
Zuswill i only have to do the key once? regardless of upgrade?10:09
nigelbZus: https://help.launchpad.net/YourAccount/ImportingYourPGPKey10:13
geserZus: the gpg key you generate is your own personal key10:13
geserand you can use it not only within Ubuntu but also outside Ubuntu (if you want) to e.g. sign e-mails10:13
Zusgeser even personal emails? even though its got my LP profile info?10:15
geserZus: yes, but it's up to you. the gpg key itself has no connection to LP, LP only knows which key is yours because you told LP so10:17
Zusgeser, now thats more the direction i was trying to go didnt know how to word it.10:18
=== daniloff is now known as danilos
Zuseveryday im learning something new... i have been wasting time in XP lol  thank you guys!10:22
jussi01can I bug someoen about bug 48839410:53
ubottuLaunchpad bug 488394 in launchpad-registry "Export irc_nicknames with "anonymous" requests" [Low,Triaged] https://launchpad.net/bugs/48839410:53
wgrantjussi01: Replied on the bug with the solution. It's trivial.10:57
jussi01wgrant: yeah, Im sure it is. just someone needs to do it.10:58
jussi01and it would _really_ help if its done before the 3rd, but Im not holding my breath10:58
wgrantIt's unlikely, given that it's release week and everything is frozen.10:59
jussi01wgrant: thank you for adding that though, every bit helps10:59
wgrantIf it wasn't week 4, I'd do it now and get it landed tonight. But there's little point doing it now.10:59
jussi01So next week then?11:00
wgrantUnless we have a nice/foolish RM.11:02
jussi01wgrant: if you have time, could you get it up there so at least the work is done and all we need to wait for it just upload?11:05
Laneywhat is a "Review type"?11:35
askhlHi.  Regarding translations, I think I understand the meaning of the translation colour codings for projects that have launchpad as downstream, and a different upstream source.  But what determines the colour coding for projects whose upstream *is* launchpad?11:37
thekornLaney, a random text describeing the kind of review which is supposed to be done by someone or was done by someone, like "code", "tests", "ui", whatever11:37
Laneyoh, alright11:37
Laneyis it ok to leave it blank?11:37
askhl(by translation colour codings I mean the green/purple/blue/red bar colours)11:37
thekornLaney, launchpad provides no "correct" values for this field, it is the policy of the project you work on,11:38
Laneyalright. It's just not clear from the UI what this is for.11:39
thekornLaney, there might be the policy to never leave it blank11:39
askhlI guess those strings can only be purple ('new in launchpad') or red (untranslated).  Am I understanding this correctly?11:40
dpmaskhl, if I'm not mistaken, it should mean the same: green are the translations which are the same in the source package (i.e. the developer has exported translations from Launchpad and committed them in the code), whereas the other colours mean that they've either not been translated (red) or not yet integrated in the sources. If you are using automatic translation imports and exports from bzr branches in the same branch, you should probably see everythin11:40
dpmg green nearly always11:40
askhlGreen, really?11:41
askhlTransmission has its translations directly in Launchpad (no importing from upstream), and it seems to have lots of purple11:42
askhlAh, I was viewing only the Danish translation.  I can see that other languages have green and even blue bars also11:42
wgrantaskhl: The green strings are those that are unchanged from the last import or upload. Not necessarily upstream.11:43
askhlAh, okay.  I thought uploading was mostly for upstream-downstream traffic...11:44
dpmaskhl, it seems that Transmission is not using automatic bzr imports and exports, hence the comment on being "nearly always green" does not apply. The reason why they are purple is because translations have not yet been exported from Launchpad and integrated and committed in the sources11:46
askhlHmm.  That is alarming, as this is quite a while ago11:46
dpmaskhl, you might want to contact the Transmission devs to export translations, or even better, suggest them to use automatic bzr imports and exports, which will do that automatically for them11:47
askhlNonetheless, I observe that the Danish translation of Transmission is actually working.11:49
dpmaskhl, that's because Transmission is both open for translations on the upstream LP project and in Ubuntu. Ubuntu translations are put automatically in language packs, so that's why they are always used11:50
dpm(I'm assuming you're using Ubuntu)11:50
askhlOh, okay.  So the *crucial* piece of information here is that Ubuntu has its own downstream for projects translated in launchpad!11:50
dpmaskhl, if the upstream LP projects are also open for translation in Launchpad, yes.11:51
muelli_Heya :) https://launchpad.net/~ubuntu-bugs-auftrags-killer/+archive/muelli claims that my PPA is signed with a key, but http://ppa.launchpad.net/ubuntu-bugs-auftrags-killer/muelli/ubuntu/dists/karmic/Release.pgp does not exist. How can I get the repository signed?11:51
dpmaskhl, in the future, this might be more automated when translations are automatically shared between the Ubuntu source packages and the upstream projects in LP11:52
askhlSo let me get this straight: every translatable project in Ubuntu has a place in Launchpad where it can be translated.  This translation is imported from an upstream source which can be either outside of Launchpad or inside - in both cases these sources are 'outside' of Ubuntu, strictly speaking.11:53
askhl(I'm taking over as coordinator for the Danish translators of Ubuntu, so I really have to get these things straight)11:54
dpmaskhl: Yes, to be exact: in LP there is what we can call project space (where the translatable LP upstream projects are) and (Ubuntu) source package space (where the Ubuntu source packages are translatable). You might want to have a look at https://wiki.ubuntu.com/Translations/Upstream, since some of this applies there as well (you've made me realize I should add a section for projects where the upstream is LP)11:57
askhlAnyway, there's (I think) one more category of translations: how about entirely Ubuntu-specific things like the installation slideshow?  These exist only in Ubuntu, right?  That means they don't get synchronized from a source elsewhere in Launchpad11:57
dpmaskhl, do you know about the #ubuntu-translators channel? I think as the discussion is leaning towards Ubuntu translations, we could continue there11:58
askhldpm: I didn't know about that.  I will definitely be on that channel in the future11:58
askhldpm: I'll have to think things over for a bit, maybe I'll have other questions later.  Thanks for the very informative responses so far11:59
dpmaskhl, no worries, feel free to ask always. See you in #ubuntu-translators!12:00
noodles775muelli_: what does `gpg --list-keys| grep 2CD5CE3F` return?12:06
noodles775muelli_: hrm, weird that there is no Release.gpg there though... looking.12:08
wgrantmuelli_: Did you upload to the PPA very soon after its creation (a few minutes, maybe)?12:09
muelli_wgrant: hm. well. yes and no. I tried but I was rejected a couple of times ;-)12:10
muelli_shall I just delete and reupload it..?12:10
noodles775You'll need to bump the version (btw: I'd add a ppa suffix to your version too)12:11
* noodles775 finds help link12:11
wgrantmuelli_: You could even just delete and resurrect it (using the 'Copy packages' link)12:11
noodles775muelli_: for your next upload :) https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#Versioning12:13
muelli_noodles775: yep. thanks.12:14
=== matsubara-afk is now known as matsubara
muelli_wgrant: I reuploaded stuff (see https://launchpad.net/~ubuntu-bugs-auftrags-killer/+archive/muelli/+sourcepub/981665/+listing-archive-extra) but still there no Release.pgp: http://ppa.launchpad.net/ubuntu-bugs-auftrags-killer/muelli/ubuntu/dists/karmic/Release.pgp :-\12:32
bigjools.gpg not .pgp12:32
wgrantleonardr: Are you aware that the devel webservice is serving WADL with beta URLs?12:32
muelli_oh, it exists now.12:33
bigjoolsmuelli_: it takes time to generate the private key12:33
Zuswhen making a pgp key, i dont need to give  my password to anyone, nor will anyone see or need the password?12:33
leonardrwgrant: no, that's a problem. do the json resources serve the right urls?12:33
wgrantleonardr: Yes, which makes launchpadlib sad.12:33
bigjoolsmuelli_: but you constantly pasted a url ending in .pgp rather than .gpg so were you looking for the wrong file the whole time?12:34
muelli_bigjools: nope. I had a look at the directory listing as well :)12:34
bigjoolsok :)12:34
leonardrwgrant: ok, file a bug. i was about to say some part of the code was being lazy, but laziness would result in serving devel urls for beta, so i don't know what the problem is12:35
persiabigjools: We never caught each other last week.  What does your time look like this week for discussing native-source-syncing?12:35
bigjoolsmuelli_: 2 things need to happen in sequence: 1. the private key has to be generated, this takes time as it waits for entropy, 2.the next publisher run will write the file (up to 5 minutes later)12:35
wgrantleonardr: lazr.restful or -foundations?12:35
leonardrwgrant: lazr.restful. i'll change it if that's wrong12:36
bigjoolspersia: there's a release on Wednesday but I hope to be finished with preparations today so maybe tomorrow12:36
persiabigjools: Let's target Thurs/Fri again then.12:36
bigjoolspersia: ok12:36
persiaJust highlight me if you have time in the morning one of those days.12:37
wgrantleonardr: Bug #53000212:38
ubottuLaunchpad bug 530002 in lazr.restful "Launchpad edge 'devel' webservice serving 'beta' WADL" [Undecided,New] https://launchpad.net/bugs/53000212:38
muelli_everything works now as expected :) thanks. This PPA thing is nice btw! Still has some rough edges such as getting used to all the necessary packaging or actually activating it, but still, very convenient :)12:40
bigjoolsmuelli_: great!  let me know how you get on12:41
leonardrwgrant: it looks like a problem with launchpad, not lazr.restful12:46
wgrantleonardr: Is it keeping only one copy of the WADL?12:47
wgrantWhen I looked I could only see one.12:47
leonardrwgrant: oh, yes, that's something i still need to fix12:47
leonardri'll fix that today12:49
Zushow do i know  my key made it to the ubuntu seerver?13:08
matsubaraZus, you can check here: http://keyserver.ubuntu.com:11371/13:24
=== kfogel changed the topic of #launchpad to: http://launchpad.net | Launchpad read-only 22.00-23.30 UTC Wed 3 March for 10.02 rollout (http://is.gd/9rUhO) | Read https://help.launchpad.net for help | Recent problems browsing branches should be fixed. | Help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: see channel #launchpad-dev
=== matsubara changed the topic of #launchpad to: http://launchpad.net | Launchpad read-only 22.00-23.30 UTC Wed 3 March for 10.02 rollout (http://is.gd/9rUhO) | Read https://help.launchpad.net for help | Recent problems browsing branches should be fixed. | Help contact: matsubara | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: see channel #launchpad-dev
kangaroooTimeout error (Error ID:         OOPS-1521EB600)13:54
kangarooothats from trying search in edge. but from usual page also search error          (Error ID:         OOPS-1521A1135)13:54
=== matsubara is now known as matsubara-lunch
ChogyDanwhen I'm uploading to my ppa, it always threatens that the source package might be rejected on multiple uploads.  How can I take up that offer?  I am fixing packaging errors, so I don't need to upload the original source multiple times I would think14:54
jmlChogyDan, I don't know, sorrye14:57
jmlany bugs folk around?14:59
ChogyDanjml: no worries, it would end up being a convenience more than anything.14:59
jmlI'm looking at https://bugs.edge.launchpad.net/testresources/+bug/504092 and trying to figure out how to make the bug watch work14:59
ubottuLaunchpad bug 504092 in testresources "OptimisingTestSuite ignored by trial" [Wishlist,Triaged]14:59
bigjoolsChogyDan: you don't need to upload the orig tarball more than once15:10
persiajml: While you're waiting for a bug person, would you have time to talk about making branches from patches?15:10
ChogyDanbigjools: yes, but I don't know what I'm doing.  I just debuild -S -sa, and then dput.  The tools decide to to reupload the orig tarball.  I wish I knew how to ask it not to15:14
bigjoolsChogyDan: -sa forces inclusion of the source tarball, remove it15:15
bigjoolsin fact use -sd15:15
bigjoolswhich explicily tells it to only use the diff15:16
ChogyDanok, thanks.  Where can I look up what those switches do?  the debuild man page doesn't seem to document them15:16
jmlpersia, a little.15:16
jmlpersia, which part in particular?15:16
james_wChogyDan: dpkg-source manpage15:17
persiajml: Sorry.  Ran into a network issue.  Specifically, if there was current ongoing work to enable it, whether if work was done it was something you thought should be included, and if you had any pointers regarding possible blocking issues.15:29
jmlpersia, no work has been done yet.15:29
jmlpersia, or really work to enable it15:30
jmlpersia, afaict, it's just a matter of doing bzr branch trunk; bzr patch $PATCH_FILE; bzr ci -m "Turn $PATCH_FILE into a branch"; bzr push lp:~$USER/$PROJECT/$SENSIBLE_NAME15:32
jmlpersia, at least in the happy case15:32
persiaFrom what I'd heard from other sources, the sensible solution would be to have some job that ran against bugs, attempted to guess the right branch to target (usually whatever is defined as trunk, but good to have some way to add hints to handle stuff like patches against stable branches), grabbed the patch, applied it, either marked the bug to indicate that the patch would not apply or commited the branch and pushed it attached to the bug.15:33
jmlpersia, the unhappy case requires a way of storing and displaying errors, maybe allowing people to pick a non-trunk branch and some other things15:33
jmlpersia, yeah, that's right.15:33
persiaThe happy case is enough to start.  The unhappy case can be addressed as bugs to the happy case.15:33
jmlpersia, to me, it's not a super-complex thing, and would be great to do15:33
persiaWho would be the best person to talk to about detailed specifics?15:34
jmlpersia, it's also something that could be prototyped with relative ease outside of Launchpad.15:34
persiaMy ultimate target is Ubuntu, but I suspect that it's more sensible to target projects prior to distros.15:34
persiajml: So if something was written that used launchpadlib and bzrlib to just do it, that could be injected into the launchpad servers somewhere?15:35
jmlpersia, *probably*15:35
jmlpersia, that's how I'd do it.15:35
persiaOK.  Should such a thing be written to iterate over all bugs, or get calls on a per-project basis?15:36
jmlpersia, the main difference is that the external tool would need to store data about which patches it has tried & failed15:36
persiaAny reason not to use tags for that?15:36
* persia would prefer not to have external state15:36
jmlpersia, no technical reason15:37
jmlpersia, but we'd almost certainly not use them if we implemented this in LP proper.15:37
persiaThat subtly implies a social or aesthetic reason :)15:37
jmlpersia, aesthetic :)15:37
jmlpersia, well spotted, btw :)15:37
persiaHow would you store state if it was implemented in LP proper?15:37
jmlpersia, new columns in the DB15:37
persiaFor bug objects?15:38
jmlpersia, we'd want to store error messages so we could show them on the web ui15:38
jmlpersia, implementation detail!15:38
jmlpersia, wherever makes the most sense. maybe even a new table.15:38
jmlpersia, as for how...15:38
jmlpersia, the Right Way is to respond to the event of a new patch being attached to a bug15:39
persiaSo a hook into the patch submission, similar to how the patch-checking thing would work?15:39
persiaErr, patch-format-checking15:40
jmlpersia, yeah.15:40
jmlpersia, you can't do that (yet!) as an external client15:40
jmlstatik, how's that webhooks thing going?15:40
persiaThat's fine.  It was never likely to be implemented as an external client anyway :)15:40
jmlpersia, but you could do a similar thing with a query that looks for new or changed patches since the last run of the script15:41
persiaBut I think I have enough detail to write something up for design, etc.15:41
persiajml: That's less elegant, really.15:41
jmlpersia, yes. events are great. polling is bad.15:41
persiaUm, well, depends, but in this case, yes.15:41
jmlpersia, thumper and deryck are the relevant app leads. kfogel & adeuring have had their heads buried in the patch code recently15:41
=== salgado is now known as salgado-lunch
jmlpersia, almost always, IMHO.15:42
persiajml: heisenberg: observation can sometimes change events.  By polling, one can trigger, etc.  It's a rare case it's useful, but ...15:42
jmlI admit that exceptions to the rule might exist.15:42
jmlpersia, good point.15:42
persiajml: Thanks for all the pointers.  I'll go chase stuff and document stuff and oke the relevant folks for review along the way.15:43
jmlpersia, my pleasure.15:45
deryckpersia, hi.  yes, feel free to poke me about it as you work on it.  I would be very happy to see this work done.15:45
deryckjml, did you get your bug watch question answered or worked out?15:45
jmlderyck, not at all.15:45
jmlderyck, there are a few things that are confusing. I guess I should file them as bugs.15:46
deryckjml, yeah, it's not intuitive at all.15:46
jmlderyck, would it be helpful if I list the non-intuitive bits?15:47
persiaAre bugs about AJAX race conditions useful, or an inherent limitation of the medium?15:47
jmlderyck, anyway, separately from that, I have no idea what to do to get more information and fix the "Launchpad couldn't connect to Twisted Bug Tracker." error15:50
jmlpersia, no idea.15:50
jmlpersia, also, fwiw, conversations like the one we had are prime fodder for #launchpad-dev15:50
persiajml: Thanks, but I hadn't meant to target you with that question :)15:50
persiajml: It was more in-depth than I had expected, but yes, I'll be going there with more depth.15:51
jml(which I personally think should be merged with this channel)15:51
persiaDoesn't scale as the number of developers grows.15:51
persiaAt least for other areas in which I do things, it's helpful to separate things.15:52
deryckjml, ping allenap when he's available about the twisted tracker issue.  he's working on all this.15:52
jmlderyck, will do.15:52
deryckjml, and I think just file bugs about the non-intuitive bits.15:52
jmlderyck, ok.15:52
jmlpersia, I think we're below that point now.15:52
deryckjml, but the main problem is that we think about "bug watches" too much.  The "this is a bug in something else" workflow just needs changing.  what's all this affects mess? ;)15:52
persiajml: I'd agree :)15:52
jmlderyck, +115:53
persiaderyck: A recipe for complaints related to bug #20498015:54
ubottuLaunchpad bug 204980 in malone "bug contacts should be able to unsubscribe from implicit subscriptions" [High,Triaged] https://launchpad.net/bugs/20498015:54
deryckpersia, not sure I follow what you mean15:54
persiaderyck: I think that "Also affects ..." encourages creation of bugs that are actually collections of bugs and lead to the complaints related to 204980.15:55
persiaImplementing a fix for 204980 is really working around a problem with the workflow design.15:56
deryckpersia, maybe so.  I think the actual bug there is different.  But I agree that one impacts the other.15:56
persiaWell, sure.  I just think the importance of 204980 would be much lower were the workflow changed.15:57
deryckah, right.  maybe so.15:57
persiaRight now I probably get a complaint about how Ubuntu is spamming someone twice a week.  I suspect people with wider profiles get them more.15:58
persiaWIth a fixed workflow, it ought only be annoying for a few folk.15:58
persiaAlso reduces training effort :)15:58
persiaBut that's just supporting arguments for your initial contention.  Good luck :)15:59
deryckthanks! :-)16:01
idnarwhat happened to bzr-autoreview?16:03
=== deryck is now known as deryck[lunch]
=== beuno is now known as beuno-lunch
=== matsubara-lunch is now known as matsubara
statikjml, i haven't had a moment to breath to work on the webhooks thing, i need to write it up and post it to launchpad-dev16:24
=== kfogel is now known as kfogel-loonch
=== yofel_ is now known as yofel
=== deryck[lunch] is now known as deryck
=== beuno-lunch is now known as beuno
=== salgado-lunch is now known as salgado
=== kfogel-loonch is now known as kfogel
=== dpm is now known as dpm-afk
=== danilos is now known as daniloff
floweris it possible to 'track' an certain ppa repo, via feeds for example?18:27
beunoflower, no, but that sounds like a great feature request18:30
floweryeah, then this is a feature request!! :)18:31
beunoflower, it's not official until you file a bug!18:34
beunoflower, https://bugs.edge.launchpad.net/launchpad/+filebug18:36
=== EdwinGrubbs is now known as Edwin-lunch
matsubaraflower, beuno: bug 20064318:46
ubottuLaunchpad bug 200643 in soyuz "PPA subscription/feed" [Low,Triaged] https://launchpad.net/bugs/20064318:46
=== matsubara is now known as matsubara-afk
=== Edwin-lunch is now known as EdwinGrubbs
=== matsubara-afk is now known as matsubara
=== dpm-afk is now known as dpm
hggdhis there a minimum size for GPG keys in LP? Like 1024?20:59
wgranthggdh: It appears not.21:04
hggdhhum. I have an user trying to import his GPG key, and failing... will check more21:05
hggdhthank you, wgrant21:05
hggdhno, just tried the fingerprint the user has, it fails to import21:06
kris928hey has anyone here ever had an issue with ubuntu destroying the daily AMIs and loosing the ramdisk / kernel from your own derived builds?21:18
=== salgado is now known as salgado-afk
=== huayra_ is now known as hubuntu
=== hubuntu is now known as huayra
=== kfogel changed the topic of #launchpad to: http://launchpad.net | Launchpad read-only 23.00 UTC Wed 3 March - 00:30 UTC Thu 4 March, for 10.02 rollout (http://is.gd/9tVfU) | Read https://help.launchpad.net for help | Recent problems browsing branches should be fixed. | Help contact: matsubara | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: see channel
=== matsubara changed the topic of #launchpad to: http://launchpad.net | Launchpad read-only 23.00 UTC Wed 3 March - 00:30 UTC Thu 4 March, for 10.02 rollout (http://is.gd/9tVfU) | Read https://help.launchpad.net for help | Recent problems browsing branches should be fixed. | Help contact: -- | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: see channel
=== matsubara is now known as matsubara-afk
=== jamalta is now known as jamalta-afk

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