01:28:37 luigi1111w: cli merge list #6548, #6569, #6572, #6575, #6577 01:29:16 then you can tag :) 01:30:06 same for gui 01:30:08 thanks 01:51:03 hey what resources should i use to get "up to speed" on how the code functions? Is there an index of sorts?\ 01:53:04 git grep is good. 01:53:17 You want to know how "X" works, git grep X. 01:53:48 I started by finding little bits I wanted to change, grepped for these bits, found the code, read the ode, changed the code till it worked. 01:54:19 There's a "zero to monero" doc that explains the crypto parts. 01:54:49 Which I should go read I guess since the crypto's still eluding me. 01:55:08 git log's also very helpful. grep the commit messages, see changes. 01:56:14 I've stuck to just nuts and bolts. higher level purpose and meaning is out of my scope 01:57:29 cool thanks! moneromooo 01:58:48 @hyc might you explain a bit more 02:01:20 I mean, when I work on the code, it's to fix syntax and structural problems 02:01:37 all you need to know is C/C++ syntax and which relevant data structures are being used 02:01:53 you don't need to understand the meaning of the cryptographic functions being used 02:02:30 I only care that the functions are written correctly to do what they claim to do 02:03:02 oh ok 02:04:37 It's nice to understand the math at a deeper level, just because learning more is good. but it's not always necessary, to be able to get useful work done on the code. 02:05:44 yeah i got you. ive done c/c++ for a while so i might try doing that 02:25:31 Edmond_Dantes66: if you go for ztm, aim at the 2nd edition 05:18:08 Edmond_Dantes66: it actually doesn't take long to familiarize yourself with the code. It's pretty well organized. 05:19:11 As moneromooo says, grep is your friend. Then a decent editor that can jump around. 05:19:36 e.g. vim and ctags. 05:20:28 The less friendly part of the code is wallet2! 09:32:56 tazmanian this old Monero paper also documents some crypto functions in section 4.1: https://getmonero.org/resources/research-lab/pubs/MRL-0003.pdf 09:33:21 If you ever return I hope you read it 10:08:08 Seems like we can tag after 6575 is merged 10:28:10 I'm ready with DNS recs whenever 10:41:11 Wow, how did that finally happen :) 11:30:51 * dEBRUYNE will create a reddit thread for deterministic builds once the tag is set 16:07:49 hi, any idea how to fix it? depastedihrn3jtw.onion/show.php?md5=197d2effdf812e1b3d9a8afc579d58a3 16:57:13 fRit_^ do you have SOCKSPort 127.0.0.1:9050 in your torrc ? 16:58:57 DeanWeen, yes 16:59:54 is tor started? 17:01:04 DeanWeen, yes, netstat shows that .moderod goes trough 127.0.0.1:9050 17:01:41 DeanWeen, only trough 127.0.0.1:9050 17:01:51 then the only other thing I would think is maybe the .onion:18080 you're trying to reach is not reachable 17:02:24 either down or you cannot find a way to rendezvous 17:17:20 luigi1111w if you are still online I think you can tag now 17:19:05 was hoping to hear something like that 17:19:51 and then also gui after doing remaining merges 17:20:23 https://github.com/monero-project/monero/releases/tag/v0.16.0.0 17:21:10 yay 17:22:16 nice 17:24:32 Tagged and bagged. 17:37:42 luigi1111w: Thanks for the tag 17:38:25 nitrogen nebula is correct, yeah? 17:38:47 Monero 'Carbon Chamaeleon' (v0.16.0.0-release) 17:38:54 :S 17:39:43 doh.... yeah Nitrogen Nebula 17:40:19 what would a release be without messing something up :P 17:40:20 shall i stop my docker build? :D 17:41:49 tag to v0.16.0.1 or force push the tag? 17:42:04 Haha that did not take long. Best release ever but getting the name wrong :) 17:42:42 https://github.com/monero-project/monero/pull/6579 17:44:24 luigi1111w: you can decide 17:45:13 I would just fix and force-push the tag 17:45:15 Delete the tag. 17:45:16 I'd force push, otherwise we will get a bunch of people asking where 0.16.0.0 is 17:45:20 yeah 17:45:23 I'm confused 17:45:40 we forgot to change the name inside the source code 17:45:46 I didn’t even know that there was a name inside 17:45:57 ok cuz I named it correctly, lol 17:46:01 yep 17:46:03 pr please 17:46:08 https://github.com/monero-project/monero/pull/6579 17:46:12 Maybe we can spare that 0.16.0.1 for later. I mean, all the individual PR's look ok, but probably nobody had ran the *combination* for any length of time, to test, right? 17:47:19 I can't beleive it. We've kind of agreed that rewriting tags is bad, and first chance we get everyone votes to rewrite it. 17:48:03 has this existing tag had time to propagate anywhere? if not, what's the harm? 17:48:23 Yeah, it's about half an hour old ... give it some slack :) 17:49:52 every release requires deleting tags 17:50:02 if we don't have to, we missed something 17:50:05 lol 17:50:13 "No need to put the seatbelt on, I'm just going round the corner". But to proceed, I'll have my "I told you so" message as soon as someone pops in with a question about why his 0.16.0.0 source doesn't match the repo. 17:50:23 get it ready 17:50:25 *do proceeed 17:50:33 it's already replaced 17:51:25 we'll all do reproducible builds from the current tag, so anything older doesn't matter 17:58:28 Corresponding Reddit thread -> https://www.reddit.com/r/Monero/comments/go1ous/cli_v01600_nitrogen_nebula_has_been_tagged_you/ 19:03:03 So far so good on the Linux docker-made bins? https://paste.debian.net/1148178/ If so, I'll post the whole thing to reddit when done 19:20:20 my build seems to be remaking all dependencies, so it'll be a while before I get any binaries 19:20:54 I took care of that as soon as release-v0.16 was branched. 19:21:11 Is this strictly not supported for Ubuntu 20.04? 19:21:24 Tried running it but ran into issues with the setup step 19:21:28 using docker 19:21:33 Different toolchain, different hashes. 19:21:46 (If it works) 19:22:33 eh, inside the container it should all be ubuntu 18 19:22:42 shouldn't matter what the host is 19:23:11 So the builder pulls an 18.04 image ? Cool. 19:23:18 yes 19:23:46 fort3hlulz: https://paste.centos.org/view/1fc1ae2b 19:23:53 there are the steps I use on a Ubuntu 18.04 VPS 19:24:04 these* 19:24:41 hmm I should not pull the gitian script from master I guess 19:24:56 it hasn't changed recently so that's safe enough 19:25:01 ok 19:25:33 I don't think docker.io is in ubuntu repos now 19:25:49 I had to add a docker ppa to get it on my ubuntu 19 machine 19:25:55 tried these steps today and did not have problems 19:26:15 sure. for ubuntu 18 19:27:00 didn’t read your message properly 19:27:56 Thanks selsta I'll try that now! 19:29:09 scoobybejesus: my hashes match 19:30:05 sweet 19:32:31 Still fails for me here: https://paste.centos.org/view/b9c3ee6a 19:33:37 I'm fairly new to Ubuntu, this is my first real time using it, I'm always using CentOS/RHEL for work 19:34:15 can you try again? 19:34:21 ifconfig and see if you have a docker0 interface. 19:35:03 I do 19:35:11 docker0: flags=4099 mtu 1500 19:35:12 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 19:35:35 do you have ufw running? could be blocking 19:35:42 hyc: 3142 is thta apt-cache thing ? 19:36:02 I do have UFW running 19:36:13 I'll try allowing 3142 I guess? 19:36:14 Allow port 3142 then 19:36:49 hyc and i went round and round a while back. ufw on the host was my problem. mine's not on a VPS so i just turned it off for this purpose lol 19:37:00 yup that worked :) 19:37:04 :) 19:37:06 ufw enable 3142/tcp fixed it 19:37:34 great 19:37:52 https://paste.debian.net/hidden/9edaa361/ 19:38:27 iDunk: did you have the dependencies cached? 19:38:40 or what kind of machine do you have :D 19:38:52 :20:54 < iDunk> I took care of that as soon as release-v0.16 was branched. 19:38:54 :) 19:39:29 Actually, when I made that version change PR for gitian. 19:52:17 Any opinion on self hosting a backup for depends packages? 19:55:07 Kinda like bitcoincore.org/depends-sources/ but for our packages. 20:02:58 may not be a bad idea. I'd prefer a single canonical source for packages 20:04:07 I guess there would be no legal problems anyway as the software is open source? 20:04:16 Apart from the macOS stuff. 20:04:35 usual apple fuckery 20:04:54 Well bitcoincore.org still hosts it :P looks like they don’t care 20:04:58 imo we should stop supporting Apple, as long as they pull this proprietary shit 20:15:40 my Linux hashes also agree scoobybejesus 20:26:22 This gitian build takes a long time 0.0 putting my 1950X to work :P 20:27:48 did you do the build step with -j ? 20:31:37 yeah I did -j$(nproc) 20:31:44 its maxing out my CPU at most points 20:31:48 good 20:31:49 all 32 threads 20:32:03 an idle core is a wasted core 20:32:19 can I do -j16 with 32GB RAM? 20:32:21 ALl my idle cores are usually crunching RandomX hashes ;) But today is a build day 20:32:34 selsta that should usually work 20:32:41 I set it to -j12 for now 20:32:50 there are a few files that may need 3GB, but you'd have to have bad luck to have a conflict there 20:33:39 I personally won't buy a machine now with less than 4GB RAM per core 20:34:00 I only have 2GB per core :( Need to double the ram in this box ASAP 20:34:09 Keep forgetting to, only have 32GB with this 1950X for now 20:34:11 (excluding my phone that is) 20:36:23 Linux hashes match iDunks 20:37:15 I'm doing it :D 20:37:37 I don't have a GPG key (I know, I know...) so should I just post the hashes on Reddit? 20:37:44 Or is there something else I should do to help validate? 20:41:53 go generate a key already 20:41:59 but yeah, go ahead and post on reddit 20:43:23 this bugs me though, since you can't restore your GPG key: https://dev.gnupg.org/T169 20:45:22 I'll try and generate a key and sign this weekend, but for now I'll share all hashes on reddit/here 20:46:04 well, they merged the mnemonic restore issue with that one. still, it'd be great to have a restore mnemonic 22:02:34 Hashes I got: https://paste.centos.org/view/ed667357 22:02:37 Seem to match! 22:04:49 Hopping off for a bit now, but will try to get those GPG-signed sometime over the weekend as well. 22:05:06 Thanks for the help getting my first gitian builds going :) 22:05:21 :)