2.0.2 ???

stephenw10

When people stop finding bugs I presume.
Everyone stop looking! :P

Steve

Supermule

;D ;D

jimp

It's not always us finding bugs…

FreeBSD issued a security advisory for hostapd yesterday that affects us, so 2.0.2 needed yet another rebuild after we added a patch for it!

Gah... hopefully that will be the last one. Should be up later today.

joako

@Burnie:

It exists in 2.0.2 also.
Adding (or editing) a domain override doesn't require "apply changes", but removing domain does.

But I'm not sure it's a bug. Adding or edtiting things are less "harsh" than deleting things. IMHO.

You are correct. This is a not a bug, I was doing many changes and assumed that the process of adding/deleting was the same and each would require an apply.

MaxPF

So are the builds dated 20121126 (http://files.nyi.pfsense.org/jimp/foo/shiny/ehrmagerd/) the final official 2.0.2?

jimp

Unless one of the following happens:

We find a showstopper bug during testing
Someone releases yet another security advisory
Aliens invade and destroy all copies of the images so we have to build new ones.

My money's on 3.

Supermule

Then what happens Jim ;D ;D ;D ;D

jimp

Well once we have defeated the alien invasion, we just provision a new set of builders and make a fresh set. Easy peasy.

MaxPF

@jimp:

Unless one of the following happens:

We find a showstopper bug during testing

Someone releases yet another security advisory

Aliens invade and destroy all copies of the images so we have to build new ones.

My money's on 3.

So you are saying that I should download the images now before the aliens find the location of the hosting server. ;)
Starting download!

jimp

Supermule

And they will be on the official DL page/mirrors SOOOOOOON???? :D

jimp

See above, re: 1-3.

Still have some testing to do, but so far, so good… the more people that test it, the better. (Including installing from CD, Memstick, NanoBSD, etc, etc).

stephenw10

They're already here, and in high definition! Noooooo.

Steve

MaxPF

@jimp:

See above, re: 1-3.

Still have some testing to do, but so far, so good… the more people that test it, the better. (Including installing from CD, Memstick, NanoBSD, etc, etc).

Installing the nanobsd upgrade on my Alix at home.
It says it's not digitally signed, is that normal?

jimp

@adam65535:

Does anyone know if the issue below made it into the forthcoming 2.0.2 release? The snort alerts and blocked tabs just bring up a blank screen for me after about 2 months of uptime.

http://redmine.pfsense.org/issues/1942

Snort has no relevance to a release. It's a package. Keep it in the package forum.

jimp

@MaxPF:

@jimp:

See above, re: 1-3.

Still have some testing to do, but so far, so good… the more people that test it, the better. (Including installing from CD, Memstick, NanoBSD, etc, etc).

Installing the nanobsd upgrade on my Alix at home.
It says it's not digitally signed, is that normal?

Yes that's normal we only digitally sign the release images once we've deemed them to actually be the official release.

MaxPF

@jimp:

Yes that's normal we only digitally sign the release images once we've deemed them to actually be the official release.

Thanks, the upgrade just completed succesfully.

pierob

Just for info:

upgraded from 2.0.1 to 2.0.2 a couple of Alix
same upgrade on 2 VM
installed a new 2.0.2 VM from .ova (VMware ESXi5) and restored full config from 2.0.1

All has been properly updated.

Jon

All looking good on a few boxes I have upgraded. the only odd thing I see is that the text for the dynamically generated fields on the dashboard seem to be too small compared to the rest of the text on the page. This wasn't as visible in 2.0.1. Perhaps make them a font size bigger or make them the same font as the rest of the elements on the page?

I know its just a cosmetic issue, but they just look out of place to me.

Other than that things work great!

-J

pvoigt

@Jon:

All looking good on a few boxes I have upgraded. the only odd thing I see is that the text for the dynamically generated fields on the dashboard seem to be too small compared to the rest of the text on the page. This wasn't as visible in 2.0.1. Perhaps make them a font size bigger or make them the same font as the rest of the elements on the page?

Can confirm this font issue. Just upgraded a VirtualBox test VM from 2.0.1 using http://files.nyi.pfsense.org/jimp/foo/shiny/ehrmagerd/pfSense-Full-Update-2.0.2-RELEASE-amd64-20121126-1712.tgz.

All the rest is working fine so far :). Great work! Nevertheless, I will be waiting for the official 2.0.2 release before I'm going to upgrade my production machines.