💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2021-02-09.txt captured on 2022-07-17 at 03:14:48.
⬅️ Previous capture (2021-12-17)
-=-=-=-=-=-=-
2021-02-09T00:30:08 #kisslinux <Rio6> oh hay did repology get updated?
2021-02-09T00:30:37 #kisslinux <noocsharp> it appears so
2021-02-09T01:19:44 #kisslinux <acheam> yay
2021-02-09T04:50:26 #kisslinux <testuser[m]_> acheam: could you give me "owner" permissions in kiss-community ? I'd like to invite a few active maintainers
2021-02-09T05:43:55 #kisslinux <acheam> testuser[m]_: yep, I'll do it tomorrow. I would refrain from unnecessarily adding people to the org, but rather just to the relevant repos
2021-02-09T05:45:58 #kisslinux <testuser[m]_> sure
2021-02-09T07:06:40 #kisslinux <testuser[m]_> dilyn: did you experience any issues with packages after dropping json-glib from glib?
2021-02-09T13:06:54 #kisslinux <dilyn> none so far; I think it's just required by certain gtk+3 apps
2021-02-09T13:07:20 #kisslinux <dilyn> arch may or may not be an accurate reference
2021-02-09T13:07:21 #kisslinux <dilyn> https://archlinux.org/packages/extra/x86_64/json-glib/
2021-02-09T13:18:38 #kisslinux <buffet> Sup, just checking if Dylan is back. Is he?
2021-02-09T13:26:52 #kisslinux <testuser[m]_> buffet: no
2021-02-09T13:27:16 #kisslinux <buffet> Sad!
2021-02-09T13:33:39 #kisslinux <testuser[m]_> dilyn: hmm, I'll probably let it be then since flatpak and pantheon stuff seem to require it
2021-02-09T13:34:26 #kisslinux <dilyn> yeah i luck out because I use basically zero applications on my laptop :v
2021-02-09T15:46:32 #kisslinux <yoba> =)
2021-02-09T15:47:51 #kisslinux <testuser[m]_> dilyn: could you check if kiss-community/repo-community#85 happens for you on `chrome://flags` ?
2021-02-09T17:01:05 #kisslinux <acheam> testuser[m]_: you should be an owner now
2021-02-09T17:18:50 #kisslinux <testuser[m]_> @freenode_acheam:matrix.org thanks!
2021-02-09T17:32:57 #kisslinux <dilynm> acheam: will test later (provided feedback on issue); my kernel somehow lost efistub support yet again so I'm building my fallback atm :v too many issues to fix on this system smh
2021-02-09T17:34:57 #kisslinux <dilynm> Sry that was testuser[m]_:
2021-02-09T17:41:18 #kisslinux <testuser[m]_> dilynm: thanks for your input, i wanted to see if the issue was caused by system icu/libxml but you're using bundled libs and it still seems to happen for you... but on my old builds with less system libs it just werks
2021-02-09T17:41:31 #kisslinux <testuser[m]_> and it indeed seems to be js related cuz i havent noticed it much at all since i block it everywhere
2021-02-09T17:44:54 #kisslinux <dilynm> I may or may not have is enabled idr :S
2021-02-09T17:45:03 #kisslinux <dilynm> s/is/js/
2021-02-09T17:45:03 #kisslinux <kissbot> <dilynm> I may or may not have js enabled idr :S
2021-02-09T17:53:29 #kisslinux <testuser[m]_> hmm
2021-02-09T17:55:44 #kisslinux <testuser[m]_> So... how should we handle the ~50 outdated packages in community? Most of the maintainers haven't responded so should we assume that they don't use KISS anymore and just have 2-3 people take over maintainership for some and drop some ? What does everyone think
2021-02-09T17:59:34 #kisslinux <tracer> Hi everybody. Could some tell me if xdpyinfo is in any available package?
2021-02-09T18:04:01 #kisslinux <testuser[m]_> doesn't seem to be packaged in kiss https://github.com/archlinux/svntogit-packages/blob/packages/xorg-xdpyinfo/trunk/PKGBUILD
2021-02-09T18:04:56 #kisslinux <tracer> thx testuser[m]_
2021-02-09T18:05:12 #kisslinux <aarng> testuser[m]_: can we ping the maintainers, give them a grace period and then simply remove packages?
2021-02-09T18:11:17 #kisslinux <aarng> > Most of the maintainers haven't responded
2021-02-09T18:11:34 #kisslinux <aarng> kinda missed this, but where did they not respond?
2021-02-09T18:12:35 #kisslinux <testuser[m]_> I had made an issue on kisslinux/community tagging each package along with maint
2021-02-09T18:12:35 #kisslinux <testuser[m]_> its still open
2021-02-09T18:14:03 #kisslinux <testuser[m]_> #1681
2021-02-09T18:14:06 #kisslinux <aarng> will have a look, I had assumed I would be tagged too, since I should have outdated packages according to repology
2021-02-09T18:15:01 #kisslinux <testuser[m]_> you're tagged for a couple of packages too
2021-02-09T18:15:48 #kisslinux <aarng> weird, got no notification or anything
2021-02-09T18:20:07 #kisslinux <aarng> oh, it's an older one, thought it was more recent
2021-02-09T18:20:28 #kisslinux <testuser[m]_> I've been editing the list occasionally
2021-02-09T18:21:17 #kisslinux <aarng> I updated since then, but I've been slacking a bit with more recent package updates but I will get to it
2021-02-09T18:21:53 #kisslinux <testuser[m]_> The list is a bit smaller now since I had scripted the bumping quite a lot of packages which didn't have any patches etc. see kiss-community/repo-community#74
2021-02-09T18:21:58 #kisslinux <aarng> like if you have no commits since you originally tagged people, I'd say we should get rid of those packages
2021-02-09T18:22:16 #kisslinux <aarng> nice
2021-02-09T18:55:50 #kisslinux <dilynm> If they haven't said anything, just drop the packages
2021-02-09T18:56:33 #kisslinux <dilynm> Check the dependencies first of course but like, there's no good reason to keep outdated packages that aren't used by anything
2021-02-09T18:57:55 #kisslinux <midfavila1> nothing to suggest so on his github
2021-02-09T18:57:57 #kisslinux <midfavila1> fuck
2021-02-09T18:58:06 #kisslinux <midfavila1> way too late to respond to that message
2021-02-09T18:58:15 #kisslinux <midfavila1> not noticing the position of scrollbars is fun
2021-02-09T18:58:40 #kisslinux <aarng> uhm, so I bumped versions for 2 of my packages. But since I used the same branches for my changes, the new commits end up in the old pull requests for those packages
2021-02-09T18:58:51 #kisslinux <midfavila1> anyway UXP had its compiler version bumped up so I packaged Nuegia in case any of you are interested in that
2021-02-09T18:59:06 #kisslinux <midfavila1> it's just a binary for now but I'll likely put up a source package in the next few days
2021-02-09T19:11:04 #kisslinux <dilyn> omg i forgot i had set that quit message on my phone. incredible.
2021-02-09T19:13:57 #kisslinux <aarng> dilyn, what I wrote earlier, will commits to old PRs still get to you guys' attention for manual merging?
2021-02-09T19:19:48 #kisslinux <dilyn> technically dylan would disallow that and I agree with that. You should close old PRs and submit a new PR on a new branch
2021-02-09T19:19:56 #kisslinux <dilyn> keeps commits cleaner
2021-02-09T19:20:15 #kisslinux <dilyn> (no reason to include incremental bumps all on a single PR; if the last bump got missed there's no reason to include it)
2021-02-09T19:20:20 #kisslinux <aarng> okey, will do
2021-02-09T19:20:39 #kisslinux <aarng> yeah makes sense
2021-02-09T19:28:40 #kisslinux <dilyn> why does it seem like every MIT licensed alternative to GPL is written in rust
2021-02-09T19:28:44 #kisslinux <dilyn> is my license... bad?
2021-02-09T20:30:02 #kisslinux <acheam> lol
2021-02-09T20:30:38 #kisslinux <acheam> I gotta say, I still don't really get the aversion to anything not C/POSIX here
2021-02-09T20:34:48 #kisslinux <dilyn> rust stuff is just hard to package (in keeping with the guidestones at least), and rust itself takes forever to build
2021-02-09T20:35:13 #kisslinux <dilyn> this clipboard implementation requries more than 80 crates, for instance. and it takes quote a while to build
2021-02-09T20:55:07 #kisslinux <retrohacker> @mcpcpc @aarng: given a config file with a list of channels (optionally a nickname, server, and port), maintain a log for each channel as a separate file in a directory: https://termbin.com/ugrz
2021-02-09T20:55:52 #kisslinux <retrohacker> Maintains a separate connection for each. Could probably reuse the same connection.
2021-02-09T21:03:02 #kisslinux <aarng> retrohacker: pretty good
2021-02-09T21:03:29 #kisslinux <aarng> look up /dev/tcp, you could replace netcat alltogether
2021-02-09T21:06:07 #kisslinux <aarng> oh and I think you basically have to PONG the original parameter from the PING
2021-02-09T21:06:33 #kisslinux <aarng> I'd assume not all ircd's will allow you to only respond with an empty PONG
2021-02-09T21:09:09 #kisslinux <retrohacker> I thought so too. But this worked on freenode. Haven't tested on anything else.
2021-02-09T21:14:52 #kisslinux <retrohacker> I wonder if we could create a file alongside `.{log,error}` which would post all text written to the file to the channel. Would make it an fs based IRC client. Something like `tail -f "${FILE}.input" | prefix w/ IRC command to post to channel > "${STDIN}"
2021-02-09T21:20:31 #kisslinux <aarng> that would at least prevent input being garbled as new input appears
2021-02-09T21:20:51 #kisslinux <aarng> I wonder if rlwrap fixes that though
2021-02-09T21:34:31 #kisslinux <mcpcpc[m]> <acheam "I gotta say, I still don't reall"> for me, i think it’s pure laziness. i jump from platform to platform quite frequently. so i like it when my tools “just work”.
2021-02-09T21:35:33 #kisslinux <mcpcpc[m]> ahh will take a look at the ircc suggestions in a bit. have my 40min work commute ahead of me.
2021-02-09T21:48:45 #kisslinux <acheam> mcpcpc[m]: Sure, but Python, Rust, and Haskell, the three I see the most complaints about all support more platforms than I have ever heard of before. I kind of odubt that you are regularly jumping between platforms like z/OS, Haiku, and Solaris for prime support to matter.
2021-02-09T21:49:41 #kisslinux <mcpcpc[m]> acheam: ah. gotcha.
2021-02-09T21:57:12 #kisslinux <mcpcpc[m]> <aarng "I wonder if rlwrap fixes that th"> i think played around with that in kirc. it does work. not all vte’s implement rlwrap though, so it’s a crap shoot whether it works or not.
2021-02-09T21:58:36 #kisslinux <mcpcpc[m]> * > <@freenode_aarng:matrix.org> I wonder if rlwrap fixes that though
2021-02-09T21:58:36 #kisslinux <mcpcpc[m]> i think i played around with that in kirc. it does work. not all vte’s implement rlwrap though, so it’s a crap shoot whether it works or not.
2021-02-09T21:58:55 #kisslinux <aarng> I see, bummer
2021-02-09T23:19:25 #kisslinux <sad_plan> Testuser: seeing as there is such a big number of outdated packages, would there perhaps be of interest in creating an archive of dropped packages? Just throw them in there, and if someone wishes to maintain them, theyll create a PR to readd them or something along those lines.
2021-02-09T23:19:59 #kisslinux <dilyn> isn't that just git log | grep $pkg ?
2021-02-09T23:20:55 #kisslinux <sad_plan> I guess it is. Im not too familiar with git in the first place. I just had the idea, so I threw it out there
2021-02-09T23:21:02 #kisslinux * sad_plan shrugs
2021-02-09T23:22:46 #kisslinux <dilyn> It's a fine idea! I'm just worried about repository size
2021-02-09T23:22:57 #kisslinux <dilyn> and clutter
2021-02-09T23:23:39 #kisslinux <dilyn> and repology might try to track that archive? not sure, but then it would defeat the point of dropping orphaned packages
2021-02-09T23:46:14 #kisslinux <acheam> IMO, a slimmer, fully up to date repo is far better than a fat out of date one
2021-02-09T23:47:01 #kisslinux <acheam> If maintainers haven't been in contact with either kisslinux or kiss-community, and have not been able to be contacted, we could just drop the package, it wouldn
2021-02-09T23:47:07 #kisslinux <acheam> 't be hard to bring it back from git history
2021-02-09T23:47:52 #kisslinux <acheam> And we'd stick to a strong core base of packages, rather than a loose mess of half-maintained packages where you have to wonder whether or not what you are downloading is the latest, secure version