use curl -LO

Are you inside a jail?

What do you mean by wget works? Seems to be different links.

That's weird. Add -v ?

my end goal is making pip install frida-tools work, so i would be glad if someone could check that pip install frida-tools Collecting frida-tools Using cached frida_tools-13.6.1-py3-none-any.whl Requirement already satisfied: colorama<1.0.0,>=0.2.7 in /usr/local/lib/python3.11/site-packages (from frida-tools) (0.4.6) Collecting frida<17.0.0,>=16.2.2 (from frida-tools) Using cached frida-16.6.6.tar.gz (920 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Requirement already satisfied: prompt-toolkit<4.0.0,>=2.0.0 in /usr/local/lib/python3.11/site-packages (from frida-tools) (3.0.48) Requirement already satisfied: pygments<3.0.0,>=2.0.2 in /usr/local/lib/python3.11/site-packages (from frida-tools) (2.18.0) Collecting websockets<14.0.0,>=13.0.0 (from frida-tools) Using cached websockets-13.1-py3-none-any.whl.metadata (6.8 kB) Requirement already satisfied: wcwidth in /usr/local/lib/python3.11/site-packages (from prompt-toolkit<4.0.0,>=2.0.0->frida-tools) (0.2.13) Using cached websockets-13.1-py3-none-any.whl (152 kB) Building wheels for collected packages: frida Building wheel for frida (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for frida (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [84 lines of output] running bdist_wheel running build running build_py creating build/lib.freebsd-14.2-RELEASE-p1-amd64-cpython-311/frida copying frida/__init__.py -> build/lib.freebsd-14.2-RELEASE-p1-amd64-cpython-311/frida copying frida/core.py -> build/lib.freebsd-14.2-RELEASE-p1-amd64-cpython-311/frida copying frida/py.typed -> build/lib.freebsd-14.2-RELEASE-p1-amd64-cpython-311/frida creating build/lib.freebsd-14.2-RELEASE-p1-amd64-cpython-311/frida/_frida copying frida/_frida/__init__.pyi -> build/lib.freebsd-14.2-RELEASE-p1-amd64-cpython-311/frida/_frida copying frida/_frida/py.typed -> build/lib.freebsd-14.2-RELEASE-p1-amd64-cpython-311/frida/_frida running build_ext gmake[1]: Entering directory '/tmp/pip-install-a3i5b4xm/frida_267fc776b338431e82a38c7e2257d3d5' Makefile:3: target 'all' given more than once in the same rule Downloading toolchain 20250114... <urlopen error [Errno 54] Connection reset by peer> gmake[1]: *** [Makefile:4: all] Error 1 gmake[1]: Leaving directory '/tmp/pip-install-a3i5b4xm/frida_267fc776b338431e82a38c7e2257d3d5' *** Error code 2

Portmaster builds updates, if you haven't started the process there would be no packages.

why would the mirrors build any packages whatsoever?

I.e. portmaster works with ports, not packages.

don't they send precompiled packages that get installed when you use pkg?

the mirrors mirror the built packages

how's that a sign it has been compromised?..

i was scared thinking my pc got compromised or something lol, since yesterday freebsd-update was acting a bit weird

even though i had installed the 14.2-p2 update it was still showing up as p1 upon using uname, then i git pull 14.2 branch of src, make kernel and then it showed up as p2

uname shows the loaded kernel, not the installed one

two possible reasons: a) no reboot between updates and checks; b) no update for the actual kernel

i checked both of them, for a) i made sure to check after rebooting after update, still no change for b) it seems to be an update to actual kernel since after building from src the kernel version string was changed to p2

Actually, updating 14.2-p1 to 14.2-p2 via freebsd-update only affects binaries which are related to openssh, no kernel update.

https://cgit.freebsd.org/src/commit/?h=releng/14.2&id=ac2cbb46b5f1efa7f7b5d4eb15631337329ec5b2 yes but i meant that the version string was updated

It doesn't matter if you don't update from src.

in my case i updated with src because after freebsd-update the version string didn't change

How did you check the version string?

uname shows information from kernel, which was not updated, so that's correct.

Use freebsd-version -kru .

the kernel was updated as you can see in the commit and additionally by p2 being shown after building from src

What's in your /usr/src/UPDATING ?

even though portmaster on quarterly branch can find updates, why does pkg says no updates?

What's in your /usr/src/UPDATING ?

Need the output of freebsd-version -kru

what are you trying to check for btw?

Looks everything's fine. Check the man page of freebsd-update for the arguments.

Please, check the latest security advisory.

Then why didn't you accept my straightforward suggestion to check what freebsd-version -kru do?

https://t.me/FreeBSD1/38404 i didn't check?

So it told you everything's fine, didn't it?