Many files in the data/TWiki directory are now readonly.
This gives the famous "RCS: failed to create file /var/www/t41b1/data/TWiki/CommentPlugin.txt: Permission denied" error.
ALL data files should be rw-rw---- and the ,v files r--r-----
It seems that either the build script messes things up or many MANIFEST entries are all wrong.
I will investigate more
I checked the MANIFEST of TWiki core and some extensions. It is the extension topics that have the wrong access rights. I also checked some of the extension MANIFESTS and they are correct. So this is a build script issue.
I was going to build a beta2 but now we need this build problem resolved first.
It is because of this bug that I have not yet built a beta 2. I can build a beta 2 without this fixed but it requires that I manually set all the access rights in a special unpacked tgz and then re-tar it up. And it would be nice to avoid this. In 4.0.5 there was not this error so it is something that was broken recently.
I just tried to build a beta2. And this issue is still not resolved.
If you build a TWiki release now you have to manually fix the access rights afterwards.
Since the beta1 has bugs that prevents testing configure fully I would really like to release a beta2. There are no bug reports filed on the configure extension installer from beta testers because of this (except from me).
Can we please have the build script fixed. I have tried myself but I cannot see where the extension access rights are altered.
The build script in 4.0.5 does not have this problem so it is a problem introduced within the last couple of months.
Changed to requirement and changed the bug item title so it hopefully get noticed.
You are doing better than me then; i can't even get past the multitude of failing unit tests....
The problem is due to some code Steffen checked in to build.pl to address Item2029
. This code RCS commits .txt files coming from extensions, but it doesn't correct the permissions of the checked out files after the checkin.
Fixed, and also added warning message about building a release without passing unit tests, as this is REALLY bad practice.