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

[Greg Troxel <gdt%lexort.com@localhost>]

Sad Clouds <cryintothebluesky%gmail.com@localhost> writes:

> Hello, in the email subject I specified pkgsrc-2024Q3 release. I tend to
> use stable branches and I guess many other people do the same.

sorry, missed that.

> I have already reverted locally to the previous version which works.
> This was just a suggestion so that others don't have to face the same
> issues. I appreciate that people cannot test all packages on all
> supported architectures, but when someone finds stability issues with
> packages on a stable pkgsrc branch, perhaps there needs to be a policy
> of rectifying that? As you noted, debugging, getting stack traces,
> reporting upstream and waiting for developers to apply fixes is not
> going to be quick.

There is not a policy that it has to be fixed, and there are no people
obligated to solve your problem.  There are instead people willing to
give you advice so that you can solve your own problem, and share that
with others.

You are welcome to debug it and create a patch, and ask that this be
applied to head, and then to ask that it be pulled up.  This should
start with an upstream bug report.  That is how this problem should be
addressed, not by jumping to the conclusion that pkgsrc should adopt new
policy.

Downgrading a package and applying that to a stable branch is outside of
pkgsrc norms.  If the package were entirely broken for everyone, I can
see this happening.  But strict alignment is unusual (even if a failure
is a legit bug), and as you note pkgsrc cannot keep up with all upstream
problems.  Downgrading would have negative consequences for the other
99.5% of users.  And you have solved your immediate problem.