Guess we had overlapping emails there.
On 30 October 2018 at 18:51, D Haley wrote: | Hi, | | Thanks for the very quick response. | | On my system, it is gsl/gsl_filter.h, rather than Sorry -- I confused myself between an older installation, my sources, and then Debian testing/unstable. My bad. | gsl/filter/gsl_filter.h . I'm not sure why - I'm running stable and have | manually backported the testing release, as gsl_filter.h is new and I'm | using it in my code. | | $ apt-file find gsl_filter.h | libgsl-dev: /usr/include/gsl/gsl_filter.h | | I've raised the original concern upstream: | https://savannah.gnu.org/bugs/index.php?54921 | | Just for reference - I thought that Debian policy was to report to | Debian, and have the maintainer contact upstream? [1,2] Perhaps I am | mistaken? Sure. And then what? "In theory" I have nothing else to do and can handle that. In practice bugs sometimes get filed and then just sit there. I have done this for 20+ years and my experience suggests that end users get better coverage on upstream bugs when talking to upstream. (It's a generalization, and there are exceptions; sometimes we maintainers have close and productive relationships with upstream.) | Is it possible that this can be patched in Debian in the meantime, so | others don't have this problem? Can you propose a patch? | I've fixed it locally, so I am fine. Sounds good. Dirk | | Thanks! | | [1] https://www.debian.org/Bugs/Reporting ("If necessary, the maintainer | of the package will forward the bug upstream.") | [2] https://wiki.debian.org/BugTriage#Forwarding_reports_upstream | -- http://dirk.eddelbuettel.com | @eddelbuettel | [email protected]
