https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240097
--- Comment #6 from Lorenzo Salvadore <salvad...@freebsd.org> --- (In reply to Alexey Dokuchaev from comment #5) Bug is earlier, you are right, but commit is later. The commit for this bug report has been processed in 2019-08-25, while the commit for otter's update in 2019-10-12. Thus most probably it is that last update that broke something. Moreover, that update was not a normal one: commit message says "The last official release was 1.0.01 in january 2019, way too long ago for a web browser. Many Linux distro's also offer weekly snapshots of this browser (often calling it 1.0.81). Instead, bump to a different fake release number; I'm concerned that 1.0.81 might be too high." and according to the Makefile the sources to build from are selected through a git commit: GH_TAGNAME= 22de58d. If we add to this that the most recent weekly snapshot (not the one in ports tree) is considered likely to have bugs (see https://sourceforge.net/projects/otter-browser/files/otter-browser-weekly300/ ), then we can expect that the verions in ports tree can have even more. I suggest to update otter to the very last weekly snapshot, then, if something is broken, report it upstream. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
