IRC channel logs
2022-12-29.log
back to list of logs
<oriansj>nope, $700 and enjoying a big fat profit for very little work <Hagfish_>and avoiding a monopoly / anti-trust enforcement <Hagfish_>and at $50/ton, your competitors can't cover their costs <oriansj>at $50, you are the only option still in business and thus no point in trying to hide <Hagfish_>i guess your lawyers argue that it's the price cap that caused the monopoly, and therefore you can't be penalised <Hagfish_>and yeah, suddenly everyone can afford steel, so the use goes up, instead of down <oriansj>and because you aren't dumping (selling at below cost) you are outside of most anti-trust laws anyway <Hagfish_>it's like the Cobra Effect, except that was completely predictable, as it didn't involve any hidden knowledge <fossy>hey stikonas[m], can you send me your musl1.2.3-0_1.x86.xbps? i'm getting a different checksum on two systems (1dec185051d6039f82f62c4123597d3dc3f807f5f2f061fc6a92ce0d81151847), one qemu, one chroot... <stikonas>fossy: which commit? latest live-bootstrap master? <stikonas>I probably can't get it today (my timezone), it takes 2 hours but I'll send it to you tomorrow, so in your late evening <fossy>no worries, i can do other things in meantime <stikonas>I guess if I get your checksum, I'll just update the one we have <stikonas>fossy: and what are we doing with downloads by default? <stikonas>rickmasters was also a bit unhappy about that <stikonas>fossy: I've just got 4b0aab8540e9acc3bd2cab11825130b3ff010825ec7a2b992cd8b9a558703e1f /usr/src/repo/musl1.2.3-0_1.x86.xbps <stikonas>oriansj: one probably very useful clue for M2-Mesoplanet crash <stikonas>AMD64/bin/M2-Mesoplanet --architecture amd64 --version does not crash <stikonas>(which is also why we didn't notice it before in stage0-posix runs) <stikonas>also unrelated crash, if you specify M2-Mesoplanet --debug-mode without a number following it, then it would crash <stikonas>hmm, it's not clear though why --architecture solves the crash... <stikonas>fossy: and I'm getting the same checksum in qemu mode <oriansj>stikonas: the reasons is: hold = argv[i+1]; <stikonas[m]>Yes, this one was clear, like I said we are just missing an extra check <stikonas[m]>I haven't looked much more into --version crash though <stikonas[m]>(Besides observation that --architecture makes crash go away) <oriansj>well let me add some more sanity checking on passed arguments