Release Mismatch, fyi



  • Version 2.3.3-RELEASE (amd64)
    built on Thu Feb 16 06:59:53 CST 2017
    FreeBSD 10.3-RELEASE-p16

    The system is on a later version than
    the official release.

    I downloaded 2.3.3-RELEASE (amd64) from pfSense web site…


  • LAYER 8 Global Moderator

    And did you update it to p1?


  • Netgate Administrator

    Hmm, that's fun. Hard to see how you could be seeing that.

    Try running at the command line:

    pkg info pfSense
    

    What does it return?

    Steve



  • pkg info pfSense

    
    pfSense-2.3.3
    Name           : pfSense
    Version        : 2.3.3
    Installed on   : Thu Feb 16 21:09:37 2017 CST
    Origin         : security/pfSense
    Architecture   : freebsd:10:x86:64
    Prefix         : /usr/local
    Categories     : security kld
    Licenses       : ESF
    Maintainer     : renato@pfsense.com
    WWW            : https://www.pfsense.org/
    Comment        : Meta package to install pfSense required ports
    Annotations    :
    	repo_type      : binary
    	repository     : pfSense
    Flat size      : 2.39KiB
    Description    :
    Meta package to install pfSense required ports
    
    WWW: https://www.pfsense.org/
    

    Interestingly today it is back to normal:

    
    Version	2.3.3-RELEASE (amd64) 
    built on Thu Feb 16 06:59:53 CST 2017 
    FreeBSD 10.3-RELEASE-p16 
    
    Version 2.3.3_1 is available.	
    
    

    I changed nothing. So perhaps it was a network issue: it couldn't get an update status. Or something hadn't finished installing/updating since the install of 2.3.3

    @johnpoz: I didn't install the update for fear of cause a rip in the space-time continuum since it already said I was running a newer version than the official release…  ;D



  • Just noticed this:

    Installed on  : Thu Feb 16 21:09:37 2017 CST

    I installed this 'yesterday' (my time): April 30, 2017.
    Not sure why its saying it was installed on Feb 16…


  • LAYER 8 Global Moderator

    Because you had a rip in the space time continuum? ;) your clock on your device was OFF would be my guess..


Log in to reply