Online Package Manager

[balazsszekely]

@wp
Until Sunday I'm out in the wild with no PC and very slow internet connection.
I will update the package when I'm back.

@tudi-x
I tought that color bug is already fixed. Apparenty not. I will look at the issue Sunday.

[balazsszekely]

@wp
I updated the package today. Sorry for the delay.

[wp]

No problem, thank you.

[balazsszekely]

just installed on MX Linux Lazarus 2.0.6. Please advise if there is a solution to seeing the components besides changing the OS colors in `Online Package Manager`.
theme is adwaita-dark.
not too much can be seen now.
thank you

@tudi_x
The black textcolor issue on dark themes it's fixed in Lazarus trunk. Unfortunately it wasn't backported to 2.0.x. You should switch to Lazarus trunk or wait for the next major release. If this is not an option, let me know and we find a way to patch VTV in 2.0.6.

[anderbelluno]

Hi, we have a new version REST Dataware on Source Forge repository,  Tks.

[balazsszekely]

@anderbelluno

Hi, we have a new version REST Dataware on Source Forge repository,  Tks.

I updated the package. Thanks.

[TRon]

I am not quite sure if this is the correct forum for this to post, please advice in case my topic doesn't belong here and if so i apologise upfront.

I downloaded Synapse 40.1 (manually) from https://packages.lazarus-ide.org/

I (manually) extracted the package and installed it for usage with the Free Pascal commandline compiler (no Lazarus involved whatsoever, so that might be my mistake)

On attempt to use it with fpc (3.2rc1) the compiler throwed:

Code: [Select]

jedi.inc(611,4) Error: Illegal assembler style specified "INTEL"

Target is ARM

Line 611 reads:

Code: [Select]

  {$ASMMODE Intel}

I 'fixed' it with enclosing that define so that it reads:

Code: [Select]

  {$IFDEF CPU386}
  {$ASMMODE Intel}
  {$ENDIF}

Reason for posting:
1) I am not sure that this is the correct fix
2) i am not sure to whom to report, original author or package maintainer
3) even if i would know the answer to q2, i still have q1,
and depending on the answers to above questions
4) I do not know where/how exactly to report

Motivation is to have this compilation error solved (when using it out of the box).

[lucamar]

Reason for posting:
1) I am not sure that this is the correct fix
2) i am not sure to whom to report, original author or package maintainer
3) even if i would know the answer to q2, i still have q1,
and depending on the answers to above questions
4) I do not know where/how exactly to report

Report to the original author at the SourceForge project (click on "issues" or "bugtracker" or whatever it's called).

[TRon]

Report to the original author at the SourceForge project (click on "issues" or "bugtracker" or whatever it's called).

edit: sorry, it was not fixed in trunk, i assumed it was because the last commit to that file mentioned it (it fixed it at another location in the source)..  i hate sf online diff view (not showing line numbers whatsoever)

It was already fixed @ trunk in 2018.

If not mistaken then this only answers my first question. Besides that, if i understand correctly, official release is v40 while lazarus package manager is at v40.1.

afaik i have no way to establish who is 'responsible' for v40.1

[PascalDragon]

1) I am not sure that this is the correct fix

Correct fix would be this which I had done to a jedi.inc shipped with FPC that I encountered when working on the Windows on ARM64 port.

2) i am not sure to whom to report, original author or package maintainer

Ideally the original author.

[lucamar]

Besides that, if i understand correctly, official release is v40 while lazarus package manager is at v40.1.

afaik i have no way to establish who is 'responsible' for v40.1

The last official release was v40.1, but Lukas stopped releasing some years ago. Instead he recommends using SVN checkouts

[wp]

When a package maintainer works with Laz trunk and is not careful he may damage the package due to the new package format. This happened to me again, now with LazMapViewer.

@GetMem: Could you please add the new LazMapViewer version 0.2.2.1 where the packages are fixed again: https://sourceforge.net/projects/lazarus-ccr/files/LazMapViewer/lazmapviewer-v0.2.2.1.zip/download - thank you.

[balazsszekely]

@wp
Done. Thank you.

[TRon]

Correct fix would be this which I had done to a jedi.inc shipped with FPC that I encountered when working on the Windows on ARM64 port.

Thank you for the correction. Indeed i forgot the 64-bit check 

Ideally the original author.

uhm, yeah i know the 'correct' route  , However...

The last official release was v40.1, ...

Well, if you say so but, synapse trunk sources <> package manager 40.1 release sources  and, there is no evidence whatsoever that is able to verify that statement other then the mention of the original author in the Lazarus package (and i tried very hard, using all resources available including these forums).

I must be missing/overlooking something obvious ?

but Lukas stopped releasing some years ago. Instead he recommends using SVN checkouts

Besides package and trunk not using the same source, there were no updates in over so many years so that isn't very hopeful that it ever get fixed inside Lazarus package ... or is it ?

[lainz]

Hi GetMem, you can add BGRAControls and BGRABitmap newest releases?