[09:00] <lolek> hello all
[09:06] <mgz> morning!
[09:09] <lolek> erm... guys... i'm a bit confused... few days ago we're looking for some new versioning system. The problem was that one of the developers is using M$ platform. From what i've read bzr has got better support for m$ than for example git, but after few days i see that: bzr-eclipse plugin is... not maintained since 2008 o.O!, bzr-svn plugin doesn't have maintainer also... and my question is ... what's up...? is bazaar really a good alternative for versioning s
[09:11] <mgz> lolek: you hit the length limit
[09:30] <lolek> mgz: erm.. what was the last word you got ?
[09:32] <mgz> it was probably the last bit, "for versioning s"
[09:33] <mgz> anyway, in my experience, yes, it is, but not all plugins are as well maintained as others (bzr-svn is actually pretty well cared for, jelmer has just switched job recently)
[09:33] <mgz> and the future is a little uncertain, but people do care about bzr
[09:36] <lolek> ok here is the last part
[09:36] <lolek> system for commercial usage ? i know.. i see it's working ok for canonical, but for me ok.. bzr-svn i can live without that, but bzr-eclipse ?
[09:45] <mgz> so, people have very different attitudes to ide intergration
[09:46] <mgz> the basic issue there is you need someone who uses that ide to work on the plugin, it's not something someone else can easilly pick up
[10:27] <lolek> well i understand that
[10:28] <lolek> what i can say now, that the bzr-eclipse plugin is missing just one thing for me/us... the compare to specific revision/url
[10:28] <lolek> that's all
[10:33] <mgz> lolek: then it's really worth looking at just adding that
[10:34] <mgz> I'd be happy to assist if you have questions, but don't use eclipse
[10:34] <lolek> well ok
[10:34] <lolek> but i don't thing that my skill will allow me to add that functionality ;)
[10:35] <lolek> s/skill/skills
[11:59] <venefyxatu> I've recently learned about mercurial queues, and now that I'm using it to work on several different changesets within one branch, move them around, reorder, apply/unapply as necessary I'm beginning to really love it - is there something like this available for bzr?
[11:59] <venefyxatu> (sort of like shelve on steroids, I believe)
[12:16] <lolek> guys, i've hitted something like: http://pastebin.com/7RhxJbiM, it's error from bzr-notify...
[12:16] <lolek> any idea what could be wrong.. it's ubuntu 12.04/amd64
[12:30] <mgz> lolek: just disable bzr-notify, see bug 998994
[12:31] <lolek> :/
[12:31] <mgz> it's not used for anything significant is bzr-gtk
[12:35] <lolek> hmm don't get it ?
[12:42] <mgz> lolek: see the linked merge proposal, the code has been removed in newer versions of bzr-gtk
[12:46] <lolek> oh
[12:50] <lolek> hmm, so bzr-notify is no longer available ? i.e. it will be removed ?
[12:54] <mgz> lolek: are you actually using it, or did you just notice it breaking?
[12:55] <lolek> well i was trying to use it :)
[13:00] <lolek> i saw how this is working at my friends desk, and it's nice tool
[13:01] <lolek> and the funiest thing is he also have ubu 12.04 but .. he is using unity, and i'm using gnome-shell
[13:46] <jelmer> lolek: bzr-notify has been removed in bzr-gtk trunk
[13:47] <lolek> well that's not good
[13:47] <jelmer> lolek: mostly since there were a fair number of issues like the one you hit, and they'd been open for quite some time
[13:48] <lolek> hmm
[13:48] <lolek> and.. do You plane to give some other app for the same functionality ?
[13:49] <jelmer> lolek: perhaps if somebody steps up to do so. nobody was taking care of bzr-notify, that was one of the reasons we decided to eventually remove it.
[13:49] <lolek> :/
[15:00] <lolek> jelmer: well i've made one thing, added the missing argument as: None and.. bzr-notify is working
[15:01] <jelmer> lolek: ah, nice
[15:01] <lolek> but there is one problem
[15:02] <lolek> notification is working i see the popup with two buttons: Inspect and Branch... neither of them is working... what should the buttons ?
[15:02] <lolek> *what the buttons should do ?
[15:04] <jelmer> what their labels say :-)
[15:04] <lolek> Inspect / Branch
[15:04] <jelmer> Inspect used to open a particular revision in "bzr viz"
[15:05] <jelmer> and Branch launches the clone window
[15:05] <lolek> hmm ok
[15:05] <lolek> so both are not working ;d
[15:05] <lolek> and i dunno why :]
[15:08] <lolek> anyway i see tha problem
[15:10] <lolek> it's related to gnome-shell vs unity .. the way that they use the notification, i.e. unity doesn't allow to place buttons in notifications, while gnome-shell do... maybe there would be a possibility to, create bzr-notify as systray app, after that we could show notifications for both gnome-shell and unity  in the same way, and add to that tray options: (inspect last commit/branch last commit) ?
[15:10] <lolek> thanks to that the bzr-notify will work as usually, and both worlds would be happy
[15:11] <lolek> jelmer: what do You think about that ?
[15:11] <jelmer> lolek: that's what bzr-notify did - it supported both the appindicator API for unity and the regular systray stuff for GNOME2
[15:12] <lolek> well yeah but from what i saw on the launchpad it seems that bzr-notify will be removed.. and that's said... :(
[15:13] <jelmer> lolek: it's already been removed
[15:13] <lolek> hmm
[15:13] <lolek> bzr uncommit ?:D
[15:14] <jelmer> lolek: as I said, it hadn't been maintained in a while and there were a number of open issues with it; I don't think bringing it back without addressing that would be a good idea.
[15:14] <lolek> i can agree
[15:14] <lolek> but.. if so.. is there any replacement for that ?
[15:15] <jelmer> lolek: no, there's nothing that does anything similar at the moment
[15:15] <lolek> hmm
[15:24] <lolek> ok, be back tomorrow, bye
[20:21] <evillyEvil> How do I revert all files EXCEPT some certain files in a project to the last commit state?
[20:23] <evillyEvil> or is that even possible?
[21:01] <fullermd> Not as a single step.
[21:02] <fullermd> You could do some dancing around sh-ery with status and revert.  You could shelve the changes you want, revert, then unshelve 'em.
[21:20] <dpb___> I have a weird bzr symlink-shared-repo problem.  I wrote a test case.  Should this just be a bug, or is there something I'm doing wrong?  http://pastebin.ubuntu.com/1354131/
[21:24] <dpb___> note: the fact that the symlink points higher up in the chain is meaningless, it just needs to point somewhere outside the shared repo.
[21:27] <fullermd> It's probably another incidence of https://bugs.launchpad.net/bzr/+bug/995055
[21:36] <dpb___> fullermd: thanks.  We have a workaround for it in our narrow case. (unwind the symlink before handing it to bzr).
[21:44] <thumper> abentley: ping
[21:44] <abentley> thumper: pong
[21:45] <thumper> abentley: I have a pipeline question for you
[21:45] <abentley> Sure, what's the question?
[21:45] <thumper> abentley: I managed to get some fucked up situation in my current checkout, so I moved it and re checked out trunk
[21:45] <thumper> abentley: went into that directory and did 'bzr pipes' expecting only trunk
[21:45] <thumper> abentley: but it had the other branch there too
[21:45] <thumper> abentley: why?
[21:46] <abentley> thumper: The pipeline data is associated with the branches, not the checkout.  It is stored in .bzr/branch/branch.conf.
[21:47] <thumper> ok
[21:47] <thumper> ta
[21:47] <abentley> np
[21:47] <thumper> abentley: that was simple wasn't it?
[21:47] <abentley> :-)
[21:47] <thumper> btw, still using pipelines daily
[21:49] <abentley> Glad to hear it.
[23:49] <felipec> what should I use instead of ControlDir.open(url) in older versions of bzr?
[23:49] <jelmer> felipec: BzrDir.open(url)
[23:52] <felipec> jelmer: cool
[23:52] <felipec> that should be OK for newer versions as well, right?
[23:53] <jelmer> felipec: I had plans to deprecate BzrDir.open because of ControlDir.open, but that hasn't happened yet
[23:53] <jelmer> s/yet//
[23:58] <felipec> all right
[23:58] <felipec> jelmer: what about this error? http://pastie.org/5368946
[23:59] <felipec> er, last line: TypeError: __init__() got an unexpected keyword argument 'help'
[23:59] <jelmer> felipec: what's the actual exception?