<testuser[m]>
You could build as root after setting ulimit -n unlimited
<testuser[m]>
In build *
<micro_O>
i wonder why you would even specify that arbitrary information could be allowed in a file, that should be ignored, unless its specifically for some transition in an unstable format
<msk[m]>
could I edit the build file to say "ulimit -n unlimited" instead of "ulimit -n 4096"?
<micro_O>
like, arbitrary information that should be ignored can live in any non-specified file
<testuser[m]>
Yeah thats what i said
<testuser[m]>
But you need root
<micro_O>
(like the meta files ive seen, and /description, etc)
<testuser[m]>
(Running ulimit itself as root wont work since it needs to modify the current shell)
<msk[m]>
"bash: ulimit: open files: cannot modify limit: Operation not permitted" oh
<msk[m]>
could I put a "ssu" in the build file instead of running the whole compilation as root?
<msk[m]>
* could I put a "ssu ulimit -n unlimited" in the build file instead of running the whole compilation as root?
<testuser[m]>
I just said why you cant :p
<msk[m]>
damn I'm blind
<testuser[m]>
its a shell builtin not a binary
mahmutov has joined #kisslinux
<msk[m]>
alright thanks, maybe I need to switch matrix clients if that's messing me up
<testuser[m]>
It's the only way though, i guess. Not much more hacky than the original glibc one
<micro_O>
testuser[m] maybe we can petition baselayout to configure a higher ulimit just for the kiss build process?
<micro_O>
or maybe there is some unshare shenanegains that can be used
<testuser[m]>
There's like 3 packages needing ulimit and 2 are chromium, other is nodejs
<testuser[m]>
so i dont think its an iszue
claudia has quit [Ping timeout: 256 seconds]
<dilyn>
I didn't have a ulimit problem
<dilyn>
there isn't a whole lot we can really do about this change, because musl just implements dummies for __close anyways
<dilyn>
and from what I've been able to dig up, nothing has been said about __close since 2013
consolers has quit [Quit: \]
<msk[m]>
I forked the package, changed the line to "ulimit -n unlimited", and ran su -c "kiss b" inside the forked directory
<msk[m]>
but, it failed with "sh: error setting limit: Operation not permitted"
<testuser[m]>
ssu -sp
<testuser[m]>
kiss b
<dilyn>
afaik ulimit will only help with the max number of file descriptors being open at a time; this problem sounds more like the symbol table itself being broken
<msk[m]>
same error testuser
<testuser[m]>
Weird
<testuser[m]>
Can you do ulimit -n unlimited manually
<msk[m]>
no, that also fails
<msk[m]>
no matter how I run it as root
<testuser[m]>
do ulimit -n 999999 or something i guess lol
<testuser[m]>
Dilyn: what would break the tablsm
<testuser[m]>
Table
<msk[m]>
doing ulimit -n (9s) also fails manually
<msk[m]>
I'll see how far I can get it before it errors
<msk[m]>
ulimit -n 1000000 works which I suppose will be fine
<dilyn>
the archive being too large, perhaps...
<dilyn>
are you guys building in tmpfs?
<msk[m]>
nope
<dilyn>
hmhmhm
sad_plan has joined #kisslinux
<msk[m]>
I think it's working with ulimit -n 1000000
<msk[m]>
thanks
<kqz>
trying to build a git package, but kiss keeps spititng "checksums: no such file", are you guys able to build git packages on latest master?
<kqz>
oh looks like dilyn is having the same issue :D
<kqz>
just checked the issues on the repo lol
<dilyn>
;)
sad_plan has quit [Remote host closed the connection]
sad_plan has joined #kisslinux
<testuser[m]>
Dilyn did your chromium build finish
<dilyn>
mmhmm
<testuser[m]>
And you didnt have the archive issue ?
<dilyn>
nope
<testuser[m]>
weird
<dilyn>
i did have an issue building in tmpfs and ran out of room on the disk when kiss was taring up the package XD
<dilyn>
i was a bit miffed
<dilyn>
but otherwise, no issues
<testuser[m]>
I guess it could be related to gnu vs lolvm toolchain
<dilyn>
the superior toolchain proves itself yet again!
<testuser[m]>
Do you test everything else on wyverkiss too ?
<dilyn>
though I don't recall running into any issues building in a vanilla chroot either...
<kqz>
wow dylan just pushed a fix, this man is a machine
<dilyn>
he's a professional bug squisher
<testuser[m]>
Ill build again anyway, looks like alpine updated some stacksize patches too
<dilyn>
that should only effect runtime tho
<testuser[m]>
Yeah
<testuser[m]>
I meant to say that it'll rule out manually patching and interrupted builds being the issue
<dilyn>
ah
Uks2 has quit [Quit: Byee]
Uks2 has joined #kisslinux
GalaxyNova has joined #kisslinux
<dilyn>
I'm on the warpath :V
<dilyn>
testuser you got mighty unlucky this time around with the outdated list :P
<GalaxyNova>
Wait what?? I'm so confused... Cloning the neovim git repository manually and running the build commands works fine but not when it's done through a kiss package???
<GalaxyNova>
wtf
<GalaxyNova>
Was there a recent change of how kiss clones git repositories?
<cot>
Has Dylan showed up here yet?
<cot>
Like, you know, to say helo like he mentioned he would?
<sad_plan>
not afaik. I do belive he has been on here after his reappearance though. I think Ive seen his name in the log a couple of times or so. iirc
<dilyn>
he showed up a while back but hasn't reappeared in > a week I think
sad_plan has quit [Remote host closed the connection]
<GalaxyNova>
dilyn
<dilyn>
interesting
<dilyn>
hmmmm
<dilyn>
doesn't super explain why the releases are broken tho
<dilyn>
hmhmhm
sad_plan has joined #kisslinux
<GalaxyNova>
It's so weird
<sad_plan>
dilyn, were you able to build zlib statically? I havent dared to mess too much with it yet, seeing as aloot of my system depends on it appearantly. I did built it statically though, but it messed alot of stuff up rather quickly tbh :p so I had to revert it :p
<dilyn>
zlib is tricky lmao
<sad_plan>
I figured :p
<dilyn>
the best method mostly depends on what's linked to it currently tbh
<dilyn>
if it's nothing critical (binutils, gcc, etc. are free of it) you can just build the static library ONLY and then rebuild the programs which require it
<sad_plan>
I belive I got like 34 packages that depend on it appearantly :o
<dilyn>
in my case, llvm was linked to zlib so I had to build both libs, rebuild llvm explicitly telling it to link against libz.a (-l:libz.a) and then i was good
<dilyn>
yeah things love zlib
<dilyn>
lmfao neovim wants gunzip
<GalaxyNova>
confirmed neovim fails because of a bug in kiss itself
<GalaxyNova>
tried building the package with a 2020 version of kiss and it builds fine
<dilyn>
yeah
<dilyn>
one sec
<dilyn>
add unset DESTDIR to the build script
<dilyn>
how old is that issue...
<GalaxyNova>
works! wow
<sad_plan>
ah ok, that gives me something to start with :D
<GalaxyNova>
probably should push that fix upstream
<dilyn>
sad_plan: switching to a static system from a currently working shared libs environment is mostly a lot of rebuilding and checking lmao
<dilyn>
ldd is your friend, kiss-revdepends is your friend, -l:libfoo.a is your friend... XD
<dilyn>
galaxynova: 1d756260b9f5e650067584128094f88a97fdf94b should work for everyone now
<sad_plan>
I actually havent had too much issues now. llvm plays nice, although I havent built it statically yet, but core is mostly static now. zlib, musl and llvm left, iirc. im actually pleasently suppriced of how well its going. cmake, expat is also static aswell. probably other stuff aswell, I dont remember
<cem>
dilyn: I personally don't like it that much
<cem>
My position is similar to the `update` files that were removed back a few months ago
<dilyn>
musl has to be last :V :V :V
<dilyn>
seems fair cem
<cem>
I don't think repositories themselves should be executing code
<dilyn>
it's a reasonable concern to have
<dilyn>
in my perfect world everyone is maintaining their own repository anyways hehe
<dilyn>
aw wtf neovim. it doesn't respect LIBDIR :|
<sad_plan>
I actually tried to built musl statically, but I couldnt get it to respect the LDFLAGS/CFLAGS. not that ive checked the makefile, I just checked if it would build, and it did, but didnt build statically for some reason.
<cem>
yeah, but at that point there is no point of remote repositories lol
<sad_plan>
I also got libressl to work statically, after dumping curl as my downloader. curl kept bitching about missing libs, but stopped once I switched to axel instead, which built statically right away, no issues :D
<dilyn>
to build musl statically you just --disable-shared
<dilyn>
curl is just picky. there's a way
<dilyn>
i forced it to play nice and just manually merged the symbols into libcurl.a myself
<dilyn>
cem: remotes are bloat
<cem>
dilyn: tru
<sad_plan>
im sure there is, but I kinda like axel better, seems faster imo.
<dilyn>
axel does parallel downloads doesn't it?
<sad_plan>
yep
<sad_plan>
I get to download stuff like 4x the speed or so
<sad_plan>
its amazing
sad_plan has quit [Quit: ]
<dilyn>
hope you didn't bork your interpreter there sad_plan...
sad_plan has joined #kisslinux
<sad_plan>
not to my knowledge. i shut down the laptop, cause I just left work :p
sad_plan has quit [Quit: Quit]
mulc has joined #kisslinux
<kqz>
yay finally got encryption via bcachefs and tinyramfs working, ty illiliti for this awesome tool
gtms has joined #kisslinux
mulc has quit [Quit: WeeChat 3.2]
GalaxyNova has quit [Quit: Whoooooshh]
riteo has joined #kisslinux
<riteo>
hiiiii!
<riteo>
bruh why is public domain so hard
<riteo>
why do both 0BSD and Unlicense exist
<riteo>
oh wait I'm dumb
<riteo>
Unlicense is international, 0BSD is not
<riteo>
epic, now minekiss is under the Unlicense
<riteo>
now google can't contribute anymore to my shell script, I won
<acheam>
to make them really quake in their boots license it AGPL
<riteo>
lmao
<acheam>
does google really not use anything public domain?
<acheam>
not even sqlite?
<riteo>
they do use sqlite
<riteo>
AFAIK they only use 0BSD software at most though, so it's probably an exception
<riteo>
lmao they have a special policy esclusively for AGPL
<riteo>
based stallman actually did it
<cem>
well google needs you to sign away your soul if you want to contribute to their software
<acheam>
ever tried submitting a patch to chromium?
<cem>
nope
<riteo>
doesn't any big corporation do that?
<riteo>
microsoft does it too
<cem>
I already kind of expect "microshit <3 open shit" to do that
<riteo>
uhhh so sign this CLA because obviously you might want to sue us and you might win on your *enormous* patch
<riteo>
and that's very bad cause we might even lose some money if you had any to begin with
<cem>
every dollar counts
<riteo>
like they might even care/follow every license
<riteo>
I wouldn't be surprised if every big corpo has some gpl'd code they didn't declare on their backs
<riteo>
also, it's even more hilarious to see the WTFPL listed on a big corpo's documentation page
<riteo>
it feels almost like reading "you can't say big chungus"
<cem>
I mean, sure there is no reason to trust big corporations, but I don't think it's common for big corporations to leverage GPL without declaring it
<acheam>
lol they have a github dotfiles guide to prevent people from leaking classified info
<cem>
It's usually small-medium companies that do it
<acheam>
in case your vimrc has the top secret google master password
<riteo>
lmao
<riteo>
this stuff is hilarious
<cem>
any big-corp formality is cringe and hilarious
<cem>
> You can publish small snippets, and answer questions on Stack Overflow, but please include the following license header.
<cem>
> Copyright 2021 Google LLC. Apache-2.0
<acheam>
bruh
<riteo>
actually I read about something similar not too long ago
<riteo>
somehow someone might care about the fact that you might have taken some code from SO
<riteo>
I mean, you shouldn't copy-paste, but technically even then it should be copyright infringment?
<riteo>
on something that someone said to help you?
<cem>
Because SO is CC BY-SA
<riteo>
"uh yes, so you used this basic bubble sort algorithm from my SO answer, I will now sue you"
<cem>
Which is basically GPL
<riteo>
I'm pretty sure 99% of people there don't even know there's a license of sort there
<cem>
Yeah, that's true
<cem>
They should have read the ToS
<cem>
lol
<riteo>
I'm pretty sure that if people actually read the ToS social networks would cease to exist
<cem>
social network ToS and other formal letters are just garbled up crap that don't make sense and are super open to interpretation
<cem>
I mean, most people still wouldn't read it if they were clearer
<riteo>
true
<riteo>
the issue is that people won't change. It takes a small group of people to bring in all their friends and so on
<riteo>
it's literally the only reason I use Discord
<cem>
yeah, it's really annoying
<cem>
I've tried for a long time to convince my friends to switch to alternatives
<cem>
but eh, I gave up
<riteo>
actually a friend of mine got converted to the based mumble, expecially for its cool af directional audio feature
<riteo>
but he's waiting for other people to switch too, so we're back to square one
<dilyn>
I had to sign a cla for the patch I submitted to the go build system
<dilyn>
but they haven't even added it to their releases yet :|
<riteo>
"But Discord's so complete! There obviously isn't any other software capable of sharing both audio and video with multiple people!"
<cem>
I converted my girlfriend to use matrix a few years ago, but she was really annoyed with Riot and switched back
<riteo>
matrix is pretty bad AFAIK
<acheam>
mumble was based until I started running kiss and realized the whole thing is qt
<riteo>
noble idea, pretty bad execution
<acheam>
even the server
<cem>
yeah, I don't blame her tbh
<riteo>
>mumble is only qt
<riteo>
there are CLI client AFAIK
<riteo>
mumble is very based
<acheam>
Barnard is the only one that comes to mind
<acheam>
and thats golang, which isnt much better
<acheam>
and the server is still qt
<cem>
wdym
<cem>
golang is the holy language
<cem>
golang stands for
<cem>
God's Language
<cem>
duh
<riteo>
how can a server be qt
<acheam>
qt provides more than gui stuff
<acheam>
its also a crutch for lazy programmers
<riteo>
IIRC there was something called uMurmur which implemented an extra small murmur implementation
<cem>
yeah, what do you expect from a graphical toolkit that links to openssl
<dilyn>
i don't want to locally delete this website
<dilyn>
i want to purge it
<riteo>
ok wtf
<riteo>
>(informal) An act of sexual intercourse.
<dilyn>
not even archive.come can save this cursed place
<riteo>
how is every word similar to mumble so cursed
<cem>
hack major domain name servers, and do that
<msk[m]>
except crumble
<riteo>
stumble would be genial but for other reasons
<riteo>
>Stumble is Prakash Belawadi's debut film. It won the Indian National Film Award for Best Feature Film in English in 2003.[citation needed] It depicts the new economy, the dot-com bust, stock market scams, mutual funds, and voluntary retirement.