[Solved] What did I do to TortoiseSVN???

[Giu]

"http://svn.freepascal.org/svn/lazarus/trunk/trunk does not exist

Only one "trunk"
See http://wiki.freepascal.org/Getting_Lazarus#Getting_Lazarus_SVN_development_version

In the other side, I accustomed to start always Lazarus with --pcp=./config to avoid conflict configurations

This way I can have stable version and svn version without conflict (well, when building Laz worked for me, it does not build anymore from svn :_( )

[JuhaManninen]

But I keep my FPC directory inside the Lazarus directory.

Uhhh...

If I can't resolve this very soon I will have to do a complete uninstall and reinstall - again.

What means "uninstall and reinstall" the Lazarus SVN trunk version? You don't "install" it. You just run "make clean all" or similar and then run it.

Does anyone know if Lazarus uninstall cleans up the registry?

Lazarus does not use Windows registry. You should know it by now!

[Avishai]

What I mean by reinstall is by using ftp://freepascal.dfmk.hu/pub/lazarus/snapshots/ to get a new snapshot.  The latest seems to be Lazarus-1.1-41377-fpc-2.6.3-20130524-win64.exe.  In order to use it I must first uninstall Lazarus.  I've had to do this a few times.

And why do you think I should know that Lazarus doesn't use the registry?  Why would I even look to see as long as things are working properly?  Now I know.  I also don't see why you thing keeping FPC inside the Lazarus directory is odd.  As long as the paths are set properly it can be anywhere.  You should know this by now!

[Martin_fr]

You don't need to know, if it uses registry. But you might have noted, that installers (for some time now) offer to clean out config, if you want them to do so.
Therefore you need not know where it is.

Using SVN though is seen as an advanced field, and you should aim to learn where those thinks are. Follow my instructions in my previous post, and find the primary-config-path in the DIE internals.

Keeping FPC inside lazarus is in itself ok.
BUT (very big BUT):
Within an SVN checkout, you usually just have the SVN data, potentially a temporary backed up file of no value....
True, it does work. The thousands of extra units are no diff to the 1 or 2 (or even 50) temporary backups. It just is not the usage that one would expect with something like SVN.

[Avishai]

Thank you Martin_fr for your curious response. 

Actually I don't want it to clean the config.  That's why I asked about the registry.  I can back that up if need be.

You obviously have a different view but my reasoning on the location of FPC dir. is that Lazarus doesn't work without FPC.  Keeping such closely related items in one location instead of separately makes sense to me.  I know the development efforts are separate, but functionally, FPC is just as much a part of Lazarus as LCL or the debugger.  And SVN has had no problem with that.

If there is some concrete reason why FPC should be located elsewhere, I will gladly bow to your better understanding of the whole FPC/Lazarus effort.  You have far more experience with this than I do.

But I'm still no closer to solving my problem.

[Martin_fr]

It is similar, to you having your own project, which may use the indy package. You can keep the indy package in your project, but most people probably do not

It does not break anything, if you keep fpc in the SVN folder.

Note the distinction, Even though they are the same folder, the Lazarus and the SVN folder have different meanings...

I do not know if it causes extra load. Tortoise cache may scan all the extra fpc files.

To SVN the entire fpc folder are uncommitted files. Files that you may want to add to the repository (if you had write access), or files that you may want to be part of a patch that you make from your SVN checkout.

Sometimes you may have left overs in the folder, then you can tell SVN to delete uncommitted files.... You can still do, but you need to always uncheck fpc....

It is just the difference, between:
- a normal installation from installer => all in one folder
- SVN where you would see Lazarus as a project, that you keep in its on folder without other stuff.

------------
If my SVN goes wrong, then I can delete all,  but the top level directory (keeping only the one .svn folder, and lazarus.exe) and svn will restore all.

[JuhaManninen]

What I mean by reinstall is by using ftp://freepascal.dfmk.hu/pub/lazarus/snapshots/ to get a new snapshot.  The latest seems to be Lazarus-1.1-41377-fpc-2.6.3-20130524-win64.exe.  In order to use it I must first uninstall Lazarus.  I've had to do this a few times.

Do you mean you have a snapshot installed, and you are running it, at the same time you test your SVN trunk version? Do you use the same config settings for both, or do you use --pcp parameter for separate configs?

Using a SubVersion client is an extremely easy task. Building Lazarus from the trunk repo is also an extremely easy task.
Apparently you have problems with both which means you are doing something fundamentally wrong. I am trying to figure out what that is.
You already got advice from others but here is some more:
1. Get rid of the snapshot installations. Then never install them again. Pretend they don't exist!
2. Make sure you have FPC installed. FPC 2.6.2 is preferred. Test it on a cmd line.
3. Delete your local Lazarus configuration if you doubt it is corrupted.
4. Revert any possible local changes in your SVN directory. See "Revert" in TortoiseSVN menu in file explorer, or do "svn revert -R ." on cmd line.
5. Update the latest Lazarus sources to your SVN directory.
6. Build with "make clean all".
7. Start from cmd line: "lazarus".

And why do you think I should know that Lazarus doesn't use the registry?  Why would I even look to see as long as things are working properly?  Now I know.

You have told yourself that things are NOT working properly. With configuration problems the fist question usually is: "Where is this data stored?".

I also don't see why you thing keeping FPC inside the Lazarus directory is odd.  As long as the paths are set properly it can be anywhere.  You should know this by now!

It is odd because it brings no benefits but it causes lots of problems.
You even noticed it yourself when you had to copy FPC directory again back to your Lazarus SVN directory, didn't you?
It also slows things down when TortoiseSVN is tracking files which can potentially be revisioned.
Typically only revisioned files, and files generated from those files, are kept in an SVN directory. If you add a file there, then you typically plan to add it under revision control later.

[Avishai]

OK.  I have resolved the issue (I hope).  I did the uninstall/reinstall as I described above and that seems to have fixed whatever was wrong.  I am now able to recompile Lazarus and install packages again.

I also bowed to Martin_fr's judgement and relocated FPC to a separate directory.  I did an update and to be honest, I couldn't see any difference but just doing it one time is not a fair test.  I may see some difference later on with more updates.

[Martin_fr]

On a fast computer, with enough memory you may not notice it in speed.
And you probably do not bother to wait for all the overlay icons. Or you do not often ask SVN for locally "modified files"....

But the difference comes when you get problems with SVN. Now you do not need to touch FPC, even if you need to do Lazarus from scratch.

[Avishai]

Thanks Martin_fr.  I see your logic in relocating it outside and I know you're are far more familiar with it than I am.  And I appreciate you taking the time to explain it.  What I was doing seemed logical and still does, but FPC will remain outside the Lazarus dir.  Anyway, I seem to be back in good shape now.  Thanks.

[JuhaManninen]

OK.  I have resolved the issue (I hope).  I did the uninstall/reinstall as I described above and that seems to have fixed whatever was wrong.  I am now able to recompile Lazarus and install packages again.

Did you install a snapshot after all? Don't do that. When you use SVN, you don't need a snapshot, ever.
This is the fundamental error you still have.

[Avishai]

And when SVN doesn't work?  That's what started the whole thing, remember?

[Giu]

And when SVN doesn't work?  That's what started the whole thing, remember?

I think Juha apeáis about to daily snapshot

[JuhaManninen]

And when SVN doesn't work?  That's what started the whole thing, remember?

It works almost always. The only time it does not work is when the server is down and that is seldom.

All your problem are caused by having many copies of Lazarus sources and executables, and screwing up your local config. I know it from practice myself. If you only open a package from the other repo directory, you are in trouble. Wrong paths were added to configuration, things start to behave odd.
An easy remedy is to always use --pcp parameter, and to delete the local config dir after you have screwed it up.
Unfortunately you didn't even know those things and could not to fix it.

First you must be comfortable with one copy of Lazarus sources. Use only the sources from SVN.
Later when you are absolutely sure what you are doing, then you can jump between many versions.

A guaranteed way to get a working system always:
1. Revert local changes in SVN repo.
2. Delete your local Lazarus configuration.
3. Do a clean build of Lazarus.

That's it.

[Avishai]

I have exactly ONE copy.  And the SVN server wasn't down for days.