What did the 10.8.2 update do to break an AMP stack's vhosts?

I updated from 10.8.1 to 10.8.2 last week and since then I have yet to get certain vhosts working on my local sandbox. Some of them work fine while others just don't work at all now when they did previously. Is there anything I can do to get those working again?

Working Vhost:

<VirtualHost *:80>
    DocumentRoot "/Users/reindeerdev/Sites/patron-social-club-v2-old/app/webroot"
    ServerName pscv2.local
    ErrorLog "/private/var/log/apache2/pscv2-error_log"
    CustomLog "/private/var/log/apache2/pscv2-access_log" common
    <Directory /Users/reindeerdev/Sites/patron-social-club-v2-old/app/webroot>
        Options All
        AllowOverride All
        Order allow,deny
        Allow from all
    </Directory>
</VirtualHost>

Problematic Vhost:

<VirtualHost *:80>
    DocumentRoot "/Users/reindeerdev/Sites/Patron_Intranet/app/webroot"
    ServerName intranet.local
    ErrorLog "/private/var/log/apache2/intranet-error_log"
    CustomLog "/private/var/log/apache2/intranet-access_log" common
    <Directory /Users/reindeerdev/Sites/Patron_Intranet/app/webroot>
        Options All
        AllowOverride All
    </Directory>
</VirtualHost>

Finally saw something in my Apache configs:

[Tue Oct 16 10:52:03 2012] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
httpd: Could not reliably determine the server's fully qualified domain name, using Logans-iMac.local for ServerName
[Tue Oct 16 10:52:06 2012] [warn] NameVirtualHost *:80 has no VirtualHosts
[Tue Oct 16 10:52:09 2012] [notice] Digest: generating secret for digest authentication ...
[Tue Oct 16 10:52:09 2012] [notice] Digest: done
[Tue Oct 16 10:52:09 2012] [notice] Apache/2.2.22 (Unix) PHP/5.3.15 with Suhosin-Patch DAV/2 mod_ssl/2.2.22 OpenSSL/0.9.8r mod_perl/2.0.5 Perl/v5.12.4 configured -- resuming normal operations

I know for a fact that I have Include /etc/apache2/other/httpd-vhosts.conf in my httpd.conf file and that I have confirmed that that is the correct vhosts file that I'm using.

Determined there was a very odd user permissions change on the ~/Sites folder that was causing these errors. Fixed.