=== Quintasan_ is now known as Quintasan === yofel_ is now known as yofel === Vorpal_ is now known as Vorpal === medberry is now known as med_out [20:08] * AuroraBorealis sighs [20:08] for some reason when bazaar calls gpg it doesn't call pinentry and it just fails =( [20:13] it seems that bzr explorer needs to use --no-tty [20:13] for the gpg command [21:02] AuroraBorealis: please file a bug :) [21:06] k [21:16] submitted. https://bugs.launchpad.net/bzr-explorer/+bug/847388 [21:16] Ubuntu bug 847388 in Bazaar Explorer ""gpg: cannot open `/dev/tty': No such device or address" on Ubuntu when signing commits" [Undecided,New] [21:17] AuroraBorealis: thanks [21:17] i just commit using the regular terminal command and it works, so i think its just a --no-tty issue [21:17] however i dont know where in the code the command gets called so i can't test it xD [21:18] AuroraBorealis: it's in bzrlib/gpg.py [21:27] it seems that the tty environment variable is not set in ubuntu [21:27] and thats whats causing it to freak out [21:28] not sure if thats bad or not [21:39] it also appears that --no-tty fixes it, but i'm unsure of how to integrate that :3 [21:48] annnnnd i seem to of figured out a solution. but now how to i generate a patch or something :o [21:49] AuroraBorealis: I'd recommend running the gpg related tests and fixing anything that breaks: ./bzr selftest --no-plugins gpg [21:50] after i make my changes? [22:02] AuroraBorealis: yep [22:03] kk [22:03] AuroraBorealis: well, ideally you should fix the tests to expect what you want to happen and then fix bzrlib.gpg [22:03] but this works too, and makes more sense given you've already changed bzrlib.gpg. [22:03] where are the tests located? [22:03] and this is kinda hard to test as it requires bazaar explorer [22:04] (as os.environ("TTY") has to not be set) [22:04] AuroraBorealis: this shouldn't require bzr explorer - I just meant tests that make sure that --no-tty is specified [22:06] yeah, i'm assuming these are unit tests. but the way to check that --no-tty is only specified correctly is to be using it where the environment variable for tty is not set, like in a GUI [22:06] unless i'm misunderstanding something [22:11] AuroraBorealis: sure, but in the unit test you can override the environment variable and see if the right parameters are specified [22:11] ah ok. [22:11] AuroraBorealis: see bzrlib.tests.TestCase.overrideEnv [22:22] i cant seem to run this bazaar branch i checked out from launchpad because it can't import "shlex_split_unicode" [22:26] any idea how to fix that jelmer so i can run the tests? xD [22:35] hi jelmer [22:39] hi Noldorin_ [22:39] AuroraBorealis: I'm not sure - that should only be necessary on Windows I think [22:39] well the test cases are working i guess [22:39] so i'm trying to figure how how i borked those :< [22:46] jelmer, i am finding many bzr bugs these days... [22:46] while researching this issue [22:47] Noldorin_: what exactly? [22:47] jelmer, for a start, https://bugs.launchpad.net/bugs/846122 [22:47] Ubuntu bug 846122 in Bazaar "bzr thinks working tree is out of date after uncommit" [Undecided,Confirmed] [22:48] Noldorin_: is the history empty after that operation perhaps? [22:48] what history? [22:48] Noldorin_: what's the output of "bzr revno" [22:49] jelmer, 46 [22:49] Noldorin_: that's odd - is this in a bzr-git tree? [22:50] nope [22:50] Noldorin_: bound branch? [22:51] jelmer, maybe [22:51] i forget [22:57] is there a way to use 'print' when you are using these test cases? it seems that its not actually printing them (and causing other tests to fail) [23:03] AuroraBorealis: I generally use bzrlibtrace.mutter [23:03] AuroraBorealis: I generally use bzrlib.trace.mutter [23:04] AuroraBorealis: that will be printed as part of the test output if a test fails [23:05] also another question [23:05] bzrlib.TestCase.overrideEnv says that the environment variable will be reset after each test [23:06] is a test the entire class that extends TestCase or are they the individual methods? [23:06] the method [23:07] the class is a way to group related tests and (sometimes) test helpers that are specific to that group [23:07] ok. so i guess i have no idea why the environment variable for 'tty' would be none [23:12] as i thought it would be None if you were running like a user interface, but its none even if you invoke bzr from a command line [23:12] so i have no idea how to distinguish when you should add the --no-tty switch or not [23:37] well, it appears that just adding --no-tty works, so how do i submit this as a patch to the bug report i opened?