[00:01] no i can't, because when i want to log in /register, it's the same page "sorry you dont have the permission"... beuno [00:02] Any idea on why LP has been forking up errors left and right for a few days now? [00:02] i don' t find the page where i can to log in ... [00:02] possible ! [00:04] 5 days ago, i can't acces to shipit...now, i can't log in...^^ [00:05] ArtiShow, try clearing your cookies [00:06] you think ?? [00:09] i already request a cd but it's the first time i can't log in, i don' t think it's a opera cookies problem (sorry for my bad english language ^^) [00:16] no idea... [00:20] Launchpad down? [00:21] Hmm [00:21] Refresh worked [00:22] MattJ: Was it a 'Please try again'? [00:24] wgrant: Something about not being able to connect to a server [00:24] and it said try again in a few minutes I think [00:24] spm: ^^ [00:24] yeah i saw... ta [00:25] Are we renaming Launchpad to Launchbounce as well, now? [00:25] codebounce has stopped bouncing, mostly! [00:25] do the bounce bounce baby [00:25] i guess this is conservation of bouncyness, or something [00:25] mwhudson: Heh. [00:26] My main complaint about the new Loggerhead is that it won't even show a revision diff if there's only one file involved. [00:26] I still have to expand it manually :( [00:26] wgrant: "Are we renaming Launchpad to Launchbounce?" ask me this arvo... [00:26] wgrant: yeah, that's a bit cruddy [00:27] wgrant: file a bug, maybe [00:27] mwhudson: Will do. [00:27] (on loggerhead) [00:27] Of course. [00:27] i would like some way of computing how large a diff is going to be without having to compute it :) [00:27] (which is sadly impossible, i think) [00:28] That would be nice, yes. [00:29] part of the motivation for the change to closed by default is not wanting to DOS the user's browser [00:29] but the 1 file case, at least, is probably safe [00:30] Yep. [00:30] For multiple files it's fine to have them closed by default. [00:56] I wonder if the i386 virtual build queue is going to exceed 1000 builds today. [00:57] Holy S***.... 903 queued for i386 [00:57] Yep. [00:57] This getting beyond stupid. [00:58] What makes it worse is that there's no build success notification. [00:59] * wgrant wanders of to uni, thankful that he hasn't yet moved his production application archive to a PPA yet. [01:04] Wtf is up with the LP server? [01:04] (s) [01:43] okay, i'd like to rename a project and a team in launchpad. i understand that I need an admin to do this. what's the process? [01:45] spm: ^ [01:45] kirkland: raise a question against launchpad. https://answers.launchpad.net/launchpad/ is also to assist us with verifying that the person asking should be asking. if it's urgent, ping me back when done and I can make it so [01:46] kirkland: in general though, ask a Question [01:46] spm: lifeless: perfect, thanks. [01:50] https://answers.edge.launchpad.net/launchpad/+question/70094 [01:51] spm: it's not urgent, but it would be nice if it happened this week [01:59] kirkland: so ... by this week you mean "next 20 minutes?" ;-) [01:59] spm: :-) no [01:59] spm: by friday? [02:02] Hellow: lp is working for me... is it ok for you now? [02:04] kirkland: you haven't, yet, used that team mailing list? [02:05] spm: nope, it's empty [02:05] cool - need to blow it away for a team reanme - or manually migrate (yuk - in case you were wondering) [02:06] spm: nah, i don't really need the mailing list, and the archives are empty [02:06] spm: gotcha [02:09] kirkland: is done. note that PPA's don't migrate - I can rename the dir on germanium - or you can leave the old in situ, and create new. your call? [02:09] spm: hmm, what do you recommend? [02:09] spm: i think just leave it? [02:10] I'd leave in situ and create new - tbh. as you're doing such a major name change. I've aliased the old project name, so folks should find the new. just update the new ppa location? [02:10] spm: excellent, that sounds good === matsubara is now known as matsubara-afk === Snova_ is now known as Snova [03:23] Is it possible to change the URL for a project? I can change the project's name, but that doesn't update the URL. [03:29] jmillikin: Yes, but you personally can't do that. You need to submit a question requesting the change here: https://answers.launchpad.net/launchpad/ [03:30] spm: Thanks, will do. === Hellow_ is now known as Hellow [04:08] updates yesterday killed my networking and wireless networking... Any Ideas? Please respond with all_is_fair first [04:08] all_is_fair: wrong channel [04:08] please send me to the right channel [04:09] there are no users in the #ubuntu channel [04:09] I don't get it [04:10] all_is_fair: i see about 1400 users in that channel [04:10] the #ubuntu channel is the right place [04:11] I'm like the only user when I enter that channel?? [04:11] all_is_fair: See the topic. [04:11] all_is_fair: are you in there now? [04:12] Gah, never mind me. === verterok_ is now known as verterok === nhandler_ is now known as nhandler [05:17] spm, Re: pkg-games vs. pkg-games-devel: what options are there towards merging. I'm not sure I understand LP well enough to understand the nature of the issue. [05:18] persia: basically we can't merge a person into a team. AIUI you want the final team to have both email addresses tho? [05:19] Well, it's more that I want to concentrate branding in one place. The "person" actually represents a team. [05:19] heh. yeah I could see that - totally threw me when it oopsed :-) [05:20] So, I want to be able to have group-type access to resources (e.g. PPA, branches), and also have that group have the "Maintained Packages" list. [05:20] I'm not sure what options are available to do that. [05:22] well the pkg-games team can have all that. ahh I see the problem: https://edge.launchpad.net/~pkg-games-devel/+related-software [05:22] That's the obvious issue. The other is "contact this user" on uploads. [05:22] * spm nods [05:23] And there's a host of related social issues, but I think those two are the main ones specifically related to LP interface. [05:25] hmm. I'll throw this to the LP dev list and see if they have any ideas. i suspect we'll need to do something like convert the 'person' into a team and then merge. But how, if even possible... [05:26] I suspect it's part of a general class of issues: due to the way that "people" are imported, I suspect every Debian team has such a pseudo-user. [05:26] As long as the team doesn't want to use PPAs for special awkward backports, or use a shared code repo, this doesn't matter. [05:27] On the other hand, where the team is more closely integrated with Ubuntu, the semantics get odd. [05:56] Is there an admin here who would be able to rescore a PPA build for me? [05:56] It failed, so I fixed the dependency issue and asked for a retry, but that means the build score is zero [05:56] With the current contention for builders, it'll never manage to get to the top of the queue [05:56] https://launchpad.net/~mercurial-stable-snapshots/+archive/staging/+build/987742 is the build [06:02] won't its score go up as it ages? [06:03] I don't think scores work like that [06:05] how do you think they work ? [06:09] I think scores are assigned statically at build record creation time according to a formula involving component, pocket, urgency, etc. - and are reset to zero for a retried build [06:10] Hi, by the way :-) [06:10] We meet again, a long way from cygsetup :-) [06:11] hi :) [06:11] yup, the internet is a small small world [06:11] I'm reasonably sure delay is factored in to prevent starvation [06:11] I'm not quite sure that is implemented [06:12] spm: hey again... looks like http://launchpad.net/screen-profiles is redirecting properly, but not http://launchpad.net/~screen-profiles [06:12] spm: is it possible to have the team one redirect to? [06:12] too? [06:13] maxb - https://bugs.edge.launchpad.net/soyuz/+bug/1942654 [06:13] Error: bug 1942654 not found [06:13] maxb - https://bugs.edge.launchpad.net/soyuz/+bug/194265 [06:13] Ubuntu bug 194265 in soyuz "Page for build doesn't say where in the queue it is" [Low,Triaged] [06:15] I'm not sure what I'm supposed to learn from that bug? [06:17] that you are suffering a common confusion [06:17] oh no, I'm not confused :-) [06:18] IIRC the internals correctly the way it works is that score is a component in the queueing process but not the only one [06:18] that is, you don't need to rescore to ensure the build will happen [06:18] only to make it happen faster [06:18] anyhow, a sysadmin will be around in ~ 30 or so [06:19] My understanding based on observation is that the build will happen, but only after the queue is empty of builds with higher scores [06:20] I don't think any soyuz devs are on right now [06:20] or we could check ;) [06:20] My build isn't going anywhere, it can wait :-) [06:42] kirkland: yeah - to the best of my knowledge and searching there is no team alias - or if there is, it's well hidden in the UI :-/ [07:01] maxb: The build score does increase over time, but the others do too. The point of the build score is to determine the ordering, so it would make sense that it only builds once those builds with higher scores have built. [07:02] It's probably not optimal that a retry starts at 0, particularly as one can DoS the buildds equally well just by making lots of uploads. [07:02] (that is, if they need any help to be DoSed, which they certainly don't at the moment) [07:03] Hmm. Is the time-based adjustment visible in the UI? [07:03] Yes. [07:04] Oh. I seem to have only ever seen a small set of specific score numbers [07:05] At least, it used to be... I haven't paid attention for a while. [07:06] Unless the time based factor is extreme, it's going to take ages for a zero-based retry to get up to the several thousand of a normal build [07:06] Right. [07:06] So in the current build queue climate, a retried build will probably never get built. [07:07] * maxb will continue to lurk and wait for an admin [07:11] I'd just leave it there, go to an all-night concert and come back :P [07:12] scores can be edited? [07:13] By ~(launchpad-buildd-)admins, yes. [07:14] maxb: I suppose you already have, but why don't you ask on answers.l.n ? :) [07:16] wgrant might also be able to edit them if he's discovered a vulnerability and not reported it [07:17] jamesh: I've reported all of the vulnerabilities I've discovered, actually. [07:17] thank you :) [07:17] All except the one particularly ironic one was fixed pretty quickly. [07:17] That one's still not fixed :( [07:18] Although it's not close to the criticality of the others. [07:18] I think the biggest security vulnerability I discovered in Launchpad was the librarian [07:18] so how is the build score formed? square root of what attributes? :) [07:18] we fixed that by moving it to its own domain [07:19] jamesh: Yes, that would have been a nasty one. [07:19] iirc, the equivalent problem still exists in bugzilla [07:19] savvas: A combination of pocket, component, archive, urgency, section (IIRC), and magic dust. [07:20] I should probably go hunting for more vulnerabilities at some point, given my prior horrifying successes. [07:21] hm.. [07:22] did anyone notice a wishlist bug to distribute the "all" architecture packages to be built on an available machine and not to wait for i386? [07:22] savvas: Yes. But it wasn't well taken. [07:22] But an alternative should be happening soon - pooling the i386, amd64 and lpia buildds. [07:23] So each of those three archs will be able to build on three times as many machines. [07:23] Which includes arch-indep builds. [07:23] ah ok [07:24] I suppose they replied in a similar way as in bug 350760 ?:P [07:24] Launchpad bug 350760 in rosetta "+products-with-translations shows only products with upstream translations" [Undecided,Won't fix] https://launchpad.net/bugs/350760 [07:35] jamesh: oh? I've always wondered why the librarian was on its own domain? [07:36] maxb: it used to be on librarian.launchpad.net. Your session cookie is sent to all https *.launchpad.net sites. [07:36] you can upload text/html attachments for bugs to the librarian [07:36] html documents can contain javascript that can read cookies [07:36] Oh! [07:37] it's even worse for bugzilla, since the attachments get served from the same domain [07:37] you can load up any form you want in an iframe read its DOM, make changes and submit [07:38] Fortunately Bugzilla doesn't store private code, or have access to push code out to millions of machines. [07:38] and there is nothing XSRF protection can do about it [07:39] so you could e.g. write an attachment that searches for all security bugs the user has access to and subscribe a third party account to each. [10:04] Launchpad is the only website I primarily navigate by typing full URLs straight into my browser :-) [10:04] lol, it's so much more than just a website though. [10:06] maxb: we're going to do quite a lot of work on improving navigation for v3.0 and even more after that [10:06] we know it's a bit painful right now. if you have suggestions on how to improve it, by all means, file bugs [10:07] hello [10:07] intellectronica: actually, I'd like to navigate to bugs typing in a full url, but that is harder than I'd like. [10:08] LarstiQ: please exaplin [10:08] I just made a new hosted branch without a project name (so it ended up in +junk) and changed the project to something (bzr) a moment later. Now I have invisible, working branch at +junk and visible, unusable, empty branch at /bzr/; See: https://code.launchpad.net/~zkrynicki/bzr/bzr-logsearch and https://code.launchpad.net/~zkrynicki/+junk/bzr-logsearch [10:09] mwhudson, jml: shouldn't that change have been handled nicely? [10:09] intellectronica: I'd like to have something akin to 'bugs.debian.org/12345'. I know there is a longer url that works for launchpad irregardless of the project a bug is under, but I always fail to get it right. [10:10] intellectronica: ah, bugs.launchpad.net/bugs/ [10:10] * LarstiQ tried +bug and +bugs first [10:10] LarstiQ: launchpad.net/bugs/12345 [10:10] oh and I did push to /bzr/ using: bzr push lp:~zkrynicki/+junk/bzr-logsearch --use-existing-dir [10:11] intellectronica: thanks! [10:34] hello [10:35] I've a small question, how it is computed the Build Score I see in my PPA about a build? [10:35] and what does it mean? [10:35] This question is coming up a bit lately. [10:35] Maybe cprov can give a real answer. [10:36] this is quite urgent, I have it for weeks, I just thought I could come here to see you and ask :) [10:36] +not quite urgent [10:36] :) [10:36] uhm, I'm preparing a description for that with mrevell, should be done soon, but I can explain that quickly. [10:36] crevette: cprov said a while ago 'messy heuristic on the build archive (PPA, PRIMARY, PARTNER), source component, urgency and age in queue (basically)' [10:36] Ah, here he is. even better. [10:37] hey cprov, let's have a call about that today, if you have time [10:37] Although the pocket is in there somewhere too. [10:37] mrevell: sure [10:38] wgrant: yes, pockets are prioritized in this order: SECURITY, UPDATES, RELEASE, BACKPORTS and PROPOSED. [10:38] wgrant: but that's about to change based on https://bugs.edge.launchpad.net/soyuz/+bug/372491 [10:38] Ubuntu bug 372491 in soyuz "proposed packages have lower build priority than build packages" [Medium,Triaged] [10:38] cprov: I just saw that you'd revealed that table in a bug. [10:38] I guess build score is a kind of priority to prioritize ubuntu build vs PPA ? [10:38] Right, I read that bugmail about a minute ago. [10:38] crevette: It's the number used to order the builds. [10:38] crevette: PPA and ubuntu builds are already isolated, since they build in different farms [10:39] crevette: it's used for prioritizing builds within those 2 domains [10:39] ahokay, I don't know the launchpad platform at all, I just use it as reporter and builder [10:40] Ooh, London is awake, and today is Wednesday. Do we get buildds soon? [10:40] :) [10:41] hopefully yes, the PPA build ETA is getting more and more embarrassing each day. [10:41] And it has been 2.5 weeks. [10:43] wgrant, you said (PPA, PRIMARY, PARTNER) earlier, so it means canonical sells build time to companies ? [10:43] crevette: I was quoting cprov, but: PPA is obvious, PRIMARY is the Ubuntu archive, and PARTNER is Canonical's partner archive (archive.canonical.com) [10:44] But I'd imagine that Canonical partners can probably purchase private PPAs to use. [10:44] I don't know, though. [10:45] wgrant: that's right, the support comes as a 'package', when you buy a P3A (storage, build time, privacy, etc) [10:52] cprov: Is the build queue disaster going to happen again next release? I've been considering replacing the repository we use for deployments with a PPA, but 16+ hour build queue times make that a bit awkward. [10:53] wgrant: if we continue with the same number of builders, yes, it will happen again. But we are discussing how we can keep more builders working full time in PPA farm. [10:54] wgrant: so, it will not happen in the mid-term. [10:54] cprov: OK, thanks. === henninge_ is now known as henninge === mrevell changed the topic of #launchpad to: https://launchpad.net/ | Help contact: - | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com | karma count change: http://blog.launchpad.net/general/karma-where-did-mine-go [11:12] intellectronica: I'm not actually sure whether my comment was a complaint about the navigation, or a compliment about the URL format :-) [11:12] To be fair, half the time, I don't actually have a launchpad page open in my browser at the time [11:13] And it's become habit to use the address bar whether I do or not! [11:13] I don't think you can improve navigation for the Launchpad users who have learnt to use URLs. [11:13] It's just so much more efficient. [11:13] maxb: yes, the URLs are really clean and logical. i do think the navigation links can be improved a lot [11:14] I like SF.net's bug URLs. [11:14] wgrant: sounds like a very good benchmark to me! [11:14] I don't like SF.net :-) What does a SF.net bug url look like? [11:14] wgrant: i mean improving navigation for users already comfortable with the URLs, not matching SF's, which i don't like at all [11:15] maxb: It has .php in it, and you need to put in the query string two numbers which you can't find anywhere except in those links. [11:15] maxb: It's awful. [11:15] ah.... like :-) [11:15] Yes. [11:15] It's impossible to do better than Launchpad's bug URLs. [11:17] well... it's slightly unintuitive that bugs.launchpad.net/NUMBER doesn't work [11:17] True. [11:17] But I just launchpad.net/bugs/NUMBER, which is the same number of characters. [11:18] Sure. And it makes perfect sense that bugs.launchpad.net/NUMBER doesn't work, once you've started to see the design shining through [11:18] Well, I actually just say 'bug 1234' and the template bookmark picks it up. [11:18] Launchpad bug 1234 in launchpad-foundations "Gina is an unmaintainable mess of command line options, environment variables and shell scripts" [Medium,Fix released] https://launchpad.net/bugs/1234 [11:18] after all, there's no launchpad entity called NUMBER [11:18] maxb: what lots of people do is define a url template in firefox for bugs [11:18] Right. [11:19] heh [11:19] Poor bug 1234 gets such abuse on staging. [11:22] What is a firefox url template? [11:22] maxb: You can define a bookmark, give it a name, and put a %s somewhere in the URL. [11:22] You then type ' ', and it will call that bookmark replacing the %s with the argument. [11:24] s/name/keyword/ [11:26] Thats... amazingly useful [11:27] and completely unintuitive :-) [11:27] Yep. [11:29] They seem to be formally called "keyword bookmarks" === deryck changed the topic of #launchpad to: https://launchpad.net/ | Help contact: deryck | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com | karma count change: http://blog.launchpad.net/general/karma-where-did-mine-go [11:32] * wgrant plots nasty questions for deryck's first CHR day. [11:32] hello, all. I'm community help for the day, but it's my first day at community help. :) [11:33] deryck: the first rule of CHR is: ignore wgrant. the second rule of CHR is: ignore wgrant. [11:33] haha, harsh elmo :) [11:33] he started it :-P [11:33] (and he knows I'm joking) [11:34] That I do! [11:34] * deryck notes the rules [11:35] elmo: Although a year ago you would probably have been quite serious. [11:42] deryck: good luck! [11:42] thanks rowinggolfer_! [12:30] OMG! Additional servers! [12:35] Including one I've never seen before. [12:37] Although it was around for a few days before they were all stolen, it seems. [12:40] hello. i've tried to upload in ppa package with new upstream version, but i've got error (File already exists in ...); i've read https://help.launchpad.net/Packaging/UploadErrors and it says, that "This mean you have uploaded a file that already exists in the pointed 'LOCATION'", but - in my ppa (which i points) there is no orig.tar.gz for new upstream version, which i try to upload. I will be very appreciate for any ideas or clues ab [12:40] out this. [12:41] ia: try using dput with the -f flag [12:43] ia: Is that in the email you get back, or on the commandline? [12:43] wgrant: in email [12:43] ia: OK, so ripps' isn't the solution... hmm. Can you give the actual error message, and the URL to your PPA? [12:44] Yeah, I get that email when I botch an upload. If a build hasn't been attempted yet, than dput -f usually works [12:44] That's a rejection message, so there won't be a build for it. [12:45] wgrant: I ge that email when I upload a package with debuild -s -sd with making an upload with debuild -S -sa. It's expecting an orig.tar. [12:45] ^without [12:47] The solutin: debuild -S -sa && dput -f [12:48] ripps: You shouldn't get that message. You should get something like the opposite of it. [12:48] ripps, wgrant: where did you notice the new servers? [12:49] ia: Which is your PPA, and what was the exact text of the message? [12:49] https://edge.launchpad.net/builders [12:49] LarstiQ: Buildds, at https://launchpad.net/builders [12:49] woot! 7 i386 builders now [12:49] Blah, 5 last time I looked. [12:49] ah, and you knew the makeup before :) [12:51] Well, there's no longer woefully few. [12:51] So it's pretty obvious. [12:51] wgrant: well, look. here my ppa for git stuff - https://launchpad.net/~iaz/+archive/git ; look at package gitg - gtk frontend for git commands. in my ppa - only 0.0.1 version (and there is orig.tar.gz only for this version). so, i've tried to upload new upstream version - 0.0.3, and i get error via email - "File gitg_0.0.3.orig.tar.gz already exists in Primary Archive for Ubuntu, but uploaded version has different contents." [12:51] wgrant: I hadn't seen that page before. [12:51] ia: The Primary Archive is the real Ubuntu archive. [12:51] LarstiQ: It is well hidden. [12:52] wgrant: oh, i see - https://launchpad.net/ubuntu/+source/gitg :-) [12:52] * VK7HSE I too could do with a little more training in this field! as I've struck this a few times :-/ [12:52] cprov: I know PPAs are meant to look up the orig.tar.gz in the PRIMARY archive if it's missing, but should it really reject because a different one was uploaded? [12:53] wgrant: yes, otherwise the lookup will not work as expected in the next attempt. [12:53] cprov: Mmmm, true. [12:54] ia: So, yes, you should probably just use the Ubuntu one. [12:54] ia: And work out how you managed to get the same file with a different hash. [12:54] typically when I'm building an upstream source package, I use the vcs version in the orig.tar and changelog. (0.18.1+git090504), the package is called package_0.18.1+git090504 and the orig.tar is a called package_0.18.1+git090504.orig.tar.gz [12:54] wgrant: it's almost always caused by re-compressing it (gzip has timestamps in its header) [12:54] ripps: If it's a VCS snapshot, sure. [12:55] cprov: I'm aware, but I wonder why that would have been recompressed. [12:55] Unless it was a bz2 to start with, which some upstreams unfortunately do. [12:55] wgrant: righto [12:58] Woot! 9 i386 [13:00] sandpaperfig went away :( [13:00] Super-cprov will need to rescue those poor trapped builds :( [13:02] Back to 7 i386... [13:02] Maybe they're just teasing us. [13:03] We're gonna need 15 if we're gonna burn through all ~900 packages in a decent amount of time [13:05] And down to 6. [13:13] 4! [13:13] wgrant: down to 4, [13:13] They were just teasing. [13:13] Nice timing. [13:14] wgrant: I don't know what's going on, but they will eventually settle. [13:14] wgrant: they become immediately available, I don't have to do anything. [13:15] cprov: Oh, right, that automatic rescuing code landed last cycle? [13:15] wgrant: yes, the code for rescuing jobs assigned to unavailable builders ... [13:15] Hm, no, sandpaperfig retains a build although it has been deactivated for at least 15 minutes. [13:16] wgrant: builders from ubuntu-enablements become available by a external mechanism. [13:18] cprov: I said that you would have to rescue the trapped builds, not the builders. [13:19] oh, right, but even that isn't working 100 %, see sandpaperfig ... [13:20] cprov: Right. I initially forgot that code had landed, then remembered, but then noticed that it wasn't working. That rapid set of realisations confused things. === cjwatson_ is now known as cjwatson [13:24] wgrant: it doesn't work when builders are in "manual" [13:24] cprov: Ahh. [13:24] I was wondering why it wasn't showing up as deactivated. [13:24] wgrant: but the fact is that after this code change builders don't need to be put in manual before going anymore [13:25] The status doesn't seem to be shown anywhere any more. [13:25] Right. [13:28] What does "enablement" mean, anyway? [13:29] Saturating bandwidth, by the sound of things... [13:29] Or just trying to fit in an inappropriately marketing-like word. [13:33] So, the buildds do seem to have at least settled now. To just two more than previously, though, with one of them being on the architecture that wasn't actually problematic. [13:41] Hmm. Well, it's shaved a couple of hours off my estimated time-to-build, but that's not going to empty the queue any time soon [13:41] No, the queue is still getting deeper. [13:42] hi all : haw can i make LP identify me automatically with bzr [13:43] * wgrant pokes deryck [13:45] MaWaLe, take a look at `bzr help launchpad` or `bzr help launchpad-login` [13:46] deryck: thx for your reply : i'll see where? google or LP Help? [13:47] MaWaLe, run that via a command line to read the bzr help info on those topics. [13:48] MaWaLe, but basically, running this for me -- bzr launchpad-login deryck -- will tell bzr about me on launchpad, where deryck is my user id on launchpad. [13:48] MaWaLe, is that what you are asking, how to use bzr with your lp login? [13:49] deryck: i want to know how to make LP handle my commitment with bzr [13:49] sorry for my poor english [13:50] i explain : [13:50] i want to make bzr connect to LP with my LP account to make it handle my karma :) [13:51] MaWaLe, so you want to push your bzr branches to lp? === mrevell is now known as mrevell-lunch [13:51] yup :) [13:52] MaWaLe: Or do you want to set the name on your commits, so that LP knows it's you? [13:52] MaWaLe, see https://help.launchpad.net/Code/UploadingABranch. [13:52] wgrant: you've got it ;) [13:53] MaWaLe: bzr whoami "Your Name " [13:53] The critical bit is the email address - that has to match one of yours on Launchpad, or you won't get the karma or other attribution. [13:53] i made it but it didn't affect my karma? [13:53] The name doesn't really matter. [13:53] Right, it will only affect commits made after you've set it. [13:54] Only the new revisions will use that as their commiter. [13:55] thx guys [13:56] there isn't a way to have LP offline on a test machine to practice oflline? [13:57] MaWaLe: You don't need LP to use bzr. [13:58] i know wgrant === abentley1 is now known as abentley [13:58] in fact i'm a member of the Tunsian LoCo Team [13:58] and we will reorganize our LP pages and affiliations [13:59] so i want to manage a complete tutorial for our community and maybe have an offline test machine for practicing [13:59] MaWaLe: In that case, try staging.launchpad.net - it uses a copy of the normal database that is overwritten every night, so it's safe to play around on. It also doesn't send email, so you can try things without spamming people. [14:00] wgrant: when i try it on some page it didn't have the same effect as the real one [14:00] commitment between team and projects didn't always have the same effect [14:00] i don't know if i'am explaining clearly my thoughts [14:01] MaWaLe: Everything except email should be just the same on staging. [14:01] But I don't quite understand what you mean, right. === salgado-afk is now known as salgado [14:01] there isn't a fr channel for LP :p [14:04] bzr help launchpad [14:27] how to make bzr automatically sign all my commitment to LP? [14:28] bzr whoami "your name " [14:28] IIRC [14:30] rowinggolfer_: thx wgrant showed me that [14:30] but i'm asking for pgp signing of the commitment [14:30] oh, sorry. === deadoomik is now known as deadoomik|away [14:30] rowinggolfer_, MaWaLe: no, that just sets your email. if you want to sign all your commits you have to add `check_signatures = require` to your configuration, iirc [14:31] so intellectronica, what should i do? [14:32] MaWaLe: add `check_signatures = require` to your configuration, like i said above ;) [14:33] intellectronica: thx i see it :) === asac_ is now known as asac [14:34] intellectronica: and which file may i edit to add this directive? [14:35] MaWaLe: either bazaar.conf or locations.conf, depending on whether you want to set it globally or only for some locations [14:35] intellectronica: globally [14:37] MaWaLe: so, bazaar.conf [14:37] thx intellectronica [14:37] MaWaLe: a lot of this information is readily available in the bazaar documentation. you should have a look. there are many really nice configuration options [14:38] intellectronica: there isn't a french complete documentation for managing bzr with LP? [14:38] i'm more efficient with french :) [14:39] j'ne sais pas [14:39]