Repository navigation
Bug/problem reporting: use GitHub or use GNATS ? #102
Description
Activity
In no particular order:
- Use whichever bug reporting system you are more comfortable with. The aim is to make it as easy as possible for users to contribute bug reports, and we'll figure it out from there.
- There are no indicators as to which system is more popular amongst developers. Personally I hate GNATS, other developers hate GitHub, the only important thing is that we get bug reports.
- Please don't replicate bugs across systems.
- We have no interest in pointless bug statistics, so yes we're happy for bugs to stay open for as long as possible (within reason, obviously we'll occasionally close out issues if they refer to packages that were upgraded 15 years ago or are for OS that are no longer available).
- Use the mailing lists for queries of a more technical nature, tech-pkg for packaging and infrastructure questions, pkgsrc-users for anything related to use of the packages themselves.
- I'd recommend using IRC (Libera #pkgsrc) or Matrix for general queries and help with working on things yourself, it's thousands of times easier to work through these things in real time rather than the delayed back-and-forth of email or issues.
- It's an entirely volunteer project, there are no teams or dedicated people for anything. Volunteers work on things as and when they are interested in doing so. We love it when new people come onboard to help out, and so I'd much rather help someone get up to speed on pkgsrc so they can fix things themselves instead of me having to do it for them.
As for http://gnats.netbsd.org/56611, I think that was fixed recently, you should try with a newer checkout.
Reacted by Saulius Krasuckas and CryoThanks for the very detailed answer, Jonathan!
You went straight through all my concerns.It's probably nicest and most human answer I have received during last 10y, really. Very nice, thank you:)
- added a commit that references this issue
on May 4, 2022 - added a commit that references this issue
on Aug 11, 2022 - added 2 commits that reference this issue
on Aug 26, 2022 - added a commit that references this issue
on Oct 18, 2022 - added 2 commits that reference this issue
on Jan 22, 2023 - added a commit that references this issue
on Feb 11, 2023 - added a commit that references this issue
on Mar 30, 2023 - added a commit that references this issue
on Apr 30, 2023 - added a commit that references this issue
on Jul 10, 2023 - added a commit that references this issue
on Jul 23, 2023 127 remaining items
- added 8 commits that reference this issue
on May 15, 2026 - added a commit that references this issue
on Jun 9, 2026 - added 2 commits that reference this issue
on Jul 12, 2026
@bsiegert commented 5 hours ago on issue #101:
I know. I just saw that both problems from me and @jgoerzen had something in common:
"I'm not quite sure where to go with all these things;"
So I used the opportunity to stress this generic question.
Thanks for the tip. Some more questions:
How can I ping the related community for the possible fixes or at least direction of the needed research?
Which place has wider audience of contributors / higher priority at looking at bugs: this repo or the Gnats system?
I wonder if it be useful to replicate my pkg/56611 report on GitHub.
What is the generic flow of fixing / lifecycle of the bug / ethics of fix management for pkgsrc:
Please excuse the newbie which got lost:)
Thanks!