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

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

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

> I'm sorry if I gave you that impression. I'm not demanding that anyone
> solves my problems. I'm simply trying to have a conversation about how
> regressions and instabilities are resolved in pkgsrc stable releases.

The general practice, for a single package expressing a bug on a strict
alignment system, is to hope that someone debugs it and has a fix, and
that there is a patch which can be added to pkgsrc-current, and then
pulled up to stable.

There is no general practice of reverting an update for a failure on a
strict alignment system.

It felt like you were asking that the update in pkgsrc head be reverted
and that revert applied to the branch.  That request (which you are
saying you didn't make, so sorry for misreading) is in view
unreasonable, all things considered.

> I don't believe I suggested anything unreasonable. If there is no
> interest from pkgsrc developers to consider ways of addressing latent
> issues with packages in stable releases, then let's leave it at that. I
> solved the issue locally for myself, I was trying to suggest ways to
> improve user experience for others.

You didn't really solve it.  You worked around it.  To solve it, someone
is going to have to actually debug the code and fix it.  This is almost
certainly an upstream issue that should be addressed with upstream.  In
my view, this is (highly likely) not a pkgsrc bug.  It's only a pkgsrc
bug if the upstream release, when built by hand following upstream's
build instructions, works, and the package does not work.

Have you filed a bug report with upstream?  You haven't included the
URL.

If no one wants to spend time fixing the code, it isn't going to get
fixed.  That's where we are.