timedatectl command in Linux gives exactly the same result for all the values. Also ls -l /etc/localtime gives the same and correct timezone on both machines.Theses were the first two things I checked and both give the same and correct results, just like date and date -u.
And one Debian is a RasPi???
Andreas from Vienna had the same problem:
https://forum.lazarus.freepascal.org/index.php?topic=47317.0
(https://forum.lazarus.freepascal.org/index.php?topic=47317.0)
I don't know nothing about kindergarden computers.
a) Same hardware concerning the proc? (AMD/Intel)
b) Same Debian version ??
b) Same fpc and Lazarus version??
I wanted to get back the TZ offset for IdGlobal Indy, what is not implemented under Linux.
Yes, I might not use the latest Indy.
I have Indy 10.2.0.3 installed.
I tried to look for a full packaged later version downloadable, but could not find.
I went to https://wiki.freepascal.org/Indy_with_Lazarus (https://wiki.freepascal.org/Indy_with_Lazarus), that took me to https://www.indyproject.org/ (https://www.indyproject.org/), in it Download, Indy10. There are three links - none of them works.
In the installed 10.2.0.3 under /fpc, there was IdGlobal.pas with a function OffsetFromUTC, but that did not have a Linux defined source at all (and so the sw crashed when a NaN was handed over to the next function).
So, I went on Github and found https://github.com/IndySockets/Indy/blob/master/Lib/System/IdGlobal.pas (https://github.com/IndySockets/Indy/blob/master/Lib/System/IdGlobal.pas). I just replaced the installed OffsetFromUTC function (blame me, not the whole IdGlobal) to the Github version. This one goes onfor Linux
- Honestly I never used the OPM, because to me that is "too" Lazarus. Most of my programs are terminal ran or daemons, so try to avoid visual components. So, I use most components (not only Indy, but e.g. SQL too) with .Create() and not through adding an icon to the form, Object Inspector, etc. Indy is especially heavy in terms of components in the Components bar. This is why I had it on my machine, but was not installed as a Lazarus package. Now I have it as a package. Can it be removed and still used? Then, I guess, I cannot use the Project/Inspector/Required packages. So, is the solution to add the folder (hidden - see later) to Project/Options/Compiler/Path/Other Units?
- Now as I know how to install it, I went back and tried to find it on the Indy website, but still could not find. It is a petty that such a great piece of software is so difficult to find (at least for me).
- The earlier installed Indy-s (and other packages) are under /usr/share/lazarus/components. Within indy-10.2.0.3 there, I had separate directories for /fpc and for /lazarus with similar, or identical units. Earlier I had added the ..../fpc to my Path and used it like that (thought the /lazarus ones are for the LCL). Now, I could hardly find the installed package and the units as they are under ~/.lazarus/onlinepackagemanager/packages/indy10, a private, hidden directory. There I do not see a separate /fpc and /lazarus version. Is that normal? Shouldn't the whole package (and also the lazarus binary) be under a shared and visible directory? Did I do something incorrectly?
- Although the files are probably the latest versions (IdGlobal is just as you described), but the change log is still very old, e.g. for IdGlobal it says Rev 1.54 2/9/2005. Does it mean that the file level change log is not maintained anymore?
The site is currently broken. Did you read the link I posted earlier?
Still, IMHO this great package would deserve some easier/more explained access and more publicity.
Also, some explanation how to use it in pure FPC. I understand that you do not work on that part, but someone might know.
Would it make sense to remove one day all the old change logs
or are those still needed?
I found it really misleading when I tried to understand what changed where.
But don't tell the headquater this is nonsense.
It is not because it is Delphi compatible!!