[00:21] <nekohayo> hey there, I need to rename a hundred files or so, is there any way to not do it one by one with bazaar?
[00:29] <LeoNerd> for F in `find -name *.foo`; do bzr mv $F ${F/.foo/.bar}; done
[00:40] <nekohayo> LeoNerd: so this replaces the ".foo" string to ".bar" ? what is the ${F  for?
[00:44] <TFKyle> nekohayo: to reference the env var F (which is set to the current filename)
[00:44] <TFKyle> 'course, technically that does do it one by one
[00:50] <nekohayo> TFKyle: is there a way to do a "dry run" for this? to see what it would do without actually doing the changes
[00:53] <LaserJock> you could do "echo" instead of "bzr mv"
[00:53] <TFKyle> nekohayo: you could use echo "bzr mv $F ${F/.foo/.bar}" instead of just bzr mv,
[00:55] <nekohayo> TFKyle: hm, it just prints "bzr mv" and nothing after in the term
[00:55] <nekohayo> oh no wait :)
[00:56] <nekohayo> TFKyle, it prints this: bzr mv find -name 20070216* find -name 20070216*
[00:57] <nekohayo> the command was               for F in 'find -name 20070216*'; do echo "bzr mv $F ${F/20070216-/}"; done
[00:57] <TFKyle> nekohayo: `, not '
[00:58] <TFKyle> (for the find part)
[01:04] <nekohayo> ok, I found out the syntax                  for F in `find . -name '20070216*'`; do echo "bzr mv $F ${F/20070216-/}"; done
[01:12] <nekohayo> TFKyle: heh, when I make it echo the command it looks all fine to me (bzr mv ./20070216-gimp_ui-09.png ./gimp_ui-09.png) but when I run it, bzr says 404.
[01:23] <nekohayo> somehow, doing the rename command by hand (exactly the same input as when done through the find loop thingy), it works
[01:36] <nekohayo> ah, there needs to be no quotes near the end
[04:32] <acemo> $ bzr serve --directory=/home/acemo/development/bzr/repo --allow-writes
[04:32] <acemo>  is what am using to start my server.. from localhost i am able to do commits, but from other computer only able to update, unable to commit, getting these msges
[04:32] <acemo> added design/classDiagram.jude
[04:32] <acemo> bzr: ERROR: [Errno 13] Permission denied
[04:33] <acemo> what could be the reason of this and how to fix it?
[04:50] <spiv> acemo: when you say "from localhost", you mean via "bzr://localhost/" ?
[04:50] <spiv> If so, I have no idea what's going on.  "bzr serve" doesn't care which host you're connecting from.
[04:51] <acemo> spiv: yep bzr://localhost
[04:51] <spiv> I guess you could do "bzr -Dhpss commit ..." from the host getting the error, to see which particular command is failing.
[04:51] <spiv> (by looking in the ~/.bzr.log after it fails)
[04:53] <acemo> where in windows would the log file get placed?
[04:53] <spiv> "bzr version" will tell you
[04:54] <acemo> neatos
[05:02] <spiv> acemo: any luck?  Feel free to pastebin the relevant part of the log file.
[05:03] <acemo> spiv: friend of me is at the remote comp.. n she cant find the log file..
[05:03] <acemo> spiv: doh she was just looking for .txt
[05:04] <spiv> Ah :)
[05:06] <acemo> http://rafb.net/p/XpkL1K11.html
[05:06] <acemo> thats the full bzr.log
[05:08]  * spiv looks
[05:08] <acemo> after doing bzr checkout bzr://hostname/branch.. u can just commit and it will commit to that branch right?
[05:09] <spiv> Right.
[05:09] <spiv> It's not failing on a network operation.
[05:09] <spiv> It's failing trying to read a file in the working tree on disk, if I'm reading that traceback correctly.
[05:09] <acemo> yeah i saw that too...
[05:10] <spiv> Check the permissions/attributes on design/caseDiagram.jude, maybe?
[05:10] <acemo> she just created and bzr add them on her comp..
[05:11] <spiv> Right.  But it seems for some reason that bzr can't read it.
[05:14] <spiv> So I'd expect e.g. "bzr diff design/caseDiagram.jude" to fail too.
[05:15] <spiv> (And that operation doesn't need the network server)
[05:16] <acemo> we found the problem..
[05:16] <acemo> she still had jude open, jude locked the file while having it in use
[05:16] <acemo> thanks alot!
[05:16] <spiv> Ah!
[05:16] <spiv> Glad I could help :)
[05:17] <spiv> That error could be clearer, though.  It would have helped for it to say which file it couldn't read.
[05:18] <acemo> was pretty clear tbh.. right after it prints out what file its processing it says it doesnt has permissions
[05:18] <acemo> just i thought it was no permission on the server instead of local comp
[05:18] <spiv> Right, it's clear if you already know where the problem is :)
[05:18] <acemo> :p
[10:46] <jelmer> Odd_Bloke, cr3: externals will hopefully be supported once nested tree support in bzr gets merged
[11:11] <vila> abentley: ping, BB flooding my mailox with 'voting error' messages and may be restarting also...
[11:13] <vila> One mail is emitted every 3 minutes, this metronomic precision making me suspect a restart ;-) I voted directly on site hoping to somehow solve the problem, but no luck...
[11:28] <jelmer> mathrick: I'd be happy to answer questions wrt rebase
[11:28] <jelmer> *internals
[12:58] <cammoblammo> Is there an easy way (ie shell agnostic) way to specify directories or files which shouldn't be committed in a tree?
[13:00] <Peng> .bzrignore?
[13:01] <cammoblammo> Hmm, I hadn't thought of that. It might do the trick.
[13:01] <Peng> Or, just list the stuff you want to commit?
[13:02] <Peng> Hm, most hg commands have include/exclude options. Maybe bzr should support that.
[13:03] <cammoblammo> I have a top level tree with several directories in it. One of those directories will be committed hourly via a cron, while the others will be committed as needed. Having to specify the directories to commit every time will be a pain.
[13:04] <cammoblammo> .bzrignore might work, but I'll have to unignore it as part of the cron job.
[13:09] <Peng> Huh.
[13:09] <Peng> Note that you don't have to commit .bzrignore before changes to it will be used.
[13:10] <Peng> You might be able to kludge something together using .bzrignore.
[13:10] <Peng> hg-like exclude stuff would be better.
[13:10] <Peng> Well, sort of.
[13:11] <jelmer> Peng: afaik bzr's .bzrignore supports regexes which can do exclusion stuff
[13:11] <jelmer> not that I've ever used it..
[13:11] <Peng> Yeah, it does.
[13:12] <cammoblammo> How does that work?
[13:12] <Peng> Not that I've ever used it either..
[13:13] <cammoblammo> The problem isn't the ignoring the directory, but the unignoring of it. Also, versioned files aren't ignored.
[13:13] <Peng> Oh, right, they aren't ignored. I totally forgot that.
[13:15] <cammoblammo> I'll kludge something together in the shell for now. If an exclude option is ever added, though, I'll definitely be a happy camper!
[13:20] <Odd_Bloke> cammoblammo: Open a bug for it, if there isn't one already.
[13:20] <Odd_Bloke> Else it'll get lost in the ether.
[13:22] <cammoblammo> Will do.
[13:32] <cammoblammo> Argh, sorry folks. I forgot to search for this bug before I submitted. Turns out several other people have asked for it too. Sorry devs...
[13:35] <emgent> heya
[13:36] <Odd_Bloke> emgent: Hi.
[13:36] <dwt> Hey guys
[13:37] <dwt> I'm using (trying to use) bzr-svn to push to a subversion repository
[13:37] <dwt> when doing so I get this error:
[13:37] <dwt> Setting property 'bzr:revision-id:v3-single-open-source/animated-grid' with invalid characters in name
[13:37] <dwt> bzr: ERROR: libsvn._core.SubversionException: ('Mindestens eine Eigenschafts"anderung ist fehlgeschlagen; Projektarchiv nicht ge"andert', 175008)
[13:37] <dwt> Which I think (reading the code) means that it barfs on the "/" in the property name.
[13:37] <dwt> Well, thats where I'm a bit stuck...
[13:38] <dwt> Can anyone help me get rid of this or debug this further?
[13:40] <jelmer> dwt: What version of bzr-svn are you using?
[13:40] <dwt> 0.4.8
[13:40] <jelmer> there was a bug like that that was fixed in 0.4.9
[13:40] <dwt> Ah cool, you're the developer. :-)
[13:41] <dwt> Great work by the way. :)
[13:41] <Odd_Bloke> cammoblammo: None of the other bugs are _quite_ the same request (as they are command-specific, rather than 'this should generally exist').
[13:42] <dwt> Yeah I'm on 0.4.8 I just updated this morning to the latest released version - had that bug in the last version (0.4.8 too, but with a less expressive error message)
[13:44] <jelmer> dwt: 0.4.9 is the latest released version and should no longer contain this bug
[13:44] <jelmer> you may have to throw away your local state (~/.bazaar/subversion.conf) though
[13:44] <dwt> Does it work with bzr. 1.3.1?
[13:44] <dwt> I'm not quite ready to go to 1.4 yet...
[13:45] <jelmer> yes, it works with 1.3
[13:45] <dwt> oh dang.. sorry about that, but I am on 0.4.9
[13:46] <dwt> So the bug is still present
[13:46] <dwt>   svn                  /Users/dwt/.bazaar/plugins/svn [0.4.9]
[13:47] <jelmer> you may have to throw away your local state (~/.bazaar/subversion.conf) though
[13:48] <dwt> ok, I'l try that
[13:49] <dwt> indeed that changes the output
[13:50] <dwt> now I'm getting this : "bzr: ERROR: These branches have diverged.  Try using "merge" and then "push"." which ges me a bit, as I'm sure I didn't commit to these directories from anywhere else
 and trying "bzr merge" then gives "bzr: ERROR: Branches have no common ancestor, and no merge base revision was specified."
[13:53]  * dwt is off to the manual to find out how to get the correct merge base revision.
[13:54] <ubotu> New bug: #223042 in bzr "Feature request: Exclude option for some commands" [Wishlist,Confirmed] https://launchpad.net/bugs/223042
[13:59] <cammoblammo> Odd_Bloke: Phew!!
[14:00] <jelmer> dwt: You may have to recreate your local branch :-(
[14:01] <jelmer> dwt: this is part of the bugfix
[14:01] <dwt> :-/
[14:01] <dwt> jelmer: Is there a way to get the changes I did locally out of the bzr repo into the new branch?
[14:01] <dwt> apart from using diff and patch directly?
[14:02] <jelmer> dwt: the "replay" and "rebase" commands in the rebase plugin should be able to help you
[14:02] <dwt> thanks I'l look into them
[14:19] <dwt> jelmer: I'm a bit confused by the documentaton of the rebase plugin
[14:20] <dwt> it seems it does the exact oposite of what I want
[14:20] <jelmer> you should be able to create a new copy of the branch in svn
[14:20] <dwt> [x] done
[14:20] <jelmer> and then run "bzr replay" from there for each revision in your previous local branch that you would like to import
[14:21] <dwt> ah...
[14:21] <dwt> The important bit is not to try to use rebase. :-)
[14:21] <dwt> Thanks a bunch, I'l see what I can get done this way.
[14:29] <dwt> Yehaw. Thanks jelmer! Now I got the commit working to svn. :-)
[14:29] <dwt> On to the next question: Is there a way to make bzr remember the pasword for the svn server? Preferably in the mac os x keychain... :-)
[14:32] <jelmer> dwt: bzr-svn should already be using the os x keychain but unfortunately there are some bindings missing
[14:33] <jelmer> (python-subversion doesn't contain bindings for the os x keychain yet)
[14:33] <dwt> damn.
[14:33] <dwt> Is that going to be included in 1.5?
[14:36] <jelmer> doubt it - nobody has done the patch for that yet afaik
[14:37] <jelmer> you can still use the trick described in the FAQ though
[14:46] <dwt> whois jelmer
[14:46] <dwt> ups, sorry
[14:46] <jelmer> I'm jelmer (-:
[14:47] <dwt> :-) Yeah, I wanted to get your correct lastname to give credit on my blog
[14:48] <dwt> got it
[14:56] <abentley> vila: My apologies for the spam.
[15:05] <jelmer> dwt: ah, cool
[15:06] <dwt> :-) You're welcome jelmer
[17:42] <awmcclain> Hey all... what's the command to change the branch's remembered location?
[17:46] <radix> awmcclain: pass --remember to push or pull
[19:41] <vila> abentley: no worries, BB is a good friend. You recognize *real* good friends in that, at least once, they deceive you :-)
[20:03] <abentley> vila: :-)
[21:31] <epsy> hi
[21:31] <epsy> i'm getting problems getting a repository to work properly
[21:31] <beuno_> epsy, what problems are you having?
[21:32] <epsy> whenever i try to co from it (bzr+ssh://) i get this:
[21:32] <epsy> bash: line 1: bzr: command not found
[21:32] <epsy> i had the same problem locally, because i had bzr installed in my home dir
[21:32] <epsy> so i've put an alias in my ~/.bashrc
[21:33] <beuno_> epsy, do you have bzr installed remotely?
[21:33] <epsy> yes
[21:33] <beuno_> bzr+ssh invokes bzr on the other end too
[21:33] <epsy> when i just said locally, i meant locally on the server, heh
[21:33] <beuno_> epsy, and how about locally?
[21:34] <epsy> so i shall try with ssh:// alone?
[21:34] <epsy> beuno_, on my computer?
[21:34] <beuno_> it seems you are missing bzr on one of the ends  :)
[21:34] <beuno_> epsy, yeap
[21:34] <beuno_> try ssh://
[21:34] <beuno_> or sftp even
[21:34] <epsy> ssh:// --> unsupported
[21:35] <beuno_> epsy, sftp
[21:35] <epsy> oh, i'll have to install paramiko, this will take a little while
[21:35] <beuno_> epsy, or use http, if you have access via http
[21:35] <epsy> i don't want this repo to be accessible via http
[21:35] <epsy> :)
[21:35] <beuno_> brb, I don'nt know why I'm here twice  :p
[21:36] <beuno_> epsy, try and ssh to the remote machine
[21:36] <beuno_> and run:  bzr version
[21:36] <beuno_> and make sure it runs correctly
[21:38] <epsy> hm, cya? :)
[21:39] <epsy> wb
[21:39] <epsy> $ bzr version
[21:39] <epsy> Bazaar (bzr) 1.3.1
[21:39] <beuno> :)
[21:39] <beuno> hrm
[21:39] <epsy> [goes forth with more details]
[21:39] <beuno> both locally and remotely?
[21:39] <epsy> note that bzr is aliased
[21:39] <epsy> on the remote machine i mean
[21:40] <epsy>  $ grep "bzr" ~/.bashrc
[21:40] <epsy> alias bzr="python2.4 ~/bin/bzr"
[21:42] <beuno> epsy, well, I can't think of anything else then. If you bzr command works fine on both ends, you shouldn't be getting a command not found
[21:43] <epsy> i am trying with ftp:// right now
[21:44] <epsy> $ bzr co ftp://xclan@xclan.armagetron.co.uk/xclan.armagetron.co.uk/
[21:44] <epsy> FTP xclan@xclan.armagetron.co.uk password:
[21:44] <epsy> /  0/0
[21:44] <epsy> looks like stuck
[21:44] <beuno> epsy, might take a while if the repo is big
[21:45] <epsy> 2 revisions yet
[21:45] <epsy> :P
[21:46] <epsy> beuno, is there a way i can tell my bzr client which bzr command to use on the other end?
[21:48] <Verterok> epsy: BZR_REMOTE_PATH=~/bin/bzr
[21:48] <beuno> hey Verterok  :)
[21:48] <Verterok> beuno: hi :)
[21:49] <epsy> hi and thank you very much :)
[21:49] <Verterok> epsy: Hi, np ;)
[21:49] <abentley> epsy: There is also a configuration variable: bzr_remote_path.  I think this is better to use, because it can be specified on a per-location basis.
[21:49] <epsy> really?
[21:49] <epsy> wow, neat
[21:49] <abentley> Yep, see bzr help configure.
[21:49] <epsy> okay
[21:49] <abentley> bzr help configuration, I should say
[21:50] <epsy> haha
[21:50] <Verterok> abentley: Hi, and thanks for the tip (I wasn't aware of it) :)
[21:50] <abentley> Verterok: Hi, and np.
[21:51] <thumper> morning
[21:53] <thumper> abentley: I see you had a prolific weekend
[21:54] <abentley> thumper: Heh, still having my weekend.  Might get some moe fixes for fetch ready.
[22:25] <epsy> the documentation on the authentication.conf file isn't very clear
[22:25] <epsy> there's an example:
[22:26] <epsy> [myprojects]
[22:26] <epsy> scheme=ftp
[22:26] <epsy> host=host.com
[22:26] <epsy> user=joe
[22:26] <epsy> password=secret
[22:26] <epsy> what would i put intead of myprojects?
[22:26] <frsk> wild guess; the path to your project
[22:26] <epsy> local path?
[22:27] <frsk> maybe
[22:27] <frsk> I'm just gessing :)
[22:27] <frsk> guessing
[22:34] <epsy> blah it's still prompting me for a password, are there characters i need to excape?
[22:34] <epsy> escape*
[23:02] <igc> morning