Frank-Rainer Grahl wrote:
Don Spam's Reckless Son wrote:
It took OpenSuse until 10 days ago before they finally released a
2.53.x version via the standard repositories (their Mozilla Test
repository has been kept current since around 21 April) and the reason
for that was that there was apparently a loss of functionality between
the last 2.49.x level and the 2.53.x line.
Yes what was the loss of functionality? It't can't be bigger/greater
than Fx 52 to 57 or higher. I know they had compile problmes. IanN even
gave up trying to build a test release under OpenSuse.
Of course that does not explain why they stuck at 2.49.4 rather than
2.49.5.
This mattered to me because:
- a new version of OpenSuse Leap was released with 2.49.4
- the update process (I think) changed the default for html from
Firefox to Seamonkey so opening an html page nuked my (migrated)
Seamonkey profile.
At least that happened on my test machine so no real data was lost.
Profiles were always in different locations. Changing default browsers
should never inflict a profile loss. If this was the case it was not an
official release doing this and that is what I talk about. The official
release works fine on OpenSuse because that was what I run on my backup
server.
Before Upgrade: 2.53.3 (at a guess, or maybe 2.53.2)
After Upgrade: 2.49.4
This was an upgrade of OpenSuse, "before" used their test repository,
"after" did not. What could possibly go wrong?
There is really one obstacle and that is migration from pre 2.53.x to
the later nss with a master password in place. That is basically why the
backup profile before upgrading warning is still in place. Andthere may
be problmes with ancient add-ons and themes too. It can't be helped.
Either someone updates them or they are gone.
There may be reasons to stay on an older release but citing the growing
list of known problems is just laughable. Older releases had far more
problems.
I have seen no missing functionality since upgrading to 2.53.4, but it
was the reason cited when we asked what the holdup was. There have been
a couple of "issues" with "save as" not working as before (or in one
case, at all) but Nuno Silva pointed me at the solution to the worst
variation.
That said everyone can do what he/she wants.
FRG
--
spammo ergo sum, viruses courtesy of https://www.nsa.gov/malware/
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
