<Guest54>
"./autogen.sh: line 30: aclocal: not found"
<Guest54>
Ah maybe it is automake i need
<midfavila>
that's correct.
<Guest54>
ok i will open up a github issue
<testuser[m]1>
Btw use nc termbin.com 9999 < log next time
<testuser[m]1>
Easier to open
<midfavila>
does busybox include netcat?
<Guest54>
Alright i was not familar with that. I never used busybox except on Android :D
<testuser[m]1>
Yeah
<midfavila>
i'm not sure if I should be impressed or disgusted
<midfavila>
or both
<testuser[m]1>
You're using busybox if you havent customized kiss
<testuser[m]1>
You can disable everything in the config,
<dilyn>
for anyone interested in breaking their machines, the small PRs Dylan has submitted are in master if you'd like to test :) will make a tag probably tomorrow when I just run the whole thing through the gamut
<Guest54>
At me?
<midfavila>
testuser[m]1 i just use seperate packages to provide dedicated tools
<midfavila>
nmap provides my nc for example
<testuser[m]1>
How did you fix the kiss init script with sbase getty?
<testuser[m]1>
or ubase
<midfavila>
I didn't.
<midfavila>
I use hummingbird
<midfavila>
but for the record,
<midfavila>
suckless getty requires an absolute path to the tty file
<midfavila>
and it doesn't accept baudrate or termtype args
<midfavila>
so getty /dev/ttyN is valid
<testuser[m]1>
Ok
<testuser[m]1>
Thanks
<midfavila>
but getty ttyN, or something else, isn't
<midfavila>
and yeah, np
<dilyn>
just use util-linux (:
<midfavila>
only reason I keep util-linux around is fdisk
<dilyn>
f
<testuser[m]1>
I only have it for the libs
<midfavila>
fsck is nice, but I'd have no qualms about writing a couple if blocks to handle fs-specific fsck calls if the general tool wasn't available
<dilyn>
my ubuntu install didn't pick up on my external hard drive being plugged in. worst distro ever :'(
<dilyn>
tfw you didn't build ext4 support into your kernel...
<midfavila>
>using extfs
<midfavila>
how unbased can one man be
<dilyn>
this isn't even my final form...
<midfavila>
dear god
<testuser[m]1>
Ntfs
<illiliti>
fsck is evil
* acheam
spits on testuser[m]1
<midfavila>
wait until you see testuser's shell, acheam
<midfavila>
it's very powerful
<technoznc>
midfavila: what do you use instead of ext? :D
<midfavila>
xfs
<midfavila>
and nilfs
<acheam>
what about /boot though
<midfavila>
xfs
<midfavila>
*did I stutter*
<testuser[m]1>
Wat
<testuser[m]1>
How
<acheam>
^
<midfavila>
by using a tool called mkfs.xfs
<testuser[m]1>
Don't mobos just recognise fat
<midfavila>
extlinux has xfs support, ya know
<midfavila>
and no, BIOS doesn't give a damn
<acheam>
oh
<midfavila>
it just loads the first 512 bytes and goes in hard
<acheam>
I didn't know it supported xfs
<midfavila>
the first 512 bytes, coincedentally,
<acheam>
well
<midfavila>
are raw data
<acheam>
then I regret using ext on this install lol
<midfavila>
ext is... fine
<midfavila>
but that's just it
<midfavila>
it's mediocre
<acheam>
I like xfs but didn't want two partition types
<acheam>
and I didn't know syslinix supports xfs
* midfavila
nods
<midfavila>
xfs is for high-performance partitions, and nilfs is for my home directory
<midfavila>
real-time snapshots are based as hell
* acheam
still doesnt get the difference between syslinux and extlinux and is too afraid to ask
<midfavila>
syslinux is used for removeable media
<midfavila>
extlinux is used on hard drives and stuff
<midfavila>
that's it
<acheam>
oh
<acheam>
ok
<midfavila>
ye
<acheam>
why do they need to be different?
<midfavila>
presumably for compactness
<midfavila>
iso9660 support isn't needed if you're only going to be booting off ext or xfs
<midfavila>
unrelated note; i've uploaded my scripts and dotfiles to my git repo, so you can all bully me for that now, if you'd like
<midfavila>
plumber may be of particular interest to anyone using links2
<midfavila>
semi-related note when it comes to scripts:
<midfavila>
the latest version of kiss breaks when I attempt to install packages or change alternatives
<midfavila>
doesn't seem to be escalating privileges
<testuser[m]1>
How do you use yewtu.be in links, isn't it crimeflared
<midfavila>
nope.
<testuser[m]1>
Btw tou can change s/http\/ to s|http/ in your script
<midfavila>
why's that? I've not seen anyone use | in sed scripts before
<testuser[m]1>
So you don't need to escape it again
<testuser[m]1>
You can use & or anything
<midfavila>
Aaah.
<midfavila>
Alright, I'll update that right now.
<midfavila>
Thanks for the tip.
<dilyn>
the git version mid?
<midfavila>
yes
<midfavila>
i've attempted with KISS_SU set to su, ssu, and blank
<midfavila>
all three cause the same behavior
<midfavila>
oddly enough,
<midfavila>
if the package is built as an unprivileged user, it appears to work fine
<midfavila>
not sure if this is me being 2am brained or what
<midfavila>
...nope, that's not it... just checked...
<testuser[m]1>
also i don't think "${1}" is necessary, it can be useful if you want to do something like `"${var}iable"` so you don't try to access variable instead of var
<midfavila>
yes, I know
<midfavila>
i just want to maintain consistency
<midfavila>
anyway, dilyn, the specific errors reported are from cp and chmod, when operating on /var/db/kiss/{installed/$package,choices/$package-contets}
<midfavila>
stating that permission is denied and operation not permitted, respectively
<midfavila>
this makes sense, considering that unprivileged packages are installed with midfavila:midfavila owner and group, but I would have expected kiss to perform privilege escalation when installing...
<midfavila>
to be clear, this is a clean install of KISS that's having these problems. my existing install has the permissions you would expect, and doesn't encounter any such errors
<testuser[m]1>
dilyn what do you think of adding multiple processes to the kiss-outdated script, it goes much faster for me but dunno about repology rate limits
<dilyn>
Interesting. I'll see if I can reproduce anything tomorrow
<testuser[m]1>
just add `wait` at the end so it doesnt exit early
<midfavila>
re: multiprocess or privs?
<testuser[m]1>
reproduce so i guess perms
<dilyn>
testuser: making kiss-outdated faster would be cool (though I don't find it terribly slow?) but yes, not hammering repology is ideal
<midfavila>
(also if we're making suggestions, having the ability to use axel as an alternative to curl would be neat)
<dilyn>
yes, reproduce your issue mid
<testuser[m]1>
i think its more cuz of my trash net
<dilyn>
something something if you write a patch... ;)
<midfavila>
i mean
<midfavila>
my fork of kiss already has a working implementation
<dilyn>
it may very well be. I get 25MB/s down lmfao
<midfavila>
just gotta replace the hardcoded call with a variable like KISS_DL or w/e
<testuser[m]1>
turn your modification to use something like KISS_COMPRESS
<testuser[m]1>
yea
<midfavila>
multi-threaded downloads in mainline, here we coooooooooooooooooooooooooooooome
<midfavila>
...also, incidental FTP support
<Guest54>
Anybody know if the mpv package was compiled with LUA support for OSD (the GUI when you move the mouse)
<midfavila>
check the buildfile Guest54
<testuser[m]1>
build luajit before mpv itll be enabled
<dilyn>
^
<midfavila>
anyway, your suggestions have been applied to plumber, testuser[m]1
<Guest54>
ok ty
<testuser[m]1>
nice
<dilyn>
gn folx
dilyn has quit [Quit: Connection closed]
<testuser[m]1>
gn
<midfavila>
i should probably sleep soon as well
<midfavila>
can't reimage my laptop until this permissions problem is sorted
<Guest54>
Sleep is for the weak
<midfavila>
kind of a bummer, too. i'm excited to see how well my new cflags work
<midfavila>
speaking of which, are there any non-gnu seds that are feasible for daily use? beyond busybox, I mean
<midfavila>
suckless sed and plan 9 sed are on my list to try, but I don't know how well they'd work
<midfavila>
hmm
<midfavila>
i should fork snarf
<midfavila>
axel is over 60 kb, while snarf is only around 30
<midfavila>
only thing snarf's missing is ssl...
<midfavila>
...and I could probably decrease the size further if I made ftp and gopher support optional...
<midfavila>
...yeah, that's going on the list. being able to wipe out axel and curl in one fell swoop would be based
<testuser[m]1>
how do you use git
<testuser[m]1>
without libcurl
<midfavila>
libcurl is statically compiled into git
<testuser[m]1>
so its still there
<midfavila>
Yup.
<testuser[m]1>
:p
<midfavila>
The utility isn't, nor is the other junk on my filesystem, though.
<midfavila>
the binary for static curl alone is something like 3.2mb
<midfavila>
3.9*
<testuser[m]1>
its cuz glibc, muslone is 2mb
<midfavila>
even still
<testuser[m]1>
it does a LOT more than axel though
<midfavila>
2mb+whatever other shit curl has
<midfavila>
versus
<midfavila>
34kb for snarf
<midfavila>
or 63kb for axel
<midfavila>
also,
<midfavila>
fwiw,
<midfavila>
the only thing I actually use curl for is the occasional HTTP POST
<midfavila>
add SSL and potentially multithread to snarf, and the ability to POST, and it would be far superior to curl and axel, in my case
<midfavila>
FTP, FTPS, HTTP, HTTPS, and Gopher, all in a single tiny statically-linked ELF, with the ability to POST and make multi-threaded downloads...
* midfavila
performs a chef's kiss
<midfavila>
mwah
<testuser[m]1>
nice
<testuser[m]1>
does it provide a librayr ?
<midfavila>
it does not
<midfavila>
but I'm sure it wouldn't be particularly hard to write one
<midfavila>
the whole project is 2083 lines of C
Guest54 has quit [Quit: Client closed]
<midfavila>
with 159 lines of headers
<midfavila>
really teeny
<midfavila>
like, incredibly so.
<midfavila>
i'm really going to have to study this.
gtms has joined #kisslinux
<midfavila>
i've just triggered github's bot protection mechanism... by engaging in the highly stressful activity of scrolling through search results...
<midfavila>
good job, microshit
<testuser[m]1>
Yeah its super annoying you can't even go 2 pages without being flagged
<testuser[m]1>
And then it even allows u to search up another term but no tthe same one
<testuser[m]1>
Useless
<midfavila>
i'm just looking for non-GNU greps that would be nice
<midfavila>
it's the one userspace command I use regularly that I have to rely on gnu for
<onodera>
since dylan is back, what will happen to the fork?
<testuser[m]1>
hi onodera
sad_plan has joined #kisslinux
sad_plan has quit [Read error: Connection reset by peer]
sad_plan has joined #kisslinux
<sad_plan>
hey
<testuser[m]1>
hi
<sad_plan>
how to you find compiler options really? I mean, how do you know which packages has what options, and what theyre called? the documentation? or by running ./configure and watch the output?
<testuser[m]1>
thats no compiler option
<testuser[m]1>
you mean stuff like --disable-feature ?
<testuser[m]1>
./configure --help | less
<sad_plan>
yes
<sad_plan>
aaaah. fantastic
<testuser[m]1>
sometimes all the stuff isnt listed in help so you can open the script yourself
Uks2 has quit [Ping timeout: 272 seconds]
<sad_plan>
for some reason I thought it was way more complicated than that tbh :p which was a bit of a relief :p
<acheam>
much quicker than a PR, and respects my freedom
<cem>
You also can't lock Github PRs on a repository
<acheam>
oh nice phoebos[m]
<acheam>
cem: can you do that with email?
<acheam>
oh you mean disable them entirely?
<ang>
I still have't actually set up email, so I just use `git format-patch --stdout HEAD~ | xsel`
<acheam>
Ah nice
<cem>
acheam: yes, you can't disable pulls unless you archive the repository
<cem>
You can only disable issues
<acheam>
send-email does require Perl so....
<testuser[m]1>
If i send patches via proton's web ui will they get fucked
<acheam>
cem: oh interesting. another advantage of gitea then
<ang>
no, if you disable html email
<acheam>
which you should so anyway
<ang>
I use webmail too, testuser[m]1
<testuser[m]1>
Nice
<ang>
just make sure to write your commit messages wrapped to something like 64 chars
<testuser[m]1>
I prefer shithub to this method since main browser is links and proton needs weird bridge stuff to use another client
<testuser[m]1>
Ill try it though
<cem>
acheam: Yeah, perl is a big bummer. I recall mcf was using git imap-send instead, which is C
<ang>
I like that you can simply do your changes in the actual repo, commit, format-patch and then reset --hard HEAD~
<cem>
imap-send basically puts your patches to your imap Drafts folder for you to send with your mail client
<ang>
I don't really mind perl, just haven't decided on what mail system I want to use
<konimex>
iirc in the past dylan would like to have full control of the infra (that means org, and probably anything related to KISS), don't know if he changed his stance
dilyn has joined #kisslinux
<dilyn>
Dylan archived his community repository, so it's not obvious what exactly he's up to :)
<dilyn>
I'm certain he'll say something if/when he wants to *do* something
<testuser[m]1>
dilyn: what should be done about the install usage in packages ?
midfavila-laptop has quit [Ping timeout: 265 seconds]
<dilyn>
nobody should use -t :v
<dilyn>
it's just uthash and vundle in the entire repository
<testuser[m]1>
I think there's more
<testuser[m]1>
Try grepping for `install.*-t`
<testuser[m]1>
I guess im mistaken
<dilyn>
even more gross
<dilyn>
My thoughts are that if you can accomplish something with install without using t, you should. because it sucks.
<dilyn>
but I don't think it should be blacklisted from community... probably...
<ang>
which implementations have -t and which don't?
<dilyn>
busybox, toybox, coreutils certainly do
<dilyn>
uutils doesn't...
<dilyn>
suckless
<dilyn>
whatever bsd uses probably doesn't
midfavila has quit [Ping timeout: 252 seconds]
<ang>
I see, fuck -t then :>
Uks2 has quit [Quit: Byee]
Uks2 has joined #kisslinux
<acheam>
ugh why does llvm take so long to compile
<acheam>
every time I change my build file, I'm in for a many hour ordeal only to have it fail in some build command after the compilation step
<acheam>
phoebos[m]: I couldn't get your kiss continue build thing to work, it would complain about a a missing ./var/db/kiss
<acheam>
and when creating that directory manually, it would do some weird recursion thing
<phoebos[m]>
Hm. Probably an uninitialised variable
<testuser[m]1>
acheam did you install wyverkiss
<phoebos[m]>
acheam: what's it saying exactly?
<phoebos[m]>
did you run kiss co from the pkg_dir
<acheam>
testuser[m]1: in a sense
<phoebos[m]>
/tmp/pkg-$pid/$pkg or whatever
<acheam>
oh no
<acheam>
gotcha
<acheam>
will do
<phoebos[m]>
finger guns
krjst has quit [Quit: bye]
krjst has joined #kisslinux
gtms has joined #kisslinux
gtms has quit [Remote host closed the connection]
Uks2 has quit [Ping timeout: 265 seconds]
Uks2 has joined #kisslinux
Guest2856 has joined #kisslinux
midfavila has joined #kisslinux
<kiedtl>
Is dylanaraps planning to merge in changes from the community repos, or will he just continue with the old repos?
<kiedtl>
Also, it looks like he bought kisslinux.xyz. Will k1sslinux.org be discontinued?
<midfavila>
nobody seems to know yet
<midfavila>
i imagine dylan and dilyn'll have that conversation and announce what's going on when they're ready.
<midfavila>
DnD
<Guest2856>
Tbh k1sslinux.org is kind of ugly
<Guest2856>
The domain name that is
<kiedtl>
It's what people are used to, though.
<midfavila>
also
<kiedtl>
The first domain (well, second) was k1ss.org
<Guest2856>
It used to be k1ss.org
<Guest2856>
Yeah
<kiedtl>
Yes
<midfavila>
a .org is... slightly less...
<midfavila>
illegitmate feeling than an .xyz
<midfavila>
:v
<kiedtl>
Precisely
<kiedtl>
:(
<Guest2856>
All the luke smith clones use xyz domain
<midfavila>
xyz is just used for random stuff
<kiedtl>
dilyn: Mind if I go ahead and email dylanaraps (or ask on one of the repos) about the domain, repos, package manager, irc, mailing list, etc? Or do you think we should wait until dylan decides to contact us?
<Guest2856>
Only "professional" use for it i've seen is Alphabet's abc.xyz
<dilyn>
kiedtl: I don't terribly care what you do :) I'm of the mind that Dylan's just doing his thing, and if he wants something to change he'd say something
<dilyn>
I imagine he still hasn't actually made a grand plan of any sort
<kiedtl>
Okay
<midfavila>
oh, btw, dilyn: any updates on the weird permissions bug?
<dilyn>
not yet
<midfavila>
Alright. Keep me posted on any info.
<midfavila>
I'll keep trying stuff.
<dilyn>
for sure
<dilyn>
can you give me an example of the package that caused the problem?
<midfavila>
uh, everything
<dilyn>
or roughly how you identified it
<dilyn>
lmfao alrighty
<midfavila>
and I identified it by
<midfavila>
"oh, uh, I don't think installing python is supposed to give me thousands of lines of "Permission denied" output"
<midfavila>
...so, other weird shit:
<midfavila>
somehow the permissions of my root directory ended up all weird
<midfavila>
gonna try and fix those... I really don't want to redo the past three days of work
<dilyn>
ohoohooo
<dilyn>
ls -al / ?
<dilyn>
if /. happens to be owned by user and not root, that's your problem :P
<dilyn>
cannot currently reproduce
<midfavila>
right, that would make sense
<midfavila>
I just have no idea how that would have happened, considering...
<midfavila>
well
<midfavila>
i hadn't even had another user aside from root to assign permissions *to* until yesterday
<dilyn>
did you do something like tar xf foo@ver-1.tar.xz -C / ?
<midfavila>
nope.
<dilyn>
hm
<dilyn>
I did that once :v
<midfavila>
up until last night when I mentioned it, everything had been done as root
<acheam>
has anyone been able to use distcc on kiss?
<midfavila>
i tried it
<midfavila>
once
<midfavila>
it didn't work
<testuser[m]1>
It's been packaged in an old commit
Guest2856 has quit [Quit: Client closed]
<phoebos[m]>
i tried it on the one gentoo machine i had
<phoebos[m]>
didn't work
<testuser[m]1>
Wdym didn't work
<midfavila>
man, it's more than just owners and groups that are fucked... permission bits are screwed, too
<midfavila>
...fuck, you know what I bet I did?
<midfavila>
i bet I ran a chown -R .* in /home/midfavila
<acheam>
testuser[m]1: do you know in what repo?
<testuser[m]1>
Community
<midfavila>
okay cool, permissions adjusted
<dilyn>
lmfaoooo
<midfavila>
kiss works properly now
<midfavila>
excuse my retardation
<dilyn>
rm -rf ~/.*
<midfavila>
2am brane
<midfavila>
honestly, chown .* is worse than rm -rf /
<midfavila>
because there's still that faint hope you can fix things
<midfavila>
rm -rf at least gets it over with quickly
<acheam>
Thanks testuser[m]1 !
<acheam>
how big are yalls's kernels?
<acheam>
I'm at 8.6M
<midfavila>
i usually average around 13m for my desktop and 11 for my laptop
<midfavila>
but I compile all my stuff statically
<dilyn>
6MB if I don't bother with kvm...
<dilyn>
10 if I do
<testuser[m]1>
Mine is 3 or 4 mb
<testuser[m]1>
Ye 4
<dilyn>
what are you using to compress your kernel :o
<midfavila>
oh, right, that's totally a thing, isn't it...
<midfavila>
i normally just use lz4
<testuser[m]1>
How much size do gpu drivers take in the kernel? I don't have any cuz novideo on pc and server kernel doesn't need gpu
<midfavila>
well
<testuser[m]1>
zstd only dilyn
<midfavila>
amdgpu is like 30% of linux's codebase or something on its own
<midfavila>
so
<dilyn>
my man
<midfavila>
>zstd
<midfavila>
begone, corporate shill
<midfavila>
your compression algorithms are problematic
<testuser[m]1>
I don't care as long as it ain't got zucc's spyware in it
<dilyn>
zstd is all you need baybee
<dilyn>
xz/gzip/bzip2 begone
<dilyn>
there is only the standard
<midfavila>
i mostly use lz4 for zram or w/e anyway
<acheam>
more than I'd like to individually package
<omanom>
you can make it a single binary with pyinstaller --onefile, although depending on your dependencies it may require some configuration manipulation
<acheam>
what are you suggesting? pyinstalling it into a binary and then hosting using that as my kiss source?
<acheam>
OK thanks
<omanom>
yeah, or you can write a requirements.txt file and use pip install -r requirements.txt, that would allow you to specify dependencies and even specific versions
<acheam>
still requires internet access during the build phase
<omanom>
there's further options for pip that allow installing from archives on disk (rather than going out to the internet)
ax has quit [Changing host]
ax has joined #kisslinux
<acheam>
eh this seems like too much work for a personal package lol
<omanom>
i don't remember off the top of my head, something like pip install -f /path/to/your/packages
<claudia>
You can prob install to $PWD too and make them available at buildtime or whatever.
<acheam>
doesnt stop the issue of multiple packages wanting to provide the same dependencies though
<claudia>
What do you want to package exactly?
<cem>
Oh no, I packaged it correctly when I was first packaging webkit, but dylan accidentally added it to community as libXslt
<acheam>
claudia: sphinx-doc
<phoebos>
oof
<acheam>
oof
<midfavila>
oof
<acheam>
ugh there are 1 too few dashes under this heading in the llvm documentation source. I expected better
claudia has quit [Read error: Connection reset by peer]
claudia has joined #kisslinux
<dilyn>
demand a refund
<cem>
I'm sure warranty will cover it
<cem>
o wait
<claudia>
acheam, a quick look at the arch pkg-build, most of the deps should be packable like qutebrowser.
<claudia>
Downside is ofc, you have to watch out for many many versions ^^
<claudia>
'pip install -U Sphinx' is prob the sanest way.
<dilyn>
yeah I just defaulted to pip for certbot because i cba to handle python's bullshit
<acheam>
hmm yeah Im lazy
claudia has quit [Quit: Leaving]
<midfavila>
man, this is the second time I've sat here wishing we had a "provides"
<midfavila>
or at least some way to OR dependencies
<dilyn>
wdym
<midfavila>
see: libinput
<midfavila>
can't include eudev or libudev-zero in the depends, because it'll fuck stuff up, but if you *don't* include it, and it ends up being pulled in as part of a chain of packages...
<midfavila>
it's just a real pain in the ass
<dilyn>
"Pain in the ass" seems a bit of an overstatement
<midfavila>
considering that I now have to spend another hour and a half or so recompiling packages because of it,
<midfavila>
not really
<midfavila>
ultimately it's not a huge deal, but it's still - like i said - a PITA
<illiliti>
instead of "provides" file we can use symlinks
<dilyn>
what do you mean recompiling
<illiliti>
e.g: libinput depends file contains udev. udev is a symlink that points to libudev-zero/eudev
<dilyn>
that sounds like a worse way. now if I want to switch I have to change a link && recompile, instead of just rebuilding
<midfavila>
also still requires setup in advance...