*** Bug 2373 has been marked as a duplicate of this bug. ***

CC: (none) => saythrenshaw

I stand by this demand. Lazarus is needed to compile a lot of software.

CC: (none) => olivier.delaune

Don't you mean request instead of demand?

I looked into this, but seems lazarus still wants gtk+ version 1 to compile! I don't think we should still have gtk 1 in the distro. So spec file needs work to get rid of that (also has gtk+2).

CC: (none) => olav

Indeed, request is more suitable.
About gtk 1, I do not know. However, I found this spec file on Mandriva : http://svnweb.mageia.org/packages/cauldron/lazarus/current/SPECS/lazarus.spec?revision=137908&view=markup
It looks they use gtk 2.

The spec referenced gtk1, but seems that was just a spec file error. I've cleaned it up. Asked someone with submission rights to review it.

Now available in Cauldron. Please test as I don't use it myself. I did tes that it starts, but nothing more. dmorgan (packager) said that there is a possibility to backport it to Mageia 1 if people test the Cauldron version. That would make it an exception because it would also mean updating fpc to a newer version.

Hi Olav,
It doesn't work for me as it's not possible to add new package in the IDE. (e.g. menu package, install/remove package, right box lazreport, install selection, save/rebuild IDE or something like that as I don't use the english menu). It should create a new tab with some lazreport object on it but it'doesn't. The version number let me think this package is a fix only on lazarus 9.30 and not the full version of lazarus. the rpm package on lazarus download site works (http://www.hu.freepascal.org/lazarus/). 
e.g.:
fpc-2.4.4-20110906.x86_64.rpm
fpc-src-2.4.4-20110906.x86_64.rpm
lazarus-0.9.31.32192-20110906.x86_64.rpm

best regards

(In reply to comment #7)
> Hi Olav,
> It doesn't work for me as it's not possible to add new package in the IDE.

@ John
Were you using cauldron, when you tried the Mga lazarus package?


@ Olivier
Did you run into the same problem?

CC: (none) => marja11
Source RPM: (none) => lazarus
Whiteboard: (none) => Mdv, cauldron

Hello Marja,

No, I've not been able to get a full Cauldron machine running. So I use 
fpc-2.4.4-1.mga2.x86_64.rpm
fpc-src-2.4.4-1.mga2.x86_64.rpm
lazarus-0.9.30.1.30881-1.mga2.x86_64.rpm
that I downloaded on cauldron miroir and install them on a Mageia 1 machine. But it doesn't look to be the cause of the problem

I progressed one step:

The file /etc/fpc.cfg comes from a 32 bit install and several lines refer to /usr/lib instead of /usr/lib64

Then at least one file is missing in fpc-src: Contnrs.pas is not in the package so that EDI does not compile when you add new components.

Regards

@ john

Thx for replying.

I think Olav meant to test in cauldron. After a package has been used in cauldron by different users with al sorts of hardware and other software and no problems were reported (or the reported ones were fixed), it is safe to package it for "1"

Lazarus wouldn't need to go into backports, though, because it was in Mandriva 2010.x

(In reply to comment #10)
> @ john
> 
> Thx for replying.
> 
> I think Olav meant to test in cauldron.

More clear: I think Olav asked for people to test the package in cauldron, not in Mga 1

Well, I installed a virtual machine with cauldron and get through the trouble that lazarus windows appears but are empty (even the menu is not displayed in the windows).

(In reply to comment #12)
> Well, I installed a virtual machine with cauldron and get through the trouble
> that lazarus windows appears but are empty (even the menu is not displayed in
> the windows).

Please open a new bug for that.

lazarus-0.9.30.4 is now available in Cauldron. I believe this provides a solution to your bugreport. Please reopen in case the problem still persists for you.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Assignee: bugsquad => remco

Thank's. That's OK now in cauldron for the windows which appear correctly. Programm is installed in /usr/lib64/lazarus so that a simple user cannot configure it (when you add components, lazarus has to re-compile itself). But that's not a big problem to start it from root console. However, even beeing root, adding lazreport component to the IDE still not work.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Hi John,

As I'm not a lazarus user myself, can you give me brief instructions on how to add the lazreport component so I can see if I can reproduce it?

Having to recompile lazarus all the time sounds like a security risk to me. Perhaps we, as a distro, have to package the commonly used components as well / better ?

Hello Remco,

Well, in the "Lazarus EDI v0.9.30.4" window:
- Click in the menu "Package", "Install/Uninstall packages"
- Select Lazreport 0.9.8 (or any other available component you wish to install) in the "Do not Install" component box and click the "install selection" button to move it in the "install" box
- Click the "save and rebuild IDE" button
- In the "Confirm new package set for the IDE" windows that has appeared click on the "continue" button
Then Lazarus compiles and restart. In the Lazarus EDI v0.9.30.4, at the bottom right should be now a new tab named LazReport but there is not (Cauldron x86_64  in virtualbox). If you have chosen other component e.g. lazparadox, it should only place a new item "Tparadox" on the already existing tab named "Data Acess".

On my standard computer I work on magiea 1 x86_64 with lazarus 1.1 (lazarus, fpc, fpc-src rpm files downloaded from the snapshot area on Lazarus site). When I apply the same procedure as above, everything  works well.

Thanks, I can reproduce the issue now. One more question for you:

Can you see how (and if) the directories under "Environment --> Options --> Environment --> Files" vary between the package Mageia has and your local package which works?

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Hi Joseph, thanks for stepping up and working on some long outstanding bugs. I hope you won't mind me assigning this bug to you now.

Assignee: remco => joequant

This bug was fixed for Mageia 4 and in new versions of lazarus: we have lazarus-1.0.12 for Mageia 4 and Cauldron.
Reason was in Makefile, which was deleted in rpm package, but Makefile was returned and users and root can rebuild lazarus now. But I'm not sure I can update lazarus for Mageia 3 without update fpc.
Please try to reproduce.

Keywords: (none) => NEEDINFO
CC: (none) => loginov_alex
Assignee: joequant => loginov_alex

Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:WONTFIX

Status: REOPENED => RESOLVED
Resolution: (none) => WONTFIX