Post incident, here's the #FreshPorts bump at midnight (UTC) mentioned in a recent previous post. It may not seem like much...
Looking back, it seems 0000 and 1200 are favored times.
Post incident, here's the #FreshPorts bump at midnight (UTC) mentioned in a recent previous post. It may not seem like much...
Looking back, it seems 0000 and 1200 are favored times.
More on #FreshPorts vs restrictions on search, etc.
Last night, I received a CPU alert regarding the database server.
I logged in and restricted search to logged-in users.
[13:15 aws-1 dvl ~] % sudo grep 'joe' /var/log/auth.log.1
May 4 00:57:46 aws-1 sudo[37761]: dvl : TTY=pts/0 ; PWD=/usr/home/dvl ; USER=root ; COMMAND=/usr/local/bin/joe /jails/nginx01/usr/local/etc/freshports/constants.local.php
This change means anyone not logged into FreshPorts with their FreshPorts account will get a 401 for any search.
This morning, the graph for Nginx requests graph looks like this.
Search was enabled again at May 4 13:14:37
Because #FreshPorts' search is now limited to logged in users, I hacked together an alternative: https://tmb.codeberg.page/portssearch/
Do you happen to know what make target builds the SUB_FILES, e.g. files/pkg-message.in?
I've found this bit: https://cgit.freebsd.org/ports/tree/Mk/bsd.port.mk#n4600
My goal, build pkg-message without building the port.
It is so very satisfying to see a FreshPorts commit processing queue quickly fill up when it comes back online after being down (for modification in this case).
case in point:
https://gist.github.com/dlangille/0c62a3a68c9b3b6b14eba5b04fa4c7dc
<https://www.freshports.org/textproc/py-pdftotext/#pkg-plist> "There is no configure plist information for this port."
I wonder why.
There's probably a generic explanation, not specific to this port. If so, maybe I can add something to <https://www.freshports.org/faq.php> …
Everything you never wanted to know about #FreshPorts processing of #FreeBSD vuxml entries:
https://news.freshports.org/2025/07/30/how-freshports-processes-vuxml-entries/
Turbulent times.
It was necessary to explain that the three cookies on the baking tray are not collecting personal data.
https://www.reddit.com/comments/1l6atsf/respect/mwo9yk0/
Postscript: https://www.reddit.com/comments/1l6atsf/respect/mwolp77/ ends the turbulence. Still, I do like the idea that Tux cookies might have collected data about what's in the oven.
#privacy #cookies #data #FreeBSD #FreshPorts #Tux #Beastie #Linux #daemon #demon #penguin #demonpenguin #pride #daemonpenguinpride @dvl