Submitting a Bug to FreeBSD

#FreeBSD #OpenSource #Unix #windows #garyhtech #2024 #technology #tech
Let's check out how to submit a bug to FreeBSD's Bugzilla.
bugs.freebsd.o...
Don't forget to check out my Discord server where you can talk open source operating systems and software
/ discord
FOSS
FreeBSD Handbook
FreeBSD Networking
FreeBSD PKG
FreeBSD ports tree
FreeBSD Bugs

[@sfuoncall]

That is weird. Normally, I would say that it was a server issue. But I think it is a metadata issue. If I use curl to grab the file on my Mac, I get the following headers:
< HTTP/1.1 200 OK
< Date: Mon, 25 Mar 2024 20:28:46 GMT
< Last-Modified: Mon, 25 Dec 2023 00:52:53 GMT
< Content-Length: 35559
< Content-Type: application/x-gzip
< X-Varnish: 142165068 178883807
< Age: 79
< X-Cache: HIT
< X-Cache-Hits: 1
< Accept-Ranges: bytes
< Connection: keep-alive
which reports for the HTTP GET the length of the content return is 35559 (which matches the file). So the server is reporting the correct length. Which leads me to believe that the metadata about that version is incorrect.

[@bobbuilder3748]

A file size or checksum mismatch would affect all users.

[@Mysticsam86]

This was a really good video!
When i have a problem with a port i just lookup who is the maintainer and mail them directly. Am i going it wrong?

[@fdg394]

Maybe the package is compromised?