01:41:48 i'm sort of hoping that between now and 16.0, someone will learn how to use pkgbase and have enough time to wtfm for it 01:43:01 it would be a little awkward if we dropped dist set support and still didn't have any pkgbase docs 01:45:46 I really like the current organization of base upgrading as a cohesive whole. I am sure the system will boot and run. And then upgrade the ports/pkgs. 01:46:20 I am a little worried that putting everything in pkgs to upgrade will upset that robust paradigm. See the "pkg delete -a" issues. 02:26:46 i've always found it awkward, just worked with what i have. 03:03:22 ivy: Yeah. :/ 03:04:11 Although, there has been plenty of talk about separating "pkg" and "pkgbase". That could clear a lot of things up and avoid things such as "pkg delete -a". But, we'll see what comes to fruition. 03:04:31 that will never happen 03:05:48 I can't imagine it happening. But, there does need to be some kind of fail-safe in place to avoid just wiping your system via pkg. 03:06:45 you already can't do that, pkg delete -a will refuse to delete anything as long as you have at least one vital set installed (which always happens in a normal install) 03:07:11 the specific problem that came up before was people using 'pkg delete -af', i.e., 'delete all my installed packages and override all safeguards intended to prevent breaking your system' 03:08:24 Yes. Trying to start from scratch via pkg was never an issue in the past. A "pkg delete -af" might catch a lot of people by surprise. 03:08:29 perhaps pkg delete -fF should be required to delete vital packages, or something like that... there was very little useful discussion about actual solution in the previous thread, just a lot of ranting 03:09:12 Agreed. Lots of ranting and no solutions. An additional flag could be a good solution. 03:11:23 (i don't like pkg ... -f much anyway, i think it's too ungranular and too dangerous to ever use... so reworking that might solve both problems, if someone wanted to) 03:13:57 I don't use "-f" often (unless it's an update/upgrade situation) 03:14:45 But, IIRC, the problem I had when trying to "pkg delete -a" was that I had to accept the removal of the request to delete "vital" packages. 03:15:19 So, 160 or so (Y/n) prompts later, I was able to remove non-base packages. 03:15:27 if you're trying to remove ports, i believe 'pkg -r FreeBSD-ports delete -a' is now supported (not 100% sure there, maybe it's not merged yet) 03:15:48 er, 'pkg delete -a -r FreeBSD-ports', i mean 03:15:53 I believe that's been merged? I haven't tested it, but I did see it. 03:15:58 Yeah. 03:16:41 hm, it's not in 2.6.2 apparently, wonder what's going on there 03:17:13 Once I saw what was happening, I could just ignore "^FreeBSD-\*" packages. Worked fine. But, I can see how mistakes could be made. 03:17:53 Erm? I thought that was merged like 6 weeks ago? 03:30:51 Nope. 03:31:03 I see nothing about it. Bummer. 03:47:07 ek: we might be thinking of pkg-unregister(8), which is what's used for depkgbasify 03:58:47 ivy: Ah, yes. That could be exactly it. 04:32:37 q:q 04:32:45 * kevans runs away 04:48:56 this seems excessively slow: https://people.freebsd.org/~ivy/tmp/pkg-create.txt - what is it doing? hashing? 10:56:17 dch: i see you're maintaining the go-anubis port. ai crawlers seem to have found an expensive gitea endpoint not covered by REQUIRE_SIGNIN_VIEW = expensive, so I'm looking into deploying it. i see it has some kinda meh/tbd data poisoning feature and would rather transparently deliver some cached documents from https://rnsaffn.com/poison3/ – any idea if that's doable? 13:35:45 morning. 14:42:15 jadawin: Howdy 14:45:21 here's a patch for cgit crash on cgit.freebsd.org https://git.zx2c4.com/cgit/commit/?id=0d8e5fbc31e10 15:53:13 hello, just installed KDE plasma ... everything looks smooth, but keyboard layout kinda not working 16:04:23 what parts are not working? 16:13:21 How does one patch KDE2 under FreeBSD? 16:17:36 patch it to do what? 16:24:35 I'm trying to get brightness control to work on this laptop using devd. 16:25:05 All the examples I've found assume the keypress sends "brightness up" or "brighness down", but on this laptop it's sending what it thinks the actual value should be. 16:25:58 Is there a way, in a devd config, to use the value of a "match" rule as an argument to the "action" rule? 16:42:56 i just added backlight to my waybar. but acpi_*.ko often gets those keys to work without devd 16:43:10 (i've not done it with devd) 16:47:26 I've got acpi_video and acpi_wmi loaded. I guess I thought acpi_video was getting it into devd in the first place. 16:49:10 Like, it sees this in devd: !system=ACPI subsystem=Video type=brightness notify=95 16:49:41 I think that's coming from acpi_video? 16:51:30 anth: i am not a devd expert, but if that's the event, i think you can use $notify in the action to get the value? 20:59:43 good day #freebsd 21:00:15 Ok this is weird. After upgrading this one machine to 15, I cannot log in as root, nor does syslogd start. 21:00:30 after spending some time on the tunables, I have 14.4-RELEASE running stable 21:00:30 zerotime: Howdy 21:00:43 On console, after logging in as root and getting the MOTD, it hangs. I press ctrl-T and get "load: 0.21 cmd: sh 5060 [ttydcd] 1.08r 0.00u 0.00s 0% 3520k" 21:00:53 thank you freebsd-devs for another quality release 21:01:10 Similarly I get syslogd hanging in ttydcd - until I remove the output to /dev/console from syslogd.conf 21:01:18 I really appreciate the legacy support! 21:01:27 !inspire 21:01:29 Do what you can, with what you have, where you are. -Theodore Roosevelt [https://zenquotes.io/] 21:01:59 Ltning: did you botch a merge on one of the files 21:02:09 It has booted successfully before today 21:02:11 After -15 21:02:12 good day Ltning 21:02:24 zerotime: last time I tried 15.x (two months ago) it was not able to connect to Ethernet (re0) to obtain IP over DHCP. 14.3 does it well. 21:02:59 checkpoint: I think 14.3 does better than 14.4 21:03:13 I didn't have to mess with any tunables for 14.3 21:03:52 however, 14.4 is still solid 21:04:26 zerotime: I have not tried 14.4 yet. 21:04:55 It just came out a couple days ago 21:05:05 yes 21:05:09 Been having trouble with the ath driver in 14.4 21:05:15 Heh. ttys was indeed theproblem. Copied it from a working box ... 21:05:28 but I finally got it working 21:06:32 It still complains but atleast it fails gracefully now instead of purely crashing 21:08:31 What was the tunable you ended up needing? 21:08:52 (also good day to you too :) ) 21:10:16 I'm not sure which one fixed it yet, but it was a couple handful of patches 21:12:02 mostly dealing with disabling N-mode features 21:13:29 I haven't figured out how to persist it yet - /etc/rc.conf isn't fully working for wlan0 to include all my switches 21:14:10 what are the extra options? 23:15:36 ivy, that was exactly right, thank you!