I subscribe to the thunderbird latest/candidate channel (because i needed some functionality from the slightly never thunderbird version) and then one day, the thunderbird profiles did not work anymore. So it seems thunderbird 141.0-3 went to candidate, the snap upgraded the profile version, then later a thunderbird 128.13 went candidate(stable is a 128.12) which does not work with the new profile version.
So i reverted to the 141 thunderbird and I guess I need to wait for a newer thunderbird to make it to stable and switch to stable channel i guess.
Is that the intended use of the candidate channel?
For the moment I switched to stable channel and set hold for a week.
I guess using epochs on the thunderbird side would prevent these cases?
As far as understand using the profile version or the thunderbird version if the data format changes should work. So e.g. 128* and 141* being the epochs in this case.
The 141 thunderbird would have upgraded the profiles, but it would have prevented the binary downgrade to thunderbird 128.
@hellsworth1 should i maybe make this a feature request?
hi A333, so sorry the candidate channel bit you! as you correctly identified, the candidate channel was rolled back to 128 to stay in line with the ESR in latest/stable. (We will be updating the latest/stable channel to the most recent 140 ESR sometime in August.)
you can only go forward (increasing major number) with a profile and still have it work. so that’s why it didn’t work when you went from 141 to 128.
I would recommend that you instead track the latest/beta since this is essentially the monthly release, and your profile will work again.
Did you people change the channels? I refreshed to revision 775 which is published on latest/beta (while holding and tracking latest/stable) and it told me something unexpected.
‘Channel latest/stable for thunderbird is closed; temporarily forwarding to beta’
snap info thunderbird still shows the latest/stable channel though.
Don’t have access to the machine right now. I tried successfully to reproduce on another system:
snap refresh --channel latest/candidate
snap refresh --revision 767
snap refresh --hold
snap switch --channel latest/stable
snap refresh --revision 775
That gave shortly a confusing message like ‘Downloading thunderbird (775) from channel latest/stable’ and then the install success message and then the ‘closed’ message.
I also tried 769 and that gave
Channel latest/stable for thunderbird is closed; temporarily forwarding to candidate.
So I guess the message actually means ‘Revision 775 for thunderbird is not available on channel latest/stable; it is currently published on channel latest/candidate.’ or
‘Revision 775 for thunderbird was never published on channel latest/stable; temporarily forwarding to candidate.’.
Also the ‘temporarily forwarding’ is a bit cryptic. But it may make sense, depending on how the store is implemented.
Seems the message should be part of the paperclip initiative or the store use cases are not too well defined.
Wow, you are giving Snapd a serious reliabillity test there. (: I didn’t even now switch.
I wouldn’t refresh directly to a revision number because that wouldn’t track a different channel. So if you are just trying to follow Heather’s advice, the canonical command would be
snap refresh --beta thunderbird
Hopefully that will get past the confusing output or state.
Using a certain revision with hold works quite well if you do not want any surprises.
I do not need any new features, I am fine with the ESR version and would like to switch back to that as frictionless as possible.
So I need thunderbird on the ESR track (in future i guess that will be the latest track); a newer version which supports my profiles.
And I need to prevent to upgrade to a newer profile version while trying to get the latest security updates. Yikes.
yes, but the ESR version does not work if you started a newer thunderbird inbetween; which converted the profile version. I need to wait until the ESR version is at least as new as the current one.
My profile works with the installed version, but prevents starting with current ESR version
The ESR profile version will probably never match the monthly profile version. So I need to hold the package until ESR fits. But in the meantime i do not get any updates for the installed version, missing out also on security updates.
Yikes. I checked out the firefox release train schedule which i think thunderbird follows, and it will be 140 all year long.
So I guess no ESR for me on this machine. I will unhold and follow the monthly track until it breaks (hoping it won’t) and then spend the time to recreate on the ESR track.
The ESR profile version will probably never match the monthly profile version. So I need to hold the package until ESR fits. But in the meantime i do not get any updates for the installed version, missing out also on security updates.
Ah, that makes sense.
Yikes. I checked out the firefox release train schedule which i think thunderbird follows, and it will be 140 all year long.
Yikes indeed, sorry about that.
One last thing you could try after backing your profile up: --allow-downgrade. Maybe…
