Java 17 for build-debian-package

Description

The "Build Debian Package" stage produces the Okapi Debian package.
However, that stage runs on focal that has openjdk 11 but we need openjdk 17.

https://jenkins-aws.indexdata.com/job/Automation/job/build-debian-package/92/console

dpkg-buildpackage: info: source distribution focal dpkg-buildpackage: info: source changed by MAINTAINER <jenkins@0cfdce9b77fa> dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 dpkg-source: info: using options from repo/debian/source/options: --extend-diff-ignore=(^|/)(.DS_Store|.git|deb-src)$ dpkg-checkbuilddeps: error: Unmet build dependencies: openjdk-17-jdk dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting

Task: Update the build-debian-package pipeline so that the package openjdk-17-jdk is available.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Craig McNally November 7, 2024 at 4:30 PM

Support for debian packages is going away. We will not create java 17 compatible debian packages.

Julian Ladisch September 19, 2024 at 11:55 AM

This issue is about Debian packages for Okapi >= 5.0.2. Okapi 5.0.2 has been released September 2023.

FOLIO supports only the latest two officially released flower releases.

This also applies to docs.folio.org, therefore we only change Poppy and Quesnelia documentation. Older documentation should have a “NO LONGER SUPPORTED” warning, for example https://juniper.docs.folio.org/docs/ , but doesn’t get any updates.

Existing Debian packages for Okapi will be kept at least until Ramsons gets released.

Ingolf Kuss September 19, 2024 at 11:20 AM

| If certain members of community feels strongly that deb packages still need to be made available to the FOLIO community, …

I would find it a natural solution to keep the old okapi packages on https://repository.folio.org/packages/ubuntu/ for focal (Ubuntu 20) and older, while not supplying new ones. Will this produce time and resources to the community ?

Ingolf Kuss September 19, 2024 at 11:13 AM

| Any documentation, including the “single-server folio-install” (which is way out of date, anyway) should be updated or removed.

It doesn’t make sense to update old install docs of, say, Morning Glory and older, to use Okapi docker image. Still, I am not aware of any policy or common practice that it “should be removed” from docs.folio.org, then. docs.folio.org currently offers all release versions back to Honeysuckle. If this is not intended, that should be discussed in and announced by the documentation working group, #folio-documentation, who is maintaining this site.

Craig McNally September 12, 2024 at 6:15 PM

Thanks John. Please make the announcement. I will try to spread the word as well by raising this at an upcoming TC meeting.

Won't Do

Details

Assignee

Reporter

Priority

Development Team

FOLIO DevOps

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 14, 2023 at 6:47 AM
Updated February 13, 2025 at 4:02 PM
Resolved November 7, 2024 at 4:30 PM
TestRail: Cases
TestRail: Runs