=== ampelbein is now known as Ampelbein === Ampelbein is now known as ampelbein [03:39] when i reported some bug, may I change in launchpad the release nominate? or it's only the sponsor can do this? [03:40] when i report some bug, may I change in launchpad the release nominate? or it's only the sponsor that has to do this? [03:43] Andre_Gondim: I don't understand what you're asking. Can you rephrase it? [03:46] wgrant, at this https://bugs.edge.launchpad.net/ubuntu/+source/gwibber/+bug/344426 I changed the release nominate. May I could do this or only the sponsor that has to do this? [03:46] Ubuntu bug 344426 in gwibber "gwibber crashed with NoKeyringDaemonError in get_data()" [Undecided,New] [03:47] wgrant: he set the +nominate [03:54] Andre_Gondim: The release manager (driver) of the series has to approve/decline that. === abentley1 is now known as abentley === Andre_Gondim is now known as Andre_Gondim-afk [08:41] https://answers.edge.launchpad.net/someproject/+createfaq <- the keywords are separated with spaces or with commas? [08:43] savvas: It strips out commas, so I presume it uses spaces natively. [08:43] thanks :) [08:43] it should be mentioned however :P [08:44] It should. You could file a bug. [08:44] I will :) [08:55] bug 346247 [08:55] Launchpad bug 346247 in launchpad "+createfaq keywords should mention the delimiter" [Undecided,New] https://launchpad.net/bugs/346247 [08:55] * wgrant retargets it. [08:56] there's a launchpad-answers project? sorry :\ [08:58] launchpad is sort of the gateway project, where you can file bugs and somebody will eventually redirect them to the right project. [08:58] Since it's often hard to work out which bugs belong to which team. === mdz_ is now known as mdz [10:12] morning folks [10:16] ah, there it is.. even before asking the question. thanks. [10:18] I like questions like that. [10:18] gmb: sup? === abentley1 is now known as abentley === abentley1 is now known as abentley === soeb is now known as soeb_afk [13:16] hi, everyone... [13:17] we try to reclaim ID for the LoCo team, but got no answer so far [13:17] https://answers.edge.launchpad.net/launchpad/+question/64313 [13:18] are there other ways we can contact LP admins (I believe they are ones we need to reach with this Quest) [13:20] kwah, an admin is assigned to it [13:21] Said admin tends to be very busy, and it has only been a couple of working days. [13:22] cody-somerville, thanks [13:22] wgrant, I understand, but there is no indication what so ever how much such a request may take [13:23] and we are currently in the reorganization phase and aiming for the next loco council to get approved [13:23] did not mean to offense anyone === abentley1 is now known as abentley === mikro_ is now known as mikro [14:37] is it possible to use security target? example debian/control for PPA? === abentley1 is now known as abentley [14:37] sorry debian changelog [15:18] Can the launchpad team simplify installing PPA keys easier? [15:18] I can't just wget | apt-key add - === Andre_Gondim-afk is now known as Andre_Gondim [15:26] magcius: gpg --recv-key | apt-key add -? [15:26] or well [15:26] export inbetween [15:27] LarstiQ, mind explaining it a bit more in your instructions? [15:28] magcius: the way I'd normally get a key is by asking gpg to retrieve it from the keyservers [15:28] Ah, so I must use --keyserver. [15:44] The cryptic oneliner is: [15:44] apt-key adv --keyserve keyserver.ubuntu.com --recv-key KEYID [15:44] Oops, --keyserver [15:45] Wait... apt-key uses PGP? I thought it used RSA [15:46] maxb: oh hey, nice, didn't know apt-key adv [15:46] Your question is rather unclear. PGP is a software framework, RSA is an algorithm [15:46] LarstiQ: Yeah, obscure, but so useful! I've put that command into the description of the mercurial-snapshots PPA [15:47] For my own PPA I made a *-keyring package. I'm not sure which I like better === abentley1 is now known as abentley [16:57] hi - is there a dashboard type screen where I can see a list of my projects? [16:57] it is a bit annoying having to search for them each time even when i am logged on === MTeck is now known as MTecknology [18:26] I think the copy and rebuild actions in PPA don't work [18:28] I copied luckybackup from https://launchpad.net/~medigeek/+archive/ppa to https://launchpad.net/~luckybackup-maintainers/+archive/ppa - it didn't rebuild the .deb source: http://ppa.launchpad.net/luckybackup-maintainers/ppa/ubuntu/pool/main/l/luckybackup/ [18:29] * I copied and asked to rebuild from copied source [18:31] I think it's because I copied them before, I'll delete the packages and try again in 15-30 minutes === asabil_ is now known as asabil === abentley1 is now known as abentley [19:19] hello [19:19] is it possible to change a project's url [19:20] I want to change https://launchpad.net/gnome-doc-centric-playground to https://launchpad.net/gnome-zeitgeist [19:27] are there any launchpad admins in here? :( [19:31] aantn: Please file the request here: https://answers.launchpad.net/launchpad/+addquestion [19:31] jpds: thanks! [19:32] aantn: And an admin will get round to you when they have time. [19:32] jpds: ok === Andre_Gondim is now known as Andre_Gondim-afk === ursula is now known as Ursinha [20:37] hello people [20:37] I'm working on an interface to the LP API [20:37] * intellectronica is curious [20:37] hanska: tell us more :) [20:38] is there any way to have info from https://launchpad.net/ubuntu/jaunty/+queue ? I'm missing it from the docs! [20:39] hanska: i don't think so [20:40] hanska: please file a bug on soyuz so that this can be considered for scheduling [20:48] intellectronica: I will do, thank you. [20:48] (d'oh. I started launchpad-sharp just to programmatically watch Debian and Jaunty's NEW... I succeeded with Debian's, but now... :P) [20:52] intellectronica: https://bugs.launchpad.net/soyuz/+bug/346491 , thank you :)... how come you were so interested on API implementation? :P [20:52] Ubuntu bug 346491 in soyuz "Provide NEW via the API" [Undecided,New] [20:53] ahah, funny :), I didn't know about ubottu :P [20:53] hanska: i do a lot of the work on the bugs portion of the api [20:54] also in general we're interested in how people use the api [20:54] ah, great [20:54] intellectronica: well, I started a little project to watch the NEW queue in Debian (I'm a Debian maintainer/DD in the next few months I hope), then I decided to give it the ability of watching Ubuntu too [20:55] also, so far we only have a python interface library. having a library that runs on the CLR would be awesome [20:55] ..and I fell off LP API. It looked a bit weird (and I had some difficulties implementing it, at the beginning, because I wasn't completely understanding it) [20:55] hanska: sounds very cool [20:55] I still have _lot_ to do, i.e. I can only make GET requests atm [20:55] but is kinda usable, at least I can get /beta/bugs/xx :) [20:56] hanska: you should look at the launchpadlib sources. it's a great example of how you can generate the entire library from the WADL [20:57] hanska: if you have any questions about this sort of stuff, talk to leonardr. i'm sure he'll be glad to help you [20:57] intellectronica: thank you, I'm going to download launchpadlib :) [20:57] hanska: i think kfogel and mrevell might be interested in hearing about this project too. you could get some publicity :) [20:58] hanska: is your project hosted on LP? [20:58] intellectronica: eheh, I would like to make it some more usable first -- I just found out the api-docs _tonight_ [20:58] intellectronica: nope, I'm not a bzr fan :) [20:58] ah, that's a shame. where is it hosted, then? [20:58] hanska: what intellectronica said [20:58] :-) [20:58] (re interest in API projects) [20:59] intellectronica: nowhere currently, a friend is setting up a redmine on his own server for other projects, and I'll put those two projects (watch-new and launchpad-sharp) there [20:59] intellectronica: too bad you don't host git too :P [21:00] hanska: watch this space ;) [21:00] what's redmine? [21:01] looks like some kind of trac clone to me? :-) [21:01] is that about right? [21:01] Nafallo: right, my friend said "better than trac" :P [21:01] Nafallo: I don't really know it, I'm sorry [21:01] (it's written in Ruby, and I'm more a c#-python'er, so I'd tend to avoid it ;) [21:01] written in ruby by the looks of it [21:01] hanska: b.t.w, not that i have anything against C#, but did you try using launchpadlib with ironpython? [21:01] heh [21:02] hanska: also, did you consider using the Launchpad bug tracker? you can use it even if you host your code elsewhere [21:02] intellectronica: not really [21:02] may i ask why? [21:03] oh my wait :) [21:03] not really was re ironpython [21:03] ah ok [21:03] about using the tracker.. well, LP has some good features (I'm thinking at moving bash-completion tracking there), but seems like redmine can directly mangle bugs from commit logs === _trmanco is now known as trmanco [21:04] anyone here? What is difference between 'Display name' and 'Title' in project registration form? [21:04] hehe. someone put intellectronica in powersave mode! ;-) [21:04] intellectronica: apart from splitting code hosting and bug tracking (I'd do that for bash-completion nevertheless, since Debian's Alioth ReallySucks®), that would be a nice thing I'd miss in LP [21:04] hanska, It wouldn't be too difficult to do that with launchpad and bazaar plugins [21:04] Nafallo: throttle him down! [21:04] cody-somerville: uhm? [21:05] closing of bugs from bzr commits [21:06] cody-somerville: yes, but you're missing I'm already hosting it in git [21:07] pecisk: display name: "Foobarizer", title: "An free, object-oriented, optimizing foobarizer for Linux" [21:07] ok, got it [21:07] thanks ;) [21:07] intellectronica: whoa, I was missing yet another foobarizer! [21:07] $ foobarize intellectronica [21:07] hanska, Nafallo: redmine gets the dvcs model better than trac does [21:08] LarstiQ: seems like you know it -- in what ways? [21:08] this time we're going to do it right, though. it will be self-hosting foobarizer, and it will contain a complete implementation of emacs [21:08] LarstiQ: also, I know a single installation can handle multiple projects (each with a wiki, a tracker, [..]) [21:08] hanska: in that it actually understands more than one branch :) [21:09] ah, nice! [21:09] hanska: really, trac is just horrible in this regard [21:09] LarstiQ: does it also make nice graphs out of this? (like gitk/gitg/github?) [21:09] hanska: I don't know (it that well) [21:10] hanska: I know gitk, and of github, but I'm not really a git person [21:11] LarstiQ: I see. But "branch graphing" would be useful for other branch-supporting-VCS'es, no? [21:11] hanska: I guess, maybe. [21:12] bzr gtk has a very nice graphing interface [21:12] i hope LP will have something like that soon [21:12] hanska: I'm more a fan of offline tools, svn/cvs need something like trac because they're centralized, why would a dvcs need the same crutch? [21:13] intellectronica: uh, I didn't know bzr gtk! [21:13] yeah, it's awesome, you should check it out [21:13] hanska: so, gitk or bzr viz/qlog, or the mercurial equivalents [21:13] LarstiQ: s/gitk/gitg/, far better IMVHO [21:15] hanska: is that a gtk rework instead of tk? [21:15] LarstiQ: exactly. [21:16] hanska: ah, I see how that can be far better :) [21:16] eheh :P [21:17] hanska: honestly, it's a mystery to me why tk was used in the first place? [21:17] LarstiQ: who knows, some nostalgic? [21:18] * hanska runs away [21:18] hanska: heh, maybe :) [21:18] for what? bad 60s acid trips? [21:30] tk is weird, but it seems it was fairly easy to add [21:30] unfortunately it still is like 70es today === sale_ is now known as sale [22:30] Hi, I have some questions about shared and stacked repositories in Launchpad. [22:30] Does anyone know how Launchpad uses these? [22:31] cocooncrash: afaik, Launchpad doesn't use shared repositories, and it (can/does) stack on the branch associated with the development focus [22:32] LarstiQ: Does stacking require that you use a repo format which supports it? [22:32] cocooncrash: certainly on the Launchpad side, I don't know about the client. [22:33] LarstiQ: That's what I'm trying to find out ;-) [22:33] Thanks though [22:33] shouldn't be hard to test though? [22:34] LarstiQ: I do see messages about stacking, but how do I know if it's actually been done? [22:35] cocooncrash: You can check the branch page on Launchpad - if it is a stacked branch, it will say 'Stacked on: lp:~path/to/branch' [22:36] wgrant: Cool, thanks [22:36] wgrant: Do you know if LP uses shared repos? [22:36] cocooncrash: It requires that the stacked branch has at least format 1.6. It will try to convert automatically if it's incompatible. [22:36] It doesn't. [22:36] Okay [22:36] But you don't really need those once you have stacking. [22:36] Yeah, true [22:37] Thanks wgrant [22:37] np [22:40] had cocooncrash stuck around, I would have told him that bzr.dev has recently fixed one misreporting of stacking. [22:43] jml: I'll tell him - I came to see the result of his questions [22:43] tumbleweed: thanks. [22:43] jml: How exactly does it misreport? [22:43] Does it say that it's stacking but actually doesn't? [22:43] cocooncrash: bzr says "using default stacking branch" and then doesn't stack. [22:43] Right [22:44] ok, yes I've seen that [22:44] cocooncrash: let me find the bug for you... [22:44] btw, has anyone else been having difficulty pushing to lp from jaunty bzr? [22:44] it just hangs for me unless I use sftp [22:44] tumbleweed: which version is that? [22:45] bug appeared in the last few days [22:45] 1.13~rc1 [22:45] hangs during traversing tree [22:46] I can't find any relevent bugs on lp - but it has to have hit other people too [22:46] tumbleweed: lots of small requets in ~/.bzr.log? [22:46] didn't know there was such a long [22:46] log [22:46] * tumbleweed looks [22:46] bug 345169 [22:46] Launchpad bug 345169 in bzr "bzr push to a new lp branch of bzr from a local copy fails to stack" [Critical,New] https://launchpad.net/bugs/345169 [22:46] that's the one [22:47] there was also another bug that occured during 1.13rc1 [22:47] but that was different. [22:47] jml: ah, I saw that [22:47] anyway, take home message: 1.14dev is a lot more reliable. [22:47] jml: that bug was too terse for me to see if it was what I was seeing [22:48] tumbleweed: *nod* I reported it on IRC on #bzr and lifeless filed a developer-oriented version of the bug. [22:48] which I didn't mind at all, since the bug got fixed very very quickly :) [22:49] jml: Do you know what the actual cause was? [22:49] i.e. will I have to upgrade to actually get it to stack? [22:49] cocooncrash: yeah, you'll have to upgrade. [22:49] Bleh [22:49] Any workarounds? [22:49] cocooncrash: upgrading is a good idea for a lot of other reasons though. [22:50] actually, one reason: speed. [22:50] jml: did it get fixed before or after 1.13 final? [22:50] LarstiQ: bug 345169 got discovered after 1.13 final. [22:50] Launchpad bug 345169 in bzr "bzr push to a new lp branch of bzr from a local copy fails to stack" [Critical,New] https://launchpad.net/bugs/345169 [22:50] LarstiQ: the other stacking bug (number escapes me) got fixed in time [22:50] ok [22:51] cocooncrash: I don't know of a workaround. #bzr might. [22:51] jml: Okay, thanks. [22:51] cocooncrash: they will, however, strongly recommend you upgrade your formats :) [22:51] jml: But that won't solve it, will it? [22:51] rom1v: Just tried it myself, and compiz segfaulted in the guest session. This worked a few months ago. [22:51] will we? [22:51] cocooncrash: it will, I think. [22:51] LarstiQ: many of you will :) [22:51] Oh, that's fine then [22:54] jml: ah, upgraded my branch format to 1.6 and I don't hit that bug [22:54] s/branch/repo/ [22:54] cool. [22:54] may I recommend 1.9 [22:54] it comes with a complimentary side order of love. [22:54] hah [22:54] jml: Do repo formats matter when pushing/pulling to other branches? [22:54] done [22:55] cocooncrash: yes. [22:55] I've noticed that they both have to have the same rich-root support or not [22:55] right. rich-root has to be the same. [22:55] * LarstiQ wonders how long between dput and showing up in ppa build records is usual [22:55] jml: But otherwise? [22:55] apart from that, AIUI, any two formats will interoperate. [22:55] Awesome [22:55] but they'll probably perform badly. [22:56] but, they might need to convert on the fly, depending on how different they are. [22:56] exactly. [22:57] ah, there we go, packging went from not listed to building. === thunderstruck is now known as gnomefreak