i really do not know what i am doing wrong but i am fed up
Let me explain. Every CodeTyphon version is fixed to specific FPC and Lazarus version, which both were the most recent at the time when it was decided to go with another release. So, it is easier to have package being tested against just one FPC/LAZ combo. From time to time they drop some components when they do not catch up with trunk FPC and LAZ. On the other hand, OPM collects so many packages from different authors, OPM is just used for distribution, and each author is responsible for testing his own packages. However, OPM is distributed with so many LAZ/FPC combos, that authors even in their craziest effort would not be able to test them all. For example, some users will try to install package on some old LAZ 1.6 with FPC 3.04 on x86 Debian, someone else will try the same package on LAZ 2.0 with FPC 3.2 on x64 Windows, another one will try with LAZ trunk and FPC trunk on Pi (32 or 64) or even some old ARMv5 or ARMv6 board, and another while chasing a bug that shows just on Apple M1. Do you really expect that everything compiles everywhere in all possible combos? That is not a realistic expectation. A package can be made for latest FPC, while you might have old 3.0.4, or FPC and LAZ move on but author did not upgrade his package (or OPM version was not yet updated). To ease things a little, some packages provide info on what platform and FPC/LAZ combos they have been tested. As an example, most of CodeTyphon packages in OPM (they all have pl_ prefix) are tested with stable FPC/LAZ combo on Windows x32 and Linux x64. But even in such a case, you can not expect a Windows specific package to magically work on Linux just because it is available in OPM.
So, when you find that some package does not work, uninstall it and report it to the author mentioning your exact FPC/LAZ/OS/Bitness combo and see where that goes. And never install more then few packages at once, so that you can easily do a manual roll back. Or... simply stay with CodeTyphon if that works for your use case.