Packages all fixed

Over the past couple days, the packages have all been fixed bit by bit. As of right now they should all be working. If there are any that still do not work please let me know.

We also have all the packages pointing to our servers now, so packages will break far less frequently from now on. Virtually all package breakage in the past has been related to disappearing or moving files on servers we don’t control, which will no longer be an issue.

Share this Post:

20 Responses to “Packages all fixed”

  1. John Doe Says:

    I just saw that the iPerf package does not install.

  2. StarScream Says:

    sshterm still not working

  3. Marcus_DK Says:

    I have trouble installing tinyDNS
    Warning: main( [function.main]: failed to open stream: No such file or directory in /usr/local/www/pfswww/packages/config/tinydns/tinydns_status.php on line 32

    Fatal error: main() [function.require]: Failed opening required ‘’ (include_path=’.:/usr/local/share/pear’) in /usr/local/www/pfswww/packages/config/tinydns/tinydns_status.php on line 32

  4. George Says:

    Snort is half broken. Seems to install and load ok, but it won’t update its rules.

  5. StarScream Says:

    widentd not working too.
    sshterm installed now but diag_shell.php broken.
    same thing at diag new states: diag_new_states.php broken too

  6. JohnM Says:

    LCDproc wont install. Fails on:
    Checking for successful package installation… failed!

    Snort installed but cant view rules, whitelist or alerts. Bombs at snort_download_rules.php on line 34

  7. me Says:

    darkstat problem, phpsysinfo problem,..

    Can you please check this packet before you post it is ok?!

  8. akong Says:

    It’s snort and tiny dns server is unused.

  9. baskin Says:

    I can also confirm that iperf does not install yet.

  10. dbruner Says:

    RRD graphig dose not work, traffic shapping does not work, netflow export does not work…

    RC was better than RELEASE…

  11. Chris Buechler Says:

    There are some package issues still, we’ll get them fixed as soon as we can.

    dbruner: RRD and traffic shaping have no known issues and after well over 100,000 downloads of 1.2 you’re the only person to report either not working. If you can provide specific information on what is broken and how to fix it, open a bug report, otherwise take it to the forum or mailing list. Netflow is a package, it could be affected by the same package issues as other packages.

  12. Chris Buechler Says:

    All the package issues should now be fixed. Please let us know if you run into any more troubles.

  13. f4nt0m4ss Says:

    Downloading package configuration file… done.
    Saving updated package information… done.
    Downloading Zabbix Agent and its dependencies… done.
    Checking for successful package installation… failed!

    Installation aborted.

  14. JohnM Says:

    Thanks for all your hard work.

  15. Chris Buechler Says:

    Zabbix is apparently still broken, though the rest all work. Scott will be looking at it shortly.

  16. Nicolas Boissé Says:

    I’m Having issue with squidGuard filtering. Even after a successfull black list URL uptade, the default filter don’t filter at all.

    Thank you very much for all that great stuff!

  17. Paolo Says:

    pkg_add -r still not work (refer to broken… URL)

    Patch/hints to install packages (like mc 😉 )?

  18. Chris Buechler Says:

    Nicolas: not sure, that’s not related to any of these issues, you’ll need to ask about that on the list or forum.

    Paolo: pkg_add -r will not work anymore, just like it won’t work anymore on a stock FreeBSD 6.2 install. That’s hard coded in FreeBSD to that location on their servers.

    You can fetch package files from and then ‘pkg_add filename’ rather than pkg_add -r.

    The coming pfSense 1.2.1 release will be based on FreeBSD 6.3, and pkg_add -r will work again at that point since there are 6.3 packages on the FreeBSD servers.

  19. Paolo Says:

    Any news about the 1.2.1 release?

  20. Chris Buechler Says:

    I’ll post something later on 1.2.1 and 1.3 status.

Please don’t post technical questions or off-topic comments. It is far more likely that your questions and concerns will be addressed effectively through one of our support channels.

Leave a Reply