Re: pkgsrc-2024Q3 net/tigervnc is broken on sparc64

[Martin Husemann <martin%duskware.de@localhost>]

On Mon, Oct 28, 2024 at 06:10:06AM +0000, Sad Clouds wrote:
> Once again, you fail to understand my point of view. When there is a
> known regression with packages in a stable release, and it may take some
> time to fix them, there seems to be no provision to update the stable
> release to include previous working version of the packages, so people
> affected by the issue, could simply issue:
[..]

I agree with both of you :-)

The typical way is something like:

 - you fix your (presumably urgent) local problam by downgrading manually
   in your own checkout and use the downgraded pkg

 - optionally someone adds BROKEN markers to the pkg makefile

 - when you get around to debug the newer version you create patches
   and report them upstream. At the same time we add these patches to
   pkgsrc, with a pointer to the upstream report. We bump the pkg
   revision.

 - once upstream imports the fixes (or fixes the issues differently) and
   releases a new version, the patches are removed from pkgsrc

This way long ignored patches don't prevent a working pkgsrc version.

For some pkgs (most prominent examples are probably rust and firefox)
we impose special rules and require "known working" state on several
architectures/environments - but as Greg said, this is always a big
time sink and should be avoided where possible.

Martin