[2022-10-03T02:51:08Z] <wael[m]> Hi
[2022-10-03T04:38:19Z] <testuser[m]> Hi
[2022-10-03T06:41:29Z] <virutalmachineus> HI!
[2022-10-03T09:27:30Z] <testuser[m]> phoebos: 
[2022-10-03T09:27:31Z] <testuser[m]> any idea why installing baselayout with KISS_ROOT set doesn't set correct perms for /tmp etc?
[2022-10-03T09:42:32Z] <Ogromny> Hi
[2022-10-03T09:42:37Z] <Ogromny> Do any of you use River ?
[2022-10-03T09:45:21Z] <Ogromny> If yes, how did you compile it ? It requires libevdev, but on Kiss we use libudev-zero right ? It will fuck up the system if I install libevdev too ?
[2022-10-03T09:46:00Z] <Ogromny> I have absolutely 0 knowledges on evdev/udev/libinput things
[2022-10-03T09:46:23Z] <testuser[m]> evdev is unrealted to libudev-zero
[2022-10-03T09:46:48Z] <testuser[m]> it needs libevdev, but that's currently bundled into libinput
[2022-10-03T09:46:54Z] <testuser[m]> https://codeberg.org/kiss-community/repo/pulls/114 will be fixed by this
[2022-10-03T09:47:21Z] <Ogromny> Oh thanks !
[2022-10-03T09:48:17Z] <Ogromny> Hope the PR will be merged soon 
[2022-10-03T09:50:10Z] <testuser[m]> its ready to merge 
[2022-10-03T09:50:17Z] <testuser[m]> but i havent tested it much
[2022-10-03T09:50:32Z] <wael[m]> does mako get split into another package in that PR?
[2022-10-03T09:50:44Z] <testuser[m]> yea
[2022-10-03T09:50:47Z] <testuser[m]> 3 python packages
[2022-10-03T09:50:48Z] <wael[m]> or does it remove the ability to build dependencies at build time and instead does them in package
[2022-10-03T09:50:48Z] <testuser[m]> so bad
[2022-10-03T09:51:00Z] <wael[m]> so bad indeed
[2022-10-03T10:32:22Z] <Ogromny> Any of you use zig ?
[2022-10-03T10:33:37Z] <Ogromny> Zig's working fine except when I try to link libc I got a segfault. GDB say absolutely nothing, it seems that there is only a _start function in the binary
[2022-10-03T10:34:16Z] <testuser[m]> you're using the official binary?
[2022-10-03T10:34:18Z] <testuser[m]> it happens with that for some reason
[2022-10-03T10:35:54Z] <Ogromny> I built zig with the package from community
[2022-10-03T10:36:15Z] <Ogromny> I tried with a master build of zig, same issue
[2022-10-03T10:41:12Z] <phoebos> testuser[m]: https://codeberg.org/kiss-community/kiss/commit/1933a19e105d83a512c9312022ba1d57bc04fd73
[2022-10-03T10:41:23Z] <phoebos> maybe to do with this
[2022-10-03T10:43:01Z] <Ogromny> phoebos: Zig build fine, but whenever I try to build a zig app linked with libc it segfaults...
[2022-10-03T10:43:50Z] <testuser[m]> he's not talking about the zig isue
[2022-10-03T10:43:56Z] <Ogromny> Oh my bad
[2022-10-03T10:47:19Z] <phoebos> ah testuser[m]: file_rwx gets st_mode & 0777 so it doesn't realise the sticky bit is set
[2022-10-03T10:47:34Z] <phoebos> ie. /tmp is 1777, but file_rwx /tmp gives 777
[2022-10-03T10:58:02Z] <phoebos> this is the kind of place where a bit of C makes it much easier
[2022-10-03T11:08:46Z] <phoebos> testuser[m]: with reverting 1933a19e105d83a512c9312022ba1d57bc04fd73 and the PR I opened, I think it is fixed?
[2022-10-03T11:18:37Z] <phoebos> not sure why explicit tar -p is required though. it should be used by default for root
[2022-10-03T11:19:03Z] <testuser[m]> im installing as user
[2022-10-03T11:26:28Z] <testuser[m]> wrks
[2022-10-03T11:27:50Z] <phoebos> oh yeah
[2022-10-03T11:28:00Z] <phoebos> KISS_ROOT is owned by whoever
[2022-10-03T11:28:06Z] <phoebos> works with explicit -p?
[2022-10-03T11:29:00Z] <testuser[m]> same with and without
[2022-10-03T11:29:06Z] <testuser[m]> as use
[2022-10-03T11:29:08Z] <testuser[m]> user
[2022-10-03T11:29:40Z] <phoebos> what's your umask
[2022-10-03T11:30:10Z] <testuser[m]> 0022
[2022-10-03T11:30:19Z] <phoebos> same
[2022-10-03T11:32:30Z] <phoebos> without -p, /tmp in KISS_ROOT is 0755
[2022-10-03T11:33:13Z] <phoebos> with -p, 1777
[2022-10-03T11:34:30Z] <phoebos> with -p but without rwx patch, 0777
[2022-10-03T11:44:46Z] <testuser[m]> s
[2022-10-03T11:45:53Z] <testuser[m]> ig ill just spoof uid with bwrap
[2022-10-03T11:45:54Z] <testuser[m]> works fine with that
[2022-10-03T11:47:05Z] <testuser[m]> along with ur patch
[2022-10-03T12:05:38Z] <testuser[m]> https://termbin.com/3095
[2022-10-03T12:07:41Z] <testuser[m]> the script is garbage but much better than manually creating ta
[2022-10-03T12:07:42Z] <testuser[m]> tar
[2022-10-03T12:07:55Z] <testuser[m]> https://codeberg.org/kiss-community/maintainer-utils/src/branch/master/kiss-bootstrap/bootstrap.sh
[2022-10-03T12:12:43Z] <testuser[m]> i need to fix the error handlig
[2022-10-03T12:12:56Z] <testuser[m]> it doesnt work if kiss build fails, the whole script ends with 
[2022-10-03T12:12:59Z] <testuser[m]> "Terminated"
[2022-10-03T12:26:57Z] <sad_plan> o/
[2022-10-03T12:27:05Z] <wael[m]> \o
[2022-10-03T13:56:18Z] <testuser[m]>  phoebos why are `old`, `sys` and `new` checksums compared for /etc, can't we just `if hash(new) != hash(existing) mv new new.new`
[2022-10-03T13:56:24Z] <testuser[m]> why does it matter what the original checksum was
[2022-10-03T13:57:39Z] <testuser[m]> oh it's just to avoid saving the file as .new if it's same as the original one
[2022-10-03T13:58:38Z] <testuser[m]> is that really needed though, removing that logic will get rid of storing checksums anywhere which simplifies the b3 transition a bit
[2022-10-03T14:00:50Z] <testuser[m]> ioraff: illiliti ?
[2022-10-03T14:04:39Z] <testuser[m]> Wait nvm
[2022-10-03T14:04:44Z] <testuser[m]> I forgot the main purpose lol
[2022-10-03T14:05:01Z] <testuser[m]> it'll keep installing .new files otherwise even if everything is unchanged
[2022-10-03T14:14:18Z] <phoebos> testuser[m]: who owned KISS_ROOT when you were testing earlier
[2022-10-03T14:14:50Z] <testuser[m]> phoebos: my user
[2022-10-03T14:15:01Z] <testuser[m]> uid 1000 
[2022-10-03T14:15:30Z] <phoebos> i don't understand why you didn't need tar -p but i do
[2022-10-03T14:16:23Z] <testuser[m]> it doesnt work either way with non-root user
[2022-10-03T14:25:45Z] <testuser[m]> btw i think i figured out a way to reduce conflict detection time by inf %
[2022-10-03T14:26:11Z] <testuser[m]> make the whole file list into a fat (/file1|/file2) expr instead of 1000 individual patterns
[2022-10-03T14:26:25Z] <testuser[m]> runs in 0.06s instead of 10s but idk if it even works so
[2022-10-03T14:28:17Z] <testuser[m]> this is for 5000 files
[2022-10-03T14:29:31Z] <phoebos> ooh sounds nice
[2022-10-03T14:30:34Z] <phoebos> https://tmp.bvnf.space/log
[2022-10-03T14:31:11Z] <phoebos> testuser[m]: kiss owns /bin/tar ?
[2022-10-03T14:31:27Z] <testuser[m]> busybox
[2022-10-03T14:31:35Z] <testuser[m]> actually
[2022-10-03T14:31:35Z] <phoebos> ah
[2022-10-03T14:31:48Z] <testuser[m]> not in kiss
[2022-10-03T14:31:48Z] <testuser[m]> i was trying with raw tar 
[2022-10-03T14:31:49Z] <testuser[m]> but it should be the same so
[2022-10-03T14:32:34Z] <phoebos> gtar?
[2022-10-03T14:32:49Z] <testuser[m]> i mean i was trying iwth busybox tar outside of kiss
[2022-10-03T14:33:11Z] <phoebos> ok
[2022-10-03T14:35:10Z] <testuser[m]> yea busybox tar is shit
[2022-10-03T14:35:11Z] <testuser[m]> λ ls -ld busy/tmp
[2022-10-03T14:35:11Z] <testuser[m]> drwxr-xr-t    2 testuser testuser        40 Oct  3 18:58 busy/tmp
[2022-10-03T14:35:11Z] <testuser[m]> λ ls -ld gnoo/tmp
[2022-10-03T14:35:11Z] <testuser[m]> drwxrwxrwt    2 testuser testuser        40 Oct  3 18:58 gnoo/tmp
[2022-10-03T14:38:41Z] <testuser[m]> btw how does `grep -q ":/var/db/kiss/installed/" "$_tmp_file" || safe=1` ever match ? my grep doesn't seem to do anything if i try `echo test | grep :t`
[2022-10-03T14:38:54Z] <testuser[m]> : means line starting with substr i think
[2022-10-03T14:40:48Z] <testuser[m]> maybe he meant to use ^
[2022-10-03T14:42:42Z] <testuser[m]> OH
[2022-10-03T14:42:55Z] <testuser[m]> its cuz when grepping on multiple files it appends : after filename
[2022-10-03T14:43:32Z] <phoebos> ah
[2022-10-03T14:43:42Z] <phoebos> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html
[2022-10-03T14:43:52Z] <phoebos> : has no special meaning except in [::]
[2022-10-03T14:44:57Z] <testuser[m]> now tell me
[2022-10-03T14:45:06Z] <testuser[m]> how to escape filenames to safely includein  (|)
[2022-10-03T14:47:42Z] <illiliti> what are you trying to do?
[2022-10-03T14:49:51Z] <testuser[m]> make pkg_conflicts do grep -E '(/usr/bin/file1|/usr/bin/file2|...)' /var/db/kiss/installed/*/manifest 
[2022-10-03T14:49:59Z] <testuser[m]> instead of making file1 file2 as individual patterns
[2022-10-03T14:50:08Z] <testuser[m]> grep can make a trie with -E
[2022-10-03T14:54:42Z] <illiliti> it already does it via -f, no?
[2022-10-03T14:55:17Z] <phoebos> escape .[\*^$, don't escape 1-9(){}
[2022-10-03T14:55:22Z] <illiliti> -f pattern_file
[2022-10-03T14:55:39Z] <phoebos> oh yeah thats a better way
[2022-10-03T14:55:58Z] <testuser[m]> illiliti: no
[2022-10-03T14:56:17Z] <testuser[m]> what it does with -f is equivalent to -e
[2022-10-03T14:56:18Z] <testuser[m]> not -E
[2022-10-03T14:56:31Z] <testuser[m]> and that works cuz it tells grep to treat is as a string not a pattern
[2022-10-03T14:56:38Z] <testuser[m]> so .* | etc arent an issue
[2022-10-03T14:56:50Z] <illiliti> why do you need -E
[2022-10-03T14:56:51Z] <testuser[m]> but to make it go big fast it must be made into a ( pattern )
[2022-10-03T14:56:53Z] <phoebos> is the grep -Fxf the slow bit
[2022-10-03T14:57:03Z] <testuser[m]> for fast
[2022-10-03T14:57:05Z] <testuser[m]> look
[2022-10-03T14:57:12Z] <testuser[m]> wait
[2022-10-03T14:58:06Z] <illiliti> i would say that -E is slower
[2022-10-03T14:58:11Z] <illiliti> generally
[2022-10-03T15:01:13Z] <testuser[m]> https://termbin.com/m9fi
[2022-10-03T15:01:17Z] <testuser[m]> ignore the partial matches i have to figure that out
[2022-10-03T15:01:35Z] <midfavila> -E being slower would make sense considering it uses a more complex regex engine.
[2022-10-03T15:02:00Z] <testuser[m]> 116x diff
[2022-10-03T15:02:51Z] <illiliti> which grep?
[2022-10-03T15:02:56Z] <testuser[m]> busybox
[2022-10-03T15:03:02Z] <illiliti> try gnu
[2022-10-03T15:04:24Z] <testuser[m]> hmmmm yea its 0s vs 0.06s
[2022-10-03T15:04:30Z] <testuser[m]> ig ggrep does this sort of optimization by itself
[2022-10-03T15:13:06Z] <illiliti> just use gnu grep
[2022-10-03T15:13:13Z] <illiliti> no need to attempt to workaround busybox using -E and stuff like that
[2022-10-03T15:14:38Z] <illiliti> iirc freebsd grep is also fast
[2022-10-03T15:15:34Z] <testuser[m]> btw 
[2022-10-03T15:15:57Z] <testuser[m]> like wireguard-tools's wg-quick needs /usr/bin/ip set to iproute2
[2022-10-03T15:16:16Z] <testuser[m]> what would be a good way to indicate that somewhere
[2022-10-03T15:16:32Z] <testuser[m]> i mean like without swapping /usr/bin/ip
[2022-10-03T15:16:44Z] <testuser[m]> prefixing all of iproute's binaries?
[2022-10-03T15:16:57Z] <illiliti> post-install message
[2022-10-03T15:17:06Z] <testuser[m]> but it seems hacky
[2022-10-03T15:17:17Z] <testuser[m]> busybox so bad
[2022-10-03T15:19:39Z] <testuser[m]> [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820
[2022-10-03T15:19:39Z] <testuser[m]> ip: invalid argument '51820' to 'table'
[2022-10-03T15:19:49Z] <testuser[m]> is this something missing inside busybox or an actual bug
[2022-10-03T15:19:55Z] <illiliti> the ideal option would be to make it work with busybox
[2022-10-03T15:20:22Z] <illiliti> probably busybox has no idea about table arg
[2022-10-03T15:20:45Z] <testuser[m]> then thats probably out of scope for a KISS specific patch
[2022-10-03T15:22:24Z] <illiliti> is upstream interested in busybox compatibility?
[2022-10-03T15:22:33Z] <illiliti> but considering how they recklessly harcoded bash and shit, i guess no
[2022-10-03T15:23:18Z] <testuser[m]> I meant more like adding the feature to busybox
[2022-10-03T15:23:26Z] <testuser[m]> I don't think there's a "portable" alternative to that rule
[2022-10-03T15:25:24Z] <illiliti> so you want to contribute a patch to busybox? do it then
[2022-10-03T15:25:32Z] <illiliti> btw what about toybox
[2022-10-03T15:27:10Z] <sad_plan> toybox needs a patch for removing the bash make dep. unless we wanna put bash into the repo..
[2022-10-03T15:27:24Z] <sad_plan> its also.. way less complete
[2022-10-03T15:27:53Z] <testuser[m]> illiliti: can u read today's conversation about tar and sticky bits
[2022-10-03T15:33:49Z] <illiliti> phoebos has sent a fix already and you merged, no?
[2022-10-03T15:34:10Z] <phoebos> i'm still unsure about tar -p
[2022-10-03T15:34:13Z] <illiliti> or fix depends on tar implementation?
[2022-10-03T15:36:24Z] <testuser[m]> Its a partial fix
[2022-10-03T15:36:43Z] <testuser[m]> sticky bit is preserved, but only as root with busybox tar
[2022-10-03T15:36:57Z] <testuser[m]> stick bit is not preserved as regular user with busybox tar
[2022-10-03T15:37:03Z] <testuser[m]> but it works in both cases with gtar
[2022-10-03T15:37:26Z] <phoebos> ^ only with tar -p
[2022-10-03T15:46:27Z] <illiliti> i doubt that we can do anything with this bug
[2022-10-03T15:46:48Z] <testuser[m]> ~~other than C rewrite~~
[2022-10-03T15:46:55Z] <midfavila> speaking of bugs and C,
[2022-10-03T15:47:04Z] <midfavila> could one you guys take a hot minute to do me a small favor?
[2022-10-03T15:47:05Z] <illiliti> not with tar
[2022-10-03T15:47:10Z] <illiliti> we could use pax
[2022-10-03T15:47:45Z] <midfavila> i need someone to compile XMag with tcc, then attempt to magnify a section of the display and report back any errors
[2022-10-03T15:48:20Z] <illiliti> also i doubt that current fix is good fix
[2022-10-03T15:48:26Z] <midfavila> there seems to be a problem with tcc potentially generating incorrect output with programs that use Xt inheritance operations... whatever that means
[2022-10-03T15:48:42Z] <illiliti> some systems don't support setting sticky bit on files
[2022-10-03T15:48:52Z] <illiliti> this could be problematic
[2022-10-03T15:49:56Z] <testuser[m]> phoebos: are there more cases that rwx needs to handle other than stick and rwx stuff already present? Eg if you were to do something like this, will it work?
[2022-10-03T15:49:57Z] <testuser[m]> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=flutter#n42
[2022-10-03T15:51:27Z] <phoebos> isn't that just adding rw-rw-rw-
[2022-10-03T15:51:54Z] <phoebos> rwx handles that already
[2022-10-03T16:29:28Z] <illiliti> imho we should use chroot() rather than inventing our own using KISS_ROOT
[2022-10-03T16:29:49Z] <testuser[m]> wdym
[2022-10-03T16:31:36Z] <illiliti> i mean chroot() looks cleaner than prepending KISS_ROOT to everything
[2022-10-03T16:32:32Z] <illiliti> chroot(KISS_ROOT)
[2022-10-03T16:36:53Z] <testuser[m]> You mean in terms of post install files?
[2022-10-03T16:36:59Z] <testuser[m]> How else would pkgs get installer
[2022-10-03T16:37:05Z] <testuser[m]> if ur talking about KISS
[2022-10-03T16:37:16Z] <testuser[m]> not the post* hooks
[2022-10-03T16:37:39Z] <testuser[m]> And i think for hooks we should chroot cuz there can be many hooks like for adding users, which won't work without chrot
[2022-10-03T16:44:23Z] <illiliti> i mean in general. if i haven't missed anything, chroot(KISS_ROOT) is a cleaner way
[2022-10-03T16:44:31Z] <illiliti> but as you noted, how kiss would access ~/.cache/kiss/bin. does it need such access
[2022-10-03T16:46:13Z] <illiliti> re adding users, imo packages shouldn't modify anything in /etc
[2022-10-03T16:47:29Z] <illiliti> they can only add new files and/or modify only their own files
[2022-10-03T16:48:04Z] <illiliti> that's something we should enforce in sandbox
[2022-10-03T16:54:48Z] <testuser[m]> illiliti: what about openssl certificate updaye
[2022-10-03T16:56:11Z] <illiliti> it's ok cuz /etc/ssl/* is owned by openssl
[2022-10-03T16:56:48Z] <illiliti> to be exact, openssl is a sole app that writes to /etc/ssl/*
[2022-10-03T16:57:20Z] <illiliti> things get messy when apps start write to /etc/shells
[2022-10-03T16:57:25Z] <illiliti> or /etc/passwd
[2022-10-03T16:58:07Z] <illiliti> and on remove, they don't cleanup their shit
[2022-10-03T16:58:40Z] <sad_plan> midfavila: I managed to build tinyx statically, if youre interested in doing so yourself
[2022-10-03T16:59:12Z] <midfavila> that would be something I'd be interested in seeing, yeah
[2022-10-03T16:59:57Z] <sad_plan> set XSERVERCFLAGS_CFLAGS to --static. maybe -static works for you, but for me it didnt seem to work.
[2022-10-03T17:01:00Z] <sad_plan> you may also have to add some libs to XSERVERLIBS_LIBS aswell. I had to add libz, freetype and harfbuzz and libpng. I also set *.a aswell to begin with. dunno if it made any difference tbh.
[2022-10-03T17:02:49Z] <midfavila> could you package the changes and send me a copy?
[2022-10-03T17:03:07Z] <sad_plan> just the buildscript?
[2022-10-03T17:03:12Z] <midfavila> correct
[2022-10-03T17:03:32Z] <sad_plan> http://0x0.st/oJqB.sh there you go
[2022-10-03T17:10:19Z] <midfavila> thanks, I'll fiddle with it next time I'm looking at tinyx
[2022-10-03T17:10:29Z] <midfavila> for now I've put any X-related stuff off to the side
[2022-10-03T17:10:39Z] <sad_plan> youre welcome :D
[2022-10-03T17:10:51Z] <sad_plan> alot of other stuff to figure out first?
[2022-10-03T17:11:01Z] <midfavila> no, stuff that I'm not capable of figuring out right now
[2022-10-03T17:11:17Z] <midfavila> tinycc doesn't generate executables that use motif or athena properly
[2022-10-03T17:11:29Z] <midfavila> that's not something I can fix
[2022-10-03T17:11:29Z] <midfavila> xwx
[2022-10-03T17:12:08Z] <sad_plan> well I cant help you there unfortunatly. 
[2022-10-03T17:12:14Z] <sad_plan> do you have to use those though?
[2022-10-03T17:12:45Z] <sad_plan> I mean, if I cant use tool x, then sometimes I look for tool y or z instead, that might fit the bill
[2022-10-03T17:12:59Z] <midfavila> do i have to use athena/motif, or do i have to use tcc?
[2022-10-03T17:13:07Z] <sad_plan> athena/motif
[2022-10-03T17:13:07Z] <midfavila> technically no to the former, yes for the latter
[2022-10-03T17:13:17Z] <midfavila> i could just use programs that exclusively use xlib directly
[2022-10-03T17:13:20Z] <midfavila> but that's a horrible idea
[2022-10-03T17:13:34Z] <midfavila> motif and athena are the only toolkits that my system can build
[2022-10-03T17:13:34Z] <midfavila> so
[2022-10-03T17:14:11Z] <sad_plan> but they dont generate executables, so dont build properly now do they? but whats wrong with using xlibs tools?
[2022-10-03T17:14:34Z] <sad_plan> I mostly like tools that depend purly on xlibs, as theyre likely simpler to build statically..
[2022-10-03T17:14:44Z] <midfavila> the code is valid and some athena programs work as they should
[2022-10-03T17:14:45Z] <sad_plan> some are anyway, not everyone
[2022-10-03T17:14:53Z] <midfavila> this is a problem in tcc that needs to be resolved
[2022-10-03T17:14:58Z] <sad_plan> hm, ok
[2022-10-03T17:15:16Z] <midfavila> anyway, while i can appreciate that mindset, going toolkit-less isn't viable for larger-scale projects, I think
[2022-10-03T17:18:53Z] <sad_plan> im not saying you should drop something you initially need, but if some other tool can accomplish what you want, why not give that a try? I get that some tools might not be easily replacable though.
[2022-10-03T17:19:57Z] <sad_plan> also dont waste too much time on 1 issue. if you cant figure it out, do something else for some time, then come back to it afterwards
[2022-10-03T17:20:21Z] <sad_plan> I do that all the time. makes troublesome issues.. abit less troublesome imo
[2022-10-03T17:20:37Z] <wael[m]> illiliti: why does mdev still have to run as a service when baseinit specifies mdev to kernel via /proc/sys/kernel/hotplug
[2022-10-03T17:22:22Z] <illiliti> because mdev need to listen to uevents
[2022-10-03T17:22:40Z] <illiliti> /proc/sys/kernel/hotplug is an old way for that
[2022-10-03T17:22:53Z] <illiliti> it can fork bomb system
[2022-10-03T17:23:11Z] <illiliti> because it fork/execs mdev for each uevent
[2022-10-03T17:23:49Z] <illiliti> testuser[m]: mirror to github doesn't seem to work?
[2022-10-03T17:24:06Z] <testuser[m]> illiliti: I forgot to sync it
[2022-10-03T17:24:11Z] <testuser[m]> Codeberg interval is disabled
[2022-10-03T17:24:17Z] <testuser[m]> So i have to click the mirror. Button manually
[2022-10-03T17:24:27Z] <illiliti> got it
[2022-10-03T17:26:25Z] <testuser[m]> I'd set up a cron job but the endpoint for triggering push mirror is only going to be available in the next gitea version
[2022-10-03T17:26:28Z] <testuser[m]> It's present in latest git
[2022-10-03T17:28:31Z] <testuser[m]> Synced all repos
[2022-10-03T17:31:21Z] <phoebos> why does codeberg add so many crap tags to merge commit message
[2022-10-03T17:32:03Z] <testuser[m]> Idk
[2022-10-03T17:32:25Z] <testuser[m]> Ask on #codeberg.org:matrix.org 
[2022-10-03T17:50:41Z] <phoebos> eh
[2022-10-03T17:52:09Z] * testuser[m] uploaded an image: (11KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.pratham.cc/WqsxpQQmIbeMAhuZZHzFIHvc/image.png >
[2022-10-03T17:52:11Z] <testuser[m]> It's a gitea setting
[2022-10-03T18:13:27Z] <illiliti> is it possible to drop python packages from unbundle branch?
[2022-10-03T18:14:08Z] <testuser[m]> illiliti: why
[2022-10-03T18:14:11Z] <testuser[m]> mesa needs mako for codegen
[2022-10-03T18:14:15Z] <testuser[m]> templation
[2022-10-03T18:14:25Z] <testuser[m]> docutils can be remover
[2022-10-03T18:14:47Z] <testuser[m]> But you'll still have markupsafe and mako
[2022-10-03T18:22:50Z] <illiliti> i would like to keep repos free of python packages
[2022-10-03T18:23:05Z] <illiliti> there's no rush to drop them
[2022-10-03T18:25:36Z] <illiliti> and this is not a blocker also
[2022-10-03T18:25:49Z] <illiliti> we could merge unbundle branch once it done
[2022-10-03T18:27:14Z] <illiliti> just having python-free repo would be good for general sanity
[2022-10-03T18:31:32Z] <illiliti> at least making it clear that they are present solely as dependencies for mesa, mpv would be enough too
[2022-10-03T18:32:12Z] <illiliti> and not intended or guaranteed to work with normal use cases
[2022-10-03T18:35:31Z] <illiliti> btw has anyone investigated netbsd patch that removes nodejs dep for firefox?
[2022-10-03T18:36:25Z] <testuser[m]> You'd have to generate the nodejs junk outside 
[2022-10-03T18:36:27Z] <testuser[m]> Just like openssl
[2022-10-03T18:36:46Z] <illiliti> it is generated already
[2022-10-03T18:37:02Z] <testuser[m]> But we have to update it
[2022-10-03T18:37:20Z] <illiliti> true but how often
[2022-10-03T18:37:33Z] <testuser[m]> However often devtools and stuff are updated
[2022-10-03T18:37:35Z] <testuser[m]> I'll check the exact files