1 2017-04-16 06:13:56	0|harrymm|exit
 2 2017-04-16 06:30:54	0|harrymm|exit
 3 2017-04-16 09:16:14	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #10078: [qa] Fundraw: Use named args to limit scope of names (06master...06Mf1703-qaNamedShadow) 02https://github.com/bitcoin/bitcoin/pull/10078
 4 2017-04-16 09:22:44	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #8319: [qa] wallet*.py: Check for salvagewallet regressions  (06master...06Mf1607-qaSalv) 02https://github.com/bitcoin/bitcoin/pull/8319
 5 2017-04-16 09:36:13	0|MarcoFalke|github removed all pulls from our leveldb repo after the transition. Maybe send them a follow up sipa? E.g. https://github.com/bitcoin-core/leveldb/issues/17
 6 2017-04-16 09:43:12	0|sipa|MarcoFalke: no, i moved the repo
 7 2017-04-16 09:43:16	0|sipa|and created a new one
 8 2017-04-16 09:43:23	0|sipa|that was the only way to fix it
 9 2017-04-16 09:44:06	0|sipa|https://github.com/bitcoin-core/leveldb-old/pulls
10 2017-04-16 09:44:24	0|sipa|i recreated my own PRs in the new repo, though
11 2017-04-16 09:50:00	0|MarcoFalke|Ah ok. Maybe enable the "issues" tab in the new repo.
12 2017-04-16 09:50:23	0|sipa|oh!
13 2017-04-16 09:59:48	0|sipa|MarcoFalke: well i was planning to just delete the old repo
14 2017-04-16 10:00:04	0|sipa|i moved it at first to make sure no important branchss were lost
15 2017-04-16 10:02:36	0|MarcoFalke|Hmm. What about the comments and pull request history?
16 2017-04-16 10:07:50	0|sipa|unsure, i don't feel strongly either way
17 2017-04-16 11:49:25	0|__0|got this issue https://github.com/bitcoin/bitcoin/issues/7970 what to do? apt-get install libdb-dev already did
18 2017-04-16 11:49:40	0|__0|debian 8.7
19 2017-04-16 11:55:05	0|sipa|follow the instructions in https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md
20 2017-04-16 11:55:11	0|sipa|it lists all packages you need to install
21 2017-04-16 12:00:18	0|__0|thanks, sipa, i'll try this!
22 2017-04-16 12:06:13	0|__0|debian 8.7 has no libdb4.8-dev or libdb4.8++-dev packages:-(
23 2017-04-16 12:08:07	0|sipa|use 5.3
24 2017-04-16 12:08:16	0|sipa|and use --with-incompatible-bdb, as explained in the document
25 2017-04-16 12:08:36	0|sipa|your wallet file won't be usable by release binaries, though
26 2017-04-16 12:08:41	0|sipa|but there are tools to convert it
27 2017-04-16 12:09:44	0|__0|i till have no wallet, so new one will be usable?
28 2017-04-16 12:10:40	0|sipa|yes, everything will work fine; you just won't be able to move your wallet file with other builds of bitcoind
29 2017-04-16 12:11:33	0|__0|thanks,sipa, for clearing:-)
30 2017-04-16 12:28:38	0|__0|try ./configure --with-incompatible-bdb, same mistake(
31 2017-04-16 12:29:41	0|__0|5.3 is apt-got)
32 2017-04-16 12:33:23	0|sipa|this is not a support channel; ask in #bitcoin or on stack exchange
33 2017-04-16 17:39:06	0|SopaXorzTaker|Someone posted this private key: L1jHtEcxdsjdD43AhstSXww2vwZyTVaf5nKHtqPAUrPSp3HAvBVr on this channel
34 2017-04-16 17:39:11	0|SopaXorzTaker|it once contained 1 BTC
35 2017-04-16 17:39:20	0|SopaXorzTaker|and probably was spent when it was posted
36 2017-04-16 17:39:21	0|SopaXorzTaker|WTF
37 2017-04-16 17:39:44	0|SopaXorzTaker|https://blockchain.info/address/1Db7jHHLdD1TUqhRZKEcgAJNSkMTeyLWV
38 2017-04-16 17:40:05	0|SopaXorzTaker|sorry for the offtopic, obviously