--- Log opened Sun Mar 21 00:00:02 2021
00:02 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
00:03 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
00:32 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
00:32 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
01:26 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
01:26 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
02:24 -!- MasterdonX [~masterdon@titan.pathogen.is] has joined #c-lightning
02:26 -!- MasterdonX [~masterdon@titan.pathogen.is] has quit [Read error: Connection reset by peer]
02:28 -!- MasterdonX [~masterdon@titan.pathogen.is] has joined #c-lightning
02:33 -!- masterdonx2 [~masterdon@172.83.42.132] has joined #c-lightning
02:34 -!- MasterdonX [~masterdon@titan.pathogen.is] has quit [Ping timeout: 276 seconds]
03:09 -!- jonatack [~jon@37.167.3.195] has joined #c-lightning
03:14 <@cdecker> Yep, the remote end must've had an old estimate or a very conservative estimate on the expensive close. The low fee between c-lightning's is pleasant though
03:21 -!- masterdonx2 [~masterdon@172.83.42.132] has quit [Quit: ZNC 1.7.5 - https://znc.in]
04:31 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds]
04:31 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
04:40 -!- jonatack [~jon@37.167.3.195] has quit [Read error: Connection reset by peer]
04:50 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
04:51 -!- belcher [~belcher@unaffiliated/belcher] has quit [Remote host closed the connection]
05:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has left #c-lightning []
05:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has joined #c-lightning
05:46 -!- Zanth [5ceae07f@cpc101546-mort7-2-0-cust126.19-2.cable.virginm.net] has joined #c-lightning
05:54 -!- Zanth [5ceae07f@cpc101546-mort7-2-0-cust126.19-2.cable.virginm.net] has quit [Quit: Connection closed]
06:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 268 seconds]
06:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
07:05 -!- jonatack [~jon@37.167.86.91] has joined #c-lightning
07:17 < fiatjaf> trying to setup lightningd on a new ubuntu machine with postgres and ./configure is not detecting it
07:17 < fiatjaf> pg_config returns ok
07:17 < fiatjaf> but it still doesn't work
07:18 <@cdecker> Are `POSTGRES_INCLUDE` and ~POSTGRES_LDLIBS` set in the config.vars file?
07:21 < fiatjaf> POSTGRES_INCLUDE=-I/usr/include/postgresql
07:21 < fiatjaf> POSTGRES_LDLIBS=-L/usr/lib/x86_64-linux-gnu -lpq
07:21 < fiatjaf> this doesn't exist though: /usr/include/postgresql
07:21 < fiatjaf> pg_config is returning an invalid directory
07:21 <@cdecker> Hm, sounds like a broken postgres installation tbh
07:22 <@cdecker> We use pg_config explicitly to detect the location of files we need, and if it returns non--existent directories/files there's little we can do on our end
07:22 < fiatjaf> I just did apt install postgresql
07:22 < fiatjaf> yes, I'm not saying it's a problem on your end
07:24 <@cdecker> Just postgresql? You probably need libpq-dev, that inclues the libraries and headers, and will likely populate the directory
07:24 < fiatjaf> sorry, yes
07:24 <@cdecker> Sorry if that came off as defensive, I meant to narrow the scope of things :-)
07:24 < fiatjaf> I hadn't installed libpq-dev
07:24 < fiatjaf> that fixed it
07:25 <@cdecker> Nice^^
07:25 < fiatjaf> but still pg_config is broken, it shouldn't return a directory that doesn't exist
07:25 < fiatjaf> or maybe not
07:25 < fiatjaf> it's just not idiot-proof
07:26 <@cdecker> Hehe, yeah, it's definitely not intuitive to return a value when it points into the void
07:30 < fiatjaf> thank you very much!
07:31 <@cdecker> No problem ^^
08:28 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
08:31 -!- bitdex_ [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
11:59 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 268 seconds]
12:01 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
13:00 < openoms> one last question before the 2016 blocks pass since my stale channel @cdecker. The peer is stuck with CentOS 7 where CL 0.9.0 and bove does not compile. Is there any info ehich can be still extracted now and can't be done later? Will obviously watch this space, but is there any pale hope of recovering the funds once the pending channel is forgotten? https://github.com/ElementsProject/lightning/issues/4416#issuecomment-802955473
13:14 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
13:14 < carboncarlo> hi everyone, I set up my c-lightning node today. I'm a new user of linux, so it way quite a journey, but very doable.
13:15 < carboncarlo> I already had Bitcoin Core running for a few weeks, so that part was done already.
13:17 < carboncarlo> I want to test the waters and maybe route some payments. Is it bad for this purpose if I use Tor or does this make no difference? thanks.
13:35 -!- jonatack [~jon@37.167.86.91] has quit [Ping timeout: 264 seconds]
13:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has left #c-lightning []
13:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has joined #c-lightning
13:56 -!- jonatack [~jon@37.167.86.91] has joined #c-lightning
14:16 < fiatjaf> carboncarlo: people have been running tor since always, it's very recommended that you do!
14:16 < fiatjaf> (or not do. I personally never do)
14:17 < carboncarlo> ok cool, thanks.
14:24 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has quit [Ping timeout: 240 seconds]
14:25 -!- jonatack [~jon@37.167.86.91] has quit [Ping timeout: 246 seconds]
14:28 -!- carboncarlo [900263cd@bbcs-99-205.pub.wingo.ch] has joined #c-lightning
14:47 -!- jonatack [~jon@37.166.26.72] has joined #c-lightning
15:37 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
15:37 < warren> openoms: is there a ticket for not building on CentOS 7?
15:46 < warren> ../../../libwally-core/src/ctest/test_psbt_limits.c:62:38: error: ‘MAP_ANON’ undeclared (first use in this function)
15:46 < warren>               PROT_READ | PROT_WRITE, MAP_ANON | MAP_PRIVATE, -1, 0);
15:47 < warren> openoms: was it this?
15:50 < warren> https://stackoverflow.com/questions/5446698/map-anonymous-with-c99-standard
15:51 < warren> ... -std=c99 -MT ctest/test_psbt_limits-test_psbt_limits.o -MD -MP -MF ctest/.deps/test_psbt_limits-test_psbt_limits.Tpo -c -o ctest/test_psbt_limits-test_psbt_limits.o `test -f 'ctest/test_psbt_limits.c'
15:51 < warren> looks easy to fix that build error but I don't know how to make a fix that would be portable
17:10 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 268 seconds]
17:11 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
17:27 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
18:17 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
18:31 -!- gwillen [~gwillen@unaffiliated/gwillen] has joined #c-lightning
18:56 -!- spinza [~spin@102.132.245.16] has quit [Quit: Coyote finally caught up with me...]
19:00 -!- spinza [~spin@102.132.245.16] has joined #c-lightning
19:38 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 246 seconds]
19:44 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
19:45 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
19:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 276 seconds]
19:58 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 264 seconds]
20:00 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 268 seconds]
20:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
21:20 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection reset by peer]
21:21 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
21:45 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds]
21:49 < openoms> warren: yes it is similar: ../../../libwally-core/src/ctest/test_psbt_limits.c:49:38: error: ‘MAP_ANON’ undeclared (first use in this function) PROT_READ | PROT_WRITE, MAP_ANON | MAP_PRIVATE, -1, 0);
21:49 < openoms> There is no ticket and it is not my system unfortunately.
22:03 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has left #c-lightning []
22:03 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-iyngssqtppxfqsbk] has joined #c-lightning
22:05 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning
23:54 < warren> close's fee_negotiation_step option ... the default is 50%. What are the practical reasons why not make 10% the default? Could the negotiation actually fail?
--- Log closed Mon Mar 22 00:00:03 2021