<phinxy>
Installing a python module from source code does make the module listed under `pip list`.. Could anything get borked if it was uninstalled from pip instead of kiss?
<phinxy>
I mean, obviously nothing happens.. but..
faensage has joined #kisslinux
faensage has quit [Quit: Leaving]
Guest30 has joined #kisslinux
<Guest30>
Hello
<Guest30>
I have an error on boot. "starting version 250.3-1-arch" "fsck:error 2 (no such file or directory) while executing fsck.ext4 for /dev/sda3" "ERROR: fsck failed on '/dev/sda3'" "mount: /new_root: unknown filesystem type 'ext4'." "You are now being dropped into an emergency shell." "sh: can't access tty; job control turned off"
<Guest30>
I have e2fsprogs installed, so I don't know why it cant do the fsck
<noocsharp>
acheam: i think dilyn's just trying to learn go
<jason123onirc>
Has anyone here used glasnost linux? I want to use it to comple packages on my one pc abd send it over to my not powerful pc to install kiss
<jason123onirc>
When I try and do a glasnost install in a vm packages fail to install because of some ssl error
<testuser[m]>
Show
<jason123onirc>
show the error?
<testuser[m]>
Yeah
<jason123onirc>
curl: (60) SSL certificate problem: unable to get local issuer certificate
<testuser[m]>
Run /etc/ssl/update-cert*.sh
<testuser[m]>
That script will update ur certs
<testuser[m]>
Else u can manually download them and disable tls verification temporarily
<jason123onirc>
still gives me the same error
<jason123onirc>
should I update ssl in the chroot or out of the chroot
<jedavies>
Hey jason123onirc, you should do this inside the chroot
<jason123onirc>
yeah i am doing it in the chroot just making sure
<jason123onirc>
I did get a kiss linux install before but now I am trying glasnost to send packages to the less powerful pc I have
<jedavies>
You using an arm device?
<jason123onirc>
x86_64 to x86_64
<jason123onirc>
but I first need to install glasnost in a vm to compile the packages
<jason123onirc>
unless there is a different way to do it
<jedavies>
Shouldn't need to use a vm, would be slow to compile packages.
<jedavies>
You can just extract the x86_64 tarball on the build machine and on the client
<jason123onirc>
so I don't need to have glasnost installed to build packages?
<jason123onirc>
Do I just mount the chroot and then use kiss-chroot to go into it?
<jason123onirc>
oh I got it now
<jason123onirc>
same error when I chroot from my host pc
<jedavies>
OK, will look into it. For now as suggested you can temporarily disable tls verification
<jedavies>
In /etc/ssl/update-certdata.sh, add a "-k" argument to curl
bibliocar has joined #kisslinux
<bibliocar>
hi hi hi
<bibliocar>
Yeah, I had the same problem, i think I just copied all the ssl certificates over from my host machine, which is definately not the correct way to do things.
<bibliocar>
It's a problem because you need the certificates in order to update the certificates, I think...
<bibliocar>
I really need to go in and do a write up, but it's one of about five different things I need to do.
<bibliocar>
also have a problem with netsurf-vi updating, but I'm not even sure which repo it's from... I should probably get around to that, I'm just trying to polish up a pull rekwest with someone else first.
<bibliocar>
oh, -k, okay.
<jason123onirc>
yeah a guide on how to use glasnost and compile stuff from it would be cool
<jedavies>
There is some basic info on the repo page in github. Let me know if you have more specific questions, I can add more
<jedavies>
bibliocar: what's up with netsurf-vi?
barpthewire has joined #kisslinux
<jason123onirc>
jedavies: I downloaded the tarball inside the install and extracted it and when I run KISS_ROOT=glasnost-linux kiss b neofetch it gives me an error about the package not being found
<jason123onirc>
or any package really
<jason123onirc>
nevermind just any package fails to build
<jason123onirc>
and when i run a kiss u it tells me ERROR '*' not found
<jedavies>
Did you set KISS_PATH ?
<jason123onirc>
yes I did set kiss path
<jason123onirc>
do I need to set kiss path in the tarball?
m3g has quit [Read error: Connection reset by peer]
litharge has quit [*.net *.split]
<jedavies>
You need to set KISS_PATH to build packages, or cd to the package directory and run "kiss b" there. Also neofetch is in the community repo, but pfetch is available in the main repo
bibliocar_ has joined #kisslinux
bibliocar has quit [Read error: Connection reset by peer]
<jason123onirc>
do I need to set kiss_root or just run kiss from glassnost? Since I am using x86_64 to x86_64 I might be able to just build right from the chroot
<jason123onirc>
oh yeah when I build a package it gives me an error about /dev/tty not being found
m3g has joined #kisslinux
litharge has joined #kisslinux
<jedavies>
I think you don't need a KISS_ROOT in your case. Built packages should be in ~/.cache/kiss/bin/local
<jason123onirc>
ok that makes sense
<jason123onirc>
but it gives me an error about /dev/tty not being found
<jedavies>
Can you post the full error?
<jason123onirc>
oh I figured it out
<jason123onirc>
chroot is annoying
<jason123onirc>
now its saying unknown user 1000
<jason123onirc>
a guide on how to setup a chroot to compile packages would be nice
<jason123onirc>
the full error is
<jason123onirc>
Using /usr/bin/su (to become 1000) su: unknown user 1000
<bibliocar_>
My solution was just to chown everything to root. I'm pretty sure what I do would make most people cringe... I made one person even go "nooooo"
<bibliocar_>
ah, you are an unknown user
<bibliocar_>
I'm the newb
<jason123onirc>
oh yeah that did work
<jason123onirc>
i mean
<jason123onirc>
as long as it works and builds the package
<bibliocar_>
I intend to go back and do everything correctly... eventually. I'm just a bit overloaded at the moment.
<jason123onirc>
There needs to be a guide on how to setup a chroot to build packages
<jason123onirc>
right now the github page just lists generic steps and leaves the user to doing most of the work on setting up the envirement to build the packages
<jason123onirc>
even though its not as easy as chrooting into the tarball
<bibliocar_>
Well, maybe it's not supposed to be easy, and little problems will continue to crop up. I don't know, not really my place to say. I'm just new here.
<bibliocar_>
Personally, I agree with you.
m3g has quit [Remote host closed the connection]
<bibliocar_>
I need to poke at the kernel config this guy was having trouble with, but it takes forever for my computer to build anything.
mahmutov_ has quit [Ping timeout: 240 seconds]
mahmutov_ has joined #kisslinux
jason123onirc has quit [Quit: leaving]
Jason123santaOnI has joined #kisslinux
mahmutov_ has quit [Ping timeout: 256 seconds]
humky_ has joined #kisslinux
humky has quit [Ping timeout: 268 seconds]
bibliocar_ has quit [Ping timeout: 240 seconds]
<Jason123santaOnI>
Is there a way to now compile the kernel on the build machine? Looks like there is only a kernel build for the pinephone. I want to make glasnost on the target machine just like a regular kiss install and not just be in a chroot
humky__ has joined #kisslinux
humky_ has quit [Ping timeout: 240 seconds]
humky_ has joined #kisslinux
humky__ has quit [Ping timeout: 240 seconds]
humky__ has joined #kisslinux
humky_ has quit [Ping timeout: 250 seconds]
humky__ has quit [Remote host closed the connection]
<dilyn>
testuser[m]: I agree with noocsharp on that front; 'crazy' is also a loaded term. mental health is important :v
<dilyn>
acheam: llvm is permissive *enough* xD
<dilyn>
jason123onirc: you should extract chroot tarballs as root so that the permissions are proper; if you extract as your user every file will have your user as the owner/group, which is not what you want (your user doesn't exist in that chroot, and this is the problem you're encountering)
<dilyn>
I always keep a copy of kiss-chroot around so that I can quickly have a chroot setup in the proper ways (for instance, you perhaps didn't bind mount /dev which is why /dev/tty could not be found...)
<Jason123santaOnI>
kiss-chroot does not work in this instance because the tarball is not mounted
<Jason123santaOnI>
though I got it all working now I just need to figure out how to get it installed on the other pc now