#47717 idm-console-framework: Switch to java-headless (build)requires
Closed: wontfix None Opened 7 years ago by rmeggins.

Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 1068147

idm-console-framework or one of its subpackages currently Requires and/or
BuildRequires
java. OpenJDK package has been split and most packages should now Require
package 'java-headless' instead. Requires and BuildRequires on java-devel
remain
unchanged.

Few exceptions where packages can not use java-headless but must keep using
full java package.
 * software using Java awt subsystem
 * software using Java sound subsystem

Your options:
1. Leave this bug untouched and after March 17th 2014 an automated tool will
   migrate this package to java-headless and run a rebuild in Fedora Rawhide.
2. Change bug to 'Assigned' if you plan to review and migrate to java-headless
   manually. Automated tool will not touch bugs that are not in NEW state.

See tracking bug #1067528 or Headless Java change proposal[1] and Java
Packaging
guidelines[2] for more details about this change.

If you have more questions about this change feel free to ask on java-devel
mailing list[3] or #fedora-java Freenode IRC channel (mostly 9:00-18:00 CET).


[1] https://fedoraproject.org/wiki/Changes/HeadlessJava
[2] https://fedoraproject.org/wiki/Packaging:Java\#BuildRequires_and_Requires
[3] http://lists.fedoraproject.org/pipermail/java-devel/

DS and Admin Consoles are unaffected.

Shouldn't this be the other way around? If you are installing 389-console and idm-console-framework, this means you want the full java with all of the graphics. However, you could install ds-console and admin-console on a server, and never actually run ds-console and admin-console on that server, but instead just remotely manage that server from a GUI, downloading the ds-console and admin-console jars to your local workstation.

Replying to [comment:5 rmeggins]:

Shouldn't this be the other way around? If you are installing 389-console and idm-console-framework, this means you want the full java with all of the graphics. However, you could install ds-console and admin-console on a server, and never actually run ds-console and admin-console on that server, but instead just remotely manage that server from a GUI, downloading the ds-console and admin-console jars to your local workstation.

That makes sense. However, the DS and admin console currently do not "Require" java at all(except as a build requirement "BuildRequires: java-devel >= 1:1.6.0") - which is why I skipped them over. So maybe nothing needs to be done at all then.

ds-console and admin-console packages might have implicit requirements. RPM will sometimes add Requires to packages based on the BuildRequires. Take a look at the rpms for those packages. If they have Requires: java, then we will have to put in an explicit Requires: java-headless.

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 389-admin,console 1.1.36

4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1051

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)

a year ago

Login to comment on this ticket.

Metadata