=== thumper-afk is now known as thumper === rickspencer3 is now known as rickspencer3-afk === thumper is now known as thumper-fud === thumper-fud is now known as thumper [02:30] I want to start a project. It's taking something that's being developed in git and modifying it signaficantly. I doubt we'll continue on this project once our efforts are merged into the main branch. So it will be somewhat displosable... Any suggestions for how to handle it? [02:50] MTeck: request a git import for the project [02:50] MTeck: then you can work with the bzr copy [02:51] thumper: I was just wondering if I should make a whole new team for it [02:51] MTeck: so your changes are intended to be merged back into the git trunk? [02:51] hope so [02:51] MTeck: well, register the project in LP, request a git import and mark it as the trunk branch [02:52] MTeck: what is the rationale about wanting a team? [02:52] MTeck: individuals can work colaboratively too without teams [02:52] It's a few people that will be working on the project [02:53] I think just 4, but I don't want access to trunk to be given to just one person [02:53] MTeck: sure, register a team, it's pretty simple [02:53] MTeck: well, trunk will be owned by ~vcs-imports initially [02:53] MTeck: your version can be owned by whomever you want [02:53] I was mostly concerned if it would be worth the new project [02:54] Thinking about it - it might be [02:54] if you are intending your code to be merged back [02:54] I don't see the point of a new project [02:54] it is just new work for the existing project [02:54] oh, ok [02:54] that may or may not be merged back [02:54] if the direction changes and effectively forks [02:54] I have the new team - no project until I click a button [02:54] then it is worthwhile registering a new project [02:55] I doubt a fork will happen :P [02:55] in which case [02:55] stick with the original project [02:55] ok [02:55] so.. how do I request the merge? [02:55] import* [02:56] MTeck: which project? [02:56] coreutils [02:57] MTeck: https://code.edge.launchpad.net/code-imports/+new [02:57] oops [02:57] not that [02:57] I lost something :( [02:57] was it my mind? [02:58] MTeck: https://code.edge.launchpad.net/+code-imports/+new [02:58] so - I need to create a project for it then? [02:58] there is a coreutils project [02:58] The Gnu Core Utilities [02:58] is that it? [02:58] ok [02:58] ya [03:01] now I just wait? [03:01] yep [03:01] MTeck: shouldn't be long [03:02] thumper: then I can be given the repo? [03:02] MTeck: the import is running [03:02] MTeck: I can't remember if we email you when it is done or not :) [03:05] Are there currently problems with the remote bug watching for gnome bugzilla? [03:05] arand: not sure sorry [03:05] spm: any idea? [03:08] I noticed Bug #246177 [03:08] Launchpad bug 246177 in gnumeric "gnumeric help on plot log scale unclear" [Medium,Triaged] https://launchpad.net/bugs/246177 [03:09] thumper: so that machine is doing 3 imports. [03:09] " Launchpad couldn't import bug #563275 from GNOME Bug Tracker. " [03:09] Error: Launchpad bug 563275 could not be found [03:09] lp is confusing - always new features [03:11] what is a heartbeat? [03:11] MTeck: we could slow down if you like? [03:11] thumper: I know in passing that gmb has been doing some things around the watcher (or so I construed), but to actual issues - not aware of any. [03:11] MTeck: it means that the import slave is alive :) [03:11] MTeck: if we stop getting heartbeats, it has zombied, so we kill it :) [03:12] thumper: What is a heartbeat though? [03:12] MTeck: it is the import slave talking to the import controller [03:13] oh [03:15] thumper: you've had an import runnign for 1/2 mo ? [03:15] MTeck: heh, that's the linux kernel [03:15] MTeck: we try it every now and then [03:15] lol - how long does it usually take? [03:16] MTeck: well, the new bzr repo format should make that go much faster [03:16] MTeck: we normally kill it before it has finished [03:18] YOu should move "Last heartbeat" to the right a few spaces [03:18] MTeck: the new 3.0 layout has changed some things [03:18] MTeck: table padding is one [03:18] MTeck: we will be fixing it soonish :) [03:19] whenever the new layout is finished? :P [03:20] MTeck: it should be for 3.0 [03:20] in about 3ish weeks [03:20] cool [03:20] This import is going to take a while, isn't it? [03:21] * thumper looks again [03:22] MTeck: yes [03:22] at least I started now instead of when I needed it :P [03:22] any guesses how long? [03:25] So, after the import, do I just take ownership of the branch and if I ever need, request an import of a fresh one? [03:41] MTeck: well it started 40 minutes ago and is 1/3 through [03:41] MTeck: so check back in 1.5h [03:41] ok, cool [03:41] and the last question? :) [03:41] thumper: thanks for checking too [03:42] MTeck: no, the import will track the changes [03:42] MTeck: you branch it and have a personal copy [03:42] MTeck: you should set the import as the development focus [03:42] MTeck: actually you can't, it is owned by registry admins [03:42] ok, thanks [03:42] spm: can you set the import as the dev focus for coreutils? [03:43] hello [03:43] new here === jon is now known as Guest23179 [04:15] Could someone change the permissions on this blueprint: https://blueprints.launchpad.net/giftwrap/+spec/use-libunique I am a member of the giftwrap-devs and I cannot edit this blueprint, I can edit all of the other ones. [04:16] I think it is because there used to be a different team that that branch was registered under. [04:26] Any lp admins on? [04:28] days_of_ruin: if no one answers, you can file a request here: https://answers.launchpad.net/launchpad [04:30] days_of_ruin: You need to file a request for something like that anyway [04:30] afaik [04:31] MTeck, ok thanks for the info. [04:32] days_of_ruin: oh - I call the lp admins "rubber duckies" [04:32] lol [04:32] why? [04:34] days_of_ruin: look at the bottom - https://edge.launchpad.net/~spm [04:35] xD [04:37] days_of_ruin: it is the icon of the admin team :) [04:37] thumper: https://edge.launchpad.net/~hardware-certification [04:37] s/towards/toward/ [04:38] MTeck: what about it? [04:38] thumper: I just thought I'd let somebody know it's wrong [04:39] towards isn't actually a word [04:41] MTeck: yep it is [04:41] kinda depends who you ask [04:41] I'll check my shorter oxford later [04:41] maybe a us/uk thing? [04:41] No - an English vs. Bad English thing [04:42] http://en.wiktionary.org/wiki/toward#Usage_notes [04:42] it's like when people say probly instead of probably [04:42] MTeck: no it isn't [04:43] ok.... [04:43] however [04:43] * MTeck world has been flipped [04:43] launchpad is mostly us-ian english [04:44] mwhudson: thanks for that link [04:44] I need to run off now [04:44] towards something, perhaps... [05:04] mthaddon: heh [05:05] :) [05:57] Hmm, Launchpad is confused about me upgrading a hosted branch to 2a. [05:58] spiv: how so [05:58] lp:~spiv/bzr/insert-stream-check-chk-root is now 2a. It is stacked on lp:bzr/2.0, which is also 2a. But LP says: " [05:58] lp:~spiv/bzr/insert-stream-check-chk-root is now 2a. It is stacked on lp:bzr/2.0, which is also 2a. But LP says: "CHKInventoryRepository('lp-mirrored:///~bzr-pqm/bzr/2.0/.bzr/repository') is not compatible with KnitPackRepository('lp-mirrored:///~spiv/bzr/insert-stream-check-chk-root/.bzr/repository') different rich-root support [05:58] « No branches proposed for merging into this one. " [05:59] spiv: hey, the puller is open source now, feel free to fix it :) [05:59] The wrong piece of that puzzle would appear to be that lp-mirrored:///~spiv/bzr/insert-stream-check-chk-root/ is apparently not upgraded. [06:00] spiv: i guess we're trying to open the branch in it's mirrored area to determine it's format [06:00] and of course, if we could open it, we'd find it was different from the format in the hosted area and delete it [06:00] heh [06:01] oops [06:01] \o/ finally have tests for this annoying email bug [06:01] thumper: are you working on the merge proposal listing bug? [06:01] no [06:01] poolie elevated it to critical [06:01] and I reduced it to high [06:01] ok [06:02] mwhudson: oh, so the issue is that it needs to open it to find out the format, but because the branch is now unopenable because the stacked-on is now incompatible, it all falls over in a big heap? [06:02] spiv: that's my guess [06:03] spiv: haven't looked at the code yet though [06:03] mwhudson: that can probably be worked around by opening just the repository directly, I guess. [06:03] spiv: we want to check the branch format too though? [06:03] mwhudson: sure, but if the repository formats don't match you don't need to check the branch :) [06:03] i guess [06:04] Alternatively, [06:04] There's an ignore_fallbacks flag on open_branch now. [06:04] except errors.NotBranchError: [06:04] You could probably use that. [06:04] -> except (errors.NotBranchError, whatevers raised here): [06:04] in puller/worker.py:310 would also do it [06:04] but it's a bit of a hack [06:06] mwhudson: I'll file a bug I guess. This is pretty important though because it means no existing 1.9 bzr branches that are stacked can be upgraded. [06:06] * mwhudson points spiv at his build engineer hat [06:07] spiv: but yes [06:07] mwhudson: that would be a hard hat, I suppose. [06:07] spiv: it has special attachments to collect the tears of blood [06:14] mwhudson: would it be excessively rude to file it with Critical priority? [06:15] spiv: yes [06:15] spiv: high is fine [06:16] thumper: So "high" would merely be rude, rather than excessively so? ;) [06:16] :) [06:16] thumper: #424136 [06:16] spiv: do you know how to fix this? [06:17] spiv: because to speed it up we could get some branches copied to staging, and try it there [06:17] thumper: yes; see the conversation I just had with mwhudson or the bug description [06:17] spiv: feel free to provide a branch that fixes it :) [06:17] spiv: and I'll support the criticality of it [06:42] thumper: it doesn't look like the import finished correctly [06:42] it ran 3hr 20min [06:42] http://launchpadlibrarian.net/31298189/coreutils-ddhash-log.txt [06:46] gah - how do you guys pick server names :S [06:50] depends on how vindictive the dce is feeling when it comes time to name them [06:50] dce? [06:50] data centre engineer [06:51] galapagos isn't so bad - but neumayer and russkaya .... [06:51] way over my head [06:51] some of the others are just way out there too :P [06:51] mind you... we typically use ssh cmd completion so it's no such a big deal ;-) [06:52] praseodymium aka prasé [06:52] ? [06:52] I've tried learning other languages - never could [06:52] spm: so the acute on that é is the notation for where to use TAB completion? ;) [06:52] is one of the ... controller servers fwiw. [06:52] 2 years and all I have is , mas cervas por favor [06:53] adn puedo ir al bano [06:53] spiv: nah, was james having a troll at mwhudson and myself when we started shortning praseodymium to prase. he felt it had earnt the é :-) [06:53] MTeck: all the importd slaves are named after antartic research stations [06:53] oh [06:53] fwiw [06:54] I'd name them like importslave01 [06:54] MTeck: I didn't know you were studying accountancy at Uni? ;-) [06:54] hm? [06:55] call it the zen of sysadmin. always give servers real names. not numerical ones. they tend to be... cared for??? better. [06:55] I've been studying accounting - failed two classes so far [06:55] MTeck: my meaning being that only accounting/managerial types tend to want "professional server names". [06:55] I wouldn't really name them like that - I do like simple names though [06:56] like carpo, sermo, inferno, etc [06:57] oh - yes, I do likey the latin spins [06:57] having real names has the advantage that the servers are... distinct. You dont get gobbledegook like CBTG01FP07 [06:57] you mean like what happens in windows? :P [06:57] no comment [06:58] :-) [06:58] C3P0 and R2D2? [06:58] every server name I get has some light spin from this - http://www.math.ubc.ca/~cass/frivs/latin/latin-dict-full.html [06:58] heh. nice! [06:58] minerals was one prior favourite [06:59] I'm just thinking - if I had a honeypot system, what would I call it [06:59] I did laugh at how the Centre for Information Technology Research named all their machines after fruit. CITR == citrus == fruit. [06:59] winnie [07:00] corip is what I would name a honeypot system [07:00] corripio : to seize, snatch up, steal, (of a disease) attack [07:02] I just like short easy to pronounce names :P [07:03] spm: that's interesting [07:08] MTeck, prase is a terrible name :) === abentley1 is now known as abentley [08:21] hi all [08:21] launchpad/code: registering a new branch [08:22] what's the difference between 'hosted' and 'mirrored' choice? [08:22] mirrored means that launchpad will pull the code from somewhere else [08:23] hosted means you will push the code with bzr directly to launchpad [08:23] does it have to be another bzr repository or can it be github ? [08:23] if you want to host code directly on launchpad, you don't actually have to "register a branch", you just need to push to lp:~// [08:23] dreamcat4, if you want, you can import a branch from github. [08:24] radix, that's pretty cool [08:24] okay looks like i should go the hosted route [08:24] thanks all [08:25] actually... i have written up a page about bzr-git importing [08:25] http://dreamcat4.jottit.com/working_together_-_git_and_bzr [08:25] you are welcome to put it in the ubuntu wiki [08:39] Hi [08:40] I#ve a question about projects and translations [08:40] someone here who can answer? [08:41] uwesch: please post the question first :-) [08:42] dpm: okay ;) [08:43] I am a translator in the inkscape project https://bugs.launchpad.net/inkscape [08:43] there is a button "Translatins" but there is nothing inside [08:44] i would like to use this for my translations [08:44] Who can help here? [08:46] uwesch: I seem to remember that inkscape does not use Launchpad for translations. They only use it for bugs. Let me check... [08:46] i know [08:47] and i don't know how other translation teams work together [08:47] I'm in the German Team and i would like to use launchpad for translation issues [08:47] oh, I understand your question now... [08:48] well there would be 2 options, if I'm not mistaken: [08:50] okay? [08:50] uwesch: https://help.launchpad.net/Translations/ [08:50] uwesch: https://help.launchpad.net/Translations/YourProject [08:51] 1) Only inkscape upstream can decide on this, so you could contact them and convince them to use Launchpad for translations [08:51] henninge: thx [08:52] henninge: he's not upstream, though. He's a translator and would like to use LP for inkscape translations (which are not currently in LP) [08:52] uwesch: you can point upstream to the links henninge showed you === vorian is now known as s8n [08:54] okay, thank you [08:58] uwesch: or 2) you (or upstream) can create a translation group (https://translations.edge.launchpad.net/+groups/) for inkscape and have it translatable in LP only for those teams who wish to use LP (see Gnucash as an example -> https://translations.edge.launchpad.net/gnucash). I've never done this myself, so I cannot help you much with the details, but danilo, henninge or jtv might be able to assist you if you'd like to go down that route [09:00] dpm: ah, ok. I did that out of reflex .... ;) [09:01] :-) [09:08] thanks a lot [09:09] hi [09:10] uwesch: and one last note: for 1) getting upstream's translations into Launchpad would be as easy as mirroring upstream's SVN repo from http://inkscape.svn.sourceforge.net/viewvc/inkscape/ in a bzr branch in LP and importing their translations. And with the new "commit translations to branches" feature, they could even set up a bzr branch where translations can be committed to automatically and they can then import them to their SVN [09:10] But upstream would have to decide on that [09:11] i need to delete a team... :/ and send every current member a message, there's no mailing list configured for the team... can someone help me please? [09:11] dpm: I've to talk to the maintainers of the inkscape project ;) [09:12] uwesch: sure, I just wanted to let you know the options :) [09:12] philn: Only an admin can delete a team, but you can easily email all the members if you're a member. [09:12] philn: https://launchpad.net/~someteam/+contactuser [09:13] i am admin [09:13] philn: A Launchpad administrator, sorry. [09:13] ok [09:13] philn: You can ask somebody to deactivate the team for you at https://answers.launchpad.net/launchpad/+addquestion [09:14] ok [09:14] i'll first send the goodbye message [09:19] uwesch: I looked at the inkscape translations [09:19] uwesch: it looks like it would be pretty easy to start using Launchpad Translations. [09:19] henninge: really? [09:20] uwesch: They already generate a template file [09:20] uwesch: inkscape.pot in http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/po/ [09:20] i'm trying to log in to the wiki... but the connection page keeps loading, endlessly [09:20] okay. so what would be the next steps? [09:21] uwesch: to setup code imports into Launchpad from that svn repository [09:21] uwesch: and then activate translation import from bzr [09:21] bzr? [09:21] uwesch: bazaar [09:22] ubottu: http://www.bazaar-vcs.org/ [09:22] Error: I am only a bot, please don't think I'm intelligent :) [09:22] uwesch: ^ [09:22] ;) [09:23] uwesch: when the svn repository is imported into Launchpad it is converted to bzr. [09:23] a bazaar repository, I mean. [09:23] uwesch: and Launchpad Translations can import directly from there. [09:23] uwesch: BUT [09:24] never heared about a bazaar repository [09:25] uwesch: to use the translations made in Launchpad, they will have to be exported again and then merged into inkscapes svn repository. [09:25] uwesch: yeah, we were discussing that problem on the mailing list .... ;-) [09:25] uwesch: I mean, that not enough people even know a about Bazaar. [09:26] uwesch: Bazaar is a great alternative to subversion. [09:26] uwesch: it is a distributed version control system, not centralized like subversion is. [09:27] uwesch: anyway, I am sure the inkscape people do know about it since they seem to have been working with Launchpad for longer. [09:27] uwesch: You might hear a common prejudice (Voruteil) concerning Launchpad Translations [09:28] uwesch: Vorurteil [09:28] meine Güte [09:28] predjudice [09:28] pardon my spelling, English and German ;) [09:28] wir können auch deutsch reden ;) [09:37] uwesch: The predjudice is that Translations in Launchpad are bad because anybody can add translations. [09:37] uwesch: that is OLD and has been fixed a long time ago. [09:37] okay, that make sense [09:38] i should really takl to the maintainers of the inkscape project [09:38] uwesch: Launchpad Translations has mechanisms in place to let anybody make *suggestions* which are then approved by the core translators. [09:39] uwesch: yes, you should. Maybe there are other translations teams for incscape that would like to use Launchpad, too. [09:39] uwesch: raise it on the mailing list [09:39] I assume there is one ;-) [09:39] henninge: that's a very good idea, thank you [09:40] uwesch: my pleasure [10:42] Hi people [10:43] Is the server hosting bazaar's web interface down ? I can't browse revisions at the moment [10:43] Hi all. Does LP provide read-only mirrors of bzr branches, or are all branches on LP read-write? [10:47] Kamping_Kaiser: they're all read/write, but only by the user the branch belongs to [10:48] Kamping_Kaiser: so, ~intellectronica/launchpad/my-branch is read/write to me, but read-only to you [10:48] Kamping_Kaiser: and ~kamping_kaiser/yourproject/yourbranch is read/write to you but read-only to me [10:49] Kamping_Kaiser: you can use teams to make a branch that is read/write for more than one user, but the usual model is that another user should branch and then offer the changes for merging, rather than modify trunk directly [10:50] intellectronica: thanks for that. it all sounds sane enough. :) === bac changed the topic of #launchpad to: Launchpad is now open sourced: https://dev.launchpad.net/ | Help contact: bac | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com/ | irc://irc.freenode.net/#launchpad-dev is the developer channel [11:01] Hello Launchpad. I'm the help contact today. Please contact me with your questions. === wgrant_ is now known as wgrant === bigjools-afk is now known as bigjools [12:16] hi [12:16] why 'ubuntu' as project in not valid in Also affects project ? [12:16] Kmos: It's a distribution, not a project. [12:19] ah ok.. how could I assign a bug to the team who takes care of ubuntu launchpad page? bug 421078 [12:19] Launchpad bug 421078 in apport "no "apport-collect" link on bug pages" [Undecided,New] https://launchpad.net/bugs/421078 [12:19] or subscribe [12:20] I'm not sure if ubuntu drivers are acorrect [12:23] Kmos: you'd want to file that against Soyuz. [12:23] lfaraone: No, Soyuz is not relevant here. [12:23] lfaraone, KmosL actually, that has nothing to do with soyu [12:23] wgrant: sorry, I mean malone. [12:24] lfaraone: you can't add apport-collect to every project in launchpad [12:24] Kmos: but it'd need to be modified in malone. [12:24] lfaraone is right. [12:24] Kmos: next week, we're going to disable bug filing via the web interface, and point users to a wiki page with clear instructions on how to use these tools. i think that pretty much covers what you're asking for? [12:24] lfaraone: see my comment in the bug report, that can be avoided [12:25] intellectronica: This is from within within existing bugs. [12:25] intellectronica: sure [12:25] if you add some extra text about existing bugs [12:25] Kmos: I think intellectronica is kidding. [12:25] lfaraone: i am very serious, actually [12:25] intellectronica: Oh? Hm. [12:26] wgrant: i don't understand, is the suggestion that we display information on how to add more information using apport-collect on bug pages for existing bugs? [12:26] intellectronica: Precisely. [12:26] intellectronica: Yes. [12:26] hmmm ... that's an interesting idea [12:26] intellectronica: or better yet, add something akin to "apt:" which calls on apport from a browser. [12:27] well, file the bug on malone, we'll have to think if that's really something we want to do, but it's not a bad idea [12:27] intellectronica: that'd be harder, but prolly a good project for next year's GSoC [12:27] ok [12:27] Kmos: I added malone to the bug. [12:27] we write code all year round. lfaraone, if you want to jump in and contribute a patch i'll be happy to help [12:28] but let's wait a bit until we're sure we actually want this feature and how it's going to be designed [12:28] intellectronica: if I had 5usd for each time I said "hey, that'd be a cool project to do when I'm free", I wouldn't have to worry about paying for college :) [12:28] lfaraone, Kmos: thanks [12:28] lfaraone: I saw it now =) thanks [12:28] np [12:28] Kmos: glad to help, sorry for the initial misdirection. [12:29] I think we need it to be enabled only in some distributions. (x)ubuntu [12:29] Kmos: that'd be the easy part :) [12:29] hehe [12:29] lfaraone: oh, you don't get five bucks whenever you have a good idea? here in europe we do. it's part of the comprehensive health care system ;) [12:30] intellectronica: yeah, but you end up paying 4.99$ of it back due to VAT ;) [12:30] :) [12:31] loll [12:37] lfaraone: you can edit the target of a bugtask instead of creating a new one, FYI [12:37] soyuz is going to get bugmail now :( [12:38] until deryck fixes that ;) [12:39] This is why we have the null project. [12:41] bigjools: well, I marked it as invalid. [12:41] lfaraone: I saw - but unfortunately it will still get bug mail :( [12:41] bigjools: that's silly. [12:41] yep [12:53] um.. is there anything wrong the doubah machine? [12:54] (ppa) https://answers.edge.launchpad.net/launchpad/+question/81881 [12:55] sav: That's impressive, but nothing to do with that particular builder. [12:55] Oh. [12:55] erm.. [12:56] * Builder: https://launchpad.net/builders/doubah * Source: not available [12:56] That's probably the buildd-manager race thing again. [12:56] bigjools: ^^ [12:57] sav: So, everything is OK, except the build status. The binaries are built and published. [12:58] thanks for helping! :) [12:58] wgrant: I just noticed that https://launchpad.net/builders/doubah says the builder deactivated. Should I just rebuild it? [12:58] wgrant: remind me what that was again? === matsubara-afk is now known as matsubara [13:00] bigjools: buildd-manager sometimes races with itself and dispatches a successful build a second time. [13:00] ah the double build [13:00] yeah [13:00] thought that was fixed. [13:00] sav: No need. It's all fine now, but will fail the same way if you retry. [13:00] hm [13:00] Maybe get cprov to beat that build over the head when he wakes up. [13:00] (ie. fix the status up) [13:01] bigjools: So did I. [13:02] wgrant: ok, thanks, I'll just leave it there, I have to get the next package ready. I won't touch it for the next 3-4 days (or even more heh) [13:03] sav: The only problem you'll see is the red X on your PPA page. Everything else is fine. [13:03] ooohh alrighty then :) === cprov-afk is now known as cprov === rickspencer3-afk is now known as rickspencer3 === jacob_ is now known as jacob === salgado_ is now known as salgado === fjlacoste is now known as flacoste [15:06] Hi, I'm trying to set up my own PPA. I want to have daily builds of Digikam in my PPA. I'm wondering how to upload the source code to my PPA. I can only upload .changes files [15:06] cumulus007: https://help.launchpad.net/Packaging/PPA/Uploading [15:06] I read that, but that doesn't help me. It says I can only upload .changes files [15:07] no it doesn't :) [15:07] "Dput uploads the following files: " [15:07] yes I see, but can it upload source code in a tar.gz archive? [15:07] cumulus007: no, source packages don't work like that [15:08] hm okay, I'll read https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage then [15:08] you need to read about debian packaging [15:08] great [15:08] cumulus007: let me know how you get on [15:08] sure :) [15:12] I wonder if vcs will ever finish importing this package :( [15:21] Hey, when I want to upload a patch to launchpad which files are needed? [15:21] c0rtis0n: #launchpad-dev can help you better [15:21] thx [15:23] bigjools: debian packaging is complicated :| [15:23] Öhm sry but i thought -dev is for Launchpad-development only? What i ment were that i want to patch a bug wich is reported at launchpad [15:23] yep :/ [15:23] hi! [15:27] c0rtis0n: bug number? [15:30] MTeck Bug #158784 (I'am tkranz there...) [15:30] Launchpad bug 158784 in cowbell "Typo in the translation makes cowbell writing wrong titles" [Undecided,New] https://launchpad.net/bugs/158784 [15:32] c0rtis0n: oh - Click "Add an attachment", add a comment, pick your patch file, then click the check box "This attachment is a patch" [15:34] I just don't know what the patch file is exactly... the diff.gz, the .dsc file, both or ist just the .fix file needed [15:34] combine them into a tarball [15:35] ok thank you very mcuh [15:36] All they probably need is the diff.gz - but you may as well give them the whole thing [15:38] I've uploaded the tarball now. Thx again. [15:52] bigjools: I don't understand how to make a source package. I downloaded the latest revision of the digikam trunk and what should I do next? according to the ubuntu Wiki, I should download a pre-made debian source package but of course that isn't available for digikam trunk [15:52] cumulus007: have you looked to see if someone has already built a package? [15:52] well I don't think so because it's trunk [15:53] I suggest you start with an existing package [15:53] and update it [15:54] that's a good idea [15:54] then amend debian/control to change the version to something more appropriate for your PPA [15:54] Mez: So... how've you been? [15:54] where can I find source packages? Do I have to enable the "source code" checkbox in Software Sources? [15:54] cumulus007: yes [15:54] Okay :) [15:58] bigjools: I enabled it, reloaded my package lists but there is still can't find a digikam source package [16:00] cumulus007: apt-get source digikam [16:03] bigjools: lol forgot about that, it's downloading :) [16:05] bigjools: done. All I have to do now is to package the trunk into a tar.gz archive and rename it to a orig.tar.gz file? [16:06] something like that, but check the package. your best bet now is to ask in #ubuntu-motu for more packaging advice [16:07] Okay, thanks for the help :) === deryck is now known as deryck[lunch] === salgado is now known as salgado-lunch === danilos is now known as Guest54570 === danilo_ is now known as danilos === flacoste is now known as flacoste_lunch === rickspencer3 is now known as rickspencer3-afk [17:19] You guys think this will ever finish? https://code.edge.launchpad.net/~vcs-imports/coreutils/ddhash === thunderstruck is now known as gnomefreak === rickspencer3-afk is now known as rickspencer3 [17:30] henninge, jtv, Ursinha, danilos hi! [17:30] hi emma :) [17:30] :) [17:32] heya emma :) [17:32] Hehe :) === matsubara is now known as matsubara-lunch === deryck[lunch] is now known as deryck [17:44] Ursinha: You know anything about vcs-import? [17:44] MTeck, what exactly? [17:44] (hi, btw :)) [17:44] hi :), how've you been? [17:44] Ursinha: thsi keeps failing - https://code.edge.launchpad.net/~vcs-imports/coreutils/ddhash [17:45] MTeck, let me see the cause [17:46] hmm [17:46] rockstar, hi :) [17:46] Ursinha, hello. [17:47] rockstar, I'm looking for a bug for this: http://launchpadlibrarian.net/31314543/coreutils-ddhash-log.txt and decided to ask you about it === flacoste_lunch is now known as flacoste [17:49] Ursinha, I don't think there's a bug for that, but I'm willing to bet it's actually a bug in bzr-git. Maybe search there. [17:49] rockstar, I just found bug 419478 [17:49] Launchpad bug 419478 in launchpad-code "lp:~vcs-imports/rainbow-olpc/mstone-trunk import failing: NoSuchRevision" [Undecided,New] https://launchpad.net/bugs/419478 [17:49] that mentions bug 402814 [17:49] Launchpad bug 402814 in bzr-git "NotImplementedError importing a branch with submodules" [Medium,Triaged] https://launchpad.net/bugs/402814 [17:50] I think I need to take off pretty soon [17:50] MTeck, I'd suggest you to subscribe yourself to bug 419478 [17:50] Launchpad bug 419478 in launchpad-code "lp:~vcs-imports/rainbow-olpc/mstone-trunk import failing: NoSuchRevision" [Undecided,New] https://launchpad.net/bugs/419478 [17:51] ok, I will [17:51] Thanks [17:57] Ursinha, is jelmer subscribed to those bugs as well? [17:57] rockstar, don't know [17:58] Ursinha, bugs in git importing probably need to be seen by him. [17:59] rockstar, in the bzr-git he might be indirectly, he made comments in that bug [18:00] in the bug 419478 don't think so [18:00] Launchpad bug 419478 in launchpad-code "lp:~vcs-imports/rainbow-olpc/mstone-trunk import failing: NoSuchRevision" [Undecided,New] https://launchpad.net/bugs/419478 [18:00] rockstar, hm, it seems he's on both [18:01] Okay, great. Just so that he knows. [18:03] rockstar, but it seems he marked the bug as incomplete === Rohit is now known as Guest31837 === salgado-lunch is now known as salgado === matsubara-lunch is now known as matsubara === kiko is now known as kiko-phone [18:25] sinzui: did you intend that OEM call to be 11 hours long? i may have to decline. [18:26] bac: there should also be an email sent 30 seconds later that shows it may be 45 minutes long === salgado_ is now known as salgado === matsubara_ is now known as matsubara === Ursinha is now known as Ursinha-dhm [19:19] how do I get to the source code of a branch from the branch page now? [19:40] g'morning [19:40] wondering if it would be possible to get someone to review these files: https://translations.launchpad.net/tangocms/trunk/+imports?field.filter_status=all&field.filter_extension=pot === rickspencer3 is now known as rickspencer3-afk === bac changed the topic of #launchpad to: Launchpad is now open sourced: https://dev.launchpad.net/ | Help contact: - | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com/ | irc://irc.freenode.net/#launchpad-dev is the developer channel [19:48] hi AlexC_, unfortunately the translations team is finished for the day. [19:49] oh man [19:50] well thanks anyway, guess I'll have to wait another few days for automatic translations to import so I can do what I wanted to do days ago :P === kiko-phone is now known as kiko === rickspencer3-afk is now known as rickspencer3 === Philip5 is now known as Philip5-Hero === Philip5-Hero is now known as Philip5 === ia__ is now known as iaz === iaz is now known as ia [22:00] hello [22:04] I would like to have your feeding, is the actual version of launchpad suitable to run on production environement ? i mean, i would like to host an application using a local instance of lanchpad. I have just installed it on a fresh jaunty server and have seen some warnings about some features to disable in production [22:05] one more question please, i'm stuck at this step https://dev.launchpad.net/Running/RemoteAccess [22:09] In fact my /etc/apache2/ports.conf is very light, it only contains NameVirtualHost *:80 and Listen 80 (it referes to /etc/apache2/sites-enabled/000-default) [22:09] ohmy: The code you have is the exact code that runs on launchpad.net. So yes, it is production ready. HOWEVER [22:09] I point you to the third paragraph on https://dev.launchpad.net/Getting [22:10] And I also wonder why you want to run your own. [22:11] wgrant, Simply because we have a very large LAN network and no internet access (trust me !) [22:11] wgrant, thank you for the answers [22:12] ohmy: So, you can't run your own production Launchpad instance without a lot of work to replace the images and branding. [22:12] wgrant, i believe this is the easiest part of the work [22:14] wgrant, for the moment i'm stuck with "seeing is believing", i mean with https://dev.launchpad.net/Running/RemoteAccess step :) === matsubara is now known as matsubara-afk [22:27] i don't know why but i can"t access my server from an LAN machine, it always redirect me to the default apache "It works!", any one have an idea please ? [22:28] You have looked at how many images there are, right? I actually made a list of them all, because I'd like to have a private instance too, but when I did I discovered that the magnitude of a project to replace them all would be HUGE [22:31] Also, I am the author of the RemoteAccess page in its current form, so I can assure you that it does work, though it assumes you're confident with understanding Apache vhosts [22:34] maxb, of course, i've never doupt it works i'm just trying to figure what did i miss since all the work was done by a proven rocketfuel-setup script [22:35] maxb, when you mentinned "Change all lines to " i have already this ligne podified in the port.config [22:35] maxb, without any change from myside [22:39] sorry, i meant i have no occurence of 127.0.0.88:80 everything is already set to *:80 (sorry for the my mistake) [22:41] Have you not seen the /etc/apache2/sites-available/local-launchpad file? === salgado is now known as salgado-afk [23:02] hi [23:03] a small suggestion: it would be nice to add this: https://answers.launchpad.net/soyuz/+question/59047 to https://help.launchpad.net/Packaging/UploadErrors [23:07] It is a wiki, remember :-) === doctormo_ is now known as doctormo [23:17] Hello again [23:17] I have just switched to my old launchpad install witch is ok [23:18] could you please tell me how to add new admin and to remove the username: admin@canonical.com [23:19] maxb: indeed, i did not quite realize this yet :) [23:23] ohmy: Removing users is impossible without messing with raw SQL [23:23] which is likely to be severely difficult [23:24] maxb, indeed === rickspencer3 is now known as rickspencer3-afk