I'm stuck on the patching stage:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201250
Thanks
Anton
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-un
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
Before I get started on something that is likely to devolve into
something a bit "rant-ish," I will take this opportunity to thank the
folks who work on things such as maintaining ports, the port- and
package-building infrastructure, and maintaining the vulnerability
database(s). (For about 3 deca
On 2015/07/03 14:01, David Wolfskill wrote:
> And that combination of things catalyzed this note.
>
> Here's what I'm seeing:
> - There is a claim that the port to which I was trying to update was
> "vulnerable" per vuxml.
vuxml currently states that netpbm versions /less than/ 10.35.96 are
vul
On Fri, Jul 03, 2015 at 02:36:05PM +0100, Matthew Seaman wrote:
> On 2015/07/03 14:01, David Wolfskill wrote:
> ...
> vuxml currently states that netpbm versions /less than/ 10.35.96 are
> vulnerable, and has done since about 48h ago.
H
> Given that the latest available version of netpbm
On Fri, 3 Jul 2015, Matthew Seaman wrote:
On 2015/07/03 14:01, David Wolfskill wrote:
And that combination of things catalyzed this note.
Here's what I'm seeing:
- There is a claim that the port to which I was trying to update was
"vulnerable" per vuxml.
vuxml currently states that netpbm
