phoebos changed the topic of #kisslinux to: Unofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://yewtu.be/watch?v=S81bNIK4MaE
angerisagift has quit [Ping timeout: 252 seconds]
op_4 has quit [Remote host closed the connection]
op_4 has joined #kisslinux
chungstoin has quit [Quit: Konversation terminated!]
chungstoin has joined #kisslinux
<chungstoin> why do I get the error /boot/grub/i386-pc/normal.mod not found?
<sad_plan> probably because its missing?
<kris_> for anyone here who actively uses codeberg: what are their file size limits
<kris_> sad_plan the github host plan has failed, some of my packages are >100MB so i can't store them on a repo
<kris_> i don't see anything related to individual files on codebergs website so
<kris_> i'm assuming there isn't a per file limit but rather an overall repository imposed limit of 750MiB, which is the only actual number i can find
<sad_plan> kris_: sewn might know the limit
<sewn> hallo
<sad_plan> hm, can you push them as a release though?
<kris_> i believe for the pages thing to work for me to do this, they have to just be uploaded to the repo raw
<sewn> what are you hosting kris
<sad_plan> that sounds rather small actually
<kris_> i may or may not be using github pages / codeberg pages as an xbps repo
<kris_> or trying to anyway lol, github said no with one of my packages because it's too large
<sad_plan> I mean, linux is way bigger. linux-firmware is bigger, linux is bigger. although not on codeberg though
<kris_> like i got this working just with smaller packages
<kris_> yeah but i figure these aren't >=100MB blobs just straight up in the source tree
<sad_plan> well, no
<sewn> kris
<kris_> ...im kinda mindblown that mullvads vpn client is >100MB even when compressed with zstd
<sewn> why are you hosting that in pages meant for websites
<sewn> use S3 storage
<kris_> it's just the perfect amount of incredibly stupid
<sad_plan> damn, wouldve figured a damn vpn client wouldnt be so damn big
<chungstoin> idk how to install it though I built and installed grub
<sewn> just use efibootmgr
<sewn> stop being in the past
<kris_> sewn it legitimately works as long as i don't need to like
<sewn> ya ya ik
<kris_> limit what i can upload on a per file basis
<sad_plan> chungstoin: check arch wiki, or gentoo wiki. or as sewn said, even better, use efistub. buut im guessing hes using bios?
<kris_> the alternative is to just host an actual fileserver on my existing vps
<sewn> then syslinux or limine
<kris_> but i like my solution more, it's moderately funny
<sewn> kris_: hm
<sewn> why can't you just upload packages to needed machines
<kris_> because i have over 20 void installs
<sad_plan> he wants to abuse githubs action instead
<kris_> and id like to just have a repo for my stuff at this point
<sewn> why do you have 20 void installs
<kris_> don't judge me, it's an addiction
<kris_> :p
<sewn> so, 20 machines..?
<kris_> nah, split between VMs/containers/hardware
* sewn judges
<sad_plan> it shouldve been 20 kiss installs instead
<kris_> i guess ill just try the same thing w codeberg
<kris_> i just feel bad because i legitimately respect codeberg and dont want to waste their storage
<sewn> don't touch codeberg
* kris_ touches codeberg
<sewn> its going to be too slow for your needs
<kris_> it was actually fine, thats what i tested this with
<kris_> i was pulling 11MB/s down
<sewn> okei dan
<sad_plan> 11M is fine by me imo. ill rather cry if its less than 1M instead
<sad_plan> others cry if its less than 200M. I suppose we live in different times :p
<kris_> yeah its more than plenty, nothing i'm serving is too large
<kris_> primarily mullvad/jellyfin/my musl build
<sad_plan> in any case, you mightve missed it, or ignored it, or I missed your reply, what about setting packages as releases instead?
<sad_plan> iirc, dilyn did this for some packages he wanted to ignore autotools for
<kris_> because it needs to be served as part of github pages
<kris_> for this to be as smooth as possible
<kris_> that is, unless i'm missing osmething
<sad_plan> if its works, it works. its still more convinient than building everything manually
<kris_> the most obvious solution is to just create an entry in my vps' caddy config to just >serve files
<kris_> and be done with it
<sad_plan> probably
<kris_> the issue is that hetzner has *constant* outages in my experience and i don't like that for something i'm hosting something important (like my musl build) on
<sad_plan> but were not here because we like convineiences like fedora :p
<kris_> and i don't love the idea of hetzner in general really
<kris_> i *can't tell you who told me this* but they'll comply with law enforcement even without a warrant
<sad_plan> I get that. a vps should have an uptime of 99.99999999999999999% or soemthing like that :p
<sad_plan> wierd
<sad_plan> >cant comply if its encrypted though
<kris_> RAM dumps are generally enough to get further
<kris_> which they've already got stuff set up to do that with their VMs
<sad_plan> ram can also be encrypted
<kris_> again, can't tell you who told me that
<kris_> i wonder how slow that is
<sad_plan> its irrelevant to me who said it :p
<sad_plan> I dont think its that bad. iirc, grapheneOS is working on something in that direction. dont take my word for it though
<kris_> shrug
<sad_plan> veracrypt seems to have some solution for this
<kris_> idk for now it's time for me to chill out for the night and play some games
<kris_> i cant believe ive blown an entire day on turning github into an xbps repo
<kris_> like legit the whole day
<sad_plan> im not supprised. ive blown days on something really trivial numerous times :p
<kris_> another part of this is deciding how i want to have these packages build
<kris_> at the moment i have a VM on my machine (make that +1 void installs) to compile everything and dump the packages out onto my host
<kris_> which probably isnt necessary because xbps-src already builds everything in a container and outright doesnt support doing anything else
<sad_plan> use the least headachy way
<kris_> id like to automate it
<sad_plan> I wasnt saying you cant :P
<kris_> but i'm serving so few packages at the moment that there's not really a point in automating builds so ill get to that at some point
<kris_> nah that was leading back into github actions
<kris_> you can totally have github actions build your packages automatically and spit out packages
<sad_plan> i know
<sad_plan> ffs, why doesnt mk achnowledge my ldflags
<kris_> its mad at you
<sad_plan> probably. it seems to find CFLAGS correctly, but not LDFLAGS for some reason. wierd
<sad_plan> in any case. time for bed
<sad_plan> night
<kris_> gn
ulterno has joined #kisslinux
<kris_> codeberg unfortunately also has a per file limit of 100m
chungstoin has quit [Remote host closed the connection]
ulterno has quit [Changing host]
ulterno has joined #kisslinux
angerisagift has joined #kisslinux
fultilt has quit [Quit: Leaving]
zlg has joined #kisslinux
<sewn> guh
angerisagift has quit [Ping timeout: 252 seconds]
angerisagift has joined #kisslinux
zlg has quit [Ping timeout: 252 seconds]
<sad_plan> kris_: can you use some other compression to forse sizes down though? to make sure you pass the limit
<sad_plan> xz -9 is usually good, but its not always good enough :')
<sewn> its already compressed
<sad_plan> compress more
<ulterno> Use lossy compression
<ulterno> Don't worry, the receiver can use the `hollywood::enhance()` function.
angerisagift has quit [Ping timeout: 245 seconds]
angerisagift has joined #kisslinux
<riteo> ok I figured out what to do with the lil' thing
<riteo> it's indeed PERFECT for connecting to the outside
<riteo> it turns on automatically once it gets power, this means that it's blackout safe
<riteo> as in, I can go outside and if the thing dies because of an outage it's fine because it will turn back on by itself
<riteo> still I'd like to get my boscaiolo auto-turning-on eventually though
fultilt has joined #kisslinux
<kris_> sad_plan i could experiment with other compression styles yeah but this is already with zstd
<sad_plan> xz has better compression, but is terribly slow. im not sure how much you can gain here though.
farkuhar has quit [Quit: leaving]
chungstoin has joined #kisslinux
<chungstoin> could someone help me? after configuring my kernel, I can't get make to work, it gives me this https://pastebin.com/8VYazUt3
<sad_plan> lz4c is missing. either install lz4, or choose another compression algorithm
<sad_plan> gz is a good middleground
<kris_> a
gtms has joined #kisslinux
<chungstoin> yeah that got it working, thanks
<chungstoin> I'm into a new issue though
<chungstoin> grub-mkconfig -o /boot/grub/grub.cfg only makes firmware settings for uefi for some reason
<chungstoin> and my system is BIOS
<chungstoin> this results in a boot loop
<chungstoin> or something else is causing it I'm unsure
<sad_plan> both arch wiki and gentoo wiki are also great places for looking up things. offical kiss site, which is the one linked above, is a good source, so is kisscommunity.org, which is the community made wiki page, which has some info not listed in offical documentation
<sad_plan> kris_: aaaaaaaaaaaaa
<kris_> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa