ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://vid.puffyan.us/H7PvgY65OxA
<illiliti> TIL sanctions evasion is a criminal activity
<illiliti> i wonder who is going to prosecute me for that
<illiliti> i suppose drew himself
Torr has quit [Ping timeout: 252 seconds]
Torr has joined #kisslinux
Torr has joined #kisslinux
Torr has quit [Changing host]
<Torr> illiliti: He already does that: http://ix.io/4eEk
<Torr> That's from '#sr.ht'.
<illiliti> holy shit
<illiliti> > In the history of SourceHut, only two users have been banned
<illiliti> i knew this is lie
<Torr> Pretty much.
<illiliti> next thing he will start deleting are zero/one day PoCs of critical RCE vulnerabilities
<illiliti> cuz those can facilitate ransomware and bots/worms that implant crypto miners
<illiliti> this shit will never end
<Torr> Yeah, right?!!
<Torr> Luckily there are plenty of other Git hosting plataforms, just note with emphasis on email.
<Torr> But not like such flow can't be used with them.
<Torr> not* with
<illiliti> just curious, what if i package, say, cgminer for kiss and then mirror repo with it on sr.ht. will i get banned?
<Torr> Who knows, but I wouldn't pay for disservice.
<illiliti> i wouldn't pay too
<illiliti> i'm tempted to create kiss-crypto repo with miners and shit and somehow host it on sr.ht
<illiliti> i bet i'll receive ban
<Torr> Lol
<Torr> Likely it would.
<testuser[m]> Hi
<illiliti> hi
<Torr> testuser[m]: ahoy
<wael_> Hi
ella-0 has joined #kisslinux
ella-0_ has quit [Ping timeout: 246 seconds]
ghoulpine is now known as vulpine
psydroid has quit [Ping timeout: 246 seconds]
rio6 has quit [Ping timeout: 246 seconds]
dotkwa[m] has quit [Ping timeout: 246 seconds]
konimex has quit [Ping timeout: 246 seconds]
rio6 has joined #kisslinux
<Torr> illiliti planning his Sourcehut raid: https://i.ibb.co/tP1zf1M/image1.jpg
<illiliti> xd
psydroid has joined #kisslinux
konimex has joined #kisslinux
<Torr> See ya folks
Torr has quit []
dotkwa[m] has joined #kisslinux
wololo has joined #kisslinux
wololo is now known as sad_plan
<sad_plan> o/
<sad_plan> lol, drew is relentless. imidiatly banned him for disagreeing
<sad_plan> testuser[m]: the new make release doesnt seem to have configure script set to executable
ella-0 has quit [Ping timeout: 252 seconds]
ella-0 has joined #kisslinux
<illiliti> no?
<illiliti> i see executable bit
<sad_plan> hm..
<sad_plan> downloaded it 4 times now, and still no
<sad_plan> ah.. its an issue with sbase tar
<illiliti> oh
<illiliti> interesting
<sad_plan> or perhaps mcfs tar
<sad_plan> I reciently switched to it
<sad_plan> or partly, im not all done, but anyway
<illiliti> mcfs tar? that one in his sbase fork?
<sad_plan> correct
aliosablack has joined #kisslinux
<illiliti> can reproduce
<sad_plan> yeah, it seems to be an issue with sbase in general. the issue persists with upstream sbase aswell.
<illiliti> configure is marked as ... hardlink? what
<illiliti> i'm debugging
<illiliti> > Changing timestamps, modes and ownership of hardlinks makes no sense.
<illiliti> bruh
<sad_plan> why on earth would they do that..?
<illiliti> git revert 3c2f8b0c
<sad_plan> nice. doesnt that commit actually fix that though? seeing as the commit message says dont change modes etc.
<illiliti> don't change modes == don't do chmod()
<illiliti> so that commit only breaks
<sad_plan> ah
<sad_plan> huh.. sbase tar breaks webkit2gtk tarball it seems. http://0x0.st/oY0E.txt
<sad_plan> doesnt give me the same issue with busybox tar
<sad_plan> as does sbase ln. webkit seems to use a ln flag that sbase doesnt have
sad_plan has quit [Quit: sad_plan]
sad_plan has joined #kisslinux
aliosablack has quit [Ping timeout: 268 seconds]
<illiliti> gnuism
<illiliti> sbase ln supports only posix flags
<illiliti> will check tar
<sad_plan> I figured as much..
<illiliti> hmm
<illiliti> it seems that sbase tar doesn't support pax format
<illiliti> look at tar -tf output. it looks pretty fucked
<illiliti> some paths are truncated
fitrh has joined #kisslinux
<sad_plan> yeah, im just getting: tar: malformed tar archive: not ustar format
<sad_plan> wait, no
<sad_plan> wait, I see what you mean. alot of paths are just cut off at the end
<illiliti> yep
<testuser[m]> o i forgot about that fix
chomwitt has joined #kisslinux
<phoebos> did codeberg also replace the commit message with the PR name
<phoebos> testuser[m]: what are the disadvantages of fast-forwarding to merge?
<testuser[m]> none? it's just changing HEAD of master to HEAD of that branch so u have to rebase that branch before "merging"
<illiliti> no
<illiliti> rebase is only needed if branch is outdated
<testuser[m]> yeah i mean the history needs to be exact same without any commits from master being missing in the branch to be fast forwarded
<illiliti> yep
fitrh has quit [Read error: Connection reset by peer]
fitrh has joined #kisslinux
fitrh has quit [Quit: fitrh]
stjohn has joined #kisslinux
<phoebos> does fast-forwarding preserve the author's signature
<testuser[m]> probabyl
op_4 has quit [Quit: ZNC - https://znc.in]
op_4 has joined #kisslinux
<phoebos> should be codeberg's default
<testuser[m]> no
<testuser[m]> pr can have multiple spam commits
<testuser[m]> btw u can change default in repo settings
<testuser[m]> i've set it to squash
<phoebos> ah so does squash use the PR for the commit message
<testuser[m]> yea
<sad_plan> so you can make codeberg automatically sqaush commits from a pr into one merge commit?
<testuser[m]> it's automatic on every forge u just have to press a button wdym
<sad_plan> if you merge on github, all the commits from that branch + merge commits gets listed in the master branch. thats what I meant. what I was asking was, did it sqaush all those commits into the merge commit, so all those commits doesnt flood your commit log, if say you have alooot of commits from said branch
<testuser[m]> u have the arrow thing on github pr page that does the same thing
<testuser[m]> squash, rebase or merge commit
<sad_plan> ah, I wasnt aware
<sad_plan> nice
<sad_plan> btw, whats the holdup on using the 5.6.3 release and switching to b3sum? still some things to iron out?
<testuser[m]> 5.6.3 has bugs
<testuser[m]> 5.6.4 is fix
<sad_plan> I see
sad_plan has quit [Quit: nyaa~]
stjohn has quit [Ping timeout: 255 seconds]
<testuser[m]> make seems to have broken some things in latest update, do notify if anyone sees build failures
<testuser[m]> like glibc build is broken due to some race condition with /tmp/XXXX files that aren't even touched in makefiles
stjohn has joined #kisslinux
<testuser[m]> make[1]: *** cannot open output sync mutex /tmp/GmLdqZrgr: No such file or directory. Stop.
<testuser[m]> hmm gcc seems to build fine tho which has similarly complex build
<testuser[m]> ioraff: can u update openssl 3.0.7 and bump curl git etc
stjohn has quit [Ping timeout: 252 seconds]
stjohn has joined #kisslinux
<phoebos> wtf i rebuilt musl and getopt is broken
<testuser[m]> phoebos: what
<phoebos> exactly
<phoebos> getopt isn't working for every command that uses libc for it
<testuser[m]> Wat broke in it
<phoebos> doesn't recognise flags
<testuser[m]> example
<testuser[m]> Working fine
<phoebos> hm it seems it doesn't increment optind
<testuser[m]> Send
<testuser[m]> sus
<testuser[m]> Did you use some fancy build flags
<phoebos> only --enable-debug
<phoebos> has worked for months
sam_sepi0l has joined #kisslinux
<testuser[m]> Send musl.tar.xz
<testuser[m]> curious
<testuser[m]> Try gdb watchpoint also
<phoebos> hm a watchpoint says it is updated to 2
<phoebos> but the program disagrees
<phoebos> ah gcc is messing it up somehow
<phoebos> works with clang
<phoebos> hm but not with tcc
<testuser[m]> Wat
<phoebos> this is weird
<phoebos> statically linking libc gives correct behaviour, dynlinking doesn't
<phoebos> wtf
<testuser[m]> lol
<testuser[m]> Did u just try rebuilding once again
<phoebos> i think the problem came after i rebuilt binutils bison busybox bzip2 curl flex git gmp libmpc m4 mpfr musl pigz xz zlib
<phoebos> so i'm rebuilding them
<phoebos> rebuilt gcc
<phoebos> twice
<testuser[m]> Rebuilt for what purpose
<testuser[m]> U could inspect the disasm
<phoebos> because i have no idea what's going on
<phoebos> oh
<phoebos> maybe fixed
<phoebos> i think it's to do with the gcc unbundling
<phoebos> i accidentally installed gmp libmpc mpfr without rebuilding gcc
<phoebos> yes it's fixed after rebuilding gcc and musl
<phoebos> that was very weird
stjohn has quit [Ping timeout: 252 seconds]
<testuser[m]> U mean u had gcc with bundled mp* that was not rebuilt to use system stuff
<phoebos> yes
<phoebos> then i installed system mp*
<phoebos> which apparently broke getopt
stjohn has joined #kisslinux
midfavila has joined #kisslinux
midfavila has left #kisslinux [#kisslinux]
yamchah2 has quit [Read error: Connection reset by peer]
yamchah2 has joined #kisslinux
Torr has joined #kisslinux