Lazarus Release Candidate 2 of 3.0

[lainz]

Any chance we can get the Lazarus IDE released onto Valve's Steam store? 🙏🏻

What is the criteria to be accepted in Valve's Steam store?
Lazarus project does not provide installer packages for various distros. It is the responsibility of distro maintainers.
However I don't know details of Valve's Steam store. Maybe someone will volunteer to create such packages.

If I remember well, you need to pay to your application be accepted-

[vercetti]

That's right, it costs 100 bucks to publish app

https://steamcommunity.com/discussions/forum/1/1480982971170315888/

[tcrass]

Hello there,

I'm not sure if this is really the place to report problems with 3.0 RC2 (there's a bug tracker on GitLab, after all), but since I've seen people doing that I'll just drop my issue here, too. If this is inappropriate, please just point me to the right place, will you...?

Here's my problem: I've installed the amd64.deb packages on a Debian "testing" system and tried to re-compile the IDE, but I end up with the following error:

Code: [Select]

Warning: Recompiling DateTimePicker, checksum changed for /usr/share/lazarus/3.0.0/lcl/units/x86_64-linux/lclintf.ppu
datetimepicker.pas(85,12) Error: Can't find unit DateTimePicker used by DateTimeCtrls
make[2]: *** [Makefile:5055: lazarus] Error 1
make[1]: *** [Makefile:5494: ide] Error 2
Error: make: *** [Makefile:3124: ide] Error 2
I previously had 2.2.6 installed (also from the deb packages), which compiled just fined. Prior to installing 3.0 RC2, I purged the fpc-laz, fpc-src and lazarus packages and renamed my ~/.lazarus folder to make sure there were no remnants from the previous installation interfering with 3.0 RC2.

So... am I doing something wrong, or is this really a bug?

Cheers -- tcrass

P.S: Just compiled Lazarus fixes_3_0 from source, using Debian's own fpc packages -- worked flawlessly, also when re-compiling from within the IDE. So maybe there's something missing in the deb packages provided by the lazarus project?

[JuhaManninen]

So... am I doing something wrong, or is this really a bug?

It sounds like a bug. RC1 had the same problem. Mattias was looking at the issue but apparently could not fix it.
I don't have time to test RC2 packages now but I take your word for it.

[vangli]

I also got the same errors trying to rebuild IDE on Ubuntu 22.04 after installing from deb files. However, I managed to get i working after some fidling. So, honestly, I am not quiet sure what did it. Basically I did:

- Rescan FPC source directory from meny "Tools".
- Set a clean up + build, and select "Clean All", all from option page for "Configure Build" Lazarus from menu "Tools".
- I also did restart the IDE before doing the build, because sometimes the debugger option Dwarw 3 (beta) (-gw3) sometimes, on my systems, seems to forget where different units are. I don't think this has anything to do with rebuilding the IDE.
- In my desperation I also tried to delete the packagefiles.xml file from .lazarus directory. But again I think this it not necessary.

Best regards, Bent, Oslo

[andresayang]

I also got the same errors trying to rebuild IDE on Ubuntu 22.04 after installing from deb files. However, I managed to get i working after some fidling. So, honestly, I am not quiet sure what did it. Basically I did:

- Rescan FPC source directory from meny "Tools".
- Set a clean up + build, and select "Clean All", all from option page for "Configure Build" Lazarus from menu "Tools".
- I also did restart the IDE before doing the build, because sometimes the debugger option Dwarw 3 (beta) (-gw3) sometimes, on my systems, seems to forget where different units are. I don't think this has anything to do with rebuilding the IDE.
- In my desperation I also tried to delete the packagefiles.xml file from .lazarus directory. But again I think this it not necessary.

Best regards, Bent, Oslo

Hi, well I try this, and no luck.

[uganof]

Hi, well I try this, and no luck.

I also encountered the same problem but I solved it by simply opening the Lazarus as supervisor and compiling the IDE and then I close the ide

reopening lazarus as a normal user recompiled correctly.

I think it's a permissions problem and consequently the normal user is unable to update the PPU checksums

[acm]

Hello there,

I'm not sure if this is really the place to report problems with 3.0 RC2 (there's a bug tracker on GitLab, after all), but since I've seen people doing that I'll just drop my issue here, too. If this is inappropriate, please just point me to the right place, will you...?

Here's my problem: I've installed the amd64.deb packages on a Debian "testing" system and tried to re-compile the IDE, but I end up with the following error:

Code: [Select]

Warning: Recompiling DateTimePicker, checksum changed for /usr/share/lazarus/3.0.0/lcl/units/x86_64-linux/lclintf.ppu
datetimepicker.pas(85,12) Error: Can't find unit DateTimePicker used by DateTimeCtrls
make[2]: *** [Makefile:5055: lazarus] Error 1
make[1]: *** [Makefile:5494: ide] Error 2
Error: make: *** [Makefile:3124: ide] Error 2
I previously had 2.2.6 installed (also from the deb packages), which compiled just fined. Prior to installing 3.0 RC2, I purged the fpc-laz, fpc-src and lazarus packages and renamed my ~/.lazarus folder to make sure there were no remnants from the previous installation interfering with 3.0 RC2.

