2 fplanque Mar 28, 2020 03:59

You're always argumentative, Francois, and it's really tiring.
There is no step 4 and no file permissions are asked for.
Just trying to give people who go through this a hand, because nobody has EVER unequivocally answered this, least of all you.
Hi @gerardp I suppose the note @fplanque has refered to is only in the manual @ https://b2evolution.net/man/upgrade-file-options and, as you said, is not asked for during the upgrade.
My query would be ~ Why does this happen during an auto upgrade and not only on the Debian example given, I say would as I'm not currently looking for an answer :)
It is in the more recent releases, it has been specifically added to address the problem described here.
I am providing this info for other people who may land here and may not need a more complicated solution than to enter the file permissions required by their specific host in the appropriate fields.
@gerardp you provided no version info
Hi Francois:
I did not provide version info, because I have been running into this problem for at least two years now, and have sometimes postponed upgrading because of it.
But, just for the sake of it, I'm running 6.11.5 stable, and now I have figured it out, will update on a more regular basis.
Thanks,
Gerard
Did you enter the correct file permissions at step 4 here:?
https://b2evolution.net/man/auto-upgrade-procedure#step-4-ready-to-upgrade