X
Tap here to go to the mobile version of the site.

Support Forum

How to switch update channel from beta to release

Posted

Hi, I'm currently using Thunderbird 70.0b4 on Mac. I would like to abandon the beta channel and switch back to the release one, but the simple re-install method I've read elsewhere does not fit my situatioin: if I install the current release (68.2.1) and start it, it complains that my profile has been created with a more recent version and refuses to start.

Of course I do not want to create a profile from scratch because I have tons of accounts, rules, etc. in my old profile.

What can I do? Will a future release version be "recent enough" that it will be able to read my 70beta profile?

Thanks.

Hi, I'm currently using Thunderbird 70.0b4 on Mac. I would like to abandon the beta channel and switch back to the release one, but the simple re-install method I've read elsewhere does not fit my situatioin: if I install the current release (68.2.1) and start it, it complains that my profile has been created with a more recent version and refuses to start. Of course I do not want to create a profile from scratch because I have tons of accounts, rules, etc. in my old profile. What can I do? Will a future release version be "recent enough" that it will be able to read my 70beta profile? Thanks.

Modified by starless1

Chosen solution

When you downgrade versions using the same profile you must force Thunderbird to use the profile that has been used by a newer version by

 thunderbird -P --allow-downgrade
Read this answer in context 1
Quote

Additional System Details

Application

  • User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36

More Information

Toad-Hall
  • Top 10 Contributor
1865 solutions 12649 answers

re : if I install the current release (68.2.1) and start it, it complains that my profile has been created with a more recent version and refuses to start.

Try this:

In Thunderbird Help > Troubleshooting Information Under 'Application basics' at the bottom of list see 'Profiles' click on 'about:profiles'

You should see a new default profile and below it your original one should be listed. click on 'Set as default profile' click on 'Launch profile in a new browser' - do not worry, they got the text wrong, it launches in a new window.

then close the first Thunderbird window.

re :'' if I install the current release (68.2.1) and start it, it complains that my profile has been created with a more recent version and refuses to start.'' Try this: In Thunderbird Help > Troubleshooting Information Under 'Application basics' at the bottom of list see 'Profiles' click on 'about:profiles' You should see a new default profile and below it your original one should be listed. click on 'Set as default profile' click on 'Launch profile in a new browser' - do not worry, they got the text wrong, it launches in a new window. then close the first Thunderbird window.
Was this helpful to you? 0
Quote
Toad-Hall
  • Top 10 Contributor
1865 solutions 12649 answers

Make sure Thunderbird is not running. Try launching Profile Manager, then selecting the correct profile on which to open to see if this updates the 'installs.ini' file.

http://kb.mozillazine.org/Profile_Manager#Mac_OS_X

Make sure Thunderbird is not running. Try launching Profile Manager, then selecting the correct profile on which to open to see if this updates the 'installs.ini' file. http://kb.mozillazine.org/Profile_Manager#Mac_OS_X

Modified by Toad-Hall

Was this helpful to you? 0
Quote

Question owner

Thank you Toad-Hall, but both your suggestions still take me to the same point: Thunderbird 68.2.1 refuses to load my profile.

Thank you Toad-Hall, but both your suggestions still take me to the same point: Thunderbird 68.2.1 refuses to load my profile.
Was this helpful to you?
Quote
Wayne Mery
  • Top 25 Contributor
  • Moderator
602 solutions 5776 answers

Chosen Solution

When you downgrade versions using the same profile you must force Thunderbird to use the profile that has been used by a newer version by

 thunderbird -P --allow-downgrade
When you downgrade versions using the same profile you must force Thunderbird to use the profile that has been used by a newer version by thunderbird -P --allow-downgrade
Was this helpful to you? 1
Quote

Question owner

Wow, thanks, I did not know about this option. But can I be sure that nothing in my profile is lost or damaged when forcing the downgrade in this way?

Wow, thanks, I did not know about this option. But can I be sure that nothing in my profile is lost or damaged when forcing the downgrade in this way?
Was this helpful to you?
Quote
Wayne Mery
  • Top 25 Contributor
  • Moderator
602 solutions 5776 answers

starless1 said

Wow, thanks, I did not know about this option. But can I be sure that nothing in my profile is lost or damaged when forcing the downgrade in this way?

No, you cannot assume there will be no damage. That's why by default there is a check.

That said, I've used --allow-downgrade several times and not had a problem. But if you do this some time in the future, all bets are off.

''starless1 [[#answer-1264265|said]]'' <blockquote> Wow, thanks, I did not know about this option. But can I be sure that nothing in my profile is lost or damaged when forcing the downgrade in this way? </blockquote> No, you cannot assume there will be no damage. That's why by default there is a check. That said, I've used --allow-downgrade several times and not had a problem. But if you do this some time in the future, all bets are off.
Was this helpful to you?
Quote

Question owner

Wayne Mery said

No, you cannot assume there will be no damage. That's why by default there is a check.

Thanks, that's what I expected indeed, and it was strange to me that you did not write a warning about it in the first reply ;).

I did a backup of my profile and then tried your suggestion, and everything seems to be fine at the moment.

But I was wondering, for future information: if I keep using the beta but I stop updating it, will the release version one day arrive to a point where it will be able to use the old beta profile without any workaround? In theory, it should... How is the check performed?

''Wayne Mery [[#answer-1264720|said]]'' <blockquote> No, you cannot assume there will be no damage. That's why by default there is a check. </blockquote> Thanks, that's what I expected indeed, and it was strange to me that you did not write a warning about it in the first reply ;). I did a backup of my profile and then tried your suggestion, and everything seems to be fine at the moment. But I was wondering, for future information: if I keep using the beta but I stop updating it, will the release version one day arrive to a point where it will be able to use the old beta profile without any workaround? In theory, it should... How is the check performed?
Was this helpful to you?
Quote
Wayne Mery
  • Top 25 Contributor
  • Moderator
602 solutions 5776 answers

I think you are asking whether startups AFTER you use --allow-downgrade will work without it. I think yes. As long as you do not go BACK in versions on that Thunderbird profile.

> How is the check performed?

It is complicated

I think you are asking whether startups AFTER you use --allow-downgrade will work without it. I think yes. As long as you do not go BACK in versions on that Thunderbird profile. > How is the check performed? It is complicated
Was this helpful to you?
Quote

Question owner

Wayne, what you write is correct, after using --allow-downgrade I can start TB normally, the profile is now definitely downgraded. But I was not asking this.

Here is what I was asking instead. Let's forget about --allow-downgrade, let's suppose it does not exist - or maybe we do not want to use it to be on the safe side and prevent profile corruption.

In my situation, the release version of TB refused to load the beta profile because it detects that it is newer and there is the possibility that it contains new features unsupported in the release version.

But when time passes and the development of the release version goes forward, soon or later the release version of e.g. year 2020 will be NEWER than the beta version of 2019, all features of the 2019 beta should have been included in the 2020 release. So the release version will be able to load the old beta profile without any warnings.

Will this happen? Or will the release version ALWAYS warn about loading a beta profile, even if it's in a very old format?

Wayne, what you write is correct, after using --allow-downgrade I can start TB normally, the profile is now definitely downgraded. But I was not asking this. Here is what I was asking instead. Let's forget about --allow-downgrade, let's suppose it does not exist - or maybe we do not want to use it to be on the safe side and prevent profile corruption. In my situation, the release version of TB refused to load the beta profile because it detects that it is newer and there is the possibility that it contains new features unsupported in the release version. But when time passes and the development of the release version goes forward, soon or later the release version of e.g. year 2020 will be NEWER than the beta version of 2019, all features of the 2019 beta should have been included in the 2020 release. So the release version will be able to load the old beta profile without any warnings. Will this happen? Or will the release version ALWAYS warn about loading a beta profile, even if it's in a very old format?
Was this helpful to you?
Quote
marco28 0 solutions 2 answers

Hi everyone. I am having the same problem, was trying a beta last year before 68 was out, and now I am "stuck" on the beta channel because there is one beta after another since then, going from 69 to 73 without a corresponding version as an official release ever. I just stopped updating at version 72b3 hoping one final day I can install a release version 72. But no, it just went to 73 beta...

This wouldn´t be that annoying if there would be a simple release channel switch in the settings. Excuse my steam (it´s just so so annoying to always be having to refuse updates now), but why the hell isn´t there just such a switch? I could just put my TB back on release channel and it would just wait until a final release comes out that is newer than my beta.

So if anyone who has an influence on this reads this, PLEASE make TB have a simple switch for that.

Hi everyone. I am having the same problem, was trying a beta last year before 68 was out, and now I am "stuck" on the beta channel because there is one beta after another since then, going from 69 to 73 without a corresponding version as an official release ever. I just stopped updating at version 72b3 hoping one final day I can install a release version 72. But no, it just went to 73 beta... This wouldn´t be that annoying if there would be a simple release channel switch in the settings. Excuse my steam (it´s just so so annoying to always be having to refuse updates now), but why the hell isn´t there just such a switch? I could just put my TB back on release channel and it would just wait until a final release comes out that is newer than my beta. So if anyone who has an influence on this reads this, PLEASE make TB have a simple switch for that.

Modified by marco28

Was this helpful to you?
Quote
Wayne Mery
  • Top 25 Contributor
  • Moderator
602 solutions 5776 answers

> So if anyone who has an influence on this reads this, PLEASE make TB have a simple switch for that.

It's a noble idea. But it's not possible for a variety of reasons.

Perhaps there could be documentation to better describe the process of going from beta to release.

> So if anyone who has an influence on this reads this, PLEASE make TB have a simple switch for that. It's a noble idea. But it's not possible for a variety of reasons. Perhaps there could be documentation to better describe the process of going from beta to release.
Was this helpful to you?
Quote
marco28 0 solutions 2 answers

Yes, some documentation would be great.

As you for sure are having much more technical insight than me I trust you here, but still it seems quite incomprehensible.

I mean, mankind was going to moon, Russian hackers can make the world have Trump, but it´s not possible to let Thunderbird automatically wait for the next normal release update that is newer than the installed beta and then install that one? ;-)

Yes, some documentation would be great. As you for sure are having much more technical insight than me I trust you here, but still it seems quite incomprehensible. I mean, mankind was going to moon, Russian hackers can make the world have Trump, but it´s not possible to let Thunderbird automatically wait for the next normal release update that is newer than the installed beta and then install that one? ;-)
Was this helpful to you?
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.