[07:21] moin === zyga is now known as zyga-afk === zyga-afk is now known as zyga === zyga is now known as zyga-food === LyraaOptimHome is now known as jazon [13:14] hello everybody I have a problem with my bzr server when I do a push on command line it say me 'not a branch', when I try with bzr explorer it say me 'This transport does not update the working tree' [13:15] jazon: is the location you're pushing from aqctually a branch? [13:15] Yes [13:15] jazon: what does "bzr info" say about it? [13:17] jelmer http://pastebin.com/4RuAA94X [13:23] can you help me? [13:23] jazon: I mean, what does "bzr info" say about your local branch? === zyga-food is now known as zyga [13:24] I wasn't in good directory... [13:26] http://pastebin.com/fVr1VAyK [13:28] jazon: so 'bzr push' works now? [13:29] no, it's say me look at bzr help working-trees [13:30] I don't understand what is the matter [13:31] jazon: if you push to a remote location, bzr will only update the remote branch [13:31] not the remote working tree === yofel_ is now known as yofel [13:32] for that, you need to run 'bzr up' on the remote server [13:32] I have to be connected permanently on my server with ssh? [13:34] jazon: no, you just have to run 'bzr up' after you push to the branch [13:34] jazon: (if you care about the working tree on the server side) [13:36] I have to run bzr up on the server no? [13:42] jelmer: thanks for your comment on my merge proposal. Did you mean to vote "approve"? [13:45] jazon: if you want to have the working tree up to date, yes [13:45] abentley: Euhm, yes.. one sec [13:49] abentley: done [13:49] jelmer: thanks. === deryck is now known as deryck[lunch] === beuno_ is now known as beuno === deryck[lunch] is now known as deryck === zyga is now known as zyga-afk [18:50] Guys, for some reason I cannot commit this project to Launchpad, even though I got my ssh set up and everything. I keep getting the bzr: ERROR: Cannot lock LockDir() error [22:23] hello [22:29] hi mgrandi [22:30] do you happen to have gpg installed without an agent? [22:34] mgrandi: I didn't hit this particular issue but some other people did [22:34] yeah [22:34] well i meant [22:34] i'm writing up a response now, but from reading the gpg man page, it seems that $GPG_AGENT_INFO will be defined if you have an agent [22:34] mgrandi: mgz was able to reproduce it, apparently withtout a gpg agent [22:34] and i'm trying to make sure thats the case [22:34] cause then we can just check to see if that variable is define, and do the right thing from there [22:35] i have no idea what happens on windows [22:35] mgrandi: I'm wondering if we should be specifying this option at all - shouldn't gpg already try to do this by itself? [22:35] thats what i think [22:36] but the whole issue was that while bzr explorer, that gpg would be printing stuff out to a tty [22:36] gpg: cannot open `/dev/tty': No such device or address [22:36] bzr: ERROR: Failed to GPG sign data with command "['gpg', '--clearsign']" [22:36] caused that ^ [22:37] mgrandi: without a gpg agent? [22:37] that was with an agent [22:37] mgrandi: why would it need a tty if you have an agent? [22:38] good question. gpg says on the --no-tty option: "Make sure that the TTY (terminal) is never used for any output. This option is needed in some cases because GnuPG sometimes prints warnings to the TTY even if --batch is used." [22:38] and --quiet means "try and be as quiet as possible" [22:39] i dont know what happens if you tried to use bzr explorer to sign without an agent [22:39] mgrandi: it's not wrong to use the TTY [22:39] yes, but on linux it was saying that it can't find /dev/tty [22:40] which makes me think that it doesn't "have" a tty to print out to [22:40] cause its a pyqt4 app [22:40] mgrandi: was that bit fatal though? [22:40] it caused signing to fail [22:40] the code just says "failed to gpg sign" if gpg doesn't return 0 [22:40] mgrandi: but it tries to use the gpg agent first [22:43] i know [22:43] i just tried on my mac, if you enter the wrong password, it prints "gpg: Invalid passphrase; please try again ..." [22:43] to the terminal [22:43] rigfht, it falls back to the tty if using the gpg agent doesn't work [22:43] im not exactly sure whats going on with the original bug report, since it worked on windows and mac fine [22:43] with just 'gpg --clearsign' [22:44] but then on linux, somehow running bzr explorer meant it didn't have a tty? [22:44] should it have one? [22:44] mgrandi: I think we should revert the use of --no-tty for now, as it causes a serious regression [22:44] mgrandi: right, bzr explorer usually wouldn't have a tty [22:45] hmm. [22:45] thats why i was thinking of just checking to see if we have an agent [22:45] cause --no-tty works fine if you have an agent, but if you dont, you need the terminal to enter your passphrase [22:46] mgrandi: that means there won't be any fallback to the terminal if the gpg agent doesn't work [22:47] mgrandi: I'm worrying we're trying to do gpg's job for it [22:47] this sort of logic really belongs in gpg, not bzr [22:47] yeah. so if we don't want to use --no-tty, then how do we solve the original problem , with signing failing cause of no /dev/tty [22:48] you say you want to use terminal as a fallback, but then if we are using bzr explorer, then there is no terminal (in most cases) to fall back to [22:48] err, 1/3 cases [22:50] mgrandi: I think that might warrant some more investigation, but this is a serious regression.. let's at least fix that bit [22:50] yeah [22:50] go for it [22:50] or do i have to do something [22:50] mgrandi: no, that's okay [22:51] it seems that all of this is just sprouting from the fact that we are using gpg as a separate program rather then a nice api we can bind to, but don't think there is any way around that [22:51] mgrandi: it would be interesting to use pygmge to do the actual signing [22:51] but that's a significantly larger change [22:51] yeah [22:51] but we might have to cause we are juggling where bzr is being run as [22:52] command line, bzr explorer started from terminal, bzr explorer without a terminal, [22:52] and isn't that the thing that is required to check signatures? [22:53] mgrandi: how do you mean? [22:54] if you try and run bzr verify signatures without it installed you get this: bzr: ERROR: python-gpgme is not installed, it is needed to verify signatures [22:55] mgrandi: ah, yes, it is [23:00] looking at 'gpgme', the gpg folks say that applications should use that, so that seems like that would be the better solution [23:02] mgrandi: perhaps the best thing to do is to revert this fix, and just consider moving gpgme for signing a proper fix for bug 847388 [23:02] Launchpad bug 847388 in bzr (Ubuntu Precise) ""gpg: cannot open `/dev/tty': No such device or address" on Ubuntu when signing commits" [Medium,Fix released] https://launchpad.net/bugs/847388 [23:02] yeah [23:02] i say revert it, the bzr explorer bug can be worked around by just using the terminal to commit