3 ms·

Did you try to contact directly Alfred, Peter or Brian? :)

by zerr 8y ago

stevekemp 8y ago
I reported to the Debian bug-tracker where I assumed it would either be forwarded upstream, or be searched by the project authors: https://bugs.debian.org/816277 https://bugs.debian.org/816277 I appreciate that most of the time reporting directly is the right thing to do, but often there is a good relationship between packager and developer and things flow well in both directions. I guess I should make sure I chase old reports and reroute if they seem to be orphaned/ignored/overlooked.
- ifoundthetao 8y ago
  I know from a "getting bugs fixed" perspective it's important to make sure that things are being fixed, or followed up on... but geeze, is it ever a time sink.
  - stevekemp 8y ago
    The oldest bug report I think I've made is now reaching 15 years old. Sometimes I go through things, but its easy to think you've done your part if you submit a bug report, a reproducer, and even a patch.
    - acqq 8y ago
      > even a patch. I'd expect that once a patch is there and it is consistent it would be applied, whereas just reporting what a fuzzer finds is not too helpful.
- nickysielicki 8y ago
  This really should be easier. Every distro has their own bugzilla, some projects use github issues, a lot of bug tracking just happens on mailing lists, it's difficult to keep track of everything. Maybe we need federated bugzilla. By the way, we've all seen the XKCD about competing standards before.
  - monetus 8y ago
    Did you know fossil has a built-in issue tracker? https://www.fossil-scm.org/xfer/doc/trunk/www/bugtheory.wiki https://www.fossil-scm.org/xfer/doc/trunk/www/bugtheory.wiki
- alexhutcheson 8y ago
  From https://www.gnu.org/software/gawk/ https://www.gnu.org/software/gawk/: "Bug reports and feature suggestions for gawk should be sent to bug-gawk@gnu.org." Maybe try sending an email? I agree that reporting to the Debian packager often works, but in this case it's possible they just have too many things to triage appropriately.
  - stevekemp 8y ago
    Dropped a mail there now, thanks. Edit: Too late I see it was already reported before the release and apparently wasn't regarded as significant: http://lists.gnu.org/archive/html/bug-gawk/2019-04/msg00015.html http://lists.gnu.org/archive/html/bug-gawk/2019-04/msg00015.... I guess that means no fix.

Did you try to contact directly Alfred, Peter or Brian? :)

by zerr 8y ago

Did you try to contact directly Alfred, Peter or Brian? :)

I reported to the Debian bug-tracker where I assumed it would either be forwarded upstream, or be searched by the project authors: https://bugs.debian.org/816277 https://bugs.debian.org/816277 I appreciate that most of the time reporting directly is the right thing to do, but often there is a good relationship between packager and developer and things flow well in both directions. I guess I should make sure I chase old reports and reroute if they seem to be orphaned/ignored/overlooked.

ifoundthetao 8y ago
I know from a "getting bugs fixed" perspective it's important to make sure that things are being fixed, or followed up on... but geeze, is it ever a time sink.
- stevekemp 8y ago
  The oldest bug report I think I've made is now reaching 15 years old. Sometimes I go through things, but its easy to think you've done your part if you submit a bug report, a reproducer, and even a patch.
  - acqq 8y ago
    > even a patch. I'd expect that once a patch is there and it is consistent it would be applied, whereas just reporting what a fuzzer finds is not too helpful.
nickysielicki 8y ago
This really should be easier. Every distro has their own bugzilla, some projects use github issues, a lot of bug tracking just happens on mailing lists, it's difficult to keep track of everything. Maybe we need federated bugzilla. By the way, we've all seen the XKCD about competing standards before.
- monetus 8y ago
  Did you know fossil has a built-in issue tracker? https://www.fossil-scm.org/xfer/doc/trunk/www/bugtheory.wiki https://www.fossil-scm.org/xfer/doc/trunk/www/bugtheory.wiki
alexhutcheson 8y ago
From https://www.gnu.org/software/gawk/ https://www.gnu.org/software/gawk/: "Bug reports and feature suggestions for gawk should be sent to bug-gawk@gnu.org." Maybe try sending an email? I agree that reporting to the Debian packager often works, but in this case it's possible they just have too many things to triage appropriately.
- stevekemp 8y ago
  Dropped a mail there now, thanks. Edit: Too late I see it was already reported before the release and apparently wasn't regarded as significant: http://lists.gnu.org/archive/html/bug-gawk/2019-04/msg00015.html http://lists.gnu.org/archive/html/bug-gawk/2019-04/msg00015.... I guess that means no fix.