Re: Backout git revision 4179e6b78297369f [that is also stable/15 and releng/15.0 as 62c3b77d1d10]

On Sun, 9 Nov 2025 19:46:44 +0000 (UTC)
"Bjoern A. Zeeb" <bz@FreeBSD.org> wrote:

> On Sun, 9 Nov 2025, Steve Kargl wrote:
> 
> > On 11/9/25 08:56, Bjoern A. Zeeb wrote:
> >> 
> >> So if you want things to work, it's the ports which needs to be fixed.
> >> 
> >
> > First, commit the patch from the PR.  That fixes the problem.
> 
> The -D is not for a drm-kmod/ports fix please;  there's another semi-native driver
> in src which uses LinuxKPI headers and needed this and there's still a need to
> fix that.  Then I'll see if I can get away with it within LinuxKPI itself.
> 
> I added a suggested patch to your PR for the port for some grpahics/ports
> person to start work with and get it in.
> 
> 
> > Second, it is an interesting stance to to take.  It's okay to
> > break/diminish the FreeBSD experience for others in the name
> > of progress.
> 
> If that would be the case, then I probably wouldn't have bothered following up
> and helping identifying a better fix the moment I became aware of the problem.
> 
> I am sorry x11 hasn't dealt with this since (must be) end of September.
> 
> /bz
> 
> 
> -- 
> Bjoern A. Zeeb                                                     r15:7

What's interesting here looking into freebsd-pkg-fallout ML is
that (putting aside builder start failures) graphics/drm-515-kmod
alone is failing. Yes, graphics/nvidia-drm-515-kmod[-devel] doesn't.

As graphics/nvidia-drm-*-kmod[-devel] ports uses only some parts
of distfile for corresponding graphics/drm-*-kmod ports, possibly
it could help narrowing down where is the problem in. (Would be hard,
though.)

Note that I've checked posts on November and October using ML archive.

Regards.

-- 
Tomoaki AOKI    <junchoon@dec.sakura.ne.jp>