Bug 1218946 - DBD::SQLite is compiled with older version of SQLite than standalone SQLite
Summary: DBD::SQLite is compiled with older version of SQLite than standalone SQLite
Status: IN_PROGRESS
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Development (show other bugs)
Version: Leap 15.5
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Valentin Lefebvre
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-18 11:26 UTC by Ulrich Windl
Modified: 2024-06-03 16:30 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Windl 2024-01-18 11:26:27 UTC
As of today I have installed perl-DBD-SQLite-1.66-150300.3.6.1.x86_64 that was compiled using SQLite 3.32.3, but when installing sqlite3 or sqlite3-doc I would get 3.44.0-150000.3.23.1.

There are several problems with this approach:
1) When reading the documentation of SQLite, some features described may not be available via the DBD::SQLite interface.
2) A database created using the sqlite3 standalone-command might be incompatible with a program using DBD::SQLite to access the database.

Actually I had discovered the issue for an older version of Leap where I got a syntax error for a command that worked flawlessly when being entered interactively in sqlite3.  As a developer may try commands interactively before adding them to a program, it is important that both interactive tools and DB interfaces are compatible.

Command to get the version of SQLite used to compile DBD::SQLite:
perl -MDBD::SQLite -le'print $DBD::SQLite::sqlite_version'
Comment 2 Valentin Lefebvre 2024-03-08 16:02:53 UTC
(In reply to Ulrich Windl from comment #0)
> As of today I have installed perl-DBD-SQLite-1.66-150300.3.6.1.x86_64 that
> was compiled using SQLite 3.32.3, but when installing sqlite3 or sqlite3-doc
> I would get 3.44.0-150000.3.23.1.
> 
> There are several problems with this approach:
> 1) When reading the documentation of SQLite, some features described may not
> be available via the DBD::SQLite interface.
> 2) A database created using the sqlite3 standalone-command might be
> incompatible with a program using DBD::SQLite to access the database.
> 
> Actually I had discovered the issue for an older version of Leap where I got
> a syntax error for a command that worked flawlessly when being entered
> interactively in sqlite3.  As a developer may try commands interactively
> before adding them to a program, it is important that both interactive tools
> and DB interfaces are compatible.
> 
> Command to get the version of SQLite used to compile DBD::SQLite:
> perl -MDBD::SQLite -le'print $DBD::SQLite::sqlite_version'

Thanks for the bug report.
That is something that should already be fixed following this older bug reports: https://bugzilla.suse.com/show_bug.cgi?id=1195771#c5

I suspect bundled sqlite.c file interfere during the compilation even if we choose to compile with the system libraries from leap 15.3. In that way, also in Tumbleweed, we don't get the same sqlite version from sqlite3 package to the perl module package.
Comment 3 Maintenance Automation 2024-04-02 12:30:06 UTC
SUSE-SU-2024:1086-1: An update that has one security fix can now be installed.

Category: security (moderate)
Bug References: 1218946
Maintenance Incident: [SUSE:Maintenance:32928](https://smelt.suse.de/incident/32928/)
Sources used:
openSUSE Leap 15.3 (src):
 perl-DBD-SQLite-1.66-150300.3.9.1
openSUSE Leap 15.5 (src):
 perl-DBD-SQLite-1.66-150300.3.9.1
Basesystem Module 15-SP5 (src):
 perl-DBD-SQLite-1.66-150300.3.9.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
Comment 4 Valentin Lefebvre 2024-05-16 09:39:24 UTC
Update of this bug report: A maintenance has been started that will bring a fix to this wrong SQLite version given by the perl module, internally. Leap would be patched afterwards.

More information about the fix on Factory side: https://build.opensuse.org/package/rdiff/openSUSE:Factory/perl-DBD-SQLite?linkrev=base&rev=53
Comment 6 Maintenance Automation 2024-06-03 16:30:12 UTC
SUSE-RU-2024:1914-1: An update that has one fix can now be installed.

Category: recommended (moderate)
Bug References: 1218946
Maintenance Incident: [SUSE:Maintenance:34055](https://smelt.suse.de/incident/34055/)
Sources used:
openSUSE Leap 15.3 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
openSUSE Leap 15.5 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
openSUSE Leap 15.6 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
Basesystem Module 15-SP5 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
Basesystem Module 15-SP6 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Linux Enterprise High Performance Computing LTSS 15 SP3 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Linux Enterprise Server 15 SP3 LTSS 15-SP3 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Linux Enterprise Server for SAP Applications 15 SP3 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Linux Enterprise Server for SAP Applications 15 SP4 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Manager Proxy 4.3 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Manager Retail Branch Server 4.3 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Manager Server 4.3 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1
SUSE Enterprise Storage 7.1 (src):
 perl-DBD-SQLite-1.66-150300.3.12.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.