Justin Wood (Callek) wrote: > Ant wrote: >> but no internal updates yet. > > Indeed. > > Symantec again, they changed their internal process on us, and our > builds themselves were ready late thursday, while I was hoping that > Symantec would get back to me with a "we have whitelisted you" on > Friday, it seems they did not. > > I plan to (within the next 24 hours):
Ended up being even faster than that :-) > > * Install the stable 2.14 > ** Update it to 2.14.1 (by setting myself onto the "releasetest" update > channel manually) > ** See if my local, up-to-date copy of Symantec gives us the same issue > we have seen in the past. Sadly this ended up proving that Symantec was still leaving me with a broken SeaMonkey after update. So.... > * if it CONTINUES to give us an issue, I'll: > ** Manually split out windows from the update snippets > ** Push all other OS snippets This is done, now just waiting for Symantec for win32 updates (those windows users without Symantec, or willing to fight with their Symantec client can still update without issues) > ** and ONCE SYMANTEC SAYS WE ARE WHITELISTED push the windows snippets > [likely monday] -- ~Justin Wood (Callek) _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
