[00:27] Rinchen, https://help.launchpad.net/FAQ [00:27] *ugly* [00:27] now, I'm off to bed :) [00:30] beuno: sleep well :) [00:42] beuno, thanks. Fixed as best I could [00:50] hi [00:51] is there a problem with staging.lp.net? === bac is now known as bac|away [00:53] also, how can i register a project under a team? [00:58] bbyever, looking now [00:58] thanks, Rinchen [00:58] has been offline for a bit. thought it might have been the normal update but it's taking a bit longer than it should be [00:59] bbyever, you can register a project and then change the owner to a team [00:59] ok [00:59] ah ok [00:59] thanks [01:02] bbyever, not quite sure what's going on there. It's not a production machine (hence staging) so I can't wake up a sysadmin to look at it. [01:02] bbyever, the box is alive but it's possible the application server on it has died for some reason. Will be interesting to see why [01:04] bbyever, well, one of our sysadmins who doesn't sleep just kicked it and it's back [01:04] great, thanks! [01:05] i have another question. What is the best license that LP offers at project registration for things that are not software, like documentation and such? [01:05] bbyever, I'm not a lawyer...but a lot of folks use CC or GFDL [01:06] but CC doesnt appear at the project registration page... [01:08] Rinchen, unless its under some other name... Im not very experienced with this... [01:08] * LarstiQ would try to stay away from the GFDL. [01:08] bbyever: if you don't care at all, I'd probably pick the GPL. [01:09] or well, if you don't care what people do with it, BSD or PD. [01:09] bbyever, then the best thing to do is email feedback@launchpad.net, mention you talked to me and I recommended email the feedback email. We'll have someone in that area get back to you with guidance. [01:09] or listen to Rinchen [01:09] hehe. You can modify your license too, so you're not fixed [01:09] Rinchen: thanks i'll do that. [01:10] LarstiQ: I'll pick the GPL for now, i guess you can change it afterwards , right? [01:10] LarstiQ had another good suggestion with BSD. I have seen that a bit as well. [01:10] bbyever: Rinchen said so, I trust him :) [01:10] best thing bbyever is to review the available choices and then look at the licenses themselves. [01:11] true. [01:12] ok [01:12] yeah +edit allows you to change it. If for some reason you cannot, then you ask a question (see the channel topic) and a LP admin can do it for you [01:12] ok, thanks for your time! [01:12] you bet [01:12] off to a late dinner [01:12] have a good evening [01:14] same [01:14] bye! [01:19] how do I rename a project on Launchpad? [01:20] idnar: +edit? [01:20] uhm [01:21] my project is http://launchpad.net/$NAME [01:21] $NAME is what I want to change, which I can't seem to do via that interface [01:22] ah hmm [01:23] I thought about deleting it and creating a new one (I only created it about a week ago), but I can't see a way to delete it either [01:24] if you'd been here 10 minutes earlier Rinchen would still have been able to answer. [01:25] idnar: as is, I don't really know, other than asking an admin to do it. [01:25] okay [01:25] should I just hang around and wait for an admin to show up? [01:25] Or you could post a question at answers.launchpad.net and one of them will see it later. [01:26] idnar: https://answers.edge.launchpad.net/launchpad/+addquestion [01:28] okay, did that [01:28] thanks === bac|away is now known as bac [01:45] Hello [01:45] any Launchpad admin please ? ^^ [01:46] Rafik: I don't know if any are awake, but what is your problem? [01:46] hi LarstiQ [01:47] I wanted to know if it's possible to get an old inactive nickname === bac is now known as bac|away [01:47] Rafik: owned by someone else? [01:47] .... does not use Launchpad. This page was created on 2005-06-15. [01:47] Rafik: if you already own it, you should be able to merge it with your current one yourself [01:47] ah. [01:48] Im not the owner [01:48] does indeed seem like an admin request. [01:48] yes :) [01:49] I sent an email a week ago with no answer yet [01:49] Since it's my real name, my IRC nickname... I really want it :) [01:51] Hi guys! [01:51] Rafik: have you considered asking a question via Launchpad's Answers section? https://answers.launchpad.net/launchpad/+addquestion [01:51] My PPA register no packages, and it is http 404 [01:51] LarstiQ, No. I just sent an email. [01:52] You advise me to add a question ? [01:52] hello Drk_Guy [01:52] Hi Rafik [01:52] Rafik: I think that is the proces, yes. (A quick check turns up someone else asking for the same thing (different name though :)) [01:53] :) [01:53] Drk_Guy: could you give a little more context? [01:53] LarstiQ, Thank you. [01:53] LarstiQ, I uploaded a src package like 4 hours back, and it is not up still [01:54] I've signed CoC, accepted policy, everything [01:54] But it won't work [01:54] This is supposed to be my PPA: http://ppa.launchpad.net/drk-red/ubuntu [01:55] LarstiQ, Any ideas? [01:56] Rafik, [01:56] Drk_Guy: That URL is broken. [01:56] Drk_Guy: You actually meant https://edge.launchpad.net/~drk-red/+archive [01:57] RAOF, That's what Launchpad gave me [01:57] Oh, right. Yes. That'd be the url for the repository, yes. [01:57] But you haven't uploaded anything yet :) [01:57] Drk_Guy, I'm sorry. I can't help with your issue. [01:58] Drk_Guy: no mail with a build failure or anything? [01:58] RAOF, I've uploaded a special wine package like 4 hours ago [01:58] Not to that PPA you didn't. [01:58] Did you get the "accepted" mail back? [01:59] Drk_Guy: how did you upload it? [01:59] LarstiQ, dput [01:59] LarstiQ, My changes were rejected [01:59] Why? [01:59] It's my PPa, i can upload what i want [01:59] That's true. But you need to format them the correct way :) [01:59] Drk_Guy: well, within limits of course. You can't upload the Lord of the Rings :) [02:00] You'd want to pastebin the reject email if you want more help :) [02:00] LarstiQ, I'm uploading a special verson of wine, with 3DMark [02:00] Drk_Guy: I don't have PPA experience, but I have some dput experience. One issue that can trip you up is if you don't specify which host to put to, it picks the default one. [02:01] http://pastebin.ubuntu.com/26558/ [02:01] LarstiQ, I followed the PPA guide [02:01] Could not find person 'drk-red' [02:01] I don't know why that is raised, but that seems the critical problem. [02:02] if you can figure that out, you're a step closer to fixing the problem. [02:02] You'd want to pastebin your dput.cf :) [02:02] ok, I'm off to catch a ride to the airport. [02:02] Have aviatronic fun! [02:02] heh, thanks :) [02:03] RAOF, http://pastebin.ubuntu.com/26559/ [02:03] LarstiQ, Good luck [02:04] Drk_Guy: That looks OK. Try uploading the source package again? Maybe it was a transient error. [02:04] Ok [02:05] RAOF, Already uploaded [02:06] You need to pass -f to dput, because it normally won't upload twice. [02:07] RAOF, Nopey [02:07] -f won't work [02:08] A more useful response would be to paste(bin, if necessary) the output of the failed attempt. dput -f my-ppa foo.changes most assuredly will work :) [02:08] Ahh! [02:09] the -f was on a different spot [02:09] ;) === sm is now known as sm1 [02:56] can anybody elighten me as to what purpose the "Upstream Version" column in +source pages really is? [02:58] LaserJock: i think it's got something to do with being useful where upstream uses launchpad as well [02:58] as in, to link the corresponding series [02:59] but i've found next to no use for it in practice, probably because the upstreams of stuff i touch aren't on there [02:59] Or where someone bothered to define it: the "upstream series" can also link to other trackers. [02:59] The main issue is that it requires 15,000 definitions every cycle, which nobody every does. [03:00] well [03:00] my problem is that I'll set the upstream link one time in one release [03:00] but since that all has to be updated by hand [03:00] old versions are still linked to "trunk" [03:01] and since vcsimports only support trunk I'm not sure how we're supposed to use it [03:02] so now I'm removing all the links I did back in gutsy or so [03:03] and why are the names/email addresses of people in some of the changelog entries on the +source page and some aren't [03:05] it's *very* frustrating to be looking at changes and not know *who* did them [03:09] what's an example page? === bac|away is now known as bac [03:10] I can't quite follow this conversation without an example [03:11] jml: https://launchpad.net/ubuntu/+source/(anything) [03:11] jml: I'm looking at https://edge.launchpad.net/ubuntu/+source/gcompris [03:12] and 6 of the entries don't have any person attached to them [03:12] ok. [03:13] and the publishing history doesn't have *anything* either [03:13] Note that we're also missing all the changelog entries between 8.3.2-1ubuntu2 and 8.4.2-1ubuntu1 (specifically at least 8.4.2-1) [03:13] so there's a changelog issue, plus the "upstream version" thing [03:13] but they aren't necessarily directly related, right? [03:13] yeah, the upstream version thing I'm just giving up on [03:13] jml: Yes, two separate things, on the same page. No direct relation. [03:13] no, not at all related, I just saw it on the same page [03:14] LaserJock: why is only being able to import trunk an issue here? [03:14] jml: If you look at e.g. https://launchpad.net/ubuntu/+source/gdebi [03:14] jml: because the packages don't *come* from trunk [03:14] jml: so it makes linking pointless [03:15] There exist version of gdebi that would be suitable for adjustment for -updates in prior releases. There's no means to either track those well or import them. [03:15] s/version/versions/ [03:15] jml: To put it another way, it would be nice if the upstream version link could actually link to the correct upstream version for each release. [03:16] As it stands now, it might make sense to link a project to a source package, but on a per-release basis it's useless information, and requires 15,000 manual actions every six months. [03:17] persia: when you say 15,000, you are referring to the number of packages, right? [03:18] (Or not even useless information, but rather incorrect information) [03:18] jml: Yep. [03:18] good. [03:19] persia: I think it's worse than that as it stands now [03:19] LaserJock: worse than incorrect information that requires massive manual action? How? [03:19] because for vcsimports (which is the majority right now), you can only link to trunk [03:19] so you have no hope of getting correct information for even at one time [03:19] Ah, which is exceedingly unlikely to have close relation to the source used in the source package. I see what you mean. [03:21] To look at a recent example that hit the archives: the libdrm 2.3.1 update (required for Xorg1.5) specifically discludes some contentious patches being tested in trunk, as these were determined to be insufficiently stable and tested for an upstream release. [03:23] *nod* [03:24] Now, if imports were more flexible and were able to pull based on release tags for the upstream version identified in the version code, it might be rather useful. [03:25] Where versions are messy (e.g. 0.1+dfsg-3), the watch file ought contain a dversionmangle option to help determine the correct upstream version. [03:25] That depends on all upstreams properly tagging releases, but that's likely the sort of best practice we'd like to encourage anyway. [03:25] yeah [03:26] As an additional benefit, such a system is largely automated, so distro developers don't have to manually link things: they just complain to upstream that the branches aren't tagged properly, and it all automagically works. [03:27] persia: upstream might have different ideas about what "properly" means. [03:27] persia: but I agree that such a feature would be useful. [03:27] jml: Oh, certainly. I still think there's likely the possibility of there being a best practice for each common VCS. [03:28] for sure. [03:28] Much as most upstreams now release a $(sourcepackage)-$(version).tar.gz, rather than the mishmash we used to get, defining some standards and prosletysing can be fairly powerful. [03:29] Some upstreams will not comply, but if we could automate even 60% of it, and have it be correct and useful, it would be a huge step towards any sort of VCS adoption for distro packagers: without that VCS distro packaging is only interesting where 1) someone works with the same source regularly, or 2) a close team is making rapid changes to a single source package. [03:31] * jml jots down a few notes [03:31] And without VCS distro packaging, there's really no point to linking to upstream VCS, as one generally wants to grab the distro source anyway. [03:32] * persia wonders why "distro" ends in 'o' when it's short for distribution [03:33] persia: I'd like to credit it to an Australian influence [03:33] persia: but I'd just be making stuff up. :) [03:33] Heh. [03:34] Awww.. I thought there was some historical standard of -oifying things in Australian slang :( [03:35] Oh, there is. [03:35] We're all about the oing of words. [03:35] persia: well there is. [03:35] persia: but I couldn't chart it into the world of Linux distributions [03:35] RAOF: So jml is creating truth from the same substance that binds Fenris? [03:36] s/Fenris/Fenrir/ [03:36] ok, so on the changelog thing ... Launchpad currently only has record of 32 out of 51 entries since the package was first introduced into Ubuntu [03:36] persia: e.g. most Australians quickly find my given name, Jonathan, too cumbersome, and shorten it by default to Jono. [03:36] for gcompris that is [03:37] LaserJock: yeah, that changelog thing is best filed as a bug. [03:37] and it only has 32 out of the whole 114 entries that are present in the current Intrepid package [03:38] jml: One bug or two? There's the missing entries (likely from overliteral parsing of .changes files rather than checking the source changelog), and the lack of attribution for some changes. [03:38] yeah, I can at least understand the first one [03:38] because it's just grabbing the changelog entries for the versions *in* Ubuntu [03:39] but the lack of attribution is maddening [03:39] LaserJock: I suspect both have the same cause: there are ways to create a .changes file without the signature line. [03:39] there isn't any consistency to it that I can find [03:39] persia: two. [03:39] persia: hmm, well I wouldn't have though that I'd been changing how I've done .changes [03:40] *thought [03:40] LaserJock: Do you not sometimes pass -v and sometimes not? [03:40] or wait [03:40] yeah [03:40] the ones that are missing are new upstream releases [03:41] so I'd have put -v in [03:41] Also, I suspect some people pass -k even when they don't need to because they don't want to bother trying to get their changelog entry and key aligned, which might impact it. [03:41] I wouldn't have done that one I don't think [03:41] I suspect it'd be -v [03:41] * persia suspects there are other ways to make .changes suspect, but doesn't want to research it now [03:42] well, the plain fact of the matter is that it's rather stupid to not use the changelog for that kind of thing [03:42] the whole reason I write changelog entries is for people to read them!! [03:43] Well, maybe just pragmatic: one has the .changes file in the upload, but has to parse the source package to get the changelog. [03:43] yes, but that's being done anyway for changelogs.ubuntu.com [03:43] Well, yes, but by a different subsystem. [03:43] it's just trying to cut corners IMO and getting it wrong even [03:47] hmmpf, another bug to look at [03:47] maybe I'll get more done *not* being LP Liaison ;-) [03:47] i didn't think you were anymore? [03:48] that's what I'm saying [03:48] I've just found at least 3 bugs to file :-) [03:48] LaserJock: I have to confess, I didn't realise there was such a thing until I heard you were leaving :) [03:48] oh, right, maybe you'll get more done on *launchpad* when not being the liason [03:48] jml: yes yes, I certainly didn't do as thorough of a job as I probably should have [03:49] LaserJock: oh, that hadn't occurred to me :) [03:49] jml: however, since I was also an LP bug contact I saw a lot of what you guys were doing [03:49] LaserJock: it's just that most of the time I've got my head down in a pile of codehosting stuff :) [03:49] and frankly, not a ton of the bugs I did file got fixed [03:50] in fact, I'm not sure that *any* LP bug I've filed has every gotten fixed [03:51] LaserJock: oh, i'm sure maybe one did. somewhere. sometime. [03:51] either htat, or you don't file enough launchpad bugs. [03:51] heck, even wgrant and i have managed to get a few bugs marked "critical" (many months after filing, but that's another gripe) each [03:52] well, usually mine never make "critical", I just +1 you and wgrant's ;-) [03:52] heh [03:52] and of course in trying to see if any of my bugs have been fixed I've run into another one [03:52] i try not to file them now though, tbh. [03:52] for the reason you cited. [03:53] can you really *not* do an advanced search on reporter? [03:53] :) [03:53] LaserJock: https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=laserjock&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.omit_dupes.used=&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&search=Search [03:53] or a search on a person at all? [03:53] ah, I figured it out, you have to go to your personal bug page first and then do it [03:53] no you don't [03:53] LaserJock: Visit that person's page, and click on their reported bugs. [03:54] jml: that's not available from the advanced search is it? [03:54] LaserJock: that's where I found it. [03:54] I don't know I'm getting myself confused [03:54] :-) [03:54] LaserJock: https://bugs.edge.launchpad.net/launchpad-project, "Advanced search" [03:55] LaserJock: "Reporter" is in the right column of "People" [03:55] jml: the idea would be to have the reported bugs from any project, no [03:55] ? [03:55] Hobbsee: the initial question was about Launchpad bugs, I thought [03:56] ok, I'm totally lying though [03:56] 4 out of 16 LP bugs I've files have been fixed [03:56] *filed [03:56] jml: i think it was, but i took [12:53] can you really *not* do an advanced search on reporter? to be a separate thing :) [03:56] LaserJock: that's doing pretty well. [03:56] LaserJock: that's probably better than my and wgrant's ratio. [03:56] in fact, i'm sure ti is. [03:56] Hobbsee: Fix-it-Friday's [03:56] Hobbsee: oh. [03:56] I pick easy ones [03:57] LaserJock: heh. some of my bugs that are easy, like adding a checkbox, still are waiting from gutsy development. [03:57] jml: it apears you can't do an advanced search on a report *from* the reporter's page [03:57] they'll hit their 1 year aniversary in a few months [03:57] LaserJock: oh, right. [03:57] LaserJock: that sucks. [03:57] jml: it was smart enough to know that I was already there [03:57] oh, that doesn't suck then :) [03:58] but they're on a mostly-unused section, so it's understandable [03:58] fwiw, 56 / 139 for me [03:58] jml: well done! [03:59] my oldest one is "High" and was filed 2007-03-25 [03:59] oldest open one [04:00] though I guess maybe the Bug Janitor needs to get it 'cause it's Incomplete [04:01] * Hobbsee wonders if the stats are any better on launchpad questions now [04:02] speaking of that rotten janitor. [04:06] hmm. i'm sure i reported more than that. === sm1 is now known as sm [04:07] 14 not fixed, 1 invalid, 8 fixed. 23 total. [04:08] 1 high, 2 critical [04:09] ah, + 2 dupes [04:10] well, I found changelog entries at /ubuntu//+source//+changelog [04:10] but there's no /ubuntu/+source//+changelog which is sort of weird [04:11] Hobbsee: I would have thought you'd reported more than that. [04:11] LaserJock: It's also not reliable, as changelogs aren't necessarily in series between releases (and actually may not be in series within a release, but that's not usually as important) [04:12] LaserJock: Unless you'd expect it to go to the current source package? [04:12] jml: yeah... [04:13] persia: hmm, and apparently during syncs the sync requester get's the attribution for the Debian changelog entry :-) [04:14] LaserJock: Yep. This is good for Ubuntu tracking purposes, but clearly wrong for changelog purposes. [04:15] We could do better to differentiate "Changed-By", "Uploaded-By", and "Changelog-By", but it's confusing. [04:15] If we rely entirely on the changelog, we lose track of who requested the sync. [04:15] agreed [04:16] but I think it could be fairly reasonably worked out [04:16] As it is, there's still some confusion as to whether it is supposed to be the requestor or the approver, and different archive-admins do it differently. [04:16] Changelog-By should get the credit for the upload [04:16] (note that in many cases, the requestor and approver are the same party) [04:17] LaserJock: For syncs? Should Changed-By: be mangled? If it is mangled, whose name goes there? Anyway, I think it needs more general thought before launchpad can be expected to handle it sanely. [04:17] if Changelog-By != Changed-By or Uploaded-By then other fields should be filled in (Synced By: ? and Sponsored By:) [04:18] the problem is that a simply attributing an entire package version to 1 person doesn't suffice [04:19] that Changelog-By might not be the same as Change-By which might not be the same as Uploaded-By needs to be taken into account [04:20] Well, if you want to get complicated, what about team-maintained packages where Changes-By is different than Changelog-By is different than Changed-By, is different than Uploaded-By? [04:21] hmm, I'm not sure I follow that case [04:21] you mean if there are multiple people in the changelog entry? [04:22] Yes. [04:22] well, that is a point [04:22] e.g.: someone makes changes, a DD sponsors it, the changer makes a sync requests, a MOTU sponsors it, the archive admin pushes it, what does LP display? [04:23] hmm [04:25] The point being that it's hard, so I'm very much unsure of what is correct behaviour. That said, it's a bug if no name is displayed, and a bug if entries are missing. [04:27] I think Changelog-By = Debian changelog , Changed-By = sync requester, Uploaded-By = signer [04:28] s/signer/approver? [04:29] How about the multiple people who changed the package, none of whom may be the changelog author? [04:34] I personally don't think we need a sync approver field [04:34] in the case of a sync I think Uploaded-By could be blank, or perhaps be Archive Admin to show it was synced by them perhaps [04:35] well, I think we can get very complicated with it [04:35] tracking Maintainer:, Uploaders:, etc. and getting out every person who touched the package at all [04:37] but the essentials as I see it are attributing upstream, current "changer", and uploader [05:49] wow. tabs eh? === wormsxulla___ is now known as wormsxulla [06:30] Can anyone give me a clue on what OOPS-922CEMAIL1 was caused by? [06:31] gnomefreak: Signature couldn't be verified: (7, 8, 'Bad signature') [06:32] mwhudson: there isnt anything wrong with my key it works most of time and always has worked until sometime on the pre-release for 2.0 (i think thats next version [06:33] its been only the last week or so that im getting failures [06:35] that bug listed one of my posts from email but wouldnt do this bug [06:35] gnomefreak: the signature is definitely bad [06:35] gnomefreak: i don't really know enough about gpg to say why [06:35] mwhudson: than i shouldnt beable to sign any malone mail [06:35] https://bugs.edge.launchpad.net/ubuntu/+source/firefox-3.0/+bug/246694 [06:35] Launchpad bug 246694 in firefox-3.0 "Can Not Uninstall Add-Ons" [Undecided,Incomplete] [06:36] that has one from me the other one would be last one but you dont see it [06:36] gnomefreak: the mail looks a bit oddly wrapped, maybe tbird is screwing you over? [06:36] what do you mean as oddly wrapped i knwo what it means but what do you say that makes you think that? [06:37] uh [06:37] gnomefreak: that didn't make a lot of sense [06:37] in the oops report, i have a link to your original mail [06:37] if i download it, gpg refuses to verify it [06:37] mwhudson: you said its oddly wrapped what makes you think its oddly wrapped [06:37] and if i look at it, it looks like this: [06:38] sharshabeeeel wrote: [06:38] > Thank you John but the flashplugin-nonfree has been previously removed [06:38] using Synaptic Package Manager. [06:39] being on different lines shoudlnt matter its still able to be read and emailed and i know my signature is good since well you can see on bug report it let one go through but not this time [06:39] well i don't know [06:40] i would guess that somehow the mail got mangled en-route [06:41] gnomefreak: and, heh, if i manually put the long lines back together, the signature is good [06:42] that makes me think its Tbird, Maybe i use tbird 3 once i get caught up [06:49] holy cow, my edge just changed :-) [06:50] I just noticed the new tabs [06:51] * Hobbsee pokes edge. [06:51] yes, you do want to load [06:51] * Hobbsee blinks [06:52] \o/ the useful panel moved up [06:52] and, uh, yay for cascading multiple horizontal menus... [06:53] i just noticed that as well [06:53] interesting design decision... [06:53] * gnomefreak can do without the right handed menu but i guess i have to get used to it [06:53] heh, that made me chuckle [06:54] originaly they were on the right, then they were moved to the left [06:54] now they're back right [06:54] oh [07:26] OOPS-923D576 [07:26] https://devpad.canonical.com/~jamesh/oops.cgi/923D576 [07:27] Oh, right, I forgot, devpad requires HTTP auth. [07:27] Working now, so never mind. [07:32] hello Hobbsee [07:33] ooh shiny [07:34] * mwhudson off for the weekend [07:35] mwhudson: Have a nice weekend. :) [07:36] Huh, in bug displays, the related branch has been moved below the summary. [07:37] I don't like the new layout. It's a lot of white space with links and little icons and everything else all strewn about. [07:44] Hm. I think I like the new tabs. [07:47] i like the look [07:47] i haven't tried it enough to know if it works well [07:48] is it just me or is the middle of the footer a weird place for the search field? [07:48] that seems very odd [07:49] No, I think that's a strange place, too. You're not alone. [08:04] Can sombody please abort the import of https://code.launchpad.net/~vcs-imports/gnucash/trunk (the admin of the server is complaining about excessive use of bandwidth) and use http://wwwcip.informatik.uni-erlangen.de/~siretart/gnucash/svn-repo.tar.gz for the initial setup instead? mwhudson? [08:06] Laibsch: mwhudson just left. [08:06] * Peng leaves too. [08:07] peng anybody else you recommend? [08:07] mwhudson not in London time zone? [08:07] Laibsch: try with one of this people: https://launchpad.net/~vcs-imports/+members [08:08] thanks [08:08] you're welcome [08:10] ping lifeless, thumper, rockstar, jml about gnucash import six or seven lines above. please abort the download and use the tarball instead [08:13] Laibsch: I've suspended the import. [08:13] jml: thanks [08:13] can you also import from the tarball? [08:13] Laibsch: I can't kill the currently running job though [08:13] Laibsch: I personally can't. [08:14] where should I file the request for that? [08:14] Laibsch: mwhudson may be able to, but it's dinnertime on a Friday night for him. [08:14] Laibsch: ask a question on Launchpad-Bazaar [08:14] Oh, asia? [08:14]