Re: nvidia-driver and no update in /usr/ports/UPDATING
- Reply: Steve O'Hara-Smith : "Re: nvidia-driver and no update in /usr/ports/UPDATING"
- Reply: Graham Perrin : "Changes (was: nvidia-driver and no update in /usr/ports/UPDATING)"
- In reply to: tech-lists : "nvidia-driver and no update in /usr/ports/UPDATING"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 08 Apr 2022 02:35:54 UTC
It's not just this. Look at this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249252 Broken on 2020-09-11 and again on 2022-02-03 for the same reasons, an unannounced name change. In this case, a font name. Great for a website using that font. Look carefully at UPDATING like a good sysadmin, then update and bam! no website! I manage several websites using this font. It's an adobe ttf font, it's popular. I was fortunate to find it before the sites themselves were updated, because I was looking at poudriere building at the time. Nothing has been done in this ticket, it remains open and there's still nothing in UPDATING. it's becoming impossible to run an up-to-date and reliable service on freebsd because of failure of maintainers to follow the policy of updating /usr/ports/UPDATING when a port hasn't just MOVED. My irritation is *entirely* down to the changes not being present in UPDATING. I know things change, what grinds my gears is the changes not being documented in a way that is visible. Are other BSDs like this?!? -- J.