[01:08] wgrant: just so that I get this right, there's no webui for git repos just yet right [01:09] shadeslayer: There is certainly a web UI, although some bits aren't hooked up quite correctly yet. What piece do you think is missing? [01:09] shadeslayer: It depends on what you mean by that. There's always been UI for the repos themselves, but there wasn't always a way to find them. [01:09] I just pushed a repo to lp:~shashlik/packaging [01:09] (and some of the ways to find them won't be on prod until next week) [01:09] but I'm not sure where the webui for viewing it is [01:09] shadeslayer: That's the packaging project. [01:09] Did you really mean that? [01:09] oh [01:10] no xD [01:10] The LP project model hasn't changed; this isnt' GitHub. [01:10] If you want a project repo, push to lp:~person-or-team/project [01:10] You can see it by going to https://code.launchpad.net/~shashlik/packaging and selecting "View Git repositories", but as wgrant says you pushed it to the wrong place. [01:10] If you want a personal repo, push to lp:~person-or-team/+git/some-personal-name [01:11] (and there are also package repos, which are a little more complicated as we don't know exactly how they should work yet) [01:11] Fortunately you can delete repositories now ;-) [01:11] wait, so if I want to push to ~shashlik/shashlik/packaging, where does one push [01:11] cjwatson: yeah deleted :) [01:11] https://code.launchpad.net/~shashlik/packaging/+git/packaging has the link [01:11] shadeslayer: What does that mean? [01:12] wgrant: ~shashlik team, shashlik project, repo called packaging [01:12] You want a separate repo named 'packaging' inside the shashlik project? [01:12] ( same as bzr ) [01:12] wgrant: yep [01:12] That's lp:~shashlik/shashlik/+git/packaging [01:12] I see [01:12] (since lp:~shashlik/shashlik/packaging would be a bzr branch) [01:12] It's fundamentally not the same as bzr, though [01:12] That too. [01:12] I see, thanks for explaining that, it wasn't clear enough from the docs [01:12] Because branches can (and often should) be colocated within a single repository [01:13] For most projects the right thing is just to have a single repository called lp:shashlik [01:13] And then branches within that [01:13] lp:~owner/project is what we expect 99.9% of contributors to use, and the only official repo will almost always be lp:project [01:13] The named repos exist for cases where privacy is required, and because the Ubuntu kernel team is weird and has dozens of repos for no good reason. [01:13] You'd only use a separate repository if you're doing something somewhat odd, like your packaging branch sharing no history with upstream. [01:14] You probably just want a separate branch in the same repo. [01:14] (Even in the no history case, there's nothing to say it has to be a separate repo; e.g. pristine-tar) [01:15] wgrant: yeah, I'm used to the github workflow [01:16] shadeslayer: You have a separate packaging repo on GitHub? [01:16] That's pretty weird, since you can't have more than one fork of a repo per user/org on GitHub. [01:16] wgrant: no, I was trying to figure out how to host the packaging on Launchpad, the sources are on github though [01:17] that is true, however, one would expect to use branches in that case? [01:17] (that is, on GitHub you only have the equivalent of lp:~shashlik/shashlik, no lp:~shashlik/shashlik/+git/foo) [01:17] multiple forks of the same project under one team/user sounds a bit .. off to me [01:17] Yes, which is why we are discouraging them :) [01:17] ( that's what branches are for, I assumed ) [01:17] right :) [01:17] They're necessary for eg. security fixes. [01:17] Or if you need separate tag namespaces. [01:17] Or things like that. [01:18] Embargoed security fixes, that is :) [01:18] But packaging should probably just be a branch. [01:18] Since we're only doing privacy at the repository level, not at the branch level [01:18] (or a whole lot of branches in refs/heads/ubuntu/SERIES, for example) [01:20] I expect we'll end up with a bunch of packaging repositories in the lp:ubuntu/+source/SOURCE namespaces and friends once those work, so lp:~slashlik/ubuntu/+source/shashlik would also be valid. The main reason for that is completely different access control, though. === Nigel_ is now known as G === Spads_ is now known as Spads [23:32] hi [23:33] in my build it seems like something's going wrong here : ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. [23:33] https://launchpadlibrarian.net/208967130/buildlog_ubuntu-vivid-i386.shashlik_0.2%2Bgit20150613.0347%2B15.04-0_BUILDING.txt.gz [23:34] If I were you I would consider the possibility that that was a red herring given that it occurred several times before without apparent immediate failure, and that it says "ignored" [23:35] But I must to bed rather than trying to decipher Java build failures :-) [23:35] ah :) [23:35] cjwatson: night :)