My understanding (which may be flawed) is basically:
1. SeaMonkey 2.46 checks a server at a particular address to find the
latest version and therefore whether an update is available
2. That server has been changed and, for whatever reason, now has a
different address
3. SeaMonkey <= 2.46 does not know about that change, and keeps checking
the old address
4. It doesn't find any updates, because the server is no longer at that
address
5. SeaMonkey >= 2.48 has the new address, so once that's installed it
can find and install future updates [*]
6. See 1 (There's a hole in my bucket...
<https://en.wikipedia.org/wiki/There's_a_Hole_in_My_Bucket>)
The only thing "broken" about the update checker in 2.46 is that it
checks an address which was correct at the time it was released but
isn't any more.
There might be an about:config entry specifying the address check for
updates. But that can't be changed automatically without an update to do
it, so would be a manual change for a one-off update, and would probably
have to be reset afterwards to avoid the override breaking future
updates. Probably easiest and safest just to download the full installer
this one time!
Mark.
Ant via support-seamonkey wrote:
Are you saying v2.46 and earlier's update checkers are broken? :( I
thought it was a server issue?
On 7/31/2017 8:38 AM, Frank-Rainer Grahl wrote:
Yeah but how should we put up a message here if updates of the browser
are not working. Chicken and egg :)
FRG
Ant wrote:
No, when using SM's GUI's menu's "Check for Updates" option.
On 7/31/2017 7:31 AM, Frank-Rainer Grahl wrote:
Its red and big and I see it :)
Automatic upgrades from previous versions are not working for this
release.
Please download the full installer from the downloads section and
install
SeaMonkey 2.48 manually over the previous version.
FRG
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
