Skip to content

Bug/problem reporting: use GitHub or use GNATS ? #102

New issue
New issue
Closed
Closed
Bug/problem reporting: use GitHub or use GNATS ?#102

Description

@sskras
sskras
opened on Mar 1, 2022

@bsiegert commented 5 hours ago on issue #101:

@sskras If your bug report was about a different problem, then it does not belong here.

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.

There is no SLO on replies to bug reports.

Thanks for the tip. Some more questions:

  1. How can I ping the related community for the possible fixes or at least direction of the needed research?

  2. 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.

  3. What is the generic flow of fixing / lifecycle of the bug / ethics of fix management for pkgsrc:

  • Are bugs here allowed stay open forever ?
  • Can I offer patches based on different approaches (even hacks) without getting banned from being reviewed?
  • What is the patch reviewing procedure – is it a team or a single, dedicated person usually working on that?

Please excuse the newbie which got lost:)
Thanks!

Activity

  1. jperkin commented on Mar 2, 2022

    @jperkin
    jperkin
    on Mar 2, 2022
    Collaborator

    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.

  2. jperkin
    closed this as completedon Mar 2, 2022

  3. sskras commented on Mar 2, 2022

    @sskras
    sskras
    on Mar 2, 2022
    Author

    Thanks 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:)

  4. netbsd-srcmastr
    added a commit that references this issue on May 4, 2022

    restish: update to 0.14.0.

    0248a47
  5. netbsd-srcmastr
    added a commit that references this issue on Aug 11, 2022

    devel/ruby-mixlib-config: update to 3.0.27

    938595a
  6. netbsd-srcmastr
    added 2 commits that reference this issue on Aug 26, 2022

    xfce4-desktop: update to 4.16.1

    4be3edc

    xfce4-panel: update to 4.16.5

    2e90ad9
  7. netbsd-srcmastr
    added a commit that references this issue on Oct 18, 2022

    Update to 9.01. From the changelog:

    4ffacbd
  8. netbsd-srcmastr
    added 2 commits that reference this issue on Jan 22, 2023

    neon: update to 0.32.5.

    3413fb1

    textproc/hs-citeproc: Update to 0.8.1

    41ccc09
  9. netbsd-srcmastr
    added a commit that references this issue on Feb 11, 2023

    www/ruby-multipart-post: update to 2.3.0

    04a0b89
  10. netbsd-srcmastr
    added a commit that references this issue on Mar 30, 2023

    sysutils/erdtree: update to 1.7.0

    cab1abc
  11. netbsd-srcmastr
    added a commit that references this issue on Apr 30, 2023

    py-pebble: update to 5.0.3.

    2c8e23e
  12. netbsd-srcmastr
    added a commit that references this issue on Jul 10, 2023

    textproc/ruby-rails-dom-testing: update to 2.1.1

    35b1af1
  13. netbsd-srcmastr
    added a commit that references this issue on Jul 23, 2023

    devel/concurrencykit: update to ck-0.7.1

    d9e2fd3

  14. 186 remaining items

  15. tsutsui
    added 14 commits that reference this issue on Oct 17, 2026

    devel/ruby-regexp_parser: update to 2.11.2

    99e1eff

    devel/feluda: update to 1.9.8

    95e6348

    libsidplayfp: update to 2.16.0.

    6d6fad2

    devel/ruby-io-console: update to 0.8.2

    8aa114f

    py-puremagic: update to 2.0.0.

    539ea64

    p5-XML-Parser: update to 2.48.

    7532fef

    py-asn1: update to 0.6.3.

    8728425

    py-installer: update to 1.0.0nb3.

    594a8be

    py-mediafile: update to 0.16.0.

    8cc239d

    p5-YAML-Syck: update to 1.45.

    86eb168

    p5-XML-LibXML: update to 2.0213.

    a42b30f

    adwaita-icon-theme: update to 50.0.

    8b0f537

    lame: update to 4.0

    f3dc0bf

    net/ttl: update to 0.21.0

    b9cf949
  16. netbsd-srcmastr
    added a commit that references this issue on Oct 30, 2026

    devel/gitpane: update to 0.18.0

    c47d237
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions