![seamonkey 2.46 seamonkey 2.46](https://filepony.de/screenshot/seamonkey1.jpg)
(In both Seamonkey and Firefox, I am subscribed to the Adblock Warning Removal List. Yet I am not getting the "You are using an ad-blocker" warning in Seamonkey!! In Seamonkey, however, I do not even have Greasemonkey installed (!) so I am not usking the AAK usercript, nor am I subscribed to the AAK filter list. The weird thing is, in Firefox I have the Anti-Adblock Killer userscript installed (utilized by Greasemonkey), and I am subscribed to the Anti-Adblock Killer filter list.
#Seamonkey 2.46 free
If I use Seamonkey 2.46 (64-bit Linux), I get no such warning it's all free and clear: Send the announcement to newsgroups and about-mozilla.If I use Firefox 51.01.1 (64-bit Linux), I get the warning of doom: hg push ssh://hg./SeaMonkey/seamonkey-project-org.Used 'Force Build' to start the final_verification builder all tested URLs are HTTP 200 and 302 - ready for going public! Used mirrorpush.sh as documented in 2.0.3 notes to finally push the files to the public dir for mirrors to pick them up. I used the TrendMicro provided staging ftp directory to stage 2.15b2 win32 (all locales) for them to scan, and be sure there are no false-positives.Į-mailed our TrendMicro contact to let him know of the new version available on their FTP server. With make-checksums.sh as documented in 2.0.3 notes, created MD5SUMS and SHA1SUMS files containing all files we release - copying the README from last time and replacing the versions as needed, as well as doing the same for Linux x86_64.
#Seamonkey 2.46 windows
Used zipcopy.sh as documented in 2.0b1 notes to move the Windows zips into the directory we want them in for release. Used langpackmove.sh as documented in 2.0b1 notes to move the langpacks into the directory we want them in for release. Changed reference paths in verify.sh and the workdir that verify.sh and the command to call verify.sh finally unhorked the verifications (particularly macos圆4).
#Seamonkey 2.46 update
![seamonkey 2.46 seamonkey 2.46](https://windows-program.com/uploads/posts/2017-07/1498939868_seamonkey.png)
_l10n_verify and updates started automatically, triggered by the fake-signing.No longer needed to send info to metrics. We have no signing infrastructure for SeaMonkey right now, so I faked the signing step that is usually done after completion of builds and L10n repacks and before the update generation.
![seamonkey 2.46 seamonkey 2.46](http://cuccokhalomban.csillagpor.hu/pict/sea-monkey-screenshot-3.jpg)
On, modified ~/versions.sh for the current release run.ĭue to the change in our upload/download hosts, the whole update process on stage.mo have been updated.