|
Using git pull
|
05-11-2015, 11:20 PM
This could be a lack of write permission on the vtigerversion.php file. The last step of the process modifies the version number in that file.
Make sure the value contained inside that file is the same as the one you have in the database vtiger_version table
Joe
TSolucio 
05-12-2015, 05:40 AM
(This post was last modified: 05-12-2015, 08:11 AM by polanskiman.)
I have the same issue that Mweaver. I tried the git config core.fileMode false in order for git to discard all those files where the permissions where different from default. When I run git status again, git is showing fewer files, which is expected. I still have got a few though but those are probably the files where the code have been updated. After that section I have the following:
Untracked files: (use "git add <file>..." to include in what will be committed) 18145484715374875319e474.87062199install.php.txt 18145484715374875319e474.87062199install/ SendReminder_OBSOLETE.php build/wsChanges/CPAuthenticateContact.php build/wsChanges/CPChangePortalPassword.php ETC ETC ETC I've done a git add <filename> and that got rid of the problem. I still have got a problem though. When I finally try git pull I get the following: Code: serv> git pullWhat should I do?
05-12-2015, 06:40 AM
(This post was last modified: 05-12-2015, 06:41 AM by polanskiman.)
I have a recommendation. Why not post the default file permissions of all files (or type of files/directories) so that a user can simply re-apply those permissions to the CoreBOS directory and files if need be. At present I am applying the permissions that you (Joe) recommended but still GIT sees a lot of files as not having the proper permission. I am currently using the following:
Code: chmod 775 corebos
05-12-2015, 10:37 PM
You can't add the files because they are already in the project, that is why you get a conflict when you try to pull, you have to delete untracked files that are already in the base project. You can use "git reset" if you haven't committed the changes.
As to the recommended permissions the thing is that git versions the state, whether I want to or not, git is going to register and control that information, so the recommended status is the one in the repository (in most of the files). If you need something different for your specific install then you simply execute the "ignore" command on your system. I really have no choice.
Joe
TSolucio
05-13-2015, 03:47 AM
(This post was last modified: 05-13-2015, 04:16 AM by polanskiman.)
(05-12-2015, 10:37 PM)joebordes Wrote: You can't add the files because they are already in the project, that is why you get a conflict when you try to pull, you have to delete untracked files that are already in the base project. You can use "git reset" if you haven't committed the changes. Well those untracked files that I added are not the ones that are showing when I do a git pull. Anyways I did a git reset as recommended, did a git status then deleted all untracked files from CoreBOS directory then did a git pull. Same problem. This is what I get: Code: Serv> git pull
05-14-2015, 04:44 AM
Hi Joe,
All this was giving me too many headaches so I did a fresh install with a migration as described here http://corebos.org/documentation/doku.php?id=en:upgradevt2cb All seems to be working fine up until now. The question remains on what will happen next time if I chose to customise the code. Will I need to go through all this process again?
05-14-2015, 06:14 AM
I don't really know because I don't know the source of the problem. All I can say as that all my installs are done with git control and updated constantly with very little effort, just having to solve some conflict in personal customizations from time to time. I mean: I am not having problems at all with this approach.
Keep me informed.
Joe
TSolucio |
|
« Next Oldest | Next Newest »
|
