1 2012-08-11 05:54:41 <kauzu> sudo apt-get install libdb4.8++-dev does not work with ubuntu 12.04 but i need this to compile bitcoin-qt ... where can i get this ?
 2 2012-08-11 05:56:13 <Karmaon> kauzu: try 5.1
 3 2012-08-11 05:56:15 <Ferroh> kauzu, just install libdb5.1
 4 2012-08-11 05:56:21 <Karmaon> and i'm gone
 5 2012-08-11 05:58:00 <kauzu> but the bitcoin reademe says they are not compatible
 6 2012-08-11 05:58:49 <kauzu> The first time you run with a 5.X version the database will be upgraded, and 4.X cannot open the new format. This means that you cannot go back to the old statically linked version without significant hassle!
 7 2012-08-11 06:02:01 <kauzu> where is the database stored so i can make a copy of the 4.x version
 8 2012-08-11 06:08:42 <kauzu> is it ~/.bitcoin/
 9 2012-08-11 06:08:44 <kauzu> ?
10 2012-08-11 06:16:54 <kauzu> ?
11 2012-08-11 06:16:58 <kauzu> hel??
12 2012-08-11 06:17:01 <kauzu> *help
13 2012-08-11 06:40:24 <kauzu> ok --- compiles fine now...
14 2012-08-11 12:02:44 <Ferroh> :(
15 2012-08-11 12:02:54 <Ferroh> the error when a key cant be imported due to the wallet being locked,
16 2012-08-11 12:03:02 <Ferroh> is identical to the error given when the key is already in the wallet
17 2012-08-11 13:11:46 <sipa> luke-jr: mockdb fails in combination with ultraprune, with a very strange error
18 2012-08-11 13:12:26 <sipa> when "loading" the mock wallet, it tries to deserialize data that looks like it's coins.dat data
19 2012-08-11 13:12:45 <sipa> is it possible it's effectively sharing all databases in mock mode?
20 2012-08-11 13:14:02 <sipa> right, that seems to be it
21 2012-08-11 13:15:26 <sipa> luke-jr: i'll change it to use the passed pszFile as dbName, instead of "main", in mock mode
22 2012-08-11 13:55:54 <bitcoinfans> I found something better than http://www.bitcoinfans.com
23 2012-08-11 14:49:01 <dk5> is there a time the bitcoin-qt client would report an IP of 0.0.0.0 in a version message?
24 2012-08-11 14:49:13 <dk5> or a port of 0?
25 2012-08-11 14:54:38 <edcba> the question is why you shouldn't trust that...
26 2012-08-11 14:54:52 <dk5> ?
27 2012-08-11 14:55:03 <sipa> dk5: yes, when it cannot determine its own address
28 2012-08-11 14:55:16 <sipa> or knows that it cannot be reached by any
29 2012-08-11 14:55:46 <dk5> would it send around addr messages with 0.0.0.0 as well?
30 2012-08-11 14:56:11 <sipa> it shouldn't
31 2012-08-11 14:56:26 <sipa> and if it did, those wouldn't get forwarded anyway (they're not routable)
32 2012-08-11 14:56:33 <dk5> i see
33 2012-08-11 14:56:52 <dk5> is there any other address the client would report that is not the real address for the person besides 0.0.0.0?
34 2012-08-11 14:58:59 <sipa> it should only ever report either 0.0.0.0 or whatever it believes is its own address
35 2012-08-11 14:59:15 <dk5> ok. thanks :-)
36 2012-08-11 15:04:32 <dk5> is there any reason to have a legitimate ip but a port of 0?
37 2012-08-11 15:05:36 <dk5> in the version message
38 2012-08-11 15:07:00 <dk5> i've seen people sending version messages with a correct IP and a port of 0. is there a reason to be suspicious about these?
39 2012-08-11 15:29:51 <luke-jr> sipa: I don't think you can pass a dbName without breaking it..
40 2012-08-11 15:30:35 <luke-jr> dk5: lazy code?
41 2012-08-11 15:31:51 <sipa> luke-jr: seems to work fine
42 2012-08-11 15:33:43 <luke-jr> sipa: without creating any files?
43 2012-08-11 15:34:06 <sipa> sure
44 2012-08-11 15:34:09 <luke-jr> hmm
45 2012-08-11 15:34:12 <sipa> i'm talking about dbname, not filename
46 2012-08-11 15:34:18 <luke-jr> I wonder why the docs I read said it had to be NULL
47 2012-08-11 15:34:53 <sipa> in your code dbname isn't NULL, it's "main", just like in non-mock mode
48 2012-08-11 15:35:14 <sipa> i'm exploiting the fact that bdb does support multiple databases in one file
49 2012-08-11 15:37:21 <luke-jr> well, I guess if it works it works
50 2012-08-11 15:42:07 <sipa> so in normal mode you use (file=<filename>, db="main), in mock mode you use (file=NULL, db=<filename>)