Bug 29953 - Upgrade to Lazarus Release 2.2.0
Summary: Upgrade to Lazarus Release 2.2.0
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-28 08:19 CET by Alex Kotov
Modified: 2022-02-07 19:40 CET (History)
0 users

See Also:
Source RPM: lazarus-2.0.10.2-1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Alex Kotov 2022-01-28 08:19:00 CET
Hello, friends!
A truly joyful event has happened: Lazarus Release 2.2.0

Lazarus 2.2.0 release notes: https://wiki.lazarus.freepascal.org/Lazarus_2.2.0_release_notes

Now I am already transferring new projects to it as needed. There are no glitches yet. Is it possible to update Lazarus?

Thanks.
Comment 1 Lewis Smith 2022-01-28 21:12:56 CET
Thank you for the request. Our current issued version of this looks passé. In Cauldron we have version 2.0.12 from just a few months ago, but 2.2 would be even better. 

@packager:

https://forum.lazarus.freepascal.org/index.php/topic,55532.0.html?PHPSESSID=91pigltab87e3okorpgr45j5d1
says:
"We are now using GIT
« on: July 26, 2021, 11:18:38 am »
Lazarus has moved
The new official repository is now available at
     https://gitlab.com/freepascal.org/lazarus/lazarus"
However, the latest Cauldron version is more recent (Sep 13 2021), so this must have already been taken into account.

Component: New RPM package request => RPM Packages
Assignee: bugsquad => pkg-bugs
Source RPM: (none) => lazarus-2.0.10.2-1.mga8.src.rpm

Comment 2 Alex Kotov 2022-02-07 19:40:57 CET
Hello, Lewis. Lazarus-2.2.0 packages for Mageia-9 (Cauldron) have already been released. Many thanks to Wally. :)

If packages for Mageia-8 will not be released, then there is a backport here:
https://cloud.mail.ru/public/cw4x/fSApC8euD

Thank you all for your cooperation.

Sincerely,
Alex

Note You need to log in before you can comment on or make changes to this bug.