-
Notifications
You must be signed in to change notification settings - Fork 219
Update openqa containers to Leap16 #6781
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
90748c2 to
32eebb8
Compare
|
Some packages are still missing in leap16, apparently |
|
| 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 |
There was a problem hiding this comment.
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.
Well, CI is failing: I commented on that in #6781 (comment) |
32eebb8 to
96852af
Compare
There was a problem hiding this 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]>
96852af to
b1baf86
Compare
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. |
There was a problem hiding this 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.
As a side effect this should fix also the problem with the postgres incompatibility.