ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.org | post logs or else | "Seek simplicity but distrust it" -- Alfred North Whitehead
<bujeddhazeus>
Hmm... no luck still
<soliwilos>
The firefox 94 ebuild is.. fairly substantial.
<soliwilos>
The kiss build file is about a tenth of that.
<bujeddhazeus>
soliwilos: yeah, but I'm using pretty much the same stuff as the kisslinux build file
<soliwilos>
bujeddhazeus: Tried using gentoo's ebuild more or less as-is, though without the X11 only deps? Still with the no-x11 patch.
<bujeddhazeus>
soliwilos: I took a look at what deps would be installed, and I don't think that would change anything considering the patch
<bujeddhazeus>
soliwilos: or wait. That's actually what I'm doing
<bujeddhazeus>
I misunderstood at first, sorry
bibliocar has quit [Ping timeout: 256 seconds]
bibliocar has joined #kisslinux
bibliocar has quit [Client Quit]
<soliwilos>
I see. I'm not sure what more to suggest right now, as it's pretty late here I'm soon going for some sleep.
<natris1979[m]>
so I was poking around https://github.com/kiss-community/graveyard, and I'm curious why this stuff was dropped? Like should I be worried about trying to install this stuff?
<soliwilos>
I think dropped packages are usually due to someone no longer maintaining it.
<soliwilos>
bujeddhazeus: Aye. :)
<natris1979[m]>
I see, that makes sense.
<soliwilos>
natris1979[m]: If you want something, I'd say go for it, but update to latest versions.
<jason123onirc>
Would kiss on an old pc be a good idea if I am cross compiling?
<natris1979[m]>
right
<natris1979[m]>
jason123onirc: I don't see why it wouldn't work. I think the trickiest bit would be getting your kernel configured properly
<soliwilos>
jason123onirc: kiss on an old pc just means slower compile times, I think personally I'd rather deal with slower builds than cross-compiling, but I'm lazy. :p
<jason123onirc>
Well this pc would be really slow
<natris1979[m]>
I suppose it also depends on how old is old. Also, if other modern linuxes don't work, I don't think kiss would be more likely to work
<jason123onirc>
amd athlon x2 64 with 1gb of ram
<soliwilos>
Ow, I see.
<jason123onirc>
yeah not fast
<soliwilos>
Not a lot of memory either, if you would want desktop big-things like browsers.
<jedavies>
you would have problems building larger packages with 1gb ram. nodejs, firefox etc.
<soliwilos>
Indeed.
<jason123onirc>
yeah that is why I would need to cross compile
<jedavies>
Do you have another machine you can build on?
<natris1979[m]>
yeah that's the same age as the computer I had when I was frustrated with Gentoo above
<jason123onirc>
yes i do have another pc
<jason123onirc>
well I built kiss linux on a 2008 core 2 duo laptop from 2008 but gave up when I started with xorg
<natris1979[m]>
yeah, doesn't really seem like kiss is made for X. Not saying you couldn't get it going, but it's gonna be work
<jason123onirc>
the kiss xorg repo works
<natris1979[m]>
oh cool
<jason123onirc>
but I built kiss on this laptop awhile ago but this pc is different
<jason123onirc>
I am just wondering if kiss would be a good option for an old pc if I cross compile
<jedavies>
If it's x86_64 to x86_64 it's not really cross compiling. You could just build packages on one machine and copy them to another one.
<jason123onirc>
well I don't have kiss on my building pc
<jedavies>
You can build them in a chroot
<jason123onirc>
well it might be easier to cross compile directly over to the pc
<natris1979[m]>
what jedavies is saying is that's not cross compiling. Cross compiling if if you were to complie i386 or arm binaries from a x86_64 machine. The later is much more error prone and more complicated
<natris1979[m]>
so you're lucky in that sense
<jason123onirc>
so then I just compile directly to the pc
<jedavies>
You can build packages for one machine on another machine. But I'm not sure what "compile directly to the pc" means
<jason123onirc>
Would distcc work on kiss linux?
<jedavies>
aah, I think someone may have packaged that in community
<jedavies>
Not tried it though. I think they use it a lot in arch?
<jason123onirc>
I don't know
<jason123onirc>
If I don't use distcc how would I get the compiled packages onto the other pc?
<jedavies>
There's nothing as part of kiss to do that automatically. But something as simple as scp'ing the packages over and installing them would work.
<natris1979[m]>
sftp? SneakerNet?
<jedavies>
On my fork I have a script to check for new packages on a build machine, it downloads via curl and then installs them
<jedavies>
But all you need is a way of getting the files over, and then you run "kiss i *.tar.gz"
<jason123onirc>
so I setup a bin server?
<jedavies>
If you want to, but that's not something kiss supports normally. You would have to copy the files over the network with e.g. scp, or use a usb drive, or write your own script.
<jedavies>
afaik
<jason123onirc>
it sounds hard to build packages on my main pc and send them over
<jason123onirc>
It might just be better to stick with kiss in a vm
<jedavies>
There is no automated way on kiss afaik, unless anyone here has suggestions
<natris1979[m]>
I have an older laptop gathering dust and a kiss vm humming along just fine. Just sayin'
<jason123onirc>
What does it mean if when I try to update it tells me to commit your changes or stash them before merging?
<natris1979[m]>
sounds like you changed some file. Do you get something when you run `git status`?
<jason123onirc>
it says not a git repo
<natris1979[m]>
what directory are you in?
<jason123onirc>
do I need to be in my repo directoy?
<natris1979[m]>
that's probably what it's referring to in that error
<natris1979[m]>
so you want to do `git status` in there
<jason123onirc>
ok I will try that
<natris1979[m]>
that'll show you files that you changed. If you want to just revert to what was in the repo and lose your changes forever, you can do `git checkout .` but be careful
<natris1979[m]>
before that you can see what you changed with `git diff`
<jason123onirc>
I don't think I changed anything
<natris1979[m]>
huh weird. Did you check all the folders in your $KISS_PATH?
<jason123onirc>
it is the same as when it worked
<natris1979[m]>
I'm asking did you cd into each folder in your KISS_PATH and run git status?
<jason123onirc>
yes i did
<natris1979[m]>
and each has nothing? So strange. Not sure what it could be
<jason123onirc>
it does have stuff
<natris1979[m]>
what are you running when you get that error?
<natris1979[m]>
oh
<natris1979[m]>
well that's the problem :)
<natris1979[m]>
what does it show?
<jason123onirc>
it told me to run git add so I did
<natris1979[m]>
do you remember changing something there?
<jason123onirc>
nope
<natris1979[m]>
what do you get if you run `git diff master`?
<testuser[m]>
Hi
<jason123onirc>
if i run git diff master
<jason123onirc>
it gives me lines and lines of code
<jason123onirc>
the only thing I did was not update in awhile
<natris1979[m]>
I mean.. I know what to do to get you around this but feel weird about doing it without knowing how you got here
<jason123onirc>
knowing how I got there is by doing nothing
<jason123onirc>
just not updating
<jason123onirc>
it worked before
<jason123onirc>
load up kiss and it does not work
<natris1979[m]>
I mean you can run `git stash` and it will store everything changed temporarily
<jason123onirc>
git stash worked
<jason123onirc>
thanks
<natris1979[m]>
sure
<jason123onirc>
well now there is no version file for one of my packages
<jason123onirc>
weird
<natris1979[m]>
what package?
<jason123onirc>
sowm
<jason123onirc>
well it worked once i built it again
<jason123onirc>
the fun of kiss
<jason123onirc>
really easy to fix errors
<natris1979[m]>
shrug glad you got it going
<jason123onirc>
yep
<jason123onirc>
now i just have to wait for it to build the updates
<natris1979[m]>
the other fun of kiss :D
<jason123onirc>
yep
<natris1979[m]>
oh did you maybe try copying repo folders from another computer?
<natris1979[m]>
into the ones already on this one?
<natris1979[m]>
sorry, I mean into the repos already on this pc
<jason123onirc>
no I built everything on the vm I am trying to update
<jason123onirc>
what package do I need for virtualbox xorg? there is no xf86-video-vmware package
<natris1979[m]>
I've never done xorg on virtualbox, so I'm not sure
<natris1979[m]>
it should work without anything special but you might need something for like the mouse and clipboard integration with the host system
<jason123onirc>
it does not work
<jason123onirc>
I will try compiling the kernel again and enabling stuff
<natris1979[m]>
at all?
<natris1979[m]>
do you get errors?
<jason123onirc>
I get an error with startx
<jason123onirc>
same error with gentoo but I fixed it on gentoo
<natris1979[m]>
hmm
<jason123onirc>
I will just try to compile the kernel again with enabling stuff for vms
<natris1979[m]>
yeah, he goes through it on vmware, but it was fairly simple to adapt for hyper-v. I imagine virtualbox is similar
<natris1979[m]>
btw, I don't really recommend hyper-v. I'm just using it because it's used for WSL, windows can only do one hypervisor that connects deeply to the hardware
<jason123onirc>
oh yeah so I can just follow that and what I did for gentoo
<jason123onirc>
vmware video drivers are the same for virtualbox
<jason123onirc>
I use xf86-video-vmware on gentoo for virtualbox
<natris1979[m]>
oh interersting
<natris1979[m]>
didn't realize that worked
<natris1979[m]>
I've only used virtualbox to run windows (poorly) from mac
<jason123onirc>
yeah I will see if changing the kernel works
<jason123onirc>
but first I have to wait for the updates to finish
<natris1979[m]>
oh man, I'm realizing how spoiled I am by my 16 core gaming laptop
<jason123onirc>
Do you run kiss on your computer?
<natris1979[m]>
I run it in a vm
<natris1979[m]>
but yes
<jason123onirc>
oh in a vm
<natris1979[m]>
haven't set up any kind of gui yet though
<jason123onirc>
oh
<jason123onirc>
what vm software do you use?
<natris1979[m]>
hyper v
<natris1979[m]>
form microsoft
<natris1979[m]>
though I don't really like it. Might switch to virtualbox, or see if I can get kiss working under WSL
<jason123onirc>
always used virtualbox under windows
acheam has joined #kisslinux
<natris1979[m]>
probably wise
<natris1979[m]>
has anyone here played with https://github.com/eudaldgr/kiss-live? It crashes pretty hard on me, but I'm not to surprised, it being a year since it's last commit and release
<acheam>
date of last commit isn't a good metric for software completeness
<jason123onirc>
yeah things changed since then
<natris1979[m]>
fair point in the general case. But this one seemed, in the past, to tie itself to kiss releases
<natris1979[m]>
so for this one it seems not a good sign that it's not been worked on
<acheam>
where is it crashing?
<acheam>
/how
<jason123onirc>
I got it to boot on my vm
<acheam>
any crashes are probably related to the linux build rather than the kiss version... the package manager crashing wouldn't lead to the whole OS crashing
<acheam>
its a shame eudaldgr has been off the radar in the last few months... he was doing some good stuff
<natris1979[m]>
just the script crashes, not the whole machine
<acheam>
what script? kiss or kiss-live?
<natris1979[m]>
I was trying to run `kiss-live`
<acheam>
what in the script crashes?
<acheam>
I doubt the shell itself is crashing
<natris1979[m]>
hold on.. For right now I was just wondering if anyone had used it. Now that I know that, and that it still works for others, I can build up some logs and things to get some help
<jason123onirc>
eudaldgr was the person who made xfce for kiss
<jason123onirc>
I would really like to see xfce for kiss
<acheam>
natris1979[m]: sorry, gotcha
<jason123onirc>
but the xfce repo has not been updated for months
<natris1979[m]>
no worries, I was misleading
<acheam>
jason123onirc: xfce has only had one update since 4.14, and from what I can tell, the build system hasn't changed incredibly
<natris1979[m]>
it's a little hard, because the script doesn't work, then the cleanup function tries to remove the chroot'd rootfs before it's unmounted and it gives a TON of noisy rm errors
<acheam>
comment out line 108 temporarily
<natris1979[m]>
but if I disable cleanup I can get something more meaningful...
<acheam>
line 108 enables cleanup
<jason123onirc>
Yeah xfce has not changed much but there could of been changes to some packages that makes it not build anymore
<acheam>
jason123onirc: no way to tell but trying it out
<acheam>
well, there is
<acheam>
but trying it out is probably easier
<jason123onirc>
I could try it out
<natris1979[m]>
looks like it's failing to build `baseinit`
<acheam>
logs pls
<natris1979[m]>
gotta run to dinner, will totally paste some logs later tonight or tomorrow .I knew I should have waited to ask about it :)
<jason123onirc>
xfce would be really good on kiss especialy that most of the cpu and ram usage will be taken up by xfce stuff so it will be very minimal xfce
<bujeddhazeus>
(Same almost as Dylan's except the dbus support stays)
<natris1979[m]>
that's great
<natris1979[m]>
but if you're using gentoo, why can't you just use the actual fix instead of the workaround?
<bujeddhazeus>
natris1979: there is no fix
<natris1979[m]>
? but it's closed as fixed
<bujeddhazeus>
Got to `ln -s /usr/lib/libwayland-client.so /usr/lib/firefox/libmozwayland.so` for now
<natris1979[m]>
sure
<bujeddhazeus>
natris1979: because the problem went away with llvm12... but now it's back
<natris1979[m]>
seems like that should just work
<bujeddhazeus>
Besides I built it with gcc
<natris1979[m]>
oh i see. Wasn't paying attention to the dates
<bujeddhazeus>
Ah
<natris1979[m]>
huh. seems I can chroot into kiss-live's rootfs and do everything the script was trying to do. I don't get why the script didn't work. Anyway. Off to bed
<bibliocar>
are there instructions to running sway started with seatd? I have a user, but they don't have permission to write into the /run directory I don't think. Unless I can change where wayland looks for the seatd socket?
<testuser[m]>
export XDG_RUNTIME_DIR
<testuser[m]>
=/path
<bibliocar>
oh
<konimex>
soliwilos: KISS don't use apk-tools so eh
<soliwilos>
konimex: Sure, but that's not their only reason, and mostly I thought it a little funny since they haven't been on openssl very long.
Guest11 has quit [Quit: Client closed]
jleightcap has quit [Ping timeout: 256 seconds]
jleightcap has joined #kisslinux
bibliocar has quit [Ping timeout: 256 seconds]
fwz has joined #kisslinux
<phoebos>
testuser[m]: pthread_cond_wait(3p) is the same manpage as pthread_cond_timedwait(3p)
<phoebos>
kiss owns $(man -w pthread_cond_wait)
<phoebos>
> man-pages
fwz has quit [Quit: fwz]
<testuser[m]>
phoebos: bruh
<testuser[m]>
pthread_cond_timedwait exists but man -w pthread_cond_wait says man: No entry for pthread_cond_wait in the manual.
<testuser[m]>
weird
<testuser[m]>
ur using mandoc right
<dilyn>
lmfao alpine is weird. "Our own tool has broken with this latest update that has been delayed for years. Instead of resolving this problem, we should revert all of the changes we made earlier this year"