Skip to content

Conversation

@d3flex
Copy link
Contributor

@d3flex d3flex commented Sep 29, 2025

As a side effect this should fix also the problem with the postgres incompatibility.

@d3flex d3flex force-pushed the fix/update_dockerfiles branch 2 times, most recently from 90748c2 to 32eebb8 Compare September 29, 2025 07:08
@d3flex
Copy link
Contributor Author

d3flex commented Sep 29, 2025

Some packages are still missing in leap16, apparently

@Martchus
Copy link
Contributor

Martchus commented Sep 29, 2025

Some packages are still missing in leap16, apparently

How did you figure this? All tests are passing. I'd almost approve your change :-) Probably CI checks aren't using this right away.

RUN zypper install -y gcc-c++ cmake ninja pkgconfig\(opencv4\) pkg-config perl\(Module::CPANfile\) pkgconfig\(fftw3\) pkgconfig\(libpng\) pkgconfig\(sndfile\) pkgconfig\(theoraenc\) tesseract-ocr

# openQA dependencies
RUN zypper install -y 'rubygem(sass)>=3.7.4' ruby-devel npm python3-base python3-requests git-core rsync curl postgresql-devel postgresql-server qemu qemu-tools tar xorg-x11-fonts sudo make
Copy link
Contributor

@perlpunk perlpunk Sep 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're not using rubygem(sass) anymore in Leap 16.0, but perl-CSS-Sass.
I'm pretty sure we already have an according ticket to move to Leap 16.0, btw.

@perlpunk
Copy link
Contributor

Probably CI checks aren't using this right away.

Well, CI is failing:
https://github.com/os-autoinst/openQA/actions/runs/18088815946/job/51464608157?pr=6781#step:3:2841

28.68 No provider of 'rubygem(sass)>=3.7.4' found.

I commented on that in #6781 (comment)

@d3flex d3flex force-pushed the fix/update_dockerfiles branch from 32eebb8 to 96852af Compare September 29, 2025 09:05
Copy link
Member

@okurz okurz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

by the way https://progress.opensuse.org/issues/180716 is the epic about "support Leap 16.0" which also covers the work you and me mentioned about change to sass and such. https://progress.opensuse.org/issues/180731 would be the specific ticket about "Upgrade CI container image versions to Leap 16.0"

I don't think we should move to 16.0 yet as we would loose coverage for what we consider the primary version also used in production.

As a side effect this should fix also the problem with the postgres
incompatibility.

Signed-off-by: Ioannis Bonatakis <[email protected]>
@d3flex d3flex force-pushed the fix/update_dockerfiles branch from 96852af to b1baf86 Compare September 29, 2025 15:30
@Martchus
Copy link
Contributor

I don't think we should move to 16.0 yet as we would loose coverage for what we consider the primary version also used in production.

In 2022 you weren't that concerned about that and even proposed switching to Tumbleweed (#4744). Considering your change of mind you can probably close the PR from 2022.

Copy link
Contributor

@Martchus Martchus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#4744 also shows that probably many more places needed to be adjusted if we wanted to switch to Leap 16.0.

But probably we don't want to do that right now so this PR could also be closed meanwhile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants