ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.org | post logs or else | "An idiot admires complexity, a genius admires simplicity." -- Terry A. Davis
creative_name[m] has joined #kisslinux
msk[m] has joined #kisslinux
kqz has joined #kisslinux
GalaxyNova has quit [Quit: zzz]
<tleydxdy[m]>
hmm how would I create system user for a package?
<tleydxdy[m]>
I'm trying to package fcron and it wants a fcron user
<illiliti>
you can also use pre-remove hook to delete user
<tleydxdy[m]>
yes, but the build process needs that user already
<tleydxdy[m]>
I assume to install some files or something
<illiliti>
patch it out
<tleydxdy[m]>
well, if it's doing what I assume it's doing like creating some file owned by fcron then that wouldn't really work tho
<tleydxdy[m]>
kinda surprised that the build is not done in a chroot tbh
<acheam>
how would you handle dependencies in a chroot tho
<acheam>
I guess you could copy their files into it?
<acheam>
seems io heavy though
mahmutov has joined #kisslinux
GalaxyNova has joined #kisslinux
<tleydxdy[m]>
you just install the dependency into the chroot
<tleydxdy[m]>
this way you would find out if you left out a dep, as a bonus
<GalaxyNova>
I've switched to seamonkey
<GalaxyNova>
It's nice
<acheam>
as a main web browser?
<acheam>
does it still use an up to date gecko?
<GalaxyNova>
as a main web browser yes
<GalaxyNova>
acheam: IDK but honestly I coudn't care less
<GalaxyNova>
most websites that aren't shit render fine
<GalaxyNova>
I don't know if that's some kind of security vulnerability though..
<illiliti>
acheam: hardlinks or bind mounts can be used to handle deps in chroot without excessive copying
<acheam>
oh yeah, forgot about bind mounts. Hardlinks would still have the problem of duplicated file sizes, though, right?
<illiliti>
iirc hardlink is a symlink at the filesystem level. so there's shouldn't be a problem of dup sizes
<acheam>
oh okay
<tleydxdy[m]>
hardlink causes problem in case of modification
<tleydxdy[m]>
so reflink is needed for that
<acheam>
well they wouldnt be modified
<illiliti>
^
<tleydxdy[m]>
they would in the case we are talking about here
<illiliti>
i think everything in /etc/ should be just copied
<illiliti>
if you have chromium sources in /etc/, that's your problem
<tleydxdy[m]>
yeah
<tleydxdy[m]>
I mean it shouldn't be that big a problem to make a copy in chroot really
<tleydxdy[m]>
it's just the deps a package needs
<tleydxdy[m]>
not the full system
<tleydxdy[m]>
* just the make deps a
<tleydxdy[m]>
big oof, failed install leaves a dirty system
<acheam>
?
<acheam>
the make deps can be huge sometimes
<acheam>
llvm, gcc, nodejs, etc
<illiliti>
tleydxdy[m]: kiss isn't smart. it doesn't keep state to remove/fix leftovers if installation is failed
<tleydxdy[m]>
they are also huge project tho
<acheam>
tleydxdy[m]: im missing your point
<tleydxdy[m]>
I mean I understand if the post_install fails or something
<tleydxdy[m]>
but it could check the tar ball before unpacking it
<tleydxdy[m]>
acheam: the point is to not have the make environment tainted by what's in the system
<acheam>
so you want reproducible builds?
<tleydxdy[m]>
not really that far
<acheam>
having the builds autodetect features based on the build environment is fine IMO
<acheam>
take the mpv package for example
<tleydxdy[m]>
just to have less hard to pin down make problems
<acheam>
eh
<tleydxdy[m]>
"if it builds on my system, it should build on yours" sort of deal
<tleydxdy[m]>
probably a smart idea to make it configurable or something
<acheam>
on kiss people tend to customize their system so much that it wouldnt make a difference
<tleydxdy[m]>
acheam: how so?
<tleydxdy[m]>
none of the customization would be in the chroot environment
<acheam>
changing compilers, libc, providers of common utilities, etc
<acheam>
then you would need fully static binaries
<tleydxdy[m]>
no?
<acheam>
if the chroot is running musl and the chroot is running glibc, then the binary built in the chroot wont run on the host if it isnt static
<tleydxdy[m]>
I see what you mean, but in that case the package just depends on "libc"
<tleydxdy[m]>
and whatever package the user choose to provide libc is install into the chroot
<tleydxdy[m]>
the point is not to limit customization
<acheam>
but then it wouldn't be helpful for "if it builds on my system, it should build on yours" type discussions, if people's libc package is different anyway
<tleydxdy[m]>
but to make everything documented and replicable
<tleydxdy[m]>
so if build has a problem on some system, I can replicate it
<acheam>
this solves a really small problem
<acheam>
and it would limit customizations
<tleydxdy[m]>
it's a problem that happens all the time
<tleydxdy[m]>
acheam: in what way?
<acheam>
going back to the libc example
<acheam>
I cant change the libc on my system because under your proposed thing, all the builds should be the same
<acheam>
and I cant have a different libc in the chroot and on the host
<acheam>
and even if you were to use a generic "libc" package, then the reproducibility is gone
<tleydxdy[m]>
you customize your libc how you want
<tleydxdy[m]>
to reproduce it you just need a copy of the repos
<acheam>
this is obviously not going anywhere
<acheam>
if you want it, implement it
<tleydxdy[m]>
not the user's entire system
<acheam>
-e s/this/this discussion/g -e s/e$/e but the idea does have potential/g
<tleydxdy[m]>
lol, I was like "wait what is this kiss chroot
<tleydxdy[m]>
then I realized it's just an artifact of how kiss works
<tleydxdy[m]>
err, why is /usr a thing
<tleydxdy[m]>
wth is /usr/var
<GalaxyNova>
I really wish /usr didn't exist
<tleydxdy[m]>
yeah as I suspected make install tries to change the group of some files to fcron
<tleydxdy[m]>
curiously it did not work
<tleydxdy[m]>
what is installed on my system still has group root
<tleydxdy[m]>
right perm in the tar ball
<tleydxdy[m]>
seem like cp in pkg_install_file is missing a -p
<tleydxdy[m]>
not sure if it's intentional tho
<tleydxdy[m]>
nope, not the fault
<tleydxdy[m]>
err, I'm very confused
GalaxyNova has quit [Quit: zzz]
mahmutov has quit [Ping timeout: 245 seconds]
illiliti has quit [Quit: leaving]
<testuser[m]>
Hi
soliwilos has quit [Remote host closed the connection]
<acheam>
hi testuser[m]
<acheam>
what brings you here this early today?
<testuser[m]>
Class timings
<noocsharp>
so for the past day, my domain has been pointing at the wrong ip address
<acheam>
lmao
<acheam>
how'd that happen
<acheam>
hmm... dig nihaljere.xyz is timing out for me
<acheam>
and the names not resolving
<noocsharp>
i put a wrong digit in the ip address
<acheam>
oof
<noocsharp>
it resolves fine now for me
<acheam>
weird
gtms has joined #kisslinux
aspirus has joined #kisslinux
<aspirus>
ERROR: 'perl' not found
<aspirus>
nvm it fixed itself
<aspirus>
HI
<testuser[m]>
HI
<aspirus>
Sorry, I didn't introduce myself. I just found out about KISS Linux and in the proceess of installing.
GalaxyNova has joined #kisslinux
<aspirus>
Should i ask for support here?
aspirus has quit [Quit: Lost terminal]
<testuser[m]>
Perhaps
<testuser[m]>
Find your terminal first
<GalaxyNova>
lmao
<GalaxyNova>
poor terminals getting lost :(
Uks2 has quit [Quit: Byee]
Uks2 has joined #kisslinux
kayw has quit [Quit: WeeChat 3.2]
kayw has joined #kisslinux
<GalaxyNova>
Yoooo
<GalaxyNova>
fossil is amazing
<GalaxyNova>
i might just migrate my gitea to just a list of fossil servers
<testuser[m]>
Rich
GalaxyNova has quit [Ping timeout: 265 seconds]
aspirus has joined #kisslinux
<aspirus>
I just installed KISS Linux, I can't get Internet to work
<aosync>
What does fossil do better than git ?
<aspirus>
Did i had to enable something during making the kernel to get dhcpcd to use my android tethering for internet
<aosync>
aspirus: could be get more diagnostics? the output of ifconfig, your wireless card model, what you enabled when configuring the kernel?
<aspirus>
Intel Corporation Wireless 7265 (from lspci in void linux where wifi works with iwd and iwctl)
<aspirus>
i didnt edit the default .config apart from what the install guide told
<aspirus>
i copied all folders from the firmware tar to /usr/lib/firmware
aspirus has quit [Quit: Lost terminal]
Uks2 has quit [Quit: Byee]
Uks3 has joined #kisslinux
<aosync>
ok, and did you add this folder to the firmware folder thing in the kernel config
<aosync>
and then listed the iwlwifi-7265D.ucode in the field of thing to load ?
aspirus has joined #kisslinux
<aspirus>
aosync: i didnt change anything in the kernel config
<aosync>
yep, you gotta do some stuff
<aspirus>
should i just use void linux 's kernel?
<aosync>
no, configure your own, it's pretty nice
<aspirus>
i didnt understood anything in menuconfig so i just left it along
<testuser[m]>
did you check the wiki
<testuser[m]>
it should have some info about kernel confi
<aosync>
aspirus, mess around in menu config, find out how to specify the firmware dir and your firmware file