Bug 1203310 - mariadb y2038 problem
mariadb y2038 problem
Status: NEW
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other
Current
Other All
: P5 - None : Normal (vote)
: ---
Assigned To: Pedro Monreal Gonzalez
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-09-11 06:51 UTC by Bernhard Wiedemann
Modified: 2022-09-11 07:22 UTC (History)
1 user (show)

See Also:
Found By: Development
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 Bernhard Wiedemann 2022-09-11 06:51:32 UTC
While working on reproducible builds for openSUSE, I found that
our perl-DBD-MariaDB package failed tests with

> 2038-01-20  0:00:08 0 [ERROR] This server doesn't support dates later than 2038

To reproduce:
osc co openSUSE:Factory/perl-DBD-MariaDB && cd $_
osc build --noservice --trust-all-projects --vm-type=kvm \
  --alternative-project=home:bmwiedemann:reproducible \
  --build-opt=--vm-custom-opt="-rtc base=2038-01-20T00:00:00" \
  openSUSE_Tumbleweed x86_64


Background:
As part of my work on reproducible builds for openSUSE, I check that software still gives identical build results in the future.
The usual offset is +16 years, because that is how long I expect some software will be used in some places.
This showed up failing tests in our package build.
See https://reproducible-builds.org/ for why this matters.
Comment 1 Bernhard Wiedemann 2022-09-11 07:22:41 UTC
Also affected:
python-PyMySQL
python-sortinghat


so this likely needs to be fixed in the mariadb package.