Bug#981549: lazarus-ide: At startup, a message will appear if it is different from the ver described in version.inc.

[averageos2]

Package: lazarus-ide
Version: 2.0.10+dfsg-4
Severity: minor
X-Debbugs-Cc: avera...@gmail.com

Dear Maintainer,

If lazarus-ide is different from the ver name described in version.inc in / etc / alternatives / lazarus / ide at startup, an error will be displayed.
I want you to change version.inc to '2.0.10 + dfsg-4 + b1' as well as the package.


-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-2-amd64 (SMP w/2 CPU threads)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lazarus-ide depends on:
ii lazarus-ide-gtk2-2.0 2.0.10+dfsg-4+b1
ii lazarus-ide-qt5-2.0 2.0.10+dfsg-4+b1

lazarus-ide recommends no packages.

lazarus-ide suggests no packages.

-- no debconf information

[Paul Gevers]

Control: tags -1 confirmed
Control: severity -1 important

Hi,

On 01-02-2021 10:22, averageos2 wrote:
> If lazarus-ide is different from the ver name described in version.inc in / etc / alternatives / lazarus / ide at startup, an error will be displayed.
> I want you to change version.inc to '2.0.10 + dfsg-4 + b1' as well as the package.

Thanks for the report.

Interesting, when I manually add (doesn't prevent the "wrong version"
error) or replace the current content in
/usr/lib/lazarus/2.0.10/ide/version.inc (which is where this alternative
points to), I get a pop-up with the following text:

"""
Welcome to Lazarus 2.0.10+dfsg-4+b1

There is already a configuration from version 2.0.10 in
/home/paul/.lazarus
The configuration will be downgraded/converted.

If you want to use two different Lazarus versions you must start the
second Lazarus with the command line parameter primary-config-path or pcp.

For example:
/usr/lib/lazarus/2.0.10/startlazarus --pcp=~/.lazarus_test
"""

The text of that pop-up is "Downgrade configuration" which is at least
confusing as this is definitely no downgrade, if anything it's an
upgrade. The choice I have is "Abort" or "Downgrade".

On top of that, when I hit "Abort" I get an Access Violation (see
below). It seems like this all doesn't work very pretty.

So, two possibilities:
1) we should patch the check in lazarus-ide to *not* fail on
distribution changes that keep upstream version intact
2) we have to make lazarus-src-2.0 a arch:any package and have to fix
the version string during rebuilds.

Paul


paul@mulciber ~ $ lazarus-ide

(lazarus-ide:28780): Gtk-WARNING **: 10:28:11.773: Unable to locate
theme engine in module_path: "adwaita",
Adding "" as a parameter
TLazarusManager.Run starting /usr/lib/lazarus/2.0.10/lazarus ...

(lazarus:28781): Gtk-WARNING **: 10:28:11.925: Unable to locate theme
engine in module_path: "adwaita",
Hint: (lazarus) [TMainIDE.ParseCmdLineOptions]
PrimaryConfigPath="/home/paul/.lazarus"
Hint: (lazarus) [TMainIDE.ParseCmdLineOptions]
SecondaryConfigPath="/etc/lazarus"
LAZARUS END - cleaning up ...
[FORMS.PP] ExceptionOccurred
Sender=EAccessViolation
Exception=Access violation
Stack trace:
$000055B6D7C2C7C9
$000055B6D77A9135
$000055B6D773411B
TApplication.HandleException: EAccessViolation
Access violation
Stack trace:
$000055B6D7C2C7C9
$000055B6D77A9135
$000055B6D773411B
Exception at 000055B6D7C2C7C9: EAccessViolation:
Access violation.
[FORMS.PP] ExceptionOccurred
Sender=EAccessViolation
Exception=Access violation
Stack trace:
$000055B6D7C2C7C9
$000055B6D77A9135
$000055B6D773411B
$000055B6D777CE46
$000055B6D7738BF9
$000055B6D773411B
TApplication.HandleException: EAccessViolation
Access violation
Stack trace:
$000055B6D7C2C7C9
$000055B6D77A9135
$000055B6D773411B
$000055B6D777CE46
$000055B6D7738BF9
$000055B6D773411B
Exception at 000055B6D7C2C7C9: EAccessViolation:
Access violation.
[FORMS.PP] ExceptionOccurred
Sender=EAccessViolation
Exception=Access violation
Stack trace:
$000055B6D7C2C7C9
$000055B6D77A9135
$000055B6D7830BE6
$000055B6D773411B
$000055B6D77799A9
$000055B6D7738A07
$000055B6D773411B
$000055B6D777CE46
$000055B6D7738BF9
$000055B6D773411B
TApplication.HandleException: EAccessViolation
Access violation
Stack trace:
$000055B6D7C2C7C9
$000055B6D77A9135
$000055B6D7830BE6
$000055B6D773411B
$000055B6D77799A9
$000055B6D7738A07
$000055B6D773411B
$000055B6D777CE46
$000055B6D7738BF9
$000055B6D773411B
Exception at 000055B6D7C2C7C9: EAccessViolation:
Access violation.

[Abou Al Montacir]

If you just accept to do the conversion, it will work without any issue.

If you chose to abort, it should exit without crash, as it can't work with the old config without conversion.

Anyway, it seems that there is an error on the logic of detecting upgrade/downgrade with this particular version.

-- 
Cheers,
Abou Al Montacir

[Abou Al Montacir]

Hi averageos2,

The behavior was changed in 2.0.12. There is still a warning, which is normal, but no asking for upgrade/downgrade/abort.

Please check if this is fine for you.

[Abou Al Montacir]

Th ebehavior of Lazarus 2.0.12 lokks correct for me.

If no one minds, I'll close this ticket end of next week if no objection was raised by that time.

[Abou Al Montacir]

Control: fixed -1 2.0.12+dfsg1-1

This issue was fixed on 2.0.12 and nobody was objecting the closure published in last message.