gemini - kennedy.gemi.dev

💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › kisslinux-2022-10-23.txt captured on 2024-05-26 at 16:04:54.
-=-=-=-=-=-=-
[2022-10-23T03:26:00Z] <wael_> Hi
[2022-10-23T04:22:01Z] <sad_plan> o/
[2022-10-23T04:33:07Z] <testuser[m]> Hi
[2022-10-23T04:34:41Z] <sad_plan> why does iproute2 list libcap and iptables as deps? i doesnt need any of them to build
[2022-10-23T04:35:26Z] <sad_plan> only needs linux-headers. libelf needs a tiny fix to bypass it
[2022-10-23T04:40:18Z] <sad_plan> testuser[m]: http://0x0.st/oxWz.patch only thing needed to bypass using libelf.
[2022-10-23T06:16:09Z] <sad_plan> wait, does codeberg not accept ssh keys as signingkeys?
[2022-10-23T06:36:36Z] <testuser[m]> It does
[2022-10-23T06:37:35Z] <sad_plan> hm. I just got an error when trying to add mine
[2022-10-23T06:37:58Z] <testuser[m]> send
[2022-10-23T06:38:01Z] <sad_plan> although I cant even get git to recognize them either tbh 
[2022-10-23T06:38:45Z] <testuser[m]> are u uploading private key to codeberg 
[2022-10-23T06:38:55Z] <sad_plan> no, public
[2022-10-23T06:40:30Z] <sad_plan> error: No private key found for "/tmp/.git_signing_key_tmpbg4JMA"?
[2022-10-23T06:40:38Z] <sad_plan> I have added my key to gitconfig though
[2022-10-23T06:41:36Z] <testuser[m]> send
[2022-10-23T06:41:46Z] <testuser[m]> I had the same but made wrong gitconfig
[2022-10-23T06:41:57Z] <testuser[m]> Didn't u ask this like 2 weeks back
[2022-10-23T06:43:06Z] <sad_plan> not directly. I tried to use dropbear with github, which works, but it cant sign commits. doesnt have that feature. mcf created a patch for signing, but not verifying.
[2022-10-23T06:43:25Z] <sad_plan> http://0x0.st/oxWx.txt
[2022-10-23T06:44:33Z] <testuser[m]> Why do u have the same key 3 times
[2022-10-23T06:45:10Z] <sad_plan> mustve been messed up when trying to add the key
[2022-10-23T06:45:32Z] <sad_plan> which of them is initially essential? only the global one?
[2022-10-23T07:05:40Z] <sad_plan> I fixed it
[2022-10-23T07:10:41Z] <sad_plan> now just try again to add the key to codeberg
[2022-10-23T07:37:29Z] <wael_> codeberg more like
[2022-10-23T07:37:36Z] <wael_> cantsearchbecausegitea
[2022-10-23T07:42:27Z] <sad_plan> lol
[2022-10-23T07:45:42Z] <testuser[m]> sad_plan: ill fix iproute2
[2022-10-23T07:45:49Z] <testuser[m]> wireguard seems to work fine without iptables in iproute
[2022-10-23T07:56:06Z] <sad_plan> nice
[2022-10-23T08:07:54Z] <sad_plan> ffs, is the option to use ssh key as signing key some place else than in the ssh/gpg keys section? adding the ssh key to gpg section obviously dont work I mean
[2022-10-23T08:07:56Z] <sad_plan> on codeberg
[2022-10-23T08:09:41Z] <sad_plan> 'Can not verify your GPG key: failed to parse gpg key openpgp: invalid argument: no armored data found' do I have to verify the ssh key?
[2022-10-23T08:56:11Z] <testuser[m]> what
[2022-10-23T08:56:32Z] <sad_plan> thats the error I get when trying to add the ssh keys to the gpg section
[2022-10-23T08:56:37Z] <sad_plan> for signing
[2022-10-23T08:56:37Z] <testuser[m]> bruh theres 2 sections manage ssh key and manage gpg key
[2022-10-23T08:56:45Z] <testuser[m]>  why would u add ssh key to gpg...
[2022-10-23T08:57:25Z] <sad_plan> signing. theres no indication wether I can use ssh keys to sign. I now have it enabled in git, but codeberg wont recognize it, because its not added to codeberg
[2022-10-23T08:57:37Z] <testuser[m]> then add it
[2022-10-23T08:57:48Z] <sad_plan> I have added the ssh key there
[2022-10-23T08:58:19Z] <sad_plan> but codeberg wont recognize it as a signing key. so itll just say unverified or w/e it says on codeberg when a commit is unsigned
[2022-10-23T08:58:48Z] * testuser[m] uploaded an image: (256KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.pratham.cc/UyADnmKKuJQsnaoeJMnUeXre/2022-10-23T14%3A27%3A39%2C697393702%2B05%3A30.png >
[2022-10-23T08:59:27Z] <testuser[m]> u probably didnt verify it
[2022-10-23T09:00:14Z] <testuser[m]> it gives u a blob to sign
[2022-10-23T09:01:21Z] <sad_plan> no I tried that, but it errors out on ssh-askpass not existing. then incorrect pasphrase supplied, but it never prompts, because ssh_askpass isnt found
[2022-10-23T09:03:23Z] <phoebos> sad_plan: you might find it helps to ssh-add your key
[2022-10-23T09:05:12Z] <sad_plan> thought I did that already
[2022-10-23T09:05:25Z] <sad_plan> oh, so noooow it worked
[2022-10-23T09:21:12Z] <sad_plan> ok, so the ssh key is verified now, but this doesnt really solve the ssh key for signing
[2022-10-23T09:21:15Z] * sad_plan sighs
[2022-10-23T10:06:40Z] <testuser[m]> hmm b3 change broke a lot of stuff in etcsums
[2022-10-23T10:07:11Z] <testuser[m]> it doesnt save file as *.new if it already exists if pkg was never installed, and saves files as *.new if they never existed before
[2022-10-23T10:08:00Z] <testuser[m]> but it didnt change any of that code
[2022-10-23T10:10:41Z] <sad_plan> I was wondering when that patch was going into a new release, but I suppose I got my answer :p not yet
[2022-10-23T10:16:55Z] <testuser[m]> https://termbin.com/ivzf
[2022-10-23T10:17:36Z] <sad_plan> hm. I dont belive I had that issue. lemme check
[2022-10-23T10:19:21Z] <sad_plan> hm I dont get any of that by install the regular baselayout
[2022-10-23T10:19:54Z] <sad_plan> nor baseinit
[2022-10-23T10:21:04Z] <testuser[m]> it only happens if pkg wasnt installed bfore
[2022-10-23T10:21:14Z] <sad_plan> ah, ok lemme check
[2022-10-23T10:23:09Z] <sad_plan> nop, still nothing
[2022-10-23T10:23:14Z] <testuser[m]> got it
[2022-10-23T10:23:23Z] <testuser[m]> its cuz length check doesn't handle the case where its empty
[2022-10-23T10:23:28Z] <testuser[m]> sum_old
[2022-10-23T10:23:31Z] <testuser[m]> so hash is never unset
[2022-10-23T10:23:38Z] <testuser[m]> in that caes
[2022-10-23T10:26:41Z] <testuser[m]> fixed
[2022-10-23T10:26:48Z] <sad_plan> nice
[2022-10-23T10:27:00Z] <testuser[m]> badly need a test suite
[2022-10-23T10:28:17Z] <testuser[m]> https://github.com/TAAPArthur/pkgmanager/tree/master/Tests can start by shamelessly stealing this
[2022-10-23T10:29:32Z] <sad_plan> just run the scripts from top to bottom you mean?
[2022-10-23T10:30:00Z] <testuser[m]> wat
[2022-10-23T10:30:36Z] <sad_plan> isnt that what you ment? *testing*
[2022-10-23T10:31:00Z] <testuser[m]> automated tests
[2022-10-23T10:31:04Z] <testuser[m]> yeah
[2022-10-23T10:45:18Z] <phoebos> testuser[m]: nice find. i noticed that when we were testing tar perms
[2022-10-23T10:48:57Z] <testuser[m]> phoebos for fixing etcsums do I remove the reversal from tar generation itself so that broken sums never make their way into system or re-reverse / unreverse them as needed in other places?
[2022-10-23T10:49:28Z] <testuser[m]> i think first is OK cuz u can't break what's already broken
[2022-10-23T10:50:55Z] <testuser[m]> it also needs to handle files being skipped from checksum generation eg /etc/sv/*/supervise files
[2022-10-23T10:51:15Z] <testuser[m]> otherwise it compares more entries than exist in etcsums which again breaks everything
[2022-10-23T10:52:14Z] <illiliti> first is better
[2022-10-23T10:54:36Z] <phoebos> yes first sounds better
[2022-10-23T10:54:44Z] <phoebos> how do you identify broken sums?
[2022-10-23T10:55:16Z] <testuser[m]> wc -l etcsums > 1 
[2022-10-23T10:57:30Z] <phoebos> ah
[2022-10-23T11:22:47Z] <testuser[m]> phoebos: test -h vs test -L
[2022-10-23T11:23:29Z] <testuser[m]> their descriptions are character for character same
[2022-10-23T11:23:30Z] <testuser[m]> sus
[2022-10-23T11:27:28Z] <illiliti> -h is preferred
[2022-10-23T11:28:16Z] <testuser[m]> any reason
[2022-10-23T11:29:29Z] <illiliti> openbsd man page says so
[2022-10-23T11:30:21Z] <illiliti> freebsd says otherwise
[2022-10-23T11:30:24Z] <illiliti> bruh
[2022-10-23T11:30:27Z] <testuser[m]> lol
[2022-10-23T12:01:21Z] <testuser[m]> illiliti: phoebos any idea about solving issue of symlinks in /etc
[2022-10-23T12:01:35Z] <testuser[m]> i thought of just checking -h but that doesn't work for removal if user modifies that file to not be a symlink
[2022-10-23T12:01:49Z] <testuser[m]> other way is just to echo dummy value for that file in checksums
[2022-10-23T12:01:51Z] <testuser[m]> like SYMLINK
[2022-10-23T12:02:03Z] <illiliti> no need to be too smart
[2022-10-23T12:02:18Z] <illiliti> if user modifies something, that's their problem
[2022-10-23T12:02:32Z] <illiliti> handle basic case
[2022-10-23T12:04:13Z] <testuser[m]> so just -h check
[2022-10-23T12:19:29Z] <phoebos> we target posix, -h and -L are equivalent 
[2022-10-23T12:20:07Z] <testuser[m]> also this seems like a valid bug to me since it has a cascading effect on all other entries, maybe we could just add something like hash of /dev/null in place of all symlink files? That way there's no chance for mismatch of no. of entries and no.of files checked so at most only symlinks will be broken. Also easier than adding -h checks to 3-4 places
[2022-10-23T12:21:01Z] <testuser[m]> adding special value like "SYMLINK" would need adhoc logic in b3() itself which is bad
[2022-10-23T12:23:14Z] <testuser[m]> eg 
[2022-10-23T12:23:14Z] <testuser[m]> https://termbin.com/o9xr
[2022-10-23T12:26:59Z] <illiliti> just ignore symlinks
[2022-10-23T12:29:48Z] <testuser[m]> illiliti but the point is we cant do that without filling in missing lines in etcsums file
[2022-10-23T12:29:55Z] <testuser[m]> https://termbin.com/4h6p 1 line fix
[2022-10-23T12:30:07Z] <testuser[m]> i feel its an ok compromise 
[2022-10-23T12:36:02Z] <testuser[m]> removed directory check, will ignore symlinks altogether otherwise have to special case directory, non existent path, ... etc
[2022-10-23T12:51:14Z] <illiliti> https://github.com/kisslinux/kiss/issues/193
[2022-10-23T13:14:39Z] <testuser[m]> illiliti: wdym
[2022-10-23T13:21:11Z] <testuser[m]> btw what damage do charset.alias and .la files cause that they're hardcoded to be removed in KISS?
[2022-10-23T13:21:48Z] <testuser[m]> oh >  Remove this unneeded file from all packages as it is an endless source of conflicts. This is used with info pages we we do not support.
[2022-10-23T13:32:45Z] <illiliti> dylan said that fix requires refactoring of pkg_remove_files
[2022-10-23T13:33:31Z] <illiliti> which i think the proper option
[2022-10-23T13:34:27Z] <testuser[m]> we can do that later ig, i'd be wary of modifying anything  greater than 2 lines without adding  some tests
[2022-10-23T13:37:56Z] <testuser[m]> lot of stuff needs to be refactored like even removal of existing files in etcsums (removing f2 from f1 f2 f3 in /etc)
[2022-10-23T14:20:18Z] <macslash1[m]> qwhta
[2022-10-23T14:20:52Z] <testuser[m]> why is there no tar library for C other than libarchive :bruh:
[2022-10-23T14:29:00Z] <testuser[m]> https://codeberg.org/kiss-community/kiss/issues/103 thoughts?
[2022-10-23T14:46:51Z] <illiliti> full rewrite in c would be better
[2022-10-23T14:47:32Z] <illiliti> ... something something i have in TODO ...
[2022-10-23T14:49:06Z] <testuser[m]> C rewrite will already be there when the issue gets closed
[2022-10-23T14:49:15Z] <testuser[m]> and u get free libkiss
[2022-10-23T14:51:13Z] <testuser[m]> hmm maybe C stuff should be in it's own repo
[2022-10-23T14:51:43Z] <illiliti> yes
[2022-10-23T15:29:12Z] <midfavila> C stuff should totally be in its own repo
[2022-10-23T16:42:11Z] <wael_> was Dylan ever eventually was going to make a C rewrite
[2022-10-23T16:42:11Z] <wael_> or is he POSIX advocatr
[2022-10-23T17:31:16Z] <midfavila> dylan is the one who started a kiss rewrite iirc
[2022-10-23T17:31:19Z] <midfavila> "k"
[2022-10-23T17:57:18Z] <wael_> in c orrrrrrrrrr
[2022-10-23T19:20:47Z] <testuser[m]> Rust
[2022-10-23T19:20:53Z] <testuser[m]> So good
[2022-10-23T20:06:12Z] <zou41> does anyone know if ehawkvu firefox has webrtc active? I couldn't use some sites the last time because of that
[2022-10-23T20:15:15Z] <testuser[m]> zou41: should be enabled
[2022-10-23T20:15:24Z] <testuser[m]> What issue did u encounter
[2022-10-23T20:16:50Z] <zou41> I'm not running kiss anymore (I want to use it again) but last time sites like discord/slack don't work for calls
[2022-10-23T20:17:14Z] <zou41> and in console warns about webrtc failing
[2022-10-23T20:17:49Z] <zou41> I don't know if it's active or if some package was missing in the my installation
[2022-10-23T20:18:10Z] <testuser[m]> for xorg u shouldn't need anything extra beyond webrtc enabled in ff, which it is
[2022-10-23T20:18:29Z] <testuser[m]> wael: can u check x11 firefox screen sharing
[2022-10-23T21:59:56Z] <phoebos> re: libkiss, i'm concerned about what functionality should be put into a library
[2022-10-23T22:00:00Z] <phoebos> consider kiss-size
[2022-10-23T22:00:24Z] <phoebos> the bit which could be in a library is reading the manifest file
[2022-10-23T22:01:35Z] <phoebos> but the file format is so simple that all we need to do is open $KISS_ROOT/var/db/kiss/installed/pkg/manifest and getline it
[2022-10-23T22:02:33Z] <phoebos> and anything else (eg a function `char **kiss-manifest(char *pkg)` that returns an array of filenames) is more complex
[2022-10-23T22:03:43Z] <phoebos> it's easy and tempting to start writing library functions like that but i think the design of the C rewrite needs careful thought