HEADS UP: Branch changed to RELENG_2_0 - You *must* fix your update URL!
-
Anything different for nanoBSD?
-
Procedure is the same either way, full or nanobsd.
-
Does Invoke Auto Upgrade now work for the Nano version? I had manually update the June 22 install to the July 8th, but now it appears it might work.
-
It should have, if the corrected URL was entered.
-
I've just used above URLs to update my test installation and now it says: 2.1-DEVELOPMENT (amd64) built on Wed Jul 27 18:52:38 EDT 2011
I'm also using git://github.com/smos/pfsense-ipv6.git but it was last updated on May 26, 2011 so probably it shouldn't cause version change.Shouldn't I get 2.0-RC3? If yes, how to revert to 2.0-RC3?
-
Please read the sticky posts in the ipv6 forum about that. It's not related to this thread.
-
I apologize for my meatheadedness, but I've read this thread 10 times and I still don't understand what it means. If I'm using an .iso of x86 RC 3 that I downloaded on 6-Jul but is dated 22-Jun, should I use the default update URL, or update it? Under what circumstances would I change the url? Thank you for clarifying!
-
Always update it. It doesn't matter when you downloaded, it needs updated, unless the snapshot date is after July 4th. (In which case you'd be getting current updates offered via auto update anyhow)
Bottom line: When in doubt, just reselect the snapshots from the drop-down. It's not going to hurt anything even if you are using a current snapshot.
-
It should also be noted if you are using gitsync in your updater settings to change branch name from master to RELENG_2_0
-
@onhel:
It should also be noted if you are using gitsync in your updater settings to change branch name from master to RELENG_2_0
Unless you are using that to track IPv6, in which case you really do want master. :-)
I wasn't aware anyone was tracking 2.0 on top of 2.0 with gitsync, not much of a point to that. Might hurt more than it helps in some cases, but that's debatable.
