[00:46] <efes> Hello ( :
[00:47] <efes> I'd like to create my local repository from read only branch. At the same time I'd like to create an another branch to keep my sources in different branch than project's main. Do I need "bind new branch to parent location" option?
[08:45] <vila> jelmer: I'm using bzr-gtk trunk (where bzr-notify has been removed). Yet, I get notifications (good) and those weird progress bars hanging around (bad).
[08:45] <vila> jelmer: It puzzles me that I still get notifications but can't find what I did to retain them across their removal from bzr-gtk trunk.... Any idea ?
[08:46] <vila> jelmer: wtf... 'bzr-notify is /usr/bin/bzr-notify' on raring ?
[08:48] <vila> ooohh, bzr installed system-wide relying on bzr-gtk installed system-wide, no wonder I couldn't find anything relevant when running bzr from sources, ok, thanks for the help :-D
[08:49] <vila> jelmer: and bzr-dbus getting in the middle of the mess right ?
[09:07] <Pegasus_RPG> Hello. I'm trying to create a new branch that is _not_ stacked on trunk. how can I do that?
[09:07] <Pegasus_RPG> (It contains a totally separate set of files but they're related to the main project)
[09:09] <Pegasus_RPG> Just doing bzr push lp:~me/project/newbranch keeps stacking it on lp:~me/project
[09:11] <vila> Pegasus_RPG: it's lp deciding to stack but that should be harmless for you, are you planning to stack on *another* branch at some point ?
[09:12] <vila> Pegasus_RPG: harmless as in: "since you're pushing revisions that are unrelated to the trunk ones, you don't use the trunk ones"
[09:13] <Pegasus_RPG> I'm not
[09:14] <Pegasus_RPG> okay, so nothing to worry about?
[09:14] <Pegasus_RPG> (bzr reconfigure --unstacked doesnt' seem to have any effect, BTW)
[09:14] <vila> Pegasus_RPG: if you *really* want to get rid of the stacking on your newly pushed branch you can (once it's created) do: <interrupt> no, nothing to worry </interrupt>
[09:14] <vila> bzr config -d lp:<new branch> --remove stacked_on_location
[09:15] <vila> bzr config -d lp:new branch> before and after the command above to ensure you get it right
[09:19] <Pegasus_RPG> ok thank you
[09:27] <jelmer> vila:yeah, there are a fair number of open issues with bzr-notify :-(
[09:28] <jelmer> vila: we discussed removing it altogether, did that not happen?
[09:28] <jelmer> vila: ah, r794
[09:29] <jelmer> probably hasn't made it into the debian/ubuntu package yet
[09:29] <vila> jelmer: I breifly tried to debug but couldn't find how to get a pdb prompt to understand who is spawning the progress bar. I have a vague feeling the fix is probably one line to tell the offending code to use a silent pb...
[09:29] <vila> jelmer: yup, that's my feeling as well, but since I'm stubborn sometimes I still like to be able to toy around with it ;)
[09:30] <vila> jelmer: so there are really two things: how to properly remove bzr-notify for everybody and how to make it available locally to me so I can fix it ;)
[09:31] <vila> jelmer: I'm of course a teeny bit more interested by the later but I won't mind helping for the former ;-D
[09:31] <jelmer> vila: for the first, get one of the debian packagers to merge a new upstream snapshot :)
[09:31] <jelmer> vila: for the second, I guess you can just reverse merge r794 ?
[09:32] <vila> jelmer: and uninstall the system-wide versions ?
[09:32] <vila> jelmer: and... I miss the step to activate it locally for my dbus session (instead of the system one)
[09:35] <jelmer> vila: using the local dbus session requires James Henstridge's bzr-dbus branch
[09:36] <vila> jelmer: lp:~jamesh/bzr-dbus/kill-broadcast-daemon ??
[09:38] <jelmer> vila: yeah, that'sit I think
[09:39] <vila> jelmer: ok, thanks, I know what/where to look next
[09:39] <jelmer> vila: I think there were conflicts if you try to merge it into lp:bzr-dbus trunk nowadays though
[09:40] <vila> jelmer: yup, I saw your review, thanks
[09:40] <vila> jelmer: I understand I new a bit more fluency with dbus and that may just be the right exercise
[09:51] <fullermd> Somehow, this puts me in mind of "I've been wanting to learn a bit more about conducting open-heart surgery, and these chest pains I've been having all week seem like the perfect opportunity!"
[09:53] <jelmer> fullermd: I'm not sure if a broken bzr-dbus is quite as life-threatening.
[09:54] <fullermd> But it's not as cool to dig into either.
[10:02]  * vila feels warmer reading fullermd writing about me and his heart ;)
[14:36] <jelmer> vila: Does bzr-dbus actually still work ?
[14:37] <vila> jelmer: err, I get notifications with the versions installed system-wide in raring, not sure that answers your question though ;)
[14:37] <jelmer> vila: I guess that is a yes.