Providing a package, if he did so, was his choice. No one at the distro asked him to (some users may have, but that has nothing to do with the distro or its other users). If you provide the package of your own volition, you should expect that there will be complaints if it doesn’t work as expected. You need a procedure (and a certain amount of saved-up mental fortitude) to deal with them.
If someone complains to you about someone else’s buggered-up packaging job, the correct thing to do is have a prewritten reply set up saying, “Nothing to do with me, complain to the other guy.” Then close the bugs as WONTFIX and get on with your life. And see if the package host has a removal policy for broken packages, if it is genuinely broken and not just clueless users messing up.
To me, this specific case seems like the dev wasn’t prepared for what the open Internet is like, couldn’t handle it, and imploded messily. Are the users that got on his nerves at fault? Yes, on one level, but their existence was also entirely predictable. If you know what you’re doing, you factor the existence of these people in when you decide whether you’re willing to release your software to the public or not and what communication channels you should leave open.
Localhorst86@feddit.org 3 weeks ago
I don’t think we can count the AUR repository as the “default package” because:
sugar_in_your_tea@sh.itjust.works 3 weeks ago
And that’s the real fail. AUR users need to understand how things work, AUR packages are community maintained and supported. If the build fails, complain to the AUR maintainer, and they will raise the necessary bug reports to the upstream project if the bug is w/ the project instead of the build instructions.