Current vuln status is shown by a skull at the top of the page.

Which skull to show (active or greyed out) is decided by an entry for this port in the ports_vulnerable table, which has three column: port_id, current, past

The stored procedure PortsVulnerabilityCountAdjust(port_id) sets these values. There seems to be a problem with this query:

            SELECT count(distinct vuxml_id)
              INTO l_VulnCurrent
              FROM commit_log_ports_vuxml CLPV, commit_log_ports CLP, ports P
             WHERE CLP.commit_log_id = CLPV.commit_log_id
               AND CLPV.port_id      = CLP.port_id
               AND P.id              = CLP.port_id
               AND P.version         = CLP.port_version
               AND P.revision        = CLP.port_revision
               AND CLP.port_epoch    = P.portepoch
               AND P.id              = p_PortID;

I'll have to look into that to see why it goes wrong, but I suspect its because there is no commit which affects the current version of the port. This is a special case for slave ports, because their version can be derived from the master and there may not be a commit against the slave port for a given PORTVERSION value.

I am not sure how best to solve this.

At present, each port and category uses this method for providing content:

ErrorDocument 404 /missing.php

Let's change that by doing a rewrite to start with so every URL goes to missing.php (for example).

The term 'refresh a port' is misleading. It is actually refresh a commit.

Sometimes a commit does not finish processing; perhaps the svn update could not be completed successfully. The commit is marked by setting commit_log_port.needs_refresh to a non-zero value, usually 7.

When a commit is processed, the ports tree is svn up'd to that SVN number. make is invoked to extract values form the port via 'make -V'. This allows us to grab the DEPENDS etc.

We also grab the PORTVERSION and PORTREVISION and set that in the Commit History.

We also update port.version and port.revision with that value. This step is appropriate when we are processing the most recent commit for a port. If it is not the most recent commit, you get the wrong value displayed at the top of the page.

At present, logging in, updating your profile, and uploading your watch list all occur on www.freshports.org.

Would that be better done on my.freshports.org, for example?

Move all the newsfreeds to a different hostname, e.g. feeds.freshports.org

re:

https://www.freshports.org/commit.php?category=security&port=vuxml&files=yes&[email protected]

https://www.freshports.org/commit.php?category=security&port=vuxml&files=yes&[email protected]

If missing-port-categories.sh is run while a commit is being processed, false positives can occur:

This is a list of ports that do not have entries in the ports_categories table
This can be fixed with this query:
begin;  insert into ports_categories select id, category_id from ports_active PA WHERE NOT EXISTS (SELECT * from ports_categories PC where PC.port_id = PA.id and PC.category_id = PA.category_id);
 id   | category_id |   name    | category |        port        
-------+-------------+-----------+----------+--------------------
38110 |           4 | appleseed | graphics | graphics/appleseed
(1 row)

If this script is queued hourly and run from job_waiting.pl, this will not occur.

I can't recall what it was, but I know it's there. I need to search my email.

Not sure why that's not being caught, but compare with https://svnweb.freebsd.org/ports/head/GIDs

Move all the images from freshports.org to another hostname, e.g. images.freshports.org

Could we move graphs to another hostname? e.g. stats.freshports.org

One of the downsides to all these hostname: creating SSL certs.

This port moved:

http://www.freshports.org/sysutils/slurm-hpc/
http://www.freshports.org/sysutils/slurm-wlm/

FreshPorts processes MOVED and includes a link from one to the other. I don't see it there yet.

Instead of doing commit.php?message_id=X, why not put that on https://commits.freshports.org/ ?

Forums should be on forums.freshports.org

refresh-unrefresh-ports.pl is designed to run a few ports. When we have 1000s to fix, it'd be nice if they ran in the background, in between processing of incoming commits. We could do that the same way we process MOVED and UPDATING.

Add OpenSearch link to freshports.org base template so that users can add a 'Freshports Search' engine to their Browser Search Bars:

OpenSearch Homepage
Client Support

Implementation examples:

• Creating OpenSearch Plugin
• http://blog.unto.net/add-opensearch-to-your-site-in-five-minutes.html

Case in point:

http://www.freshports.org/security/polarssl/ did not list http://www.freshports.org/security/openvpn-polarssl under "This port is required by:".

Removing the cache entry for security/polarssl corrected the display.

suggestion: when setting up dependencies for a port, remember to invalidate the cache entries for those ports upon which it depends.

Thanks to Avengence and mandree for their help in identifying the cause.

Do all the PHP files need to stay in www? Could they be moved out of DocumentRoot entirely?

commits processed in the past 24 hours, past hour, past 5 minutes

commits in the queue

Whether or not commit processing is enabled

This worked once, via Javascript.

I think there should be a way to link directly to the part of the ports page below the dependency lists (which can be long and difficult to scroll past without overshooting).

With a keyword set up in the browser, I can enter, e.g. "fp www/apache24" and end up at http://www.freshports.org/www/apache24. It would be most helpful if I could jump directly to the interesting parts, such as the UPDATING entries and the commit history:

• http://www.freshports.org/www/apache24#updating
• http://www.freshports.org/www/apache24#commits
• etc.

There are some anchors, e.g. "mastersites", but they look more like development artifacts.

Sometimes, PKGNAME != dir name, which can cause issues if creating a new VULN entry... if you get it wrong.

To: [email protected]
Subject: Cron dan@supernews cd $DIR && sh test-master-port.sh 2>&1 > /dev/null
Date: Thu, 13 Aug 2015 17:47:02 +0000 (UTC)

"/usr/local/PORTS-head/Mk/bsd.port.mk", line 1493: Could not find /usr/local/PORTS-head/Mk/Uses/libtool.mk
make: fatal errors encountered -- cannot continue

Add in a way to do very simple descriptive searches using something along the lines of:

www.domain.com/search?key=irc/bitchx and it should give a reply relatively to that of
psearch irc/bitchx.

This would be nice to have.

Many makefiles were updated about the first of April, may have thrown the code off.
Trusting that it is not an april fools' event...

!! ISSUE ONE, YEH BABY !!

Currently, freshports SVN urls are in the form:

http://svnweb.freebsd.org/ports?view=revision&revision=

An alternative (shorter) form is supported, as follows:

https://svnweb.freebsd.org/changeset/ports/390304

These correctly redirect and expand to the correct place, but are much prettier when copying/pasting (especially into bugzilla, and other third party systems)

It might also help Google juice and URL crawl-ability in some cases

PS: Congratulations on the repo! I look forward to an export of the freshports.org code soon ;)

Hi, I'm trying to update e2guardian for v5.1 but the port is with the latest version as 3.5.1.

how should I do ?

Thank 😃

E2guardian repo:
https://github.com/e2guardian/e2guardian/releases

use https://svnweb.freebsd.org/doc/head/en_US.ISO8859-1/htdocs/ports/categories?view=co in fp-listen

I think config.pm needs to be split. Some stuff in there is sensitive, some is not. e.g. database passwords. Not all scripts need the db password, but some need the other stuff.

e.g. check_freshports_queue

[May 23 17:20:52] dvl: freshports appears to not be picking up ports/UPDATING changes.
[May 23 17:21:55] dvl: last update that it processed was 2016-04-18. dev.freshports.org seems fine, beta.freshports.org is even worse.