=== anthonyf is now known as Guest55250 [11:16] t [12:18] hello I want to request a code import [12:18] now my question is: what do I enter as "branch name"? [12:18] is it the "series"? [12:20] or is it the real branches' name, thats then also usable in a lp:branchname string for bzr-builder? [12:22] Not quite either of those exactly as you write :-) [12:23] The branch name is the end of the fully-qualified lp: URL, so for example lp:~cjwatson/man-db/master [12:23] ah ok [12:23] But if a branch is the development focus for a project (as that example one is), then it's aliased as simply lp:man-db [12:23] For an import it's reasonably usual to make it be the same as whatever the branch name is in the remote system [12:24] So in my example, it's an import of the master branch from a git repository, so it's just "master" [12:25] thanks [12:26] It was about a custom git branch yes. [12:28] any way to request older commits too? because you can enter specific revision ids, but only when the imports started, am I right? [12:29] (I mean: the revision ids start with the first imported commit) [12:30] Um, I don't quite understand. The importer walks the full history. [12:30] (Or at least all the history reachable from the ref name you give it.) [12:30] you are right, sorry. [12:30] That's not an option, it's an intrinsic part of doing a version control import. [12:31] quite cool :) [12:45] so, I want to execute pbuilder as non-root [12:45] any way I can accomplish this? [12:45] pbuilder-user-mode-linux complains about some tmp file not set in my ~/ [12:45] I don't use pbuilder myself; the procedure in https://wiki.ubuntu.com/SimpleSbuild should work fine though, I never run sbuild as root [12:46] pbuilder-user-mode-linux is, I suspect, a pretty experimental thing [12:57] please help how can i login into launchpad if i am windows 8 user === aditya_dev_s is now known as adidev [13:00] hello, hi i am aditya from india.. i am new to launchpad..please help me to login to download code if i am a windows 8 user [13:03] What are logs for the option: "Mail address where logs are sent to (mandatory, no default!)" inside ~/.sbuildrc? [13:03] I'm just wondering whether it requires a mail server on localhost... [13:05] est31: You can use the -n option to suppress saving logs and sending log mails. But this is really not Launchpad-specific at this point. [13:07] thanks though cjwatson any on-topic #channel I can ask for help? [13:07] adidev: I would suggest following through the instructions at https://help.launchpad.net/Code, and then if you get stuck ask specific questions about the specific error messages you're seeing. (I haven't used Windows seriously in 15 years, so there's no way I can give you a full walkthrough.) [13:07] est31: Perhaps #ubuntu-packaging [13:50] is there a way to inspect the history of a recipe? [13:50] and when I change it, will older packages still be available? [14:00] editing a recipe doesn't change what's already in the PPA [14:01] i don't know if there's a way to see a log of changes to a recipe [14:03] thanks dobey! [14:13] Yeah, we don't keep logs of old versions of recipe text, except perhaps whatever you can divine from old build logs. [17:04] cjwatson: ping [17:04] teward: Please tell me what you want and I'll reply when I'm around. [17:04] heh [17:04] autoresponder. [18:08] Hello, I have some doubts abt packaging system. [18:08] Is ubutu-packaging same as debian-packaging? [18:09] Sometimes specifics differ, but in general yes. [18:10] cjwatson: Is it true that for making PPA first we have to create a debian pacakge? [18:11] Yes. [18:12] cjwatson: I followed this tutorial https://help.launchpad.net/Packaging/PPA . It doesn't specify anything abt that [18:16] cjwatson: Is there any tutorial which explains creating PPA ? [19:37] cjwatson: on the GUI frontend for git stuff - saw those screenshots, can I say that they look decent even though they're very preliminary? === mattgrif_ is now known as mattgriffin [20:43] teward: Cool, thanks. There's definitely a long way to go, the second of those needs more infrastructure in place in order to be able to have more recent commits [20:43] (In advance of a proper integrated code browser, which I'd like to do but won't be for a while yet) [20:43] cjwatson: indeed. [20:55] cjwatson: stupid question though, why wouldn't you be able to apply the same logic as is currently used by the bzr code browser to the git side? [20:55] (granted I have no backend knowledge, so...) [20:55] (adapting of course for the bzr vs. git differences as you go) [22:08] teward: We don't have an integrated code browser for bzr; only loggerhead (which you see on bazaar.l.n), which is utterly bzr-specific and not integrated into the main webapp UI [22:09] ahh ok [22:09] cjwatson: thanks for the clarify :) [22:09] teward: We'll likely start out with a similar approach for git, probably using cgit, but it's not ideal. [22:10] cjwatson: i think the goal should be, in my opinion, functional vs. ideal [22:10] firstly [22:10] certainly [22:10] we're taking the quickest plausibleroute [22:10] cjwatson: same logic applies for bzr as well - ideally you'd have a proper integrated code browser for that as well, but function over idealism [22:11] hopefully cgit won't stick around long :) [22:11] cjwatson: hopefully you don't mind my commenting and asking though - git functionality on LP will go a long way towards making it better for projects [22:11] since a lot like git over bzr and such [22:12] so thank you for you and everyone's efforts [22:12] (on both the front and backend changes) [22:12] teward: I don't think anyone has any illusions over the current state of dvcs and where things are going. [22:12] * teward shrugs [22:13] I've only been using bzr for the last few months, but it has certainly grown on me. [22:13] blr: i use bzr only where needed - learned git for most things [22:13] but meh [22:13] blr: for those who prefer git over bzr, though... :P [22:13] (I also use bzr for my package merge debdiffs and such but that's a different matter xD) [22:16] cjwatson: regardless please pass on my thanks to those doing the backend development and such - I really do like the whole idea of having git in addition to bzr on LP - i'm not the only one either judging on that bug requesting it :) [22:17] teward: We might be able to retrofit an integrated browser to bzr without too much work, but we'd need to see whether it's worthwhile. And thanks, blr there has been doing a lot of the backend work as well as wgrant of course. [22:17] I use almost exclusively git for my own projects outside Ubuntu/Launchpad, so I'm keen to switch myself. [22:18] well then thanks to blr and wgrant :) [22:28] cjwatson: switched to get from hg several years ago as well for personal things. [22:28] git even [22:29] teward: we're certainly excited about it - it is certainly one of the most regularly requested new features for LP. [22:30] blr: well, i'd be happy to help alpha/beta test if you guys need public tests eventually before throwing it onto production - i'm a strong supporter of git for LP after all [22:30] kinda annoyed at bzr, but mostly for reasons that I won't share here 'cause Ubuntu CoC violations throughout that rant :P [22:31] until then i'll just track the bug where most of cjwatson's branches get linked to :)