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

[Martin_fr]

Just a question, I don't remember if it was ask: Is your tortoise svn up to date?

[Avishai]

Yes it is up to date.  That was one of the first things I checked when I realized there was a problem.  It is TortoiseSVN-1.7.12.24070-x64-svn-1.7.9.msi.  But the problem seems to be fixed now (I hope).

[JuhaManninen]

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

No Avishai, you told yourself that you installed also the snapshot. Then you have 2 copies, the SVN copy and the snapshot copy.
I don't know how you work with them but it sounds like a hazard.
Or did you copy them both to the same directory? That is a hazard guaranteed.

[Avishai]

As I said before, I uninstalled - deleted - removed the old copy.  The snapshot will not allow you to overwrite. You must uninstall the old one to use the snapshot.  I don't know how to make that any clearer.  Try it yourself.  Go to ftp://freepascal.dfmk.hu/pub/lazarus/snapshots/ and get a snapshot and try to install it in your Lazarus directory.  The first thing it will tell you is that the directory is not empty.  Uninstall (remove) and Reinstall (from snapshot) So YES, I have ONE copy.  I think I can count.

The other part of the quote is also true whether you want to believe or not.  When the server is down it gives you a message that it can not connect.  Instead, I would get the next Rev. number and no files.  That wouldn't happen if the server was down and that went on for several days.

[Avishai]

I'll try to be more specific.  My ONE AND ONLY copy of Lazarus is in C:\Lazarus.

To install the snapshot
A. Delete all files from C:\Lazarus (except the SVN directory).
B. Run the snapshot.
C. The snapshot copies all the new files to C:\Lazarus.

Total number of copies = ONE.

[Giu]

The other part of the quote is also true whether you want to believe or not.  When the server is down it gives you a message that it can not connect.  Instead, I would get the next Rev. number and no files.  That wouldn't happen if the server was down and that went on for several days.

I'm not sure if I understand correctly but, did you know there are mirrors of the server? I think thath some planets should be aligned to have all mirrors down.

Otherwise, I don't agree with juha. I think Working with svn is ok if there are another Lazarus installation to use if something is wrong.

For example, right now,I don't know why, but its impossible for me to build Lazarus. From the last years I always have more than 2 or 3 laz installations, and right know, I can't get it build with all my system clear. Could be something related with the problems Avishai has?

(*) http://lazarus.freepascal.org/index.php/topic,20681.msg122315/topicseen.html#new

[Martin_fr]

A. Delete all files from C:\Lazarus (except the SVN directory).
B. Run the snapshot.
C. The snapshot copies all the new files to C:\Lazarus.

You don't install a snapshot into an svn dir, that is absolutely wrong.... No wonder your SVN gave up eventually.

An SVN dir is created with an SVN checkout. That means you have all sources needed
ppu are created, so you dont need at this stage....
All exe files are in  FPC. You only need a lazarus.exe (you can build from console, but it is convenient to have one).

[Martin_fr]

@Giu:

Avishai  problem is indeed SVN, and not multiply laz installations.

You can have many Lazarus installs, SVN, snapshots, new and old releases, even with diff fpc versions.

Google the wiki, or forum for --primary-config-path

I have myself 7 Lazarus installations, several fpc, and 10 or more versions of GDB. And they work like a charm.

[Giu]

@Giu:

Avishai  problem is indeed SVN, and not multiply laz installations.

You can have many Lazarus installs, SVN, snapshots, new and old releases, even with diff fpc versions.

Google the wiki, or forum for --primary-config-path

I have myself 7 Lazarus installations, several fpc, and 10 or more versions of GDB. And they work like a charm.

I know about --pcp, for this reason I was a happy user of stable, snapshots and svn versions 

[Avishai]

Martin_fr, the method I used was enough to get SVN functional again, but I understand your concern.  You don't want others reading this to think that is a complete answer.  It isn't.  In the morning when I am fresh and not so exhausted I plan to dump the files from C:\Lazarus and do a fresh SVN Checkout.  First of course I will do a back up. I will loose SVN history but the history I have is of no use anyway.

[JuhaManninen]

A. Delete all files from C:\Lazarus (except the SVN directory).
B. ...
C. The snapshot copies all the new files to C:\Lazarus.

So, you really installed it to the same directory with the SVN checkout, like I was afraid!

...
In the morning when I am fresh and not so exhausted I plan to dump the files from C:\Lazarus and do a fresh SVN Checkout.  First of course I will do a back up. I will loose SVN history but the history I have is of no use anyway.

Avishai, no you will not loose SVN history. It is stored in the SVN server. You may have locally modified files and you must obviously backup them, but they are not part of SVN history.

[JuhaManninen]

Otherwise, I don't agree with juha. I think Working with svn is ok if there are another Lazarus installation to use if something is wrong.

For example, right now,I don't know why, but its impossible for me to build Lazarus. From the last years I always have more than 2 or 3 laz installations, and right know, I can't get it build with all my system clear. Could be something related with the problems Avishai has?

Problems in building Lazarus are different from problems in downloading files from SVN.
I believe the SVN related problems are just user errors. Here it works well, using Windows and Linux, using SVN client or Git-SVN link.

If you have the latest FPC release (like 2.6.2) installed then Lazarus trunk compiles fine almost always. It has many testers. Sometimes seldom the compilation breaks but then it is fixed quickly.
If you hit a bad revision, a revision control system lets you jump a step or two back in history to a working rev.
With a snapshot you cannot do that.

I also have multiple versions of Lazarus, all got using either SVN client or Git client.
A compiled working executable copied to a different name is enough to solve situations when you experimented with Lazarus sources and it does not compile any more. You don't need a full installation for that.

Snapshots are clumsy. They can be usefull for people who only very seldom want to check the latest developments, maybe once a year.
They should not be used by anybody who updates more often.
Using SVN or Git makes many things easier.

[Avishai]

OK.  I made my backup, purged C:\Lazarus and did SVN checkout.

New problem:  When trying to recompile Lazarus I get this message:

registerfcl.pas(43,3) Fatal: Can not find ServiceManager used by RegisterFCL, ppu=..\..\fpc\2.6.2\units\x86_64-win64\fcl-extra\ServiceManager.ppu, package FCL

I checked and the file is there.  I checked Options/Environment/Files and the paths are set correctly.  I have tried "Automatically", "Clean common files" and "Clean all".

I've had this problem before, I just don't remember the solution.

[Martin_fr]

Did you move your fpc directory?
If so did you update the paths in fpc.cfg?



your Options/Environment/Files points to  fpc\2.6.2 ? NOT to fpc\2.6.2\units\x86_64-win64

[Avishai]

I have the following paths set:

C:\Lazarus\
C:\fpc\2.6.2\bin\x86_64-win64\fpc.exe
C:\fpc\2.6.2\bin\x86_64-win64\make.exe
C:\Users\Avishai\AppData\Local\Temp\

All of these are valid.

I also have the following files:

C:\fpc\2.6.2\units\x86_64-win64\fcl-extra\ServiceManager.ppu
C:\fpc\2.6.2\units\x86_64-win64\fcl-extra\ServiceManager.o
C:\fpc\2.6.2\source\packages\fcl-extra\src\win\ServiceManager.pas