On Sun, 2 Feb 2025 at 18:28, Dan Langille <d...@langille.org> wrote: > > It just reverts back this wrongly working line to this from version > > 13. It isn't any official "hotfix", but just the commit with the fix. > > I used this to patch the FreeBSD port. It now works.
Hello Joerg and hello Dan, First, thank you for your work on this patch in FreeBSD. You are very fast. Congratulations for that. > BTW, is there an easy to find the patch from the issue? This is a good question. Usually Bacula developers mark bug fixes for the Community GitLab issues by using the issue number in the commit title. The general form of this information is org#ISSUE_NUMBER For example, this issue is 2737, so in the commit message we can see: bpipe: Fix org#2737 About segfault with bpipe For this specific commit, I found it because I know this problem, but if I wouldn't know it, then for sure I would use the org#ISSUE_NUMBER information. > That is, how did you get from > https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/issues/2737 > to > https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/commit/453dc8ef9e41ba21b7fc4b69ab49e5f31f40b067#f1a572d4e991fb723a0992744981682af66ac5e5.diff > > I ask because I can't see the link from one to the other. > > Compare with https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284250 where > there is a link to the commit. I think that your idea with including the commit link in the bug report is good. Maybe Bacula developers will be interested in using it. We will see. Best regards, Marcin Haba (gani) _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
