💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2020-03-28.txt captured on 2024-05-12 at 16:08:51.
⬅️ Previous capture (2021-12-17)
-=-=-=-=-=-=-
2020-03-28T04:25:29 #kisslinux <icyphox> Weird, firefox-bin is crashing. 2020-03-28T04:26:00 #kisslinux <icyphox> https://termbin.com/ekxy 2020-03-28T04:27:40 #kisslinux <icyphox> Ah it's probably alsa. 2020-03-28T04:29:08 #kisslinux <icyphox> Indeed, it was. :D 2020-03-28T04:39:44 #kisslinux <adamantium[m]> mforney: About the patch, "Noted." (thanks) 2020-03-28T07:48:46 #kisslinux <dylanaraps> o/ 2020-03-28T07:51:32 #kisslinux <dylanaraps> kiedtl: 'contrib' is short for 'contribution'. ie, I thought that users would _contribute_ 'kiss-*' scripts. 2020-03-28T10:20:45 #kisslinux <dylanaraps> Python really doesn't want to be static 2020-03-28T10:46:56 #kisslinux <mahmudov> gst-plugins-good is runtime dep? 2020-03-28T10:51:00 #kisslinux <dylanaraps> I'd rather we didn't include gstreamer at all 2020-03-28T10:51:20 #kisslinux <lieuxnoir> o/ 2020-03-28T10:51:36 #kisslinux <dylanaraps> ello 2020-03-28T10:51:42 #kisslinux <lieuxnoir> dylanaraps: Quick ques 2020-03-28T10:51:46 #kisslinux <lieuxnoir> is $RANDOM posix? 2020-03-28T10:51:50 #kisslinux <dylanaraps> No 2020-03-28T10:52:20 #kisslinux <lieuxnoir> oh, how unfortunate lol 2020-03-28T10:52:56 #kisslinux <lieuxnoir> i'm trying to create a pure shell `shuf` 2020-03-28T10:54:56 #kisslinux <lieuxnoir> seems impossible though 2020-03-28T10:56:44 #kisslinux <dylanaraps> I can give you fake random 2020-03-28T11:00:09 #kisslinux <lieuxnoir> dylanaraps: Yes, please! 2020-03-28T11:01:52 #kisslinux <dylanaraps> set -f -- GLOB; shift $(($ * PPID % $#)); echo "$1" 2020-03-28T11:01:59 #kisslinux <dylanaraps> Oops 2020-03-28T11:02:04 #kisslinux <dylanaraps> Ignore the '-f' 2020-03-28T11:02:08 #kisslinux <dylanaraps> set -- GLOB; shift $(($ * PPID % $#)); echo "$1" 2020-03-28T11:03:55 #kisslinux <lieuxnoir> How do I use it? 2020-03-28T11:04:17 #kisslinux <dylanaraps> That is usage 2020-03-28T11:04:30 #kisslinux <dylanaraps> 1. Populate the argument list with your items. 2020-03-28T11:04:44 #kisslinux <dylanaraps> 2. Shift the list a pseudo random amount. 2020-03-28T11:04:54 #kisslinux <dylanaraps> 3. $1 now stores the random element. 2020-03-28T11:05:29 #kisslinux <lieuxnoir> It just prints `GLOB`. 2020-03-28T11:05:44 #kisslinux <dylanaraps> Well, yeah 2020-03-28T11:05:47 #kisslinux <dylanaraps> It's an example 2020-03-28T11:07:20 #kisslinux <lieuxnoir> Ohh 2020-03-28T11:09:03 #kisslinux <lieuxnoir> Not so random, though. But it'll do. Thanks. :D 2020-03-28T11:10:59 #kisslinux <dylanaraps> Yeah 2020-03-28T11:11:08 #kisslinux <dylanaraps> Was random enough for my use case 2020-03-28T11:40:23 #kisslinux <dylanaraps> I have static Python (lib still shared as planned) 2020-03-28T11:42:45 #kisslinux <dylanaraps> But 2020-03-28T11:53:23 #kisslinux <lova> hello 2020-03-28T11:54:16 #kisslinux <dylanaraps> hello 2020-03-28T11:55:00 #kisslinux <lova> how are you? 2020-03-28T11:56:47 #kisslinux <dylanaraps> I'm good 2020-03-28T11:57:38 #kisslinux <lova> fine than you! 2020-03-28T12:08:47 #kisslinux <ax> -.-' hahaha good morning 2020-03-28T12:17:52 #kisslinux <ax> dylanaraps: for bind excellent question! actually i was seeing that some call it bind regardless and other bind utils ... 2020-03-28T12:19:51 #kisslinux <dylanaraps> Repology expects it to be called 'bind' which is also what it's called upstream. 2020-03-28T12:20:55 #kisslinux <ax> maybe he's right and we should change the package name to bind ... how do I do in these cases? redo package and redo the pull request? 2020-03-28T12:21:22 #kisslinux <ax> yeh all correct comments! 2020-03-28T12:21:29 #kisslinux <dylanaraps> Just rename the directory 2020-03-28T12:25:34 #kisslinux <ax> ok! 2020-03-28T12:52:27 #kisslinux <dylanaraps> Reduced our imagemagick package to 6MB~ 2020-03-28T12:52:29 #kisslinux <dylanaraps> :D 2020-03-28T13:05:30 #kisslinux <k1ss> saw that dylanaraps? 2020-03-28T13:05:30 #kisslinux <k1ss> https://dev1galaxy.org/viewtopic.php?id=3331 2020-03-28T13:09:58 #kisslinux <dylanaraps> Yeah 2020-03-28T13:15:58 #kisslinux <ax> dylanaraps: it should be ok now 2020-03-28T13:22:05 #kisslinux <ax> question: my .cache / kiss has grown exponentially by build ... can i obviously remove it right?don't conflict with kiss command right? 2020-03-28T13:44:48 #kisslinux <dylanaraps> ax: You'll lose your cached package tarballs and cached sources 2020-03-28T13:44:58 #kisslinux <dylanaraps> But yes, it''s fine otherwise 2020-03-28T13:45:01 #kisslinux <dylanaraps> it's* 2020-03-28T15:14:37 #kisslinux <claudia02> Re Kiss on 32bit: ok nice, kiss on alpinei585 finally build gcc 2020-03-28T15:15:33 #kisslinux <claudia02> I had to modify the buildfile https://termbin.com/usvq 2020-03-28T15:17:43 #kisslinux <claudia02> There I removed from original gcc build : --enable-__cxa_atexit --enable-default-pie --enable-default-ssp . Is this worth further trying? 2020-03-28T15:24:43 #kisslinux <claudia02> I had success building this musl crosscompiler frome here https://github.com/richfelker/musl-cross-make. The settings which this gcc has, I adopted to te buildfile above. https://termbin.com/ws3et 2020-03-28T17:00:07 #kisslinux <ominous_anonymou> @ax i periodically remove my cached tarballs and sources to keep disk usage lower, and I haven't encountered any issues after doing so 2020-03-28T17:02:06 #kisslinux <dylanaraps> Yeah, it's 100% fine 2020-03-28T17:02:15 #kisslinux <dylanaraps> You start with an empty ~/.cache/kiss after all ;) 2020-03-28T17:03:27 #kisslinux <ominous_anonymou> The first time is still very stressful even knowing that XD 2020-03-28T17:49:54 #kisslinux <micro_O> o/ 2020-03-28T17:50:12 #kisslinux <micro_O> anyone know where json-c resides? trying to install sway 2020-03-28T18:02:12 #kisslinux <claudia02> micro_O: json-c is available through community 2020-03-28T18:06:31 #kisslinux <micro_O> hmm i thought i had community updated 2020-03-28T18:08:16 #kisslinux <micro_O> ahh, needed to add community/community to KISS_PATH, not the root directory of just `community` 2020-03-28T18:09:36 #kisslinux <dylanaraps> Yeah 2020-03-28T18:12:41 #kisslinux <micro_O> wonder if that should be changed or not 2020-03-28T18:12:54 #kisslinux <micro_O> i'll make a discussion on the issue tracker 2020-03-28T18:13:02 #kisslinux <dylanaraps> It won't be changed 2020-03-28T18:13:44 #kisslinux <dylanaraps> 1. It prevents a mess of directories in the root of the repository. 2. It allows for things like 'community-testing' to be added if needed in the future. 2020-03-28T18:14:02 #kisslinux <dylanaraps> 3. It's identical to how the official repositories in its layout. 2020-03-28T18:15:01 #kisslinux <dylanaraps> 4. It'd also be a breaking change for _everyone_ over dropping a simple misunderstanding. 2020-03-28T18:15:39 #kisslinux <dylanaraps> Documentation could be improved instead. 2020-03-28T18:16:02 #kisslinux <dylanaraps> iirc, the only place the instructions live is in the install guide (towards the end). 2020-03-28T18:17:45 #kisslinux <micro_O> well another alternative to the misundertanding would be to have the other repos follow the same layout 2020-03-28T18:18:24 #kisslinux <dylanaraps> I'd need four separate git repositories to do that. 2020-03-28T18:18:46 #kisslinux <dylanaraps> With the number growing for any repositories added in the future. 2020-03-28T18:19:31 #kisslinux <micro_O> I mean, to have kiss-games and mywayland put their stuf fin subdirectories 2020-03-28T18:19:47 #kisslinux <dylanaraps> Ah 2020-03-28T18:19:53 #kisslinux <dylanaraps> Right 2020-03-28T18:26:15 #kisslinux <micro_O> https://github.com/sdsddsd1/mywayland/issues/1 and https://github.com/sdsddsd1/kiss-games/issues/15 2020-03-28T18:32:14 #kisslinux <rirc1AF30> micro_O: I am the maintainer of kiss-games and mywayland 2020-03-28T18:32:37 #kisslinux <micro_O> hi claudia02 2020-03-28T18:32:59 #kisslinux <micro_O> i figure the order of operations would be: make a PR for k1ss documentation to mention repository layout somewhere 2020-03-28T18:33:27 #kisslinux <claudia02> for mywayland it think its fine in a user repository because kiss explicily excludes wayland 2020-03-28T18:33:28 #kisslinux <micro_O> then the rest... the tricky part would be making it not a surprise for maintainers 2020-03-28T18:33:45 #kisslinux <micro_O> i mean not a surprise for users 2020-03-28T18:34:06 #kisslinux <claudia02> and for games I just see it as a nice adition and nothing really needed for the kiss base or its extension 2020-03-28T18:34:18 #kisslinux <micro_O> claudia02 - I am not sure I follow 2020-03-28T18:34:39 #kisslinux <micro_O> I don't think kiss games or mywayland should be in a subdirectory of the main or community kiss repos 2020-03-28T18:34:50 #kisslinux <micro_O> what i'm asking is that the packages themselves be in a subdirectory of the repository 2020-03-28T18:35:31 #kisslinux <micro_O> so KISS_ENV=$KISS_ENV:/path/to/mywayland.git/wayland , instead of :/path/to/mywayland.git 2020-03-28T18:37:27 #kisslinux <claudia02> I am not sure I follow 2020-03-28T18:37:43 #kisslinux <claudia02> I just depends where you clone the repo 2020-03-28T18:37:54 #kisslinux <micro_O> I can make a PR for what I want, that might make more sense. Do you not understand what I am asking or why I am asking for it? 2020-03-28T18:38:17 #kisslinux <claudia02> Iam not sure what you asking and that leads to why 2020-03-28T18:38:20 #kisslinux <claudia02> (: 2020-03-28T18:38:46 #kisslinux <claudia02> e.g I cloned community in /var/db/kiss/repo/community/community for tidyness 2020-03-28T18:40:21 #kisslinux <claudia02> ah 2020-03-28T18:40:24 #kisslinux <claudia02> now in undeerstand 2020-03-28T18:41:12 #kisslinux <claudia02> you want something like sdsddsd/wayland/mywayland in my repo? 2020-03-28T18:41:50 #kisslinux <micro_O> something like that 2020-03-28T18:42:26 #kisslinux <micro_O> mywayland/wayland, or mywayland/core or mywayland/stable 2020-03-28T18:42:38 #kisslinux <micro_O> they dont have to have semantic meaning, in fact i'd prefer they didn't 2020-03-28T18:42:48 #kisslinux <micro_O> unless dylanaraps weighed in there 2020-03-28T18:47:49 #kisslinux <claudia02> Maybe there should just be some documentation that a repository in kiss path has to point to the directory where the actual packages are and not its upper direcotory or so 2020-03-28T18:48:29 #kisslinux <micro_O> @claudia02 I think that should definitely be part of the docs 2020-03-28T18:49:06 #kisslinux <claudia02> I will cloes the issues 2020-03-28T18:49:21 #kisslinux <micro_O> claudia02 - how do you feel about https://github.com/sdsddsd1/kiss-games/pull/16 2020-03-28T18:49:26 #kisslinux <micro_O> thats an example of what I mean 2020-03-28T18:49:57 #kisslinux <micro_O> I still think it would be more consistent / less of a surprise, and have the benefits dylanaraps mentioned in the original issue 2020-03-28T18:53:24 #kisslinux <micro_O> I've also shared my current setup which might help understand my context 2020-03-28T18:53:26 #kisslinux <micro_O> https://github.com/sdsddsd1/kiss-games/pull/16#issuecomment-605503508 2020-03-28T18:53:41 #kisslinux <micro_O> I don't like to clone git repos within other git repos unless they are formally setup as submodules 2020-03-28T18:53:53 #kisslinux <micro_O> since then you have to do your own .gitignore dance 2020-03-28T19:03:14 #kisslinux <claudia02> micro_O: I get your point with consistency. But this are personal repos and I think when you understand KISS_PATH its not a big deal. I leave it open and think of it. But I am more on leave it as is 2020-03-28T19:52:59 #kisslinux <ax> ominous_anonymou and dylanaraps : yes, i delete it , thank you 2020-03-28T19:54:30 #kisslinux <ax> dylanaraps: --sbindir=/usr/bin should it always be added? 2020-03-28T19:54:48 #kisslinux <ax> even if the source automatically considers it? 2020-03-28T20:27:18 #kisslinux <ax> dylanaraps: problem ... http://linuxbrit.co.uk/downloads/giblib-1.2.4.tar.gz not work, it's official links 2020-03-28T20:29:53 #kisslinux <ax> http://freshmeat.sourceforge.net/projects/giblib/ 2020-03-28T20:31:31 #kisslinux <ax> in this case ? add source.tar.gz in package dir ? 2020-03-28T20:32:40 #kisslinux <ax> or i can add it in my github page and add it in source 2020-03-28T20:45:47 #kisslinux <ax> ok i linked it in my github page ... https://github.com/aicsx/kiss-repo/blob/master/giblib/giblib-1.2.4.tar.gz 2020-03-28T22:56:53 #kisslinux <claudia02> mmcar: you were interested in porting kiss to 32 bit? have you allready looked into it? 2020-03-28T22:58:32 #kisslinux <jedavies> How's it going with the 32-bit port claudia02? 2020-03-28T23:00:11 #kisslinux <claudia02> I am having a hard time (: 2020-03-28T23:00:38 #kisslinux <claudia02> building gcc and busybox makes problem 2020-03-28T23:01:18 #kisslinux <claudia02> for curl and gzip I had to remove the static flags to compile 2020-03-28T23:02:32 #kisslinux <claudia02> you can read in logs today how I compiled gcc. I have a complete chroot but this gcc does not work in the chroot 2020-03-28T23:03:44 #kisslinux <claudia02> there are many variables not working till now which make it not very promising for me :2020-03-28T23:04:40 #kisslinux <jedavies> GCC binary is linking to something that doesn't exist in the KISS chroot? 2020-03-28T23:05:39 #kisslinux <claudia02> I stripped some -enable options from gcc to get it compile 2020-03-28T23:05:51 #kisslinux <jedavies> When you say "gcc does not work in the chroot"? 2020-03-28T23:06:16 #kisslinux <claudia02> now when I build in chroot it says: configure error C compiler cannot create executables 2020-03-28T23:06:26 #kisslinux <claudia02> I guess I stripped to much :D 2020-03-28T23:06:59 #kisslinux <jedavies> What happens when you run /usr/bin/gcc in the chroot? Does it run OK? 2020-03-28T23:07:35 #kisslinux <claudia02> yeah it returns on gcc -v 2020-03-28T23:08:12 #kisslinux <claudia02> I get the output. mom 2020-03-28T23:08:13 #kisslinux <jedavies> any odd CFLAGS when you run env in the chroot? 2020-03-28T23:09:23 #kisslinux <claudia02> https://termbin.com/1tjp 2020-03-28T23:09:43 #kisslinux <claudia02> yes 2020-03-28T23:09:56 #kisslinux <claudia02> its march=x86-64 2020-03-28T23:10:28 #kisslinux <claudia02> ok that i can change 2020-03-28T23:11:03 #kisslinux <jedavies> Yup removing those should help 2020-03-28T23:11:28 #kisslinux <claudia02> just remove or setting something for 32bit? 2020-03-28T23:12:30 #kisslinux <jedavies> You could unset those vars and try again, see if that works. Or if you have some preferred flags for your arch... 2020-03-28T23:17:53 #kisslinux <claudia02> no still no succes 2020-03-28T23:18:47 #kisslinux <claudia02> "checking whether the C compiler work..no" 2020-03-28T23:19:12 #kisslinux <jedavies> You see a message like "...see config.log for details"? 2020-03-28T23:20:51 #kisslinux <claudia02> https://termbin.com/fqhr 2020-03-28T23:21:03 #kisslinux <claudia02> yes 2020-03-28T23:21:29 #kisslinux <jedavies> Try building it inside the chroot, but not using the KISS package system. After the ./configure step fails, you can then look at the config.log file to see more info about the failure. 2020-03-28T23:22:26 #kisslinux <jedavies> I.e. just untar the source for xz into some directory in the chroot and try building there 2020-03-28T23:23:34 #kisslinux <claudia02> alright 2020-03-28T23:25:55 #kisslinux <claudia02> okkk there fails a lot 2020-03-28T23:27:17 #kisslinux <claudia02> much stuff with error relocating 2020-03-28T23:27:34 #kisslinux <claudia02> for gcc 2020-03-28T23:29:05 #kisslinux <claudia02> https://termbin.com/eckx 2020-03-28T23:30:07 #kisslinux <claudia02> My next try would be to add option after option to the gcc build and see if I can make progress 2020-03-28T23:43:43 #kisslinux <claudia02> maybe it can be my crappy old computer? I would try soon i586 Alpine host setup on a 64 bit machine and see 2020-03-28T23:46:52 #kisslinux <jedavies> Looks like GCC is linked to an isl lib which doesn't exist in the chroot. 2020-03-28T23:47:43 #kisslinux <jedavies> Possible to prevent GCC from linking to that when building?