/srv/irclogs.ubuntu.com/2009/05/20/#bzr.txt

a_c_mhumm00:36
a_c_mi just tried out bzr-search and i think its corrupted my bzr folder, all operations seem to get stuck at Stage:Indexing...:Saving group 3/400:37
a_c_mis there any way to recover?00:37
igcmorning00:42
a_c_mmorning00:43
a_c_mhelp :) i've seemed to have corrupted my .bzr folder? i ran a bzr check, which worked fine, but when i bzr up - it hangs at Indexing...:Saving group 3/400:52
a_c_mbah00:52
a_c_mwas the bzr-search module00:53
a_c_mplugin eevn00:53
stefanlsdIm trying to get a file back which was removed in a commit. Im doing bzr revert -r 14 '80-system-jpeg-png-sqlite.diff' and getting bzr: ERROR: Path(s) are not versioned: 80-system-jpeg-png-sqlite.diff.  I've tried full patch to the file also. Am i doing something wrong?04:06
* igc bbiab04:06
stefanlsd*path04:07
igcstefanlsd: that sounds like a bug. Maybe try 'bzr cat -r14 ...'. If that doesn't work, I'd create another branch, and try without the pathname. That should recreate the file and you can copy it from there. Having said that, we really want your use case working so please raise a bug.05:01
stefanlsdigc: ok thanks. i did a bzr revert -r14   and got the file. then a bzr revert  and copied the file back in.. but yeah, sounds bug like05:03
igcstefanlsd: cool. The main catch with re-adding the file is that it will get a new internal file-id (which can cause issues with merges crossing the delete/add boundary). I'm pretty sure add has a --with-ids flag (see bzr help add) but it's annoying to have to worry about that. Hence the need for a bug report so we don't forget to fix it!05:06
arjenAUyou lost buggerror06:57
AntoineLafontainI have something that is puzzling me. I have a local shared repository with 3 branches into it. There's a main branch, a branch branched from the main called sub and the last branch, branched from sub called project.07:56
AntoineLafontainThe idea was to be able to commit changes to each branch and then merge the changes down to sub and then project07:57
AntoineLafontainand if needed create other branches from the sub branch to start other 'projects' like the project branch07:57
AntoineLafontainall this works well on my local setup07:57
AntoineLafontainbut I was wondering when I want to push things to share, I can push any branch with no problem, but I couldn't find a way to push a shared repo.07:59
AntoineLafontainI guess it's not possible. And I'm possibly thinking this the wrong way...07:59
AntoineLafontainAny one could give me her/his thoughts on this? Thanks08:00
Peng_AntoineLafontain: There might be a plugin to make pushing an entire repo easier, but mostly you just push each branch one at a time.08:02
AntoineLafontainand if I branch all the branches to say, another computer, will they keep their relational history... main being the parent of sub and so on?08:03
Peng_AntoineLafontain: That's only a little bit of meta data; if it's wrong, you can do "bzr pull --remember" (parent) or "bzr push --remember" (push location) to fix it.08:13
AntoineLafontainhumm, I think I get most of what you say... Will need toexperiement to "grasp" thing for myself. But thx for confirming that there's a way and nothing wrong with my base setup.08:15
Peng_AntoineLafontain: What were you referring to? The default "push", "pull", "merge", etc. paths/URLs?08:16
AntoineLafontainwell I did all this on my local machine, and using the default merge to propagate changes "down" my branch, using the hierarchy created by branching.08:17
AntoineLafontainbut when I considered pushing my setup to my server via sftp... I couldn't figure out how I would keep this relation between my branches...08:18
Peng_AntoineLafontain: Do you have ssh access to the server? Then you could run "bzr pull --remember", like I said. Or you could manually edit .bzr/branch/branch.conf over ssh or sftp.08:19
AntoineLafontainthe --remember option isn't only for remebering the location of the parent branch?08:20
AntoineLafontainsorry, I think my questions are a bit too basic... my experience with bazaar and versioning is quite limited...08:21
Peng_AntoineLafontain: That is what it's for.08:21
AntoineLafontainokey, so I get this part...08:22
AntoineLafontainhumm I guess that my explanation isn't clear... let me try again08:22
AntoineLafontainI made a branch from a remote repo and I called that branch main08:22
AntoineLafontainit is a local branch08:22
AntoineLafontainI've then branched that main branch into a sub branch and made some additions to it... files, folders etc08:23
AntoineLafontainthen I made a branch of that sub branch called project08:23
AntoineLafontainfrom this setup I can update main or sub and then propagate the changes to project as needed08:24
AntoineLafontainusing merge08:24
AntoineLafontainthis works quite well08:24
AntoineLafontainbut if I would like to move this setup on another machine... or share it with a co-worker...08:25
Peng_OK, so push your branches somewhere.08:25
AntoineLafontainI push all the branches to the server, but if I branch from the branch called sub from the server, the "relation" it had with main is broken08:25
Peng_What "relation"?08:26
AntoineLafontaineg, if I commit some changes to main08:26
AntoineLafontainI can just move to sub and then do a bzr merge to get all the changes to my sub branch from main08:26
AntoineLafontainI feel I just get some concepts wrong... not that bazaar can't do what I want actualy...08:27
Peng_You can still merge or whatever you want to. You may have to run "bzr merge --remember /path/to/whatever" to fix up the stored URL once, but that's all.08:29
Peng_If revisions lost their identities whenever you pushed, DVCSes would be kind of useless.08:29
Peng_:P08:29
Peng_Well, they just wouldn't be very "D".08:29
AntoineLafontainhaha08:29
AntoineLafontainokey, I think I get it (somewhat). will just get my hands dirty and try it to make sure I do get it08:30
AntoineLafontainthank you for listening to my ramblings ;)08:30
Peng_:)08:31
* igc dinner09:14
adam7Is it possible to copy a versioned file from branch A to branch B while retaining the version history?10:05
bob2I think "copy" is the wrong word10:05
bob2what are A and B?  are they related?10:05
adam7well, I have A and B, and I'd like to put them in the same branch (currently in seperate branches)10:06
adam7merge doesn't work because they didn't start from the same branch10:07
bob2merge can work10:08
adam7ok...10:08
adam7I need a flag or something?10:08
bob2I forget how to use it to merge unrelated branches, sorry10:08
adam7--weave seems to do it10:09
adam7oops10:09
adam7or not10:09
bob2I think it was -r0.., but I can't seem to find anything on google10:10
bob2try asking on the list?10:10
adam7bob2: got it10:24
adam7bzr merge -r 0..-1 ../other-branch10:24
adam7then bzr ci --unchanged10:24
bob2you shouldn't need --unchanged10:25
adam7I do, for whatever reason...10:25
adam7otherwise bzr status doesn't work10:25
bob2eh10:25
adam7mkdir C10:26
adam7cd C; bzr init10:26
adam7bzr merge -r 0..-110:26
adam7+N blah blah blah10:27
adam7bzr status10:27
adam7working tree is out of date, run 'bzr update'10:27
adam7bzr update10:27
adam7-D blah blah blah10:27
adam7maybe I'm doing something wrong?10:27
=== abentley1 is now known as abentley
=== abentley1 is now known as abentley
=== abentley1 is now known as abentley
=== abentley1 is now known as abentley
=== abentley1 is now known as abentley
=== abentley1 is now known as abentley
LeonBrusselsI have got a severe problem11:26
LeonBrusselsbzr: ERROR: Unknown record type: '\x02'  on commit11:26
LeonBrusselsis that bad :( ?11:26
Odd_BlokeLeonBrussels: There should be a full traceback in ~/.bzr.log, putting that in a pastebin will help people diagnose the issue.11:27
LeonBrusselsTraceback: http://pastebin.com/f468824e611:31
LeonBrusselsIt's not a terribly large or complicated repo11:31
LeonBrusselsoh, and my bzr check doesn't look very positive either...11:35
Odd_BlokeWell, I don't know.11:37
Odd_BlokeBut someone else who does will show up sometime soon. :)11:37
* LeonBrussels has decided he hates bzr11:47
Odd_BlokeLeonBrussels: :(11:56
Odd_BlokeLeonBrussels: I'm surprised there's no one else around to be able to help, the channel is normally much busier than this.11:56
Odd_BlokeActually, thinking about it, all the Canonical people are at their annual conference.11:57
Odd_BlokeSo that's probably not helping.11:57
Ddordahey. how do i download a specific revision of a project12:20
Peng_Ddorda: "bzr branch -r 123 whatever"?12:22
Ddordaso i can do "bzr branch -r 91" and it will download revision 91?12:23
Peng_Uh-huh.12:23
Ddordaערקשא12:24
Ddordagreat*12:24
Ddordamany thanks :D12:25
Peng_:)12:26
Peng_Ddorda: You can also use "bzr revert -r 123" to make the working tree look like it's a certain revision.12:27
Ddordaokay.. thanks12:27
=== nevans1 is now known as nevans
=== Kissaki^0ff is now known as Kissaki
Takis there a better way of checking whether a branch is bound than get_bound_location?15:41
exarkunJust encountered this failure, http://rafb.net/p/CEC6g533.html16:07
serviliohi!16:12
servilioanyone knows where can I get a bzr-rebase compatible with bzr 1.15rc1?16:13
GaryvdMservilo: lp:bzr-rebase?16:14
servilioGaryvdM: hmmm, will try that...16:15
serviliodo you know how stable is it?16:15
GaryvdMI'm running it - have no problems.16:17
servilioGaryvdM: great! are you using bzr 1.15rc1 as well?16:17
GaryvdMno16:18
GaryvdM1.14.116:18
ricardokirknerhi. I am playing with bzr-svn and dpush. I want to have a central bzr repo from which all my developers can branch off, and from which I can pull and push to a central svn repo (upstream). I configured the upstream svn repo to support pre-revprop-change hook in order to rewrite the author, and use dpush in order not to push metadata properties (as they are not wanted in upstream). The main idea here is to use bzr but try not to interfere with upstrea16:22
ricardokirknerm (because normally we can't)16:22
ricardokirknernow, I am getting this strange behaviour:16:23
ricardokirknerI have repo A (from which I dpush), repo B (branch of A)16:23
ricardokirknerwhen I dpush from A (to svn), and then (in B) pull (from A)16:23
ricardokirknerI get a message that the branches have diverged16:23
jelmerricardokirkner: yes, that's the disadvantage of dpush16:24
jelmerricardokirkner: it doesn't retain all of the metadata, and so the revisions change slightly16:25
ricardokirknerjelmer, is there any way around this? (as the branches aren't really different)16:26
ricardokirknermaybe using rebase? some option?16:26
ricardokirkneror, once I dpush I loose any chance to continue my branches?16:26
jelmerricardokirkner: bzr pull --overwrite in branch B should fix it, or using regular push16:26
ricardokirknerjelmer, alright , I'll try using pull --overwrite16:27
jelmerricardokirkner: (--overwrite that'll remove any extra revisions you have in branch B)16:27
ricardokirkneras direct push to svn is not what I want (my client has complained that a lot of properties appeared in the svn tree -- as they are using svn 1.4, its file props)16:27
jelmerricardokirkner: so, one of the things you can do is not pull from branch A until you've dpushed branch A into svn16:28
jelmerricardokirkner: as the revisions won't change after they have been dpushed16:28
ricardokirknerjelmer, but thats what I've been doing16:28
ricardokirknerthat's what made me wonder16:28
ricardokirknerI pushed from B to A , then dpushed from A to svn, then pulled from A to B16:29
ricardokirknerand got the error16:29
jelmerricardokirkner: yes, because the revisions you pushed from B into A have been rebased by dpush16:29
servilioGaryvdM: to install bzr-rebase local to my account is it enough to copy it under $HOME/.bazaar/plugins? no build necessary?16:31
* servilio answers himself: yes, just copying is enough16:35
serviliothough bzr checkout lp:bzr-rebase $HOME/.bazaar/plugins/rebase is even better16:35
serviliojelmer!16:36
serviliojelmer: got 1.15rc1 built and working, thanks again!16:36
ricardokirknerjelmer, and is this not fixable somehow by rebasing B as A was rebased? (without having to overwrite B entirely)16:37
jelmerservilio: np :)16:40
jelmerricardokirkner: not yet, for that dpush would have to store the information of how things were rebased so rebase could pick it up16:40
ricardokirknerjelmer, and the problem with pull --overwrite is that I can't do anything in branch B until branch A has been dpushed to svn (in order to avoid any diverged message), right?16:43
ricardokirknerso, if developer B pushes to A, and does nothing else on branch B until branch A has been dpushed, and after that pulls with overwrite from branch A , i should not have any issues, right?16:44
ricardokirknerit's a workflow limitation, but it may work16:45
jelmerricardokirkner: yes16:45
jelmerricardokirkner: please file a wishlist bug about dpush saving a revid map if that bit seems useful16:46
serviliois it possible to do a rebase from a subversion source? I am trying but get a "different rich-root support" error16:48
servilioshould I change the local branch format?16:48
SamBservilio: that sounds unrelated to rebase16:48
ricardokirknerjelmer, if dpush saves a revid map (locally I guess, as I don't want to push any metadata to the svn server), that would allow bzr to rebase branch B accordingly, and prevent the branches to be interpreted as diverged?16:48
SamBservilio: you get that when you to pull, too, don't you ?16:49
jelmerservilio: you need to upgrade the other branch to a rich root format16:49
serviliojelmer: the other branch is a subversion repo16:49
jelmerricardokirkner: yes, you'd just have to specify the revidmap to dpush (so it can store it) and rebase (so it can load it)16:49
* SamB doesn't get the point of dpush16:49
jelmerservilio: Sorry, I mean your local branch16:49
jelmerSamB: doesn't set any bzr-specific svn data16:49
SamBjelmer: that seems pretty useless to me!16:50
jelmerSamB: some people get annoyed by the file properties bzr-svn sets if you're running against a svn < 1.5 server16:50
SamBI guess if the repository doesn't allow revision properties, maybe it's useful ...16:50
ricardokirknerjelmer, alright.. .I will try pull --overwrite to see if it works for my needs, and file a wishlist for dpush (adding the relevant information for this irc log if you agree)16:50
serviliojelmer: what version should I upgrade it to? I tried bzr upgrade and it says it is already at the newest (I know you can override to an "experimental/devel" format forcibly, but just don't know which one is the right)16:50
jelmerservilio: "bzr upgrade --default-rich-root"16:51
SamBjelmer: do you know anything about why a repository that does allow revision properties would disallow mergeinfo ?16:51
jelmerSamB: yes, mergeinfo was added later16:52
SamBjelmer: does it also depend on something about the repository, in addition to the server ?16:53
serviliojelmer: worked great! thanks!16:53
jelmerSamB: not that I'm aware of16:53
SamBjelmer: hmm, I wonder how sourceforge does this then16:53
SamBsince right now the dosemu SVN on sourceforge doesn't allow mergeinfo, but they say that a project admin can upgrade it to do so ...16:55
* SamB looks for the ticket ...16:56
SamBjelmer: ah, here's the ticket where they told me this: https://apps.sourceforge.net/trac/sourceforge/ticket/31716:58
ubottuError: <Bugtracker.plugin.Sourceforge instance at 0x293d3b0> bug 317 not found16:58
SamBubottu: uh, it's definately there!16:58
ubottuError: I am only a bot, please don't think I'm intelligent :)16:58
* SamB was only teasing16:58
SamBjelmer: can you make anything of that ?16:59
jelmerSamB: that URL requires me to log in17:01
SamBjelmer: it does ?17:01
SamBthat's wierd ...17:02
jelmerSamB: ah17:02
jelmerSamB: yeah, there's a format change required too for mergeinfo17:02
SamBjelmer: are you going to write about that on the ticket ... or should I just reopen it and let the sf.net people do that ?17:03
jelmerSamB: I don't see what there is to comment on17:04
jelmerSamB: I mean, what is your question to me exactly?17:04
SamBnevermind, I'll just reopen and see if they can answer ...17:04
jelmerSamB: You'll have to dump and restore the repo as they say in order to use mergeinfo17:05
SamBnow, my question for you is: can bzr-svn, after a repository has been upgraded to support mergeinfo, go back and fill that in for bzr merges ?17:06
serviliois svn:ignore supported "full-duplex" in bzr-svn? I can see in workingtree.py that it import it, but aside of the tests, can't see any other reference to svn:ignore in the code17:06
dashSamB: it'll be a new repo, so you'd need a new bzr-svn import i think17:07
SamBdash: wouldn't it just be a new representation of the same repo?17:07
jelmerservilio: no, it's only supported in working trees17:07
dashi don't know what 'representation' and 'same' mean there17:07
serviliojelmer: thx!17:08
jelmerSamB: that's not possible, you can't change the file properties in historic revisions17:08
SamBjelmer: ouch :-(17:08
* SamB thinks bzr-svn ought to ask for confirmation before pushing to a repository that won't allow mergeinfo for the first time ...17:09
dashhow would that help?17:10
SamBdash: well, that way you could maybe do something about getting the repository upgraded *first*17:10
jelmerSamB: why? svn doesn't do anything like that either if the repo doesn't support mergeinfo17:10
dashSamB: what's wrong with upgrading it later? just rebranch17:11
jelmerSamB: and svn users benefit from bzr-svn setting svn:mergeinfo, bzr-svn users don't benefit from it (since bzr-svn doesn't look at svn:mergeinfo itself)17:11
SamBjelmer: hmm.17:11
SamBjelmer: is what dash says about having to re-import true?17:12
jelmerSamB: yes, that's the only way you can get bzr-svn to set those svn:mergeinfo properties17:12
SamBjelmer: I mean, after you do the dump/restore, does bzr-svn need to re-import the repository ?17:13
jelmerSamB: depends on if the dump/restore retains the repository UUID17:14
jelmerSamB: You can get it to retain the repository UUID17:14
jelmerSamB: but I think you explicitly have to set the old UUID, otherwise it generates a new one17:15
SamBjelmer: hmm, the help for "load" appears to indicate that if you load into an empty repo, it sets the UUID from the stream ...17:15
jelmerSamB: ah, I might be wrong then17:17
=== servilio is now known as Guest21385
SamBand I just did a test dump, and "svnadmin dump" seems to dump the repository UUID17:18
=== servilio_ is now known as servilio
SamBjelmer: and are SVN revisions from repositories with different UUIDs considered distinct by bzr-svn ?17:19
jelmerSamB: yes17:20
dashone hopes so17:20
* SamB wonders why git-svn doesn't use the UUID instead of the URL17:20
dashgit was written by C programmers17:21
SamBgit-svn is in perl though17:21
dashwell, perl was written by C programmers too. ;)17:21
SamBso was Python17:21
dashdisputable!17:22
dashanyway17:22
servilioisn't pull the command to get a local copy in sync with the remote subversion repository?17:22
SamBare you saying that Python is written by wannabe C coders ?17:22
dashgit succeeds because it makes the same optimization tradeoffs as C17:22
dashtrading correctness for performance :)17:22
SamBdash: are you talking about "git merge"?17:23
dashservilio: right. it creates a bzr branch containing all the revisions of the remote svn branch17:23
* SamB wants a better "git merge"17:23
SamBservilio: why do you ask?17:23
serviliodash: I already have the local branch, but I need to get it in sync with the repo to be able to push the locally committed changes17:23
SamBit sounds like you just tried it but it didn't work17:24
dashoh, you did say pull, sorry. I did not read what you wrote :)17:24
servilioSamB: I am getting an exception regarding mismatching revisions17:24
SamBservilio: paste it somewhere?17:24
SamBhere, if it's short ...17:24
servilionot short, any pastebin at hand?17:24
servilioI know none17:25
SamB!paste17:25
ubottupastebin is a service to post multiple-lined texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu.com (make sure you give us the URL for your paste - see also the channel topic)17:25
servilioSamB: nice :))17:25
SamBservilio: I had no idea if that would actually work or not ;-)17:26
serviliohttp://paste.ubuntu.com/176517/17:26
jelmerservilio: that's a known bug in 0.5.4, fixed in 0.6.017:27
serviliojelmer: using 0.6dev17:27
serviliowith bzr 1.15rc117:27
jelmerservilio: which 0.6dev revision?17:28
jelmer(I fixed that bug yesterday)17:28
serviliohow do I see the revision?17:29
jelmer'bzr revno'17:29
serviliojelmer: 299317:29
serviliojelmer: is http://bazaar.launchpad.net/%7Ejelmer/bzr-svn/0.6/ the proper URL to checkout from?17:29
jelmerservilio: no, http://people.samba.org/bzr/jelmer/bzr-svn/0.617:30
jelmer2993 should include the fix though..17:30
* servilio goes to switch to the new URL actually checking out to plugins dir directly...17:30
serviliojelmer: @2997 now, trying again...17:32
serviliojelmer: same result17:32
serviliojelmer: want me to gather some more data beyond the traceback? run it in verbose mode?17:32
jelmerservilio: please file a bug17:32
jelmerservilio: is this a public repo?17:33
serviliojelmer: no, local to the university I work17:33
serviliobut I have full access to that machine, could get some data on the repo17:33
serviliomaybe it is still in old format or something17:33
jelmerno, that shouldn't be relevant. this very much looks like a bzr-svn bug17:34
SamBservilio: is it local for a particular reason?17:34
servilioSamB: for most of the code, just lack of time to move it out17:35
serviliosome other code is quite local to us17:36
SamBservilio: as in, private ?17:36
serviliothough publishing it wouldn't do any harm17:36
servilioSamB: as in only accessible from campus network17:36
SamBah, so as in, you don't think anyone else would want it ?17:36
servilioSamB: at the beginning, yes17:37
SamBso you could probably get permission to give jelmer a copy of the repository, then ?17:37
servilioSamB: started with branding stuff, then just put there stuff that might have lived outside17:37
servilioSamB: yes17:38
servilioI can give it a try17:38
serviliodon't expect any trouble getting the OK from the stakeholders17:38
jelmerservilio: Perhaps wait until that's really necessary17:39
serviliojelmer: OK17:39
serviliojelmer: should I file a new bug or put the new data under an existing one?17:39
SamBjelmer: well, he seems to think it'd be mostly a matter of asking ...17:39
jelmerservilio: new bug please17:39
jelmerSamB: yes, but I was mainly asking so I can have a quick try to see if I can reproduce + fix it17:40
serviliojelmer: I think I know what is happening17:40
SamBwhatever ;-)17:40
* servilio goes to do a short test...17:41
SamBI just thought I'd ask about it, since I know people at universities often keep stuff private merely because they haven't bothered to make it public ...17:42
serviliohmmm, there is really a mismatch17:45
jelmerservilio: can you tell what it's doing wrong based on "svn log -v" ?17:45
serviliothe files at the svn repo are at revision 362, but somehow bzr-svn got its metadata at 38717:46
jelmerservilio: is 387 mentioned anywhere in log?17:46
jelmerservilio: is that particular path changed in 387 ?17:46
serviliojelmer: will see, svn repo is at 42717:46
servilioyes, I think I found the cause17:47
servilioI changed the base URL of the repo17:48
servilioit happened at revision 38717:48
servilio:)17:48
jelmerservilio: can you please mention this in the bug report ?17:48
servilioyep17:48
jelmerservilio: Possible with the changes as printed by "svn log -v" from that revno17:48
serviliojelmer: no problem17:48
serviliojelmer: what about doing a bzr switch on the local bzr branch?17:49
serviliocould it fix this?17:49
jelmerservilio: no, this really is a bzr-svn bug17:50
serviliook17:50
serviliofiling new bug...17:50
serviliojelmer: what about rebase? shouldn't that make the local branch sync with the remote svn? (just curious)17:55
=== nevans1 is now known as nevans
jelmerservilio: rebase basically replays your local commits on top of the remote ones17:56
jelmerservilio: the extra revisions you have locally I mean17:56
serviliojelmer: rebase just says: "No revisions to rebase."17:57
jelmerservilio: if you don't have any extra revisions locally, that's correct17:57
serviliojelmer: what is better: paste the outputs directly or attached as files?18:05
jelmerservilio: paste directly please18:07
serviliook18:07
serviliojelmer: just to confirm: I am including the output from svn log and bzr pull; am I leaving anything out?18:12
jelmerservilio: "svn log -v" ?18:19
jelmerservilio: other than that, that should be sufficient18:19
serviliook18:19
serviliojelmer: is it possible to use markup in the bug information area?18:42
jelmerservilio: don't know18:43
ricardokirkneris there a way to have a bzr smart server with authentication and allow writes, that doesn't expose the full filesystem path? (like bzr+ssh does)18:46
LarstiQricardokirkner: ClueBzr?18:47
ricardokirkneris it stable enough? (I just saw a mention of it recently) have you any experience using it?18:47
LarstiQno idea, no.18:48
LarstiQricardokirkner: barring Launchpad, it's the only server implementation I know that does that.18:49
ricardokirknerLarstiQ: alright, I will take a look at it, thanks18:49
mib_thk4aclqI'm having some permissions issues in bzr on a Linux box19:01
mib_thk4aclqAnyone with any knowledge of this?19:02
LarstiQmib_thk4aclq: not enough information given to know yet.19:02
mib_thk4aclqHere goes.19:02
mib_thk4aclqI have a project that several users on the local box use19:02
mib_thk4aclqI'd like all to have commit privileges from their local branches to the main branch.19:02
mib_thk4aclqHowever, every time I run a push to merge my local branch with the main branch, ownership is set to me alone.19:03
mib_thk4aclqNone of the other devs are able to make commits.19:03
mib_thk4aclqI'd rather not have to change permissions on the main branch location each time.19:03
mib_thk4aclqIs there a better way to set it up, to avoid this issue?19:03
LarstiQmib_thk4aclq: yes, I personally make use of posix acls19:04
mib_thk4aclqTo what end?19:04
LarstiQmib_thk4aclq: to set the permissions on /srv/bzr19:05
mib_thk4aclqI see. That seems reasonable. I'm rather surprised bzr isn't able to handle this on its own.19:06
mib_thk4aclqI expected this scenario would be fairly common.19:06
LarstiQmib_thk4aclq: something like `setfacl -m group:bzr:rwx /srv/bzr/*'19:06
LarstiQmib_thk4aclq: bzr is not in the business of handling permissions19:07
mib_thk4aclqI suppose that keeps everything nice and general, given its portability.19:07
mib_thk4aclqMany thanks.19:07
LarstiQmib_thk4aclq: alternatively, if you're using a smartserver instead of dumb transports, you could handle it there19:07
mib_thk4aclqOh? Could you direct me to the proper documentation? I investigated the smartserver but couldn't find relevant info.19:08
LarstiQmib_thk4aclq: http://pypi.python.org/pypi/ClueBzrServer/0.2 or with Apache + mod_auth19:08
dashLarstiQ: probably you can't use that if all the urls are file:// ones :)19:08
LarstiQdash: correct :)19:09
mib_thk4aclqWell, using a smartserver or dumb transport makes no difference to me19:09
mib_thk4aclqAll users are local19:09
LarstiQmib_thk4aclq: if they use file:// urls, it is purely a filesystem permissions situation.19:10
LarstiQfor which I recommend setfacl for more flexibility than traditional Unix permissions19:10
mib_thk4aclqWell, I'd prefer to do the configuration with the smartserver then.19:10
mib_thk4aclqWhich I think I shall19:10
mib_thk4aclqI'm just sick of having the other devs pissed at me for blocking commits19:11
mib_thk4aclq:/19:11
LarstiQmib_thk4aclq: you can get partway to where you want to be with the setgid bit19:12
mib_thk4aclqMhmm19:12
LarstiQbut that falls short in the area of new directories mainly19:13
LarstiQ  $ setfacl -m group:developer:rwx /bzr19:13
LarstiQ  $ setfacl -m default:group:developer:rwx /bzr19:13
LarstiQtakes care of all that19:13
LarstiQmib_thk4aclq: I've set it up once on the server, and never look back19:13
mib_thk4aclqWell, there's certainly no harm in trying it out, since the box is locked down tight19:14
jelmerservilio: did you manage to file the bug?20:00
serviliojelmer: I am trying to reproduce the bug locally, but can't get bzr to make the first commit before removing an element from the path20:00
servilioI think I'll file the bug and later try to reproduce it20:01
servilioalso because I need to find a way to put my changes into the subversion repository (I mean, the ones from the real work, not the mock situation trying to reproduce the bug)20:02
serviliojelmer: I am getting a "Not a branch" when checking out a local svn repo: http://paste.ubuntu.com/176633/20:20
jelmerservilio: yeah, because the branch you're checking out is not a branch according to the layout you're specifying20:21
jelmerservilio: it seems like you'd want to create l1/l2/trunk20:22
servilioso, what should I do to have just a directory?20:23
jelmerservilio: how do you mean?20:23
servilioI tried bzr branch like you suggested here: http://www.nabble.com/My-experience-with-bzr-svn-td23606249.html20:23
serviliobut svn+file is not a recognized protocol20:23
jelmerservilio: file:/// should work20:24
serviliowill try that...20:24
jelmerservilio: I think I see what the problem is20:25
jelmeranyway, time for groceries first, back later20:26
serviliojelmer: got the branch properly created, now doing some local changes...20:26
serviliosee you later20:26
jelmerservilio: if you end up with a script that can reproduce this, that would be very useful (for the regression testsutie in bzr-svn)20:27
serviliojelmer: yep, I know20:27
serviliojelmer: got it :)21:01
jelmerservilio: w00t :-)21:13
serviliofound that it only happens with three levels of nesting21:14
serviliotwo doesn't show up21:14
servilioand bzr missing misses the changes in the remote svn repo on the 3 nesting case21:15
jelmerinteresting21:15
servilioI am extending the script to automate the testing for different levels21:15
servilioI'd like to see what happens at 4 levels21:18
jelmerservilio: can you attach the script to the bug report?21:33
servilioI'll do it21:33
servilioI am finishing it, will test it in a minute21:33
serviliojelmer: ready, attaching it now to ticket...21:58
serviliodone22:01
serviliojelmer: is there a way I can push the changes I have in my local branch to the svn repo #378799 notwithstanding?22:03
=== krisfree is now known as krisfremen
=== Kissaki is now known as Kissaki^0ff

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!