--- Log opened Sun Jan 10 00:00:11 2021 00:01 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-builds 00:13 -!- pbase [~pbase@unaffiliated/pbase] has joined #bitcoin-builds 00:49 -!- pbase [~pbase@unaffiliated/pbase] has quit [Quit: Leaving] 02:36 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined #bitcoin-builds 02:36 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Quit: Leaving] 03:19 -!- Cathy28Balistrer [~Cathy28Ba@static.57.1.216.95.clients.your-server.de] has joined #bitcoin-builds 05:25 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds 05:26 < hebasto> MarcoFalke: as you are maintaining https://github.com/flathub/org.bitcoincore.bitcoin-qt why the flatpak option is not available on bitcoincore.org/en/download ? 05:28 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds] 05:36 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds 05:37 -!- molz_ [~mol@unaffiliated/molly] has joined #bitcoin-builds 05:39 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds] 05:41 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 264 seconds] 08:52 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Read error: Connection reset by peer] 08:52 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has quit [Write error: Connection reset by peer] 09:09 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-builds 09:09 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-builds 11:08 -!- gorazdko [59d42ea3@89-212-46-163.dynamic.t-2.net] has joined #bitcoin-builds 11:10 -!- gorazdko44 [59d42ea3@89-212-46-163.dynamic.t-2.net] has joined #bitcoin-builds 11:10 -!- gorazdko44 [59d42ea3@89-212-46-163.dynamic.t-2.net] has quit [Client Quit] 11:10 -!- gorazdko [59d42ea3@89-212-46-163.dynamic.t-2.net] has quit [Client Quit] 11:13 < wumpus> dongcarl: porting it to seL4 sounds much more involved, it hardly has any OS services at all, i think the usual way to run complicated applications like bitcoind on seL4 is... to run a linux kernel in a seL4 hypervisor with just it... but yeah it would be neat 11:15 < wumpus> hebasto: i guess because it's not built deterministically with the rest 11:15 < wumpus> bitcoincore.org only has the gitian output 14:45 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds 14:48 -!- molz_ [~mol@unaffiliated/molly] has quit [Ping timeout: 264 seconds] 15:02 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds 15:06 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds] 15:21 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds 15:25 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds] 16:29 < harding> wumpus: BitcoinCore.org also links to the Ubuntu Snap. I've never used a snap or a flatpack, but I assume they're basically similar containerized things, so it seems it be consistent to also link to a flatpack that's maintained under a similar situation to the snap. 17:20 -!- willcl_ark [~quassel@cpc123780-trow7-2-0-cust177.18-1.cable.virginm.net] has quit [Ping timeout: 264 seconds] 17:25 -!- willcl_ark [~quassel@cpc123780-trow7-2-0-cust177.18-1.cable.virginm.net] has joined #bitcoin-builds --- Log closed Mon Jan 11 00:00:12 2021