[Solved]: FreeBSD Port Of Coppermine 1.4.14 And Portaudit [Solved]: FreeBSD Port Of Coppermine 1.4.14 And Portaudit
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

[Solved]: FreeBSD Port Of Coppermine 1.4.14 And Portaudit

Started by ThisGuyIKnow, March 05, 2008, 06:34:19 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

ThisGuyIKnow

Hello folks,

The portaudit tool on my FreeBSD test server at work has been telling that I need to upgrade my coppermine installation (1.4.14), which was installed via the FreeBSD ports collection. I run "portsnap fetch update" and "portversion -v | grep '<'" daily to update my ports collection and see which ports need to be updated respectively. Coppermine never comes up, so I gather there hasn't been a update of this port.

I am wondering if I should just wait for an updated port or upgrade manually, following the instructions on the Coppermine site. I already know how to do the latter since I successfully upgraded the Coppermine installation on my personal website (Debian hosted) from 1.4.14 to 1.4.16. But if I do it that way, will portaudit "know" that I have upgraded to the new version? I doubt that it will, since I believe it goes by what it sees in the ports collection tree or the package database. (I think)

Anyways this isn't ultra important because, as I mentioned above, this is on a test server. But I also recognize that this post may potentially help other people in the future.  ;D

Nibbler

You'd need to ask the port maintainer. Using anything other than our install/update scripts is not recommended or supported here.

Joachim Müller

Please note that we're not fond of pre-installed packages. The only supported install method is the one we describe in our docs. Auto-installers (like Fantastico) or similar tend to be outdated - that's generally a problem with web-driven apps. As Nibbler suggested, you'll have to ask the maintainer of the package to update it for you.

ThisGuyIKnow

#3
Okay, works for me.  :)

For others' benefit, I did the following:

- Gavin