09:21:43 dkeav: between major upgrades you definitely wanna read it. 09:33:02 <|cos|> Did `pkg --dry-run pkg` change exit codes with 15.0, pkgbase or similar? I'm barely seeing any exit codes at all documented for pkg on https://man.freebsd.org/ for neither 14.4 or 15.{0,1}. 09:34:51 <|cos|> I guess the more interesting question is, how do one best automate creation of new boot environments? I essentially run the above named construct, but it appears I have not gotten a single bootenv since reinstalling with pkgbase. 09:36:03 <|cos|> (and, yes. i do mean `pkg upgrade --dry-run pkg`, it's not a question about invalid syntax outside of irc.) 09:39:04 you create them yourself with bectl. 09:42:24 <|cos|> of course. but does it really need to be a concious decision and an active manual step? with 14.x the return code of the construct above made the decision and triggered running bectl for me. 09:42:44 yes, i believe so 09:44:44 <|cos|> that's quite a regression in usability. but i guess if `pkg-upgrade`'s behaviour was never documented, i realize it was risky of me to rely on it. 09:45:18 maybe hang around for someone more knowledgeable to chime in. thats what i gathered from the docs though. 09:57:26 <|cos|> i guess i'll use `[ "$( pkg version --remote --match-name pkg --like '<' )" ]` instead of checking `pkg-upgrade`'s return status, as that is documented and works with 14.4 and 15.1 both. 09:59:08 |cos|: pkg does not give a useful return status? 10:02:05 <|cos|> Riviera: It used to with 14.x, but I fail to get it under 15.x installed using pkgbase. Not a single bootenv created since I installed this daily driver laptop in April. 10:03:13 <|cos|> Which I guess shows how rock solid FreeBSD has ran since I didn't notice until now... 10:03:20 hehe 10:03:27 well i can't test right now sadly 10:03:32 but ok :) 10:08:28 <|cos|> I guess it might technically not be due to the FreeBSD release, but ports since that's where pkg comes from. If reinstalling the packages from /var/cache/pkg on a host which has history, behavious appears to have changed between 2.3.1_1 and 2.4.2. 13:28:21 SYSADMINDAY >_ 13:31:03 Does that mean we get the day off? Especially since it's Friday? 13:33:24 sure 13:55:37 No get back to work and we need you here over the weekend. 14:06:46 skered: Read-only weekend! Nothing to do. Going home. 14:14:18 release 15.1-P2 is available 14:50:58 polarian: did you try moving devinit() down, or did you decide that wasn't feasible? 15:25:30 Does anybody know if geo cdn is working ok? I'm having issues trying to update pkg and base system. 15:39:15 s2r: What sort of errors are you seeign? 15:46:17 can't fetch any file, 15:46:33 pkg update stalls and does nothing. 15:47:26 "Updating FreeBSD-ports repository catalogue..." and nothing... 16:04:26 s2r: works for me. I was able to do update and upgrade, no issues. Not that I had anything to upgrade. 16:09:07 upgraded to p2 this morning, no issue 16:12:10 I can't even connect to https://pkg.freebsd.org/FreeBSD:15:amd64/base_release_1 with firefox... 16:12:20 I will try from a remote VPS. 16:19:47 Same /usr/local/etc/pkg/repos/FreeBSD.conf from work, works fine.... I will need to call my isp. 16:22:48 yep 16:23:07 are you using isp's dns? 16:28:55 Anyone on a pkg base system that has not upgraded to p2 yet? 16:29:35 If so what does this return? pkg upgrade -qn -r FreeBSD-base 16:30:01 Assuming your base repo is FreeBSD-base 16:35:26 dkeav no, local_unbound 16:51:21 skered: I'm on 14.4p8 would that help? 16:52:49 I'm seeing tcp syn packets but nothing back. 16:56:27 s2r: does the destination IP respond to pings? traceroute? 16:57:01 mns: Are you using pkg base? 16:57:43 spork_css_ no PONGs. 16:58:07 er well no. Unless if you have the 15 repo I wouldn't expect that to give me what I'm looking for which is a 15.x to 15.1-p2 update dry run. 16:58:16 spork_css_ I'm running mtr to check where the traffic is blocked. 16:58:29 skered: yes 16:59:21 skered: that returned nothing for me 17:47:37 i wonder if some ip's from your isp's block have been naughty, like part of a botnet etc and ended up in a blocklist 17:56:01 dkeav I've just talked to the isp, the might change my public IP. 17:57:02 is that something you keep track of, does your IP change regularly or does it stay pretty sticky, like mine nearly never changes but I don't have a static lease or anything 17:57:32 i just wonder if you ended up getting an IP of a previous owner who's router or some IOT device is in a botnet or something 17:59:22 dkeav I pay for a fixed IP, maybe a range was blocked, 17:59:33 yea 18:13:40 s2r: pop it in https://multirbl.valli.org (it's "for mailservers" but generally can help show if you've got an IP someone previously abused) 18:14:31 quick scan of the pkg manpage and I'm not seeing a way to manually specify a host/IP... I have to be missing it, right? 18:25:39 s2r: also worth checking on https://www.abuseipdb.com/ 20:58:07 I can reach pkg0.nyi.freebsd.org but with I try to do a pkg update -f I get "SSL certificate subject does not match host pkg0.nyi.freebsd.org" I will check abuseipdb 20:58:42 "This IP was reported 0 times. Confidence of Abuse is 0%:" 21:20:32 SSL cert issue could mean the time is off for some reason? 22:05:07 I booted that pc today and did a service ntp fetch just in case but I do have ntpd_sync_on_start="YES" in rc.conf 23:07:36 scoobybejesus: if you pop "https://pkg0.nyi.freebsd.org/" into a browser you'll get a cert mismatch as well, but also I guess you're not supposed to access it by that name since there's no SSL cert there (IMHO, there should be). 23:08:44 CN is "pkg.freebsd.org", and there's an alternate name for "pkgmir.geo.freebsd.org" but none for the actual hostname.