[08:10] <cjwatson> mark06: next deployment, I expect some time this week
[10:52] <launchgit> hi people,can somebody help with some Git questions?
[10:57] <cjwatson> launchgit: What's the problem?
[11:04] <launchgit> is the 'team' functionality adhering only to bazzar, or is it relevant to Git based repositories too?
[11:07] <cjwatson> launchgit: Most of the Launchpad permission handling is much the same between Bazaar and Git.
[11:07] <cjwatson> launchgit: So you can certainly have team-owned repositories etc.
[11:08] <cjwatson> launchgit: After all we clearly need *some* way to define who gets to push to a repository.
[11:08] <cjwatson> launchgit: So it might as well be basically the same model ...
[11:09] <launchgit> so how does a team push to a Git repository? does it push to the 'master' branch created by the owner?
[11:09] <launchgit> i.e what would the actual command be
[11:16] <cjwatson> launchgit: A team can't push to anything; it is not an actor.  A member of a team can push to a repository owned by the team.
[11:16] <cjwatson> launchgit: Other than that, in terms of commands and branches, it's the same as a Git repository on any other site.
[11:16] <cjwatson> launchgit: man git push
[11:18] <launchgit> and how do you assign a team to a branch? i.e have the owner commit to 'master' and team to 'development'(thank you very much for your really informative answers, by the way)
[11:18] <cjwatson> launchgit: That is, what branch you push to is entirely up to the options you give to "git push".
[11:18] <cjwatson> launchgit: That doesn't make sense.
[11:18] <cjwatson> launchgit: What are you actually trying to do here?
[11:19] <cjwatson> Like I say, teams don't push things, only individual members of teams do.
[11:20] <maxb> Perhaps launchgit is wondering if different branches can have different push restrictions?
[11:20] <cjwatson> Perhaps, but I'd rather get a clear problem statement than guess.
[11:21] <launchgit> maxb, yes exactly. like, leave the master untouched and assign users to work on another branch
[11:22] <cjwatson> launchgit: Launchpad doesn't support different access control for individual branches within a repository as yet.  It's on the plan, but not implemented.
[11:22] <cjwatson> launchgit: So if you want that, you'll need to use multiple repositories with different ownership.
[11:23] <cjwatson> The plan is something like you'd be able to supply a list of access control rules, each of which would be a wildcard matching against ref paths and a person/team.
[11:25] <launchgit> so if a team member wants to push, he does the following,or uses his own username git push --set-upstream lp:~<team>/<team>/+git/<name-of-private-repo> master
[11:27] <cjwatson> They would not use their own username, unless there's also a repository owned by them specifically.
[11:28] <launchgit> the 'Branch sharing policy'. Setting it to public does it mean that all the public can see and clone but only the team members can create branches and do commits?
[11:29] <cjwatson> Correct.  (Well, only the team members can push.  Anyone can branch and commit locally.)
[11:30] <launchgit> nice,thank you so much, cleared up things
[11:38] <adrien_znc> hi, I'm curious about the status of the git support overall: a few weeks ago it was considered beta, what is the current status?
[11:39] <cjwatson> adrien_znc: We still have some beta labelling, and there are quite a few more features we think we need to add, but at this point it's pretty stable.
[11:39] <adrien_znc> ok, thanks :)
[11:39] <cjwatson> Always tricky to decide what beta vs. stable or whatever actually means :-)
[11:41] <adrien_znc> hehe, definitely
[11:41] <adrien_znc> do you have the list of things to add written down somewhere btw?
[11:42] <cjwatson> We have a task tracker, but I'm afraid it's internal
[11:42] <adrien_znc> ok :)
[11:42] <cjwatson> A bunch of things are filed as bugs in Launchpad itself with the 'git' tag, though.
[11:42] <adrien_znc> well, I think I should just try and see how it goes
[11:42] <adrien_znc> ah, reminsd me
[11:42] <adrien_znc> reminds*
[11:43] <cjwatson> So https://bugs.launchpad.net/launchpad/+bugs?field.tag=git is vaguely useful, although the ones before about 1400000 relate to git->bzr imports.
[11:43] <adrien_znc> the "mingw-w64" name is already taken by the packaging project for it in ubuntu as far as I understand
[11:43] <adrien_znc> (by xno x)
[11:44] <adrien_znc> so we were wondering if we could get into it or whether we'd have to take another name on LP
[11:44] <adrien_znc> but we'll probably see that next month
[11:45] <adrien_znc> (holidays and CCC this month)
[11:45] <cjwatson> adrien_znc: You should discuss that with xnox.  Perhaps it would make sense to expand the scope of that project beyond packaging (after all, projects are meant to correspond to upstream projects first and foremost), or perhaps the packaging project can be renamed.
[11:49] <adrien_znc> cjwatson: yup, definitely something to discuss with xnox :)
[12:00] <xnox> hm
[12:01] <xnox> adrien_znc: no, mingw-w64 is foremost an svn -> bzr mirror from sourceforge.
[12:01] <xnox> adrien_znc: if you want to use it for something else, go ahead, tell me your launchpad id, and I'm happy to add you as owner/admin.
[12:01] <adrien_znc> ok, I had misunderstood because of the presence of packages (or maybe only sources)
[12:01] <xnox> adrien_znc: i know that sourceforge is down (still?!)
[12:02] <xnox> adrien_znc: there are no packages present there.
[12:02] <adrien_znc> also, it's now git, not svn
[12:02] <xnox> adrien_znc: there are "links" to ubuntu.
[12:02] <adrien_znc> SF isn't down but it's a possibility that the project will move away from SF
[12:02] <xnox> adrien_znc: right, and launchpad also supports git now, but i don't believe there is mirror available from SF -> LP of git
[12:02] <adrien_znc> (LP fits the technical bill, then it's a matter of people)
[12:03] <xnox> adrien_znc: but it's git, so one can do push --mirror command
[12:03] <xnox> adrien_znc: what's your launchpad id?
[12:03] <adrien_znc> I don't currently have one :P
[12:03] <xnox> adrien_znc: well.
[12:04] <xnox> adrien_znc: launchpad bug tracking is amazing & git integration is also very lovely these days. Imho it beats github by miles, for my use cases.
[12:04] <xnox> can have mailing lists as well.
[12:04] <adrien_znc> MLs were definitely the main issue
[12:04] <xnox> there isn't a wiki / formatted docs type of thing. But if one uses github pages, one can e.g. continue to use it.
[12:04] <adrien_znc> pretty much nothing provides them
[12:04] <adrien_znc> mingw-w64.org is currently a dokuwiki
[12:04] <adrien_znc> so it's fine
[12:05] <xnox> adrien_znc: launchpad has mailing lists on teams. Create as many teams as needed, and they all can have mailing lists.
[12:05] <adrien_znc> then people need to be spanked over and over so they write /some/ doc (i.e. problem is human more than technical)
[12:06] <adrien_znc> xnox: on https://launchpad.net/mingw-w64 there is a section "Packages in Distributions"; is it only a set of links to other projects?
[12:08] <adrien_znc> xnox: also, would you be OK that the mingw-w64 project moves over to the one on LP? (so far it's only a question and no move is planned)
[12:14] <wgrant> adrien_znc: Right, those are just links to packages in distributions.
[12:14] <wgrant> They don't mean it's a packaging project, just that it is packaged somewhere.
[12:15] <adrien_znc> ok :)
[12:18] <xnox> andi'm fine with it.
[12:18] <adrien_znc> great :)
[12:18] <adrien_znc> I'll push that around on the mailing-list but I don't expect a quick change in any case
[19:14] <mark06> cjwatson: about upload limit, that sounds pretty good, thanks
[19:25] <mark06> is there any way to upload files in automated way, e.g. rsync?
[19:26] <mark06> manual upload is a problem for packaging projects such as msys2 or other mingw-w64 distributions
[19:32] <cjwatson> mark06: You can do it with launchpadlib, e.g. lp-project-upload in the lptools package
[19:32] <cjwatson> No idea how well it works with ginormous files
[19:41] <mark06> sounds like a good start, but any way we could use rsync directly?
[19:42] <cjwatson> mark06: No.
[19:43] <cjwatson> We don't have anything shaped like an rsync daemon at the other end.
[19:44] <mark06> ok, I think some scripting can be done with lptools to upload only new files, thanks anyyway