Solved Seamonkey won't build - security issues

[Sevendogs]

Well this is odd and I can't seem to figure it out so thought I'd post. According to http://vuxml.freebsd.org/freebsd/e60169c4-aa86-46b0-8ae2-0d81f683df09.html and to the ports tree, www/seamonkey has security issues and won't build. I understand why we wouldn't want to build a port with security issues, but I have updated the ports tree and it still won't build. The version in ports is the version listed in the vulnerabilities page. I have checked /usr/ports/UPDATING and although I found a few items concerning www/seamonkey, one dated 1/24/2017, which affects www/firefox and www/firefox-esr but they build fine.

I assume when www/firefox has security vulnerabilities the fixes are integrated into the ports tree but I have never had a build stop because of these. Is it just because www/seamonkey is not a very popular browser and the security fixes have not yet made it into the ports tree?

Thanks in advance.

 

[SirDice]

but I have updated the ports tree and it still won't build. The version in ports is the version listed in the vulnerabilities page.

The security report says any version below 2.48 is vulnerable, the version in the ports tree is 2.46.

Is it just because www/seamonkey is not a very popular browser and the security fixes have not yet made it into the ports tree?

There isn't a team being paid to create or update the ports tree. The ports are a community effort. If nobody takes the time and effort to create patches or updates it simply won't get updated.

 

[Sevendogs]

Understood, that's what I thought. Thanks.