gemini - kennedy.gemi.dev

💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › kisslinux-2021-09-10.txt captured on 2023-01-29 at 03:53:33.
-=-=-=-=-=-=-
[2021-09-10T00:26:18Z] <dilyn> anybody else having a problem installing binaries as setuid with kiss? just had an issue reinstalling opendoas
[2021-09-10T00:29:20Z] <dilyn> oh, curious...?? 
[2021-09-10T01:08:08Z] <noocsharp> i recently packaged a setuid program and it was fine
[2021-09-10T01:15:40Z] <dilyn> the opendoas package doesn't seem to make itself setuid
[2021-09-10T01:16:16Z] <noocsharp> -rwsr-xr-x    1 root     root        112072 Sep  9 20:13 /usr/bin/doas
[2021-09-10T01:25:00Z] <dilyn> orly...
[2021-09-10T01:25:11Z] <dilyn> then this is a me problem. hmhmhm
[2021-09-10T02:28:18Z] <konimex> dilyn: unfortunately that tic part of yours don't work in my build
[2021-09-10T02:36:51Z] <konimex> ...and now my rebuilt netbsd-curses is broken
[2021-09-10T03:01:05Z] <noocsharp> https://github.com/kiss-community/community/pull/675/files
[2021-09-10T03:01:09Z] <noocsharp> this looks awfully familiar...
[2021-09-10T03:02:59Z] <acheam> just some casual MIT license violations, nothing to see here
[2021-09-10T03:03:35Z] <acheam> oof and phoebos found an issue in it
[2021-09-10T03:03:35Z] <noocsharp> lol, my repo doesn't even have a license
[2021-09-10T03:03:46Z] <acheam> then its just some causal IP violations
[2021-09-10T03:03:58Z] <noocsharp> maybe i should add one to screw with people
[2021-09-10T03:04:27Z] <acheam> $ cat LICENSE
[2021-09-10T03:04:45Z] <noocsharp> nah, i meant that the packaging was pulled straight from my personal repo
[2021-09-10T03:05:00Z] <acheam> > by using this software, the user forfeits the right to their PC to nihal jere
[2021-09-10T03:05:08Z] <acheam> noocsharp: ik, you interupted my really bad joke
[2021-09-10T03:06:08Z] <noocsharp> i wonder if a court would enforce that
[2021-09-10T03:06:47Z] <acheam> probably not
[2021-09-10T03:07:24Z] <acheam> its unlikely, but at least somewhat possible that they could have written that themselves, and it just happened to be the same as yours
[2021-09-10T03:07:31Z] <acheam> given that its a fairly straightforward build file
[2021-09-10T03:08:05Z] <acheam> or the court might just not see it as property after explaining for 20 minutes what a build file actually is
[2021-09-10T03:08:25Z] <acheam> but I Am Not A Lawyer(tm)
[2021-09-10T03:08:31Z] <noocsharp> but only i'm stupid enough to pull raw source files straight from cgit
[2021-09-10T03:08:46Z] <noocsharp> instead of downloading the tarball or using git
[2021-09-10T03:09:16Z] <noocsharp> i would have added it to community, but i thought it was a stupid hack to package it
[2021-09-10T03:11:50Z] <acheam> yeah why did you do that?
[2021-09-10T03:12:03Z] <acheam> oh because its in a big repo?
[2021-09-10T03:14:19Z] <noocsharp> yeah, and it hasn't been updated in several years
[2021-09-10T03:14:40Z] <noocsharp> actually, i could have just copied the files into a files subdirectory... thats what i did with bsdfmt
[2021-09-10T03:29:15Z] <noocsharp> TIL you can control monitor settings from your computer
[2021-09-10T03:29:22Z] <noocsharp> https://www.ddcutil.com/
[2021-09-10T03:34:48Z] <testuser[m]> Hi
[2021-09-10T03:40:49Z] <noocsharp> hello
[2021-09-10T03:41:45Z] <rio6> i2c over hdmi? vga?
[2021-09-10T03:45:09Z] <noocsharp> indeed
[2021-09-10T04:26:02Z] <dilyn> noocsharp: wdym? 
[2021-09-10T04:46:23Z] <dilyn> konimex: interesante. how doesn't it work? 
[2021-09-10T04:46:30Z] <dilyn> I know it was finicky but I've forgotten
[2021-09-10T04:47:09Z] <dilyn> a lot of my builds are seemingly broken; for instance, freetype's pkgconfig file reports the wrong version! lmao 
[2021-09-10T05:00:14Z] <testuser[m]> Can someone on a regular kiss system build automake
[2021-09-10T05:06:59Z] <konimex> dilyn: netbsd-curses still fails to find foot terminfo from my end
[2021-09-10T05:07:19Z] <konimex> and when I rebuilt netbsd-curses suddenly TERM=linux no longer works so there's that
[2021-09-10T05:07:29Z] <dilyn> hhhmmmmm
[2021-09-10T05:07:50Z] <dilyn> I *think* i had this same problem, at some point when I was doing stuff a couple weeks ago...
[2021-09-10T05:11:26Z] <dilyn> i haven't checked in any of my env stuff in a long while so if I WERE using a TERM variable I don't recall it :X  
[2021-09-10T05:17:45Z] <dilyn> testuser: nop; help2man complaint? 
[2021-09-10T05:18:11Z] <testuser[m]> yeah
[2021-09-10T05:18:14Z] <testuser[m]> it works fine for me but no one else
[2021-09-10T05:18:44Z] <dilyn> :thinking:
[2021-09-10T05:19:03Z] <dilyn> this is just some vanilla kiss chroot i keep around so you must've done something special? 
[2021-09-10T05:19:18Z] <testuser[m]> no i tried on my default chroot too
[2021-09-10T05:19:33Z] <testuser[m]> i guess its sorta out of date but all related packages to automake should be up to date
[2021-09-10T05:19:36Z] <testuser[m]> ill try with  a new one
[2021-09-10T05:21:22Z] <dilyn> lmfao 
[2021-09-10T05:21:37Z] <dilyn> open up the ChangeLog for automake and peep that update from 2012-04-12
[2021-09-10T05:21:48Z] <dilyn> might be a regression of some kind
[2021-09-10T05:22:07Z] <testuser[m]> 2012 ?
[2021-09-10T05:22:12Z] <dilyn> yeah
[2021-09-10T05:22:30Z] <dilyn> just checked with -j1/2/3/4, it doesn't seem to be
[2021-09-10T05:24:13Z] <testuser[m]> but it's been building fine since 1 year
[2021-09-10T05:24:18Z] <testuser[m]> https://github.com/kisslinux/repo/blob/6dfff99f4cbb79b3ec378a2e501452c01c4127ed/core/grub/files/help2man i guess i could try this
[2021-09-10T05:25:24Z] <dilyn> that would be suitable probably considering the problematic file is doc/help2man
[2021-09-10T05:28:06Z] <dilyn> tried it, then it complains about 'cannot get --help' from aclocal
[2021-09-10T05:28:07Z] <dilyn> hmhm
[2021-09-10T05:28:31Z] <testuser[m]> i forgor 💀
[2021-09-10T05:28:33Z] <testuser[m]> the issue is that
[2021-09-10T05:28:36Z] <testuser[m]> automake doesnt work
[2021-09-10T05:28:50Z] <testuser[m]> complains about some signal stuff
[2021-09-10T05:28:58Z] <testuser[m]> 1 sec
[2021-09-10T05:29:12Z] <dilyn> mfw
[2021-09-10T05:29:50Z] <testuser[m]> https://libera.irclog.whitequark.org/kisslinux/2021-09-04#30790284;
[2021-09-10T05:32:29Z] <dilyn> https://libera.irclog.whitequark.org/kisslinux/2021-09-04#30790404; they get it
[2021-09-10T05:32:54Z] <dilyn> guess i'll check on wyverkiss as well just for sanity 
[2021-09-10T05:34:25Z] <dilyn> love having to build three packages just to build a single package that allows me to *checks notes* insanely build packages
[2021-09-10T05:35:08Z] <dilyn> uuuhhh
[2021-09-10T05:35:11Z] <dilyn> automake builds fine for me 
[2021-09-10T05:35:16Z] <dilyn> on wyverkiss 
[2021-09-10T05:35:19Z] <dilyn> kekw :V :V :V 
[2021-09-10T05:35:57Z] <testuser[m]> rebuild perl
[2021-09-10T05:35:58Z] <testuser[m]> then it wont
[2021-09-10T05:36:21Z] <testuser[m]> so perl broke somehow due to external factors
[2021-09-10T05:37:14Z] <testuser[m]> my working binary was built on july 11
[2021-09-10T05:37:15Z] <dilyn> oh god if this perl reinstall breaks this chromium build smh
[2021-09-10T05:38:02Z] <dilyn> i'll install it in a safe place :V
[2021-09-10T05:39:14Z] <testuser[m]> maybe its gcc 11 ? it was updated on july 28
[2021-09-10T05:39:54Z] <testuser[m]> i guess we could just patch automake to not register handlers for SIGHUP but idk what that would break
[2021-09-10T05:40:08Z] <dilyn> yeah rebuilt perl and it's fine
[2021-09-10T05:40:25Z] <dilyn> so...
[2021-09-10T05:40:31Z] <testuser[m]> but galaxynova on wyverkiss couldnt build it so it cant be a gcc issue either
[2021-09-10T05:40:32Z] <dilyn> i have no idea what the common denominator might be here
[2021-09-10T05:41:01Z] <dilyn> maybe automake is trying super hard to get gpl software on my machine so it's bending the rules of reality to function properly 
[2021-09-10T05:43:50Z] <testuser[m]> ok so all signal handling is broken
[2021-09-10T08:37:49Z] <x4n> Hello there!
[2021-09-10T08:38:10Z] <x4n> I'm having a problem which may or may not have to do something with KISS Linux but with the wayland adoption.
[2021-09-10T08:38:29Z] <testuser[m]> What is it
[2021-09-10T08:38:45Z] <x4n> When running command "wal -i wall/wall0.jpg", I get error "FileNotFoundError: [Errno 2] No such file or directory"
[2021-09-10T08:38:56Z] <x4n> When running command "wal -i wall/wall0.jpg", I get error "FileNotFoundError: [Errno 2] No such file or directory: 'swaymsg'"
[2021-09-10T08:39:09Z] <x4n> So would I have to build swaymsg?
[2021-09-10T08:39:40Z] <testuser[m]> swaymsg is provided by sway, and this "wal" program seems to talk to swaymsg to set the backgroun
[2021-09-10T08:39:52Z] <testuser[m]> oh wal is pywal ?
[2021-09-10T08:40:16Z] <x4n> yes, pywal
[2021-09-10T08:40:38Z] <x4n> I have the sway-tiny package currently installed, is that a problem?
[2021-09-10T08:41:26Z] <testuser[m]> so /usr/bin/swaymsg doesnt exist ?
[2021-09-10T08:42:16Z] <x4n> "find: /usr/bin/swaymsg: No such file or directory" :(
[2021-09-10T08:42:39Z] <testuser[m]> build regular sway i guess, dylan might've removed swaymsg from the tiny fork
[2021-09-10T08:43:14Z] <x4n> Building regular sway package will break my current installation
[2021-09-10T08:43:22Z] <testuser[m]> why
[2021-09-10T08:43:34Z] <x4n> Because I don't have any cron daemon or something
[2021-09-10T08:43:43Z] <x4n> And configuring all that the tty only is a pain
[2021-09-10T08:44:09Z] <testuser[m]> i guess you could tell pywal to use another wallpaper setter
[2021-09-10T08:44:09Z] <x4n> Instead, is it possible to disable the wallpaper setting thing?
[2021-09-10T08:44:48Z] <x4n> Wait.. I found it!
[2021-09-10T08:45:03Z] <x4n> Yep. It worked!
[2021-09-10T08:45:09Z] <x4n> Thanks!
[2021-09-10T08:45:24Z] <testuser[m]> nice
[2021-09-10T08:46:41Z] <x4n> Time for playing with pywal
[2021-09-10T08:47:26Z] <x4n> BTW, have you tested waybar on KISS Linux?
[2021-09-10T08:47:50Z] <testuser[m]> no
[2021-09-10T08:47:57Z] <x4n> ok
[2021-09-10T08:50:12Z] <x4n> Dang gtkmm is not in KISS Linux repo
[2021-09-10T08:51:12Z] <testuser[m]> gtk2 isnt there so how would gtkmm be there
[2021-09-10T08:51:16Z] <testuser[m]> those are gtk2 bindings right
[2021-09-10T08:51:37Z] <x4n> Its not good for a package like Waybar to use gtk2
[2021-09-10T08:51:46Z] <x4n> Testing bemenu..
[2021-09-10T08:57:10Z] <x4n> bemenu also doesn't work
[2021-09-10T08:57:23Z] <x4n> is there a status bar that actually works?
[2021-09-10T09:00:15Z] <testuser[m]> bemenu works
[2021-09-10T09:00:37Z] <testuser[m]> `bemenu-run`
[2021-09-10T09:00:44Z] <testuser[m]> its not a status bar its a launcher
[2021-09-10T09:00:48Z] <x4n> How?
[2021-09-10T09:01:06Z] <x4n> I tried doing "bemenu" and it shows.. nothing.
[2021-09-10T09:01:11Z] <x4n> oooooooh
[2021-09-10T09:03:18Z] <x4n> Yes! It works
[2021-09-10T09:03:20Z] <x4n> Great
[2021-09-10T09:04:59Z] <x4n> Now its  time for a status bar
[2021-09-10T09:17:18Z] <x4n> Waybar doesn't compile due to gtkmm, nwg-panel also doesn't compile too
[2021-09-10T09:17:30Z] <x4n> Is mercurial present in the KISS repository
[2021-09-10T09:17:33Z] <x4n> or the community one?
[2021-09-10T09:18:06Z] <x4n> Or how can I clone a package from hg.sr.ht?
[2021-09-10T09:19:06Z] <testuser[m]> pip install mercurial
[2021-09-10T09:19:17Z] <x4n> OK
[2021-09-10T09:19:23Z] <x4n> Lets see
[2021-09-10T09:19:27Z] <testuser[m]> or this outdated package https://github.com/kiss-community/graveyard/tree/main/community/mercurial
[2021-09-10T09:20:00Z] <x4n> naaaaaaaaaaaaaaah
[2021-09-10T09:20:07Z] <x4n> no outdated packges allowed
[2021-09-10T09:20:40Z] <x4n> P.S.	i hope libwayland-dev, libgtk-3-dev pkg-config and meson are also present
[2021-09-10T09:23:41Z] <konimex> isn't meson already in kiss main?
[2021-09-10T09:24:41Z] <x4n> yep it is
[2021-09-10T09:24:49Z] <x4n> but what about the libraries
[2021-09-10T09:25:09Z] <testuser[m]> if the libraries didnt exist then your sway wouldnt have built
[2021-09-10T09:25:24Z] <x4n> OOOH
[2021-09-10T09:25:45Z] <x4n> "FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/share/man/man1'" when building wofi
[2021-09-10T09:27:59Z] <x4n> oops
[2021-09-10T09:28:04Z] <x4n> I'm building the wrong thing sorry
[2021-09-10T09:31:12Z] <x4n> there's no yaml
[2021-09-10T10:08:13Z] <x4n> Hello again!
[2021-09-10T10:08:26Z] <x4n> I want to have information about how to change the border thickness and color in sway?
[2021-09-10T10:08:35Z] <x4n> I'm asking this question because the man pages in sway-tiny are missing
[2021-09-10T10:11:16Z] <x4n> Also when using mold as the system linker, grim fails the compile
[2021-09-10T10:11:40Z] <soliwilos> I haven't used sway-tiny, but I reckon it's the same as sway.
[2021-09-10T10:11:46Z] <x4n> It says "clang-12: error: argument unused during compilation: '--ld-path=/usr/bin/mold'
[2021-09-10T10:12:07Z] <soliwilos> x4n: man page online https://www.mankier.com/5/sway
[2021-09-10T10:15:11Z] <x4n> soliwilos I don't know how to do it
[2021-09-10T10:15:54Z] <x4n> no information about how to change color :(
[2021-09-10T10:18:16Z] <soliwilos> Look at the client.background <color> section.
[2021-09-10T10:19:21Z] <soliwilos> client.focused for focused windows and others for other states.
[2021-09-10T10:19:51Z] <soliwilos> border color is done with those.
[2021-09-10T10:19:56Z] <x4n> oh
[2021-09-10T10:19:57Z] <x4n> nice
[2021-09-10T10:20:42Z] <x4n> wait 
[2021-09-10T10:20:58Z] <x4n> in which format is the color supposed to provided?
[2021-09-10T10:21:04Z] <x4n> hex? rgb?
[2021-09-10T10:21:31Z] <soliwilos> hex, prefixed with #.
[2021-09-10T10:22:01Z] <soliwilos> #000000 and the like.
[2021-09-10T10:22:02Z] <x4n> alright
[2021-09-10T10:22:35Z] <soliwilos> The defaults are given in the manpage there.
[2021-09-10T10:24:56Z] <x4n> So will I have to do like "client.focused #000000"?
[2021-09-10T10:29:02Z] <x4n> plz help
[2021-09-10T10:44:45Z] <soliwilos> Sorry, was busy.
[2021-09-10T10:45:11Z] <soliwilos> As far as I rerember you need to specify all the colors.
[2021-09-10T10:45:34Z] <soliwilos> s/rerember/remember/
[2021-09-10T10:45:34Z] <cotangent> <soliwilos> As far as I remember you need to specify all the colors.
[2021-09-10T10:46:03Z] <soliwilos> So "client.focused	#4c7899	#285577	#ffffff	#2e9ef4	#285577"
[2021-09-10T10:46:36Z] <soliwilos> Where the first color given is for the border.
[2021-09-10T10:58:37Z] <x4n> So in the commit https://github.com/wyvertux/wyverkiss/commit/20033f4085a97d3a3b17c22beabd4030585761b9
[2021-09-10T10:58:48Z] <x4n> Konimex mentioned to set the $TERM value
[2021-09-10T10:59:01Z] <x4n> put even when having the variable in the /etc/profile.d/
[2021-09-10T10:59:14Z] <x4n> I still don't have the value set to xterm-256color
[2021-09-10T10:59:28Z] <x4n> I tried sourcing it but it only becomes valid for the current terminal session
[2021-09-10T11:00:40Z] <testuser[m]> x4n: relogin
[2021-09-10T11:01:00Z] <testuser[m]> Also the mold failure can be fixed by removing adding `-Wno-error` to build flags
[2021-09-10T11:01:21Z] <testuser[m]> Devs like to enforce Werror for some reason, it's not good since compilers are free to warn for anything
[2021-09-10T11:01:42Z] <testuser[m]> `-Werror=somecriticalwarning` should be used
[2021-09-10T11:01:42Z] <x4n> by removing adding?
[2021-09-10T11:01:54Z] <testuser[m]> Add -Wno-error to cflags
[2021-09-10T11:01:59Z] <x4n> oh
[2021-09-10T11:02:00Z] <x4n> ok
[2021-09-10T11:02:03Z] <konimex> how did you add --ld-path=/usr/bin/mold there?
[2021-09-10T11:02:23Z] <x4n> I have it in my CFLAGS and CXXFLAGS environment variable
[2021-09-10T11:02:26Z] <konimex> just use the alternatives system
[2021-09-10T11:02:36Z] <x4n> I have used the alternatives system
[2021-09-10T11:02:49Z] <testuser[m]> It just warns since there's no linking involved in just compiling c files
[2021-09-10T11:02:55Z] <testuser[m]> You sure the guide didnt mentiond LDFLAGS ?
[2021-09-10T11:03:03Z] <konimex> if the alternative system is used then don't even bother with --ld-path
[2021-09-10T11:03:14Z] <x4n> it didn't mentioned LDFLAGS
[2021-09-10T11:03:31Z] <x4n> it had the alternative system AND the export CFLAGS in the steps
[2021-09-10T11:03:32Z] <konimex> since /bin/ld will be searched first anyway
[2021-09-10T11:03:33Z] <x4n> so I did both
[2021-09-10T11:03:52Z] <konimex> what steps?
[2021-09-10T11:04:02Z] <x4n> In https://kisslinux.org/wiki/pkg/mold
[2021-09-10T11:04:28Z] <konimex> time to open an issue to dylan then
[2021-09-10T11:04:47Z] <x4n> a'ight
[2021-09-10T11:04:53Z] <x4n> I'll close mine then
[2021-09-10T11:05:33Z] <konimex> no no, don't close it
[2021-09-10T11:05:41Z] <x4n> and what may I do for $TERM variable?
[2021-09-10T11:05:53Z] <x4n> Alright.
[2021-09-10T11:05:57Z] <konimex> just set it in your .profile
[2021-09-10T11:06:00Z] <konimex> and restart your computer
[2021-09-10T11:06:12Z] <konimex> or logout and log back in
[2021-09-10T11:06:50Z] <x4n> Alright
[2021-09-10T11:11:37Z] <x4n> well, I have "export TERM=xterm-256color" and "TERM=xterm-256color" in my ~/.profile but the environment variable is not exported
[2021-09-10T11:12:43Z] <konimex> what sh are you using?
[2021-09-10T11:12:47Z] <x4n> sh
[2021-09-10T11:12:57Z] <konimex> yeah, what sh?
[2021-09-10T11:13:06Z] <konimex> bash? dash? zsh?
[2021-09-10T11:13:21Z] <x4n> sh
[2021-09-10T11:13:23Z] <x4n> pure sh
[2021-09-10T11:13:42Z] <x4n> aka busybox sh aka POSIX shell aka ash
[2021-09-10T11:17:36Z] <konimex> ah yes, it seems foot overrides $TERM
[2021-09-10T11:18:05Z] <konimex> and ash doesn't have .ashrc it seems
[2021-09-10T11:18:40Z] <x4n> yee
[2021-09-10T11:20:59Z] <konimex> I'd recommend bash (since I personally do use it) but it'd be ironic to have a gnu-free distro using bash
[2021-09-10T11:21:17Z] <konimex> but I'll come up with something
[2021-09-10T11:21:40Z] <x4n> oke
[2021-09-10T11:22:05Z] <bountyht> There is always OpenBSD's KSH :-)
[2021-09-10T11:22:19Z] <bountyht> SOrry if I sound like a fanboi everytime I open my mouth :-(
[2021-09-10T11:22:48Z] <konimex> bountyht: open an issue on dylan's kiss, maybe he'll include it in his repos (and in turn, wyverkiss will follow)
[2021-09-10T11:23:34Z] <x4n> oksh is in the community repo
[2021-09-10T11:23:37Z] <x4n> but not in the kiss main repo
[2021-09-10T11:23:46Z] <bountyht> konimex: I am still playing with kiss in a chroot and deciding which computer I place it in for testing 
[2021-09-10T11:24:00Z] <x4n> and its from ibara
[2021-09-10T11:24:16Z] <x4n> who also made portable m4 that KISS uses
[2021-09-10T11:24:16Z] <konimex> x4n: yeah, and the solution I'm trying to make should be in line with kiss main repo, so no oksh at all
[2021-09-10T11:24:48Z] <x4n> yep
[2021-09-10T11:24:55Z] <x4n> also oksh depends on ncurses so..
[2021-09-10T11:25:11Z] <x4n> i guess it won't work out of the box in wyverkiss
[2021-09-10T11:25:42Z] <konimex> a temporary solution, of course, is invoking `TERM=linux vim`
[2021-09-10T11:25:56Z] <konimex> or `TERM=linux alsamixer`
[2021-09-10T11:26:25Z] <x4n> And so will "alias vim="TERM=linux vim" and "alias alsamixer=TERM=linux alsamixer"!
[2021-09-10T11:26:33Z] <bountyht> wtf, does it depend on ncurses?
[2021-09-10T11:26:37Z] <konimex> that should also work
[2021-09-10T11:26:38Z] * bountyht ldds ksh
[2021-09-10T11:26:46Z] <x4n> yep
[2021-09-10T11:26:57Z] <x4n> it depends on ncurses, mentioned in the depends file
[2021-09-10T11:27:31Z] <x4n> yee the alias works!
[2021-09-10T11:28:26Z] <x4n> P.S. why the git clone of vim is so big??
[2021-09-10T11:28:36Z] <x4n> it exceeds 50Mb+
[2021-09-10T11:32:46Z] <konimex> dylan uses git clones instead of tarballs since they bump the version every commit
[2021-09-10T11:33:07Z] <konimex> as for why is it big, perhaps because of the git commit itself
[2021-09-10T11:33:30Z] <x4n> I've done the clone manually with --depth 1 and the size is 15.10Mb
[2021-09-10T11:33:46Z] <x4n> Is is possible for this --depth parameter to be inserted in the kiss git clone command?
[2021-09-10T11:35:43Z] <konimex> you may want to open an issue in kisslinux/kiss since the current command is invoked from the package manager itself
[2021-09-10T11:36:12Z] <x4n> Alright, i'm doing it.
[2021-09-10T11:39:22Z] <x4n> Done.
[2021-09-10T11:40:28Z] <x4n> Also, why vim compiles with an unrecognized option "--disable-gmp"?
[2021-09-10T11:42:13Z] <konimex> gmp? are you sure? since there's no --disable-gmp in the kiss vim buildfile
[2021-09-10T11:42:36Z] <x4n> Hold up
[2021-09-10T11:42:58Z] <x4n> Maybe because of this symlink "../../kiss-repo/extra/vim/build"
[2021-09-10T11:43:36Z] <x4n> You can see it here "https://github.com/kisslinux/repo/blob/8c3548d0bdfb5f9b1152dc064f8563a75b47b58a/extra/vim/build"
[2021-09-10T11:44:53Z] <x4n> I've compiled vim manually and created an issue in the kiss linux repo
[2021-09-10T11:45:00Z] <x4n> sorry the kiss package manager repo
[2021-09-10T12:05:45Z] <x4n> Alright, the optimizations made will be 1) shallow clones 2) Tag management
[2021-09-10T12:05:58Z] <x4n> according to dylan
[2021-09-10T12:57:37Z] <x4n> Does kiss-community/bin packages work in Wyverkiss?
[2021-09-10T12:57:45Z] <x4n> Asking because of Firefox
[2021-09-10T12:57:47Z] <x4n> and Rust
[2021-09-10T12:58:53Z] <testuser[m]> They would if they were built with static libgcc and stdc but i don't think they are
[2021-09-10T12:59:23Z] <x4n> And they also require libepoxy that is not present in Wyverkiss, nice..
[2021-09-10T12:59:46Z] <x4n> And I can't use ccache because it instead slows down the building process of Wyverkiss..
[2021-09-10T13:00:03Z] <x4n> Anyways, I'm trying it.
[2021-09-10T13:01:22Z] <testuser[m]> ccache will do literally nothing for firefox or rust
[2021-09-10T13:05:10Z] <x4n> Yes, you are right.
[2021-09-10T13:05:24Z] <x4n> It takes hours for me to compile it.
[2021-09-10T13:05:33Z] <x4n> Even now I have rust update pending.
[2021-09-10T13:15:41Z] <konimex> what? I don't think firefox or rust require any libepoxy
[2021-09-10T13:17:12Z] <x4n> can tmux byobu or screen be built in wyverkiss?
[2021-09-10T13:34:31Z] <micro_O> https://github.com/epilys/buke < full text manpage search, neat
[2021-09-10T13:41:47Z] <x4n> sorry for not noticing konimex
[2021-09-10T13:41:50Z] <x4n> I got disconnected
[2021-09-10T13:42:04Z] <x4n> But I was talking about the binary packages in kiss-community/bin
[2021-09-10T15:58:29Z] <davidgarland> made progress since yesterday but now I'm up to a kernel panic-- it says "VFS: Cannot open root device "PARTUUID=..." or unknown-block(0, 0): error -6"; "Please append a correct "root=" boot option; here are the available partitions:" then goes on to list UUIDs I don't recognize from blkid
[2021-09-10T15:59:07Z] <davidgarland> I suspected it might be a missing SATA or AHCI driver based on googling the issue but it seems like I've enabled the relevant settings for an Intel controller (what lspci says I have) so I'm unsure what i could be missing
[2021-09-10T16:12:49Z] <soliwilos> Have you enabled the filesystem you're using in the kernel?
[2021-09-10T16:13:37Z] <davidgarland> let me check
[2021-09-10T16:14:21Z] <davidgarland> ext4 seems to be enabled yeah
[2021-09-10T16:14:28Z] <soliwilos> Did you also try using root=/dev/sdXY instead of uuid?
[2021-09-10T16:14:50Z] <davidgarland> worth a try, ill give that a spin
[2021-09-10T16:24:23Z] <pehaef> one of the UUID things only works if you have an initramfs that handles it with userland stuff, I forget which
[2021-09-10T16:24:30Z] <pehaef> the other I believe the kernel can do on it's own?
[2021-09-10T16:25:18Z] <davidgarland> I am under the impression efistub with no initramfs should be possible-- I've avoided allowing any kernel modules and baked in the microcode and graphics drivers
[2021-09-10T16:28:05Z] <pehaef> ah efistub, that's fun stuff; I am doing the same at work alas I never could get it to do the right thing without an initramfs; which I bake into the kernel for now but have plans to not to once efibootmgr works like it should; sorry I should say that what I am doing is not actually kisslinux related, it's a custom embedded-ish thing
[2021-09-10T16:28:25Z] <davidgarland> I see
[2021-09-10T16:28:44Z] <davidgarland> I've never tried any custom stuff, always got stuck when trying to do LFS lol
[2021-09-10T16:28:54Z] <davidgarland> figures given it's taken me a full day already to get back to this point with KISS
[2021-09-10T16:30:57Z] <pehaef> figuring out how the darn kernel wants to continue booting can be quite confusing, especially when you try EFI; but I figured "hey, no bootloader needed, one less moving part" so I went there as well
[2021-09-10T16:31:40Z] <davidgarland> for me it's more just frustration with the fact that GRUB seems to manage to always erase my windows 10 install that's on a *separate disk* somehow
[2021-09-10T16:32:21Z] <davidgarland> hoping this doesn't have the same issue (though last install also got wiped since i only started trying efistub after another failed grub attempt x_x)
[2021-09-10T16:36:30Z] <davidgarland> boots now :) 
[2021-09-10T16:37:33Z] <micro_O> js "I want range(99)" jv "we have range(99) at home" range(99) at home "[...Array(99).keys()]"
[2021-09-10T16:38:08Z] <davidgarland> lmao
[2021-09-10T16:38:52Z] <davidgarland> amazing how everything runs on a language that can't figure out what lexical scope is
[2021-09-10T16:39:48Z] <davidgarland> o/
[2021-09-10T16:40:01Z] <illiliti> hi
[2021-09-10T16:40:10Z] <testuser[m]> Hi
[2021-09-10T16:44:02Z] <pehaef> davidgarland: congrats!
[2021-09-10T16:44:23Z] <davidgarland> thanks for the help
[2021-09-10T16:44:58Z] <pehaef> davidgarland: so did PARTUUID work or did the "classic" path for the partition work?
[2021-09-10T16:46:02Z] <davidgarland> I ended up getting PARTUUID working, but I'm not entirely sure which kernel option specifically was responosible for getting it working
[2021-09-10T16:46:49Z] <noocsharp> that's how it goes
[2021-09-10T16:47:03Z] <noocsharp> one day, go through and randomly delete kernel options until it breaks
[2021-09-10T16:47:07Z] <davidgarland> lol
[2021-09-10T16:47:16Z] <noocsharp> then you will know
[2021-09-10T16:47:21Z] <davidgarland> yeah
[2021-09-10T17:07:34Z] <testuser[m]> Do this instead https://ldpreload.com/blog/git-bisect-run
[2021-09-10T17:26:10Z] <davidgarland> probably a dumb question but how do I get dhcpcd to stop printing things over the console
[2021-09-10T17:29:04Z] <davidgarland> am using the default busybox init
[2021-09-10T17:38:03Z] <davidgarland> ..just edited the run file manually, guess that works
[2021-09-10T18:12:56Z] <akira01> hi guys
[2021-09-10T18:13:22Z] <akira01> have any openjdk repo that works?
[2021-09-10T18:29:18Z] <davidgarland> if you're merely concerned with getting one onto your machine, you could use https://adoptium.net/ to grab prebuilt ones-- if that's not what you want, then disregard
[2021-09-10T18:44:10Z] <akira01> will test
[2021-09-10T18:44:24Z] <akira01> why the problem in build?
[2021-09-10T19:31:15Z] <noocsharp> i think landlock could be a lighter weight way to verify that dependencies are correct than chroot
[2021-09-10T19:31:59Z] <noocsharp> by allowing access only to files owned by particular dependencies, and if a file outside of that is accessed, then you know that it's missing something
[2021-09-10T21:31:37Z] <aws> Hello
[2021-09-10T21:31:49Z] <aws> I'm trying out hexchat
[2021-09-10T21:31:59Z] <acheam> hi
[2021-09-10T22:49:53Z] <dilyn> decided i wanted to play around with dylan's new take on baseinit and also get smdev sorted 
[2021-09-10T22:50:13Z] <dilyn> forgot that baseinit by default is fscked with toybox, so had to handle constant exits
[2021-09-10T22:50:31Z] <dilyn> been troubleshooting a 'cannot fork - try again' for a couple hours now 
[2021-09-10T22:50:49Z] <dilyn> realized it's because my chromium script is self-referring, not because something during init indefinitely blocks >.<  
[2021-09-10T23:05:00Z] <acheam> uhhh
[2021-09-10T23:05:07Z] <acheam> you launch chromium on boot?
[2021-09-10T23:05:40Z] <dilyn> no, it's just one of the first things i launch after wayfire 
[2021-09-10T23:05:53Z] <acheam> then why did you think it was an init issue?
[2021-09-10T23:05:55Z] <dilyn> which is why it was so confusing (yet should have been obvious) -- wayfire launched fine 
[2021-09-10T23:06:04Z] <dilyn> because I'm a mooran
[2021-09-10T23:06:09Z] <acheam> ah but wayfire launches chromium?
[2021-09-10T23:06:21Z] <dilyn> no it's just muscle memory to hit meta+w at this point 
[2021-09-10T23:06:33Z] <dilyn> meta+enter; meta+w, twerktwerktwerk
[2021-09-10T23:07:14Z] <dilyn> interestingly, with toybox mount, baseinit nonfatally errors saying that /dev is not in /proc/mounts when trying to mount devtmpfs...
[2021-09-10T23:07:51Z] <dilyn> but toybox mount is complete, and sufficient in this case. so that's weird