=== Verterok|out is now known as Verterok === kiko is now known as kiko-zzz === Rinchen changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com [01:07] she's away for a bit [01:13] but ask Rinchen and me cuz after all we have no life [01:13] Launchpad IS life [01:13] well, that too [01:21] * wgrant wonders how the Freeing roadmap is. [01:22] it's long [01:23] and full of fucking problems [01:23] luckily WE PERSEVERE [01:24] it probably drives poor kiko to drink [01:24] ajmitch: so, based on my day-to-day experience, it drives kiko to _work_ [01:24] oh dear [01:28] kiko-zzz: Oh dear. Big problems? [01:28] (you're sleep-IRCing again. Bad kiko) [01:31] wgrant, nothing insurmountable. just some hard decisions and then Work. [01:32] need to figure out what to do with some of the blocks so they don't conflict with customer requirements [01:32] get rid of some other proprietary bits we can't redistribute in the tree [01:32] I will release a roadmap later this month [01:32] I wondered if there would be bits like that. [01:33] Release as in to us mere mortals? [01:37] I still don't see any new events on my trac due to its linkage with launchpad. [01:37] http://allmydata.org/trac/tahoe [01:37] Also, everyone please download Tahoe and try it out. It is a secure distributed p2p filesystem. [01:37] Won't it only do things if bugs have been linked? [01:37] It's awesome. [01:38] So, then please report some bugs in Tahoe, using launchpad, and see what happens. ;-) [01:38] The pycon talk about it was certainly awesome. [01:42] Glad you liked it! [01:42] That talk was Brian Warner's doing. [01:42] I'm about to give a talk of my own: http://allmydata.org/~zooko/lafs.pdf [01:42] away I go to family time [02:06] Ok, so I'm building a package which build-depends on a package that's already in my PPA, but it's saying it can't find it [02:06] so I guess I'm doing something wrong [02:08] radix: Are the binaries in your PPA as well as the source? Other than that, it's hard to guess what might be the issue. Maybe a versioned dependency? [02:08] persia: yes, libglktermw-dev built successfully, then I uploaded glulxe, and it couldn't find it [02:08] my log is at http://launchpadlibrarian.net/18146684/buildlog_ubuntu-hardy-i386.glulxe_043-0ubuntu1_MANUALDEPWAIT.txt.gz [02:08] radix: How long between the build completion and other upload? [02:08] wgrant: not very long [02:09] radix: You might need to wait up to 20 minutes (the binaries are only published on */20) [02:09] ok, they're there, so I'll try another build of glulxe [02:09] radix: If you add the PPA to /etc/apt/sources.list, can you download the -dev package? [02:09] Just hit "Retry build". [02:09] (with apt-get install) [02:09] Or maybe wait - but it might take a while to automatically retry. [02:10] persia: I'm just looking at the http server now: http://ppa.launchpad.net/radix/ubuntu/pool/main/g/glktermw/ [02:10] radix: OK. When you *know* it's published, wait a bit for for tbe buildd internal mirror to get a copy (buildds have no network access), and then click retry. [02:10] aha [02:11] ok [02:11] Depwait builds should be automatically retried when their deps are available. [02:11] oh, sweet [02:11] I'm not sure how frequent that is for PPAs, however. [02:12] I guess I won't hit that button then [02:13] I don't see any indication that they'll be retried, but I guess I'll wait a while longer [02:13] There hasn't been a publisher for 13 minutes. [02:13] There's little point retrying before another publisher run. [02:14] that's good to know [02:15] this is the first time I've used PPA, and the only docs I've found are https://help.launchpad.net/Packaging/PPA , so I'm still pretty clueless [02:16] That build probably only started a couple of minutes too early. [02:16] It might actually work if your retry it now. [02:17] * radix pushes the buttons :) [02:18] * Hobbsee spins the dials [02:18] * wgrant turns everything off. [02:20] * Hobbsee runs 240v through wgrant. [02:20] voom! [02:20] I wouldn't voom if you put 40000V through me. [02:21] Or is it vroom? I forget. [02:21] hmm, a contested assertion [02:21] try to try Science! [02:21] "time to try" [02:21] "try to try" works too [02:21] * wgrant fails to try. [02:22] vroom, iirc. [02:22] radix: not quite as well though [02:22] Hobbsee: Probably so. [02:39] radix: Well, it worked, but failed. [02:42] wgrant: yeah, but for a reason I know how to deal with :-) [02:42] Thanks very much for the help [02:42] np [02:43] I should really set up a barebones VM so I can more easily spot these build-deps errors [02:43] Why do you need a VM? [02:43] or a chroot, whatever [02:43] We use either pbuilder or schroot. [02:44] I'll look into those [04:39] helloooo launchpad! [04:41] hey jtv! [04:42] * wgrant escapes [04:44] hi Hobbsee [04:44] Hobbsee: what did I do to scare wgrant? [04:44] jtv: i'm not sure. But he just had to deal with an incredibly dim user, and has been dealing with the forums, so he was probably already highly traumatised. [04:45] (how do people know about #ubuntu-bugs, #ubuntu-quality, etc, yet not know how to install a program with ubuntu?) [04:46] Selective cluelessness. [04:46] Hobbsee: don't ask me. I've been dealing with some guy who uses my mailing lists and bug tracker to ask for help with issues like "I'm using your C++ library and I'm getting these link errors about missing functions" [04:46] Where the issue is of course simply that he's not linking to the library. [04:46] jtv: classy. [04:46] yes, of course. [04:46] Or "I'm getting an error, something about a variable definition. Why?" [04:47] Some of the stuff in the Programming Talk subforum of ubuntuforums.org is great. [04:47] When I get him to tell me the actual error messages, it's "I'm getting this error, what's wrong with my program?" [04:47] wgrant: ah, examples! [05:00] jtv: "give me a minimal, runnable example that reproduces the problem" is my favourite way of dealing with those. [05:03] jml: In this case of mine I've moved on to "I can help you solve your problem, but you must put in some effort—such as bothering to read the error message." [05:04] jtv: sucks :( [05:05] jml: I once spent time explaining that to someone, and the guy told me what an idiot I was for wasting my time on that. [05:05] jml: we do get some entertaining stories out of it... [05:05] jtv: explaining "reading the error message"? [05:06] jml: and "produce a minimal example" and such [05:06] jtv: ahh ok. [05:06] jtv: well when they do that I reach for my ignore gun. [05:07] jml: and resolve not to spend so much time on it next time? [05:07] jtv: well, this is mostly in an IRC context [05:08] jtv: so I say, "can you please paste a minimal, runnable example to " and then generally don't actually bother elaborating until they do so (or confess that this is proprietary code they are being paid to work on or what have you) [05:09] jml: and on IRC I suppose the ignoring is more work. :-) [05:09] jtv: /ignore all [05:09] jtv: also, having op privileges is nice :) [05:10] jml: ahhhh :) === Ursinha changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Community contact: Ursinha [05:39] me again [05:43] hi [05:49] I have specified a milestone called 'demo1a' and pushed some updates to a related branch and tagged it demo1a. How can I get the demo1a milestone to be connected with the specific revision? [05:54] jdrake, with the specific revision you've pushed to lp? I'm not sure you can do such association [05:54] bzr revision, there is [05:55] What is the point of saying a milestone on lp? What does it link with to have any meaning? [05:56] jdrake, you can associate bugs and blueprints to it [05:57] so, targeting these items to a milestone, you can keep track of what is supposed to be released [05:58] But you can't associate actual code to it? [06:00] you can associate a branch to a milestone, but not a specific revision [06:00] I thought branches were associated with series, and releases could have tarballs. [06:00] Releases should really be able to have a bzr tag attached to them, IMO. [06:01] wgrant, you're right, sorry, it's a series that can be associated to a branch [06:02] you clearly have much more experience on LP than me :) [06:03] ok, I am confused here. [06:03] wgrant, when I said that you can keep track of what you'll release, I use the milestone as a "release target", as we do in LP [06:03] So I have a milestone, can I get something associated with this tag 'demo1a'/revision 3, that can be a release of some kind? [06:03] jdrake, let me try to clarify, and wgrant can correct me if I'm wrong [06:03] Ursinha: Right, Launchpad fails the dogfood test. Launchpad developers don't use Launchpad properly. [06:04] Probably because milestones don't make much sense for Launchpad. [06:04] Well, some milestones should be able to be marked as being releases, IMO. [06:04] jdrake, no, you can't associate a specific revision to something in LP [06:04] Whereas at the moment they are separate concepts. [06:04] jdrake, but yes, you can associate a whole branch [06:06] That seems buggered [06:07] It makes sense to be able to associate revisions or tags with releases, and it makes sense to have the concept of releases and milestones merged. Neither of those are currently possible. [06:07] jdrake: At the moment, you can upload files to a release for users to download. [06:07] jdrake, what I'm saying is that the smaller unit of code you can associate to something is a branch [06:07] jdrake, if you want to "release" something that belongs to a specific revision, you may package that somehow and release it [06:07] as wgrant just said [06:08] but all suggestions are welcoe [06:08] *welcome [06:10] wgrant, why you say milestones don't make much sense for LP? [06:13] Ursinha: LP 2.1.10 is a release. [06:13] But in the Launchpad webapp it is a milestone. [06:13] wgrant, it's a milestone to a release [06:13] I think 'release' should just be an extra flag on a milestone, as that's all it is. [06:13] milestone is a point to achieve [06:13] which is not wrong in the sense we use, I think [06:14] Ursinha: we don't use releases though. [06:14] If Launchpad were open, Launchpad itself 2.1.10 would have downloadable files. Thus it doesn't make sense in the current model. [06:14] maybe we should be more clear in using releases [06:14] jml, yes, faster than me [06:14] 2.0 should be a series, 2.1.10 should be a milestone with the release flag. [06:15] wgrant, the whole release/milestone/series is having a makeover [06:15] "it's in the works" [06:15] beuno: Oh, good to know. What's changing? [06:15] they are a bit confusing [06:15] Is the design public? [06:15] I think bzr shows how it's broken. [06:16] Their milestones inevitably duplicate their releases. [06:16] wgrant, I don't really remember right now, but, if IIRC, series and milestones will be collapsed unto one [06:16] And I think they make rather good use of the current functionality. [06:16] beuno: That makes approximately 0 sense. Do you mean releases and milestones? [06:16] or milestone will become releases [06:16] it's 2am [06:16] Heh. [06:16] so I'm a bit off :) [06:16] That's what I would have suggested. [06:16] hey beuno [06:16] you there [06:17] hi Ursinha [06:17] nope, not here [06:17] :p [06:17] :P [06:18] wgrant, something with series will happen as well [06:18] because it's confusing right now [06:18] beuno: I bet we're going to have this sprung on us and it will be completely broken. [06:18] you have to create a series to create a release to add download files [06:18] wgrant, I bet it won't be completely broken, and it will rock your socks off [06:18] :) [06:19] * beuno is a bit fuzzy on the details, and is very very very tired [06:19] I think that the series data model shouldn't change, but they should cease to be explicitly managed. [06:20] ie. when creating a release it should ask you to either select an existing series or create a new one. [06:20] and who said it wasn't going to work that way? [06:20] You learn to doubt Launchpad design after a while, I'm afraid. [06:20] I haven't [06:20] and I've been around for a while... [06:21] aaaaaanyway [06:21] this was fun [06:21] Sleep. [06:21] but it's way past my bedtime [06:21] g'night! [06:22] Night! === Ursinha changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com === adeuring changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Community contact: adeuring [09:35] any lp dev around that could edit a project's ownership? [09:37] siretart: I'll ask who can do it. [09:37] siretart: You'll need an ~admin unless it's owned by Registry. [09:38] siretart: probably best to file a question at https://answers.launchpad.net/launchpad [09:38] filed as https://answers.edge.launchpad.net/launchpad/+question/47001 [09:38] * wgrant agrees with stdin. [09:38] * siretart hopes it is filed in the right place [09:39] adeuring: So you are actually going to have somebody assigned to respond to things in the channel now? This is good news. [09:41] wgrant: since two week or so there should be a developer "on call" here. Excat times depend on where the person lives, of course ;) [09:41] wgrant: see the channel topic ;) [09:41] siretart: yes, a question is exactly right [09:41] adeuring: It doesn't explain the purpose of the community contact. [09:42] adeuring: danke! :-) [09:42] And I've not seen anything more about the existence of the community contact, and I watch LP things fairly closely. [09:42] wgrant: yeah, we have been parhaps a bit too silent about it... [09:43] s/a bit too/completely/ [09:43] Anyway, it is a welcome change. === jamesh_ is now known as jamesh [11:19] mrevell, ping [11:19] hi kiko-zzz [11:20] mrevell, wgrant has a good point -- we haven't told anybody about CHR [11:20] mrevell, and I was going to ask you if we could extend management of launchpad-users to the CHR [11:20] wanna pile that on the stack and clear it with ole jojo? [11:21] kiko-zzz: Interesting you should mention that. The releases team and I were discussing this yesterday and I'm going to blog about CHR today. I was wondering if we want to put the name of the current CHR person in this channel's topic. [11:21] mrevell, well, Ursula and joey did that yesterday, and I think it should become standard yeah [11:21] mrevell, but I was more suggesting we haven't said anything about it on news.launchpad.net or help [11:21] kiko-zzz: Great, I'll add it to the CHR process page, along with launchpad-users management [11:22] Excellent. [11:22] mrevell, what do we do with the password I wonder [11:22] (what does CHR stand for?) [11:22] community help rotation [11:22] Aha. [11:22] we are full of acronyms this year [11:22] Thankyou for introducing it. [11:23] wgrant, you think it's working out well? [11:24] kiko-zzz: Having somebody that people can ask, and reducing response latency, is always a good thing. [11:24] yeah, we're still figuring out how to do it, but I agree [11:26] Support latency has frankly been awful at times. [11:28] yeah, it's because we don't actually have support personnel. well, didn't! :) [11:28] Yep. [11:29] wgrant, hey, I had a thought. maybe you want to apply for a CHR post? :) [11:29] Hm? [11:30] wgrant, hmmmm? :) === jscinoz_ is now known as jscinoz === barry-away is now known as barry === zookofamilytime is now known as zooko === mrevell is now known as mrevell-lunch [12:53] Good morning! [12:53] [12:53] * zooko checks his trac to see if launchpad pushed any updates into it while he slept. [13:04] adeuring: what part of launchpad is responsible for this page: https://edge.launchpad.net/ubuntu/intrepid/i386/libquicktime1/2:1.0.2+debian-2build2 [13:04] adeuring: is that soyuz? [13:04] That's Soyuz. [13:04] siretart, wgrant: right [13:07] thanks. bug filed [13:08] yay CHR! Will it cover !european workdays, though? [13:09] Hobbsee: well, today, since I live in Germany. On other days people from other parts of the world may be on duty [13:10] adeuring: so, not most of the time. Right. [13:10] adeuring: what do you do on launchpad? Are you new? [13:11] wait. i didn't get that. you are on duty because it's not a work day for you? [13:11] Hobbsee: I'm working since ~1 year on Lauanchpad; mostly on a hardware database. [13:11] adeuring: ahhh. I'd not seen the nick before. Hardware database for distributions, or? [13:12] adeuring: Are we going to be able to get useful data out of that at some point? [13:12] The raw stuff is there, but that's not entirely useful... [13:13] Hobbsee: Distributions: yes and no; the idea is to collect data from Ubuntu users, and to get for example an idea how many devices (say, Lexmark printer 1234) are in use; links to bugs etc. [13:13] Hobbsee: We'll have soon an API for the HW database [13:14] adeuring: ah, right. Cool! [13:14] Hobbsee: But running the data collection client (hwtest-gtk) is technically not restricted to Ubuntu [13:15] adeuring: indeed. [13:15] Where is this database? I want to see it! [13:15] Hobbsee: but I am not aware of any other distros using this program [13:15] adeuring: no, it seems they have their own. Or at least some of them [13:16] Hobbsee: right; collecting hardware data became fashionable during the last two years or so ;) [13:16] adeuring: heh, yes :) [13:17] * wgrant is yet to find traversers other than +fingerprint under /+hwdb. Are there any? [13:20] wgrant: nothing really interesting; but you can look for example to lp.net/~your-account/+hwdb-submissions [13:21] adeuring: Right, that's the other I knew about. [13:21] wgrant: wait a bit and we'll have a bit more to present [13:21] Why are there so many anonymous submissions? Isn't one required to enter a valid Launchpad email address at the end of the process? [13:22] wgrant: There are many more Ubuntu users than Launchpad users, and we did not want to require an LP account for the submissions. [13:22] wgrant: But as soon as somebody registers an LP account with the email address from a submissions, he'll own that submission [13:22] adeuring: Hmm, it looked to me like it needed an LP account. But maybe I misread. [13:23] Aha. === salgado-afk is now known as salgado [13:39] siretart: FWIW, you can file bugs against "Launchpad" and they will be triaged and moved to the right place [13:42] I'm trying to copy a package in my PPA from hardy to intrepid, and I get "The following source cannot be copied: sugar-artwork 0.82.0-1ubuntu1~ppa1 in hardy (same version already has published binaries in the destination archive)" - even though it doesn't exist for intrepid yet. [13:42] https://launchpad.net/~morgan/+archive === mrevell-lunch is now known as mrevell [13:43] morgs: https://edge.launchpad.net/~morgan/+archive?field.name_filter=sugar-artwork&field.status_filter=published [13:44] cprov: hey - so can I copy it to intrepid? [13:44] morgs: it was already built and published for hardy, you can't rebuilt it for intrepid. You have to copy the exiting binaries too. [13:44] oh I see [13:45] If I want to build it for intrepid, do I have to reupload? [13:45] morgs: no, when copying, select the option (radio-button) to include the binaries. [13:47] morgs: and *hey*, didn't notice it was you Morgan. [13:48] cprov: yeah Celso :) Nice to be using soyuz... [13:48] cprov: OK, that works, but does the package actually get rebuilt on intrepid at some point? [13:48] morgs: yeah, great to see olpc stuff in the PPA too. [13:49] morgs: no, you will be using the binaries built in hardy in intrepid clients. [13:50] morgs: do you have any new library in intrepid ? [13:51] cprov: hmm, I actually want to get the packages built on intrepid too (my goal is to get a feature freeze exception to sync from debian where these packages come from), so I'll reupload. I did that for sugar - the ~ppa2 I uploaded for intrepid. [13:52] * wgrant dreams of a "Backport" button in the web UI. [13:52] * laga joins wgrant [13:52] morgs: right, when you really need to rebuild to a new series you need a new source. [13:52] cprov: OK thanks! [13:52] just copying packages to another series actually sounds broken. there is no dependency checking AFAIK [13:53] wgrant: no you don't :) [13:53] laga: We do it all the time in Ubuntu... [13:53] wgrant: without a rebuild? [13:53] laga: Yes. Or the buildds would be even more angry. [13:54] laga: Where do you think we get the binaries to start a new distroseries? [13:54] without dependency checking? it surely breaks for dpkg-shlibdeps [13:54] .. stuff [13:54] wgrant: ah, that's not a backport. [13:54] laga: It's a forward-port without rebuild, right. [13:55] laga: exactly, copying binaries over is more common (and right) than you think. [13:55] well, your first build of the toolchain on a new distroseries requires something to build it with... [13:55] We carry many binaries from Warty. [13:55] Copying backwards sometimes makes sense. [13:55] Not always. [13:55] But people should be smart enough to check this. [13:55] laga: but I'm not saying we don't have to rebuild in some cases, forward (new build-deps) or backwards (backports). [13:55] morgs: We carry over the entire archive (except for partner... or is there a bug on that?) [13:55] forward-ports to a completely new series are a different thing then letting joe sixpack copy packages in their PPA ;) [13:56] Joe Sixpack should be allowed to shoot himself in the foot and learn from mistakes, I think. It's nothing particularly damaging. [13:56] laga: yes, and it doesn't mean that plain-copy isn't necessary. [13:56] wgrant: but why are they allowed to with removing packages? [13:57] Hobbsee: Because version ratcheting is good. In some cases. [13:57] Just not those that Ubuntu people are more likely to use. [13:58] alright. i'm convinced. [13:58] * wgrant puts away the brainwashing gear. [13:59] bigjools: thanks! i've noticed that soyuz alone has about 130 untriaged bugs, and I wanted to spare you some triaging work [13:59] siretart: they all need triaging regardless of where they start :) [13:59] wgrant: occasionally. but it does seem to confuse people [13:59] but thanks for the thought! [13:59] Hobbsee: Confusing people is good... we don't want easily confused people to be publishing packages for the world, do we? [14:00] wgrant: that's a point === thunderstruck is now known as gnomefreak [15:03] interesting, does uploading something to a PPA automatically create /ubuntu/+source/ ? [15:04] no, that's separate [15:04] radix: no, the domains are separate. [15:04] because I notice that glulxe and glktermw now exist in /ubuntu/+source , empty [15:04] and I'm pretty sure glktermw at least has never been packaged for ubuntu [15:04] radix, where's the latest incarnation of twisted reality? [15:04] Are SourcePackageNames shared? [15:04] s/Are/Aren't/ [15:04] I can't find it in all of the files [15:05] Hory: it's called "Divmod Imaginary" now [15:05] aha, thanks [15:05] radix: yes, the page is available, but it says in 'no versions available' [15:05] cprov: yes I understand [15:05] it seems it became available because I uploaded to a PPA [15:06] just a curious thing I noticed :) [15:06] radix: right, it's not a 404 because of that. [15:06] Bug #157342 [15:06] Launchpad bug 157342 in launchpad-foundations "PPA-created SourcePackageNames appear to exist in Ubuntu too" [High,Confirmed] https://launchpad.net/bugs/157342 [15:07] but actually, it's interesting, because it means bugs can be filed against it [15:07] radix: No, that was fixed. [15:07] Or it was meant to be. [15:07] radix: no, the bug facet of the problem was fixed. [15:07] hum, ok, I'm just guessing based on the fact that there's a "Report a Bug" button [15:08] Grr. [15:08] Looks like it might have been unfixed. [15:08] * wgrant tries on staging. [15:08] One can certainly get the form... [15:08] otoh, it'd be nice to have a place for bugs to be filed on my PPA packages :) [15:08] Ah, no, the bug is still fixed. [15:08] radix: ubuntu-qa guys would cry loudly, I guess. [15:09] cprov: oh, sure, if I were to put bugs in there [15:09] * wgrant will gladly reject the bugs. [15:09] cprov: is there an outstanding feature request for having bug trackers specifically for PPAs? [15:09] that I can subscribe to? [15:09] radix: I think so, let me find it. [15:11] I think I found it [15:11] bug #234564 [15:11] Launchpad bug 234564 in malone "Cannot file bugs against packages in a PPA" [Undecided,New] https://launchpad.net/bugs/234564 [15:11] radix: https://bugs.edge.launchpad.net/soyuz/+bug/179873, too [15:11] ah :) [15:11] Launchpad bug 179873 in soyuz "Can't report bugs on PPA packages" [Undecided,New] [15:11] dupe! [15:13] ok, thanks guys [15:13] * radix is subscribed [15:14] that'd be much better than using my blog comment section as a bug tracker :) [15:14] radix: wordpress guys would disagree :) [15:14] * radix shudders [15:14] those guys are weird ;-) [15:15] ehe [15:15] oh ho, I just used "This bug affects me" for the first time === kiko-zzz is now known as kiko [15:21] does anyone know why there are apparently duplicate rows on https://edge.launchpad.net/ubuntu/+source/9menu/+publishinghistory ? [15:22] there are 3 lines with "Superseded Dapper release universe x11 1.8-1.1" [15:25] james_w: looks like broken overrides we had in the past. [15:28] cprov: thanks [15:30] Hi, how can i delete a branch? [15:34] jbalint: There is a little red button on the main page of the branch, [15:34] jbalint: on right to the title [15:35] aw crap , i wasnt logged in. i see it now. thanks adeuring [15:35] jbalint: common problem; happens to me too ;) [15:55] wgrant, #1 strikes again [15:57] Hello. [15:58] * zooko checks whether launchpad has synced with http://allmydata.org/trac/tahoe . [16:01] hey zooko [16:01] gmb, zooko's lookin for ya ;) [16:30] hey cody-somerville, kiko: LP blueprints is still timing out when I try and link a dep. (OOPS-1007EC106) Any idea if/when this will get looked at? [16:30] rexbron, uhhh uhhhhh uhhhhhh [16:31] matsubara, how about you escalate rexbron's problem? === kiko is now known as kiko-fud [16:31] cool, it's not critical, but a blocker [16:31] kiko-fud: will do [16:31] matsubara, who do you think could sort us out? [16:32] zooko, kiko: So, we're still seeing issues trying to sync with the Tahoe Trac. It looks like a permissions problem, which is pretty weird. [16:32] zooko: Can you confirm that the 'launchpad' user has XML_PRC and LAUNCHPAD_RPC permissions on your Trac instance? [16:32] kiko-fud: someone from registry, I think [16:33] rexbron: I need to grab lunch now. I'll take a look when I get back. [16:33] matsubara: np, enjoy :) === matsubara is now known as matsubara-lunch [16:36] hello do you speak french? [16:36] i've a bug [16:37] sylvainvh: sorry, unfortunately I don't speak French [16:39] no problem [16:39] I read about launchpad bzr integration, and thought that using --fixes on my commit and then uploading to trunk would do something automatic in my new launchpad project - but now the fix is there, https://code.edge.launchpad.net/electionaudits and the bug still says "confirmed" https://bugs.edge.launchpad.net/electionaudits/+bug/277341 Do I just need to wait some more, or is there something else to configure? [16:39] Launchpad bug 277341 in electionaudits "makeauditunits: DJANGO_SETTINGS_MODULE is undefined" [Medium,Confirmed] [16:40] when i start my computer. After the grub, i've sometime a sound and my computer crash [16:41] it's a bug [16:41] Hey there gmb! [16:42] launchpad [16:42] LAUNCHPAD_RPC [16:42] XML_RPC [16:42] sylvainvh: sorry, this channel is about Launchpad, not about Ubuntu. You might get help for example on Freendoe's #ubuntu channel [16:42] Yes -- the launchpad use has the LAUNCHPAD_RPC and XML_RPC permissions. [16:42]