dkeav: between major upgrades you definitely wanna read it.

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 man.freebsd.org for neither 14.4 or 15.{0,1}.

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.

(and, yes. i do mean `pkg upgrade --dry-run pkg`, it's not a question about invalid syntax outside of irc.)

you create them yourself with bectl.

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.

yes, i believe so

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.

maybe hang around for someone more knowledgeable to chime in. thats what i gathered from the docs though.

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.

|cos|: pkg does not give a useful return status?

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.

Which I guess shows how rock solid FreeBSD has ran since I didn't notice until now...

hehe

well i can't test right now sadly

but ok :)

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.

SYSADMINDAY >_

Does that mean we get the day off? Especially since it's Friday?

sure

No get back to work and we need you here over the weekend.

skered: Read-only weekend! Nothing to do. Going home.

release 15.1-P2 is available

polarian: did you try moving devinit() down, or did you decide that wasn't feasible?

Does anybody know if geo cdn is working ok? I'm having issues trying to update pkg and base system.

s2r: What sort of errors are you seeign?

can't fetch any file,

pkg update stalls and does nothing.

"Updating FreeBSD-ports repository catalogue..." and nothing...

s2r: works for me. I was able to do update and upgrade, no issues. Not that I had anything to upgrade.

upgraded to p2 this morning, no issue

I can't even connect to pkg.freebsd.org/FreeBSD:15:amd64/base_release_1 with firefox...

I will try from a remote VPS.

Same /usr/local/etc/pkg/repos/FreeBSD.conf from work, works fine.... I will need to call my isp.

yep

are you using isp's dns?

Anyone on a pkg base system that has not upgraded to p2 yet?

If so what does this return? pkg upgrade -qn -r FreeBSD-base

Assuming your base repo is FreeBSD-base

dkeav no, local_unbound

skered: I'm on 14.4p8 would that help?

I'm seeing tcp syn packets but nothing back.

s2r: does the destination IP respond to pings? traceroute?

mns: Are you using pkg base?

spork_css_ no PONGs.

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.

spork_css_ I'm running mtr to check where the traffic is blocked.

skered: yes

skered: that returned nothing for me

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

dkeav I've just talked to the isp, the might change my public IP.

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

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

dkeav I pay for a fixed IP, maybe a range was blocked,

yea

s2r: pop it in multirbl.valli.org (it's "for mailservers" but generally can help show if you've got an IP someone previously abused)

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?

s2r: also worth checking on abuseipdb.com

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

"This IP was reported 0 times. Confidence of Abuse is 0%:"

SSL cert issue could mean the time is off for some reason?

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

scoobybejesus: if you pop "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).

CN is "pkg.freebsd.org", and there's an alternate name for "pkgmir.geo.freebsd.org" but none for the actual hostname.