Hello Andrea,
Am 31.07.19 um 15:40 schrieb Andrea Borgia:
> Hello, Carsten.
>
>
>> unfortunately I needed to revert your modifications after I've read
>> it several times. The added additional section was more than less
>> completely redundant to the exciting section just before!The section
>
> While that section might seem "exciting" to you, it left me scratching
> my head: it provided no meaningful pointers towards a solution, unlike
> my edit. I am also a bit disappointed that what I've learnt while fixing
> this migration error cannot be passed on to the community.
the wrapper script was made to create a working new environment for the
users TB profiles after the rollout of the packages and de-branding them
back to Thunderbird.
It was *not* made for directly modifications on the file system in
parallel made by the users them self!
And the root for your reported issue wasn't the TB profile folder migration.
If you are missing some further hints, did you have followed the logging
output of the starting wrapper and / or have taken a look at the README
file within /usr/share/doc/thunderbird?
> 219 output_debug "There are already the folders or symlinks
> '${TB_PROFILE_FOLDER}' and '${ID_PROFILE_FOLDER}'"
> 220 output_debug "which not pointing to each other, will do nothing as
> don't know which folder to use."
> 221 output_debug "Please investigate by yourself! Maybe you will find
> additional information in '/usr/share/doc/thunderbird/README.Debian.gz'."
Do you believe it's really likely that about 2.5 years after the
de-branding of Thunderbird and the profile migration issue are happen
often? I haven't seen a bug report on this or some private email to me
about issues regarding to a wrong or not working TB profile folder for
about 2.25 years now. So I must getting hardly convinced that the script
isn't working.
We can write much more documentation and guidance for sure, users will
always find something that is not covered.
BTW: Until now nobody come up with a meaningful help and some
preparations about this topic, and I haven't expected any help. :)
But now I also don't see any deeper need to spend more time on this. The
de-branding is almost history and people still have a working TB
profile. Even if they have enabled AppArmor.
--
Regards
Carsten Schoenert