So... am I doing something wrong, or is this really a bug?

Cheers -- tcrass

P.S: Just compiled Lazarus fixes_3_0 from source, using Debian's own fpc packages -- worked flawlessly, also when re-compiling from within the IDE. So maybe there's something missing in the deb packages provided by the lazarus project?

Hello

I have had the same issues when I was trying to recompile lazarus to 3.0.0RC2 with new components on FreeBSD. The reason for it is when  the installation of lazarus doesn't preserve the access and modification times from generated when it was compiled. I had to add -p parameter to install command. I know it was not necessary on 2.2.6 but with this change I avoid recompile lot of packages on first time when I add a new components from OPM or from lazarus install packages option. I guess you have lazarus files/directories installed to a directory on read-only (/usr/share/lazarus) and you want to add components with unpriviliged user and rebuild lazarus

[dbannon]

Code: [Select]

Warning: Recompiling DateTimePicker, checksum changed for /usr/share/lazarus/3.0.0/lcl/units/x86_64-linux/lclintf.ppu
datetimepicker.pas(85,12) Error: Can't find unit DateTimePicker used by DateTimeCtrls
make[2]: *** [Makefile:5055: lazarus] Error 1
make[1]: *** [Makefile:5494: ide] Error 2
Error: make: *** [Makefile:3124: ide] Error 2

Yes, I can reproduce this using fpc, fpc-src and lazarus from source forge. On Debian Testing (Trixie) and Ubuntu 2004 so its pretty widespread.

But if I build Lazarus from source, still using the same fpc and fpc-src, no sign of this problem. It clearly appears during that clever trick that Lazarus does "OH, re-building in read-only space ?  OK, I'll make you a whole new, hidden install in the config dir" trick. I have no idea how that works but it generally does, but does not now.

Davo

[TRon]

Yes, I can reproduce this using fpc, fpc-src and lazarus from source forge. On Debian Testing (Trixie) and Ubuntu 2004 so its pretty widespread.

Did you happen to create a try trace as well (-vt added as custom build option) ? It might perhaps help in detecting where/why it goes wrong. fwiw building from source only and (also) not able to reproduce.

[cdbc]

Hi
@dbannon: Davo, would it help to make the laz-dir temporarily writeable, during the rebuild and then r/o afterwards?
I mean, could that perhaps fix the problem afterwards?
Regards Benny

[dbannon]

Might help but ugly thing to have to do.

On the other hand, someone suggested running and building Lazarus as root !  So, your suggestion might be a good work around by comparison. But I personally would hate to see Lazarus 3.0 released with an issue like that.

And I would really, really like to see Lazarus 3.0 released !   Sigh .....

Davo

EDIT: Yep, that works, well spotted Benny. I changed /usr/share/lazarus/3.0.0 ownership to my user name, ran lazarus as me, rebuilt the ide.  Exited, changed the ownership back to root, started Lazarus as me again and rebuilt the IDE. So, a good workaround for us here. Not something we'd want to make part of the install instructions.

Make it a post install script ?  No, stop it Davo !  ;-)

Davo

[vangli]

Changing /usr/share/lazarus or /usr/share/lazarus/3.0.0 to own user didn't help, even if I did it recursive. I got an error immediate after trying to rebuild. The spooky thing was that when changing back to root-ownership recursively, rebuilding IDE works as user.

[Martin_fr]

I am myself more familiar with the Windows installer. Though some issues may be shared (and the user rights add on top of it).

If you do an upgrade, and the lazarus dir is the same (or the config incorrectly keeps the old), then old files may remain. That is, files may have moved to new locations, since the previous release.
Say if "foo.pas" was moved to another package, then the old source remains, and may cause problems.

And it is not just the *.pas files. Each of them has a ppu and o file. And those can cause real problems, if the old ones are in place. They only get removed by a clean build. And on Linux only if you do a clean build as root. (well, you may sometimes get away without root... but that is complex)

If you don't build as root, then the clean only affects the "shadow" folders in your users dir, into which the rebuild ppu are compiled. But not all packages may get rebuild, and therefore some aren't shadowed, and thus old copies/duplicates from the install dir may get used.

Equally, if the new install is into a new folder, then the config must be updated to that new folder.

[cdbc]

Hi
Glad it worked.
As a note: I've had these pestering flaws(can't fin stdctrls etc...) aswell, in my 2.2.6 stable install, mind you, WITH laz' naughty trick with covert dir in /home/yo(u)ser/.lazarus...
I thought, why the h*** not try it with that too?!?
Now after loading a few apps, which gave me grief before, I can say it works on lazarus 2.2.6 too, at least on my PCLinuxOS system 
But you're right Davo, it's not the solution for the shipping Lazarus.
Regards Benny