Bug 521523
Summary: | RPM Dependencies for 389 console are incomplete | ||
---|---|---|---|
Product: | [Retired] 389 | Reporter: | Razvan Corneliu C.R. VILT <razvan.vilt> |
Component: | Install/Uninstall | Assignee: | Nathan Kinder <nkinder> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Viktor Ashirov <vashirov> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 1.2.1 | CC: | amsharma, brianlamere, rmeggins |
Target Milestone: | --- | Keywords: | VerifiedUpstream |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-07 16:41:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 434915, 519216 |
Description
Razvan Corneliu C.R. VILT
2009-09-06 17:48:49 UTC
Should be relatively straightforward to add a Requires: which - not sure what the problem is with java and the fonts. The problem for Java is quite simple. The console requires some fonts of some kind to be provided to Java in order for it to start up visually. Unfortunately, you can easily install an unusable console due to the lack of any fonts (from the RPM dependencies) on the system. The question is: should we have a generic "provides: fonts" in each font RPM such that yum installs some random pack? Is that really a bug? Is there a way to Require fonts in general or Require specific fonts? That would be easy to add to the spec. I'm not really sure if specific fonts would be the right thing. That's the issue that I'm fighting with. Probably the best thing to do would be to just skip this. part. Who knows what fonts Gnome or KDE will default to in the future and we don't want to force the user to use a certain font. Furthermore, if someone wants to use a localized version of the product, something like bitstream vera sans might not apply anymore or might not be optimal in CJK languages or in scripted languages like Arabic or Farsi. The other option would be to include a single fallback font in the JDK implementation. Technically, it should be a requirement for the Swing/AWT/SWT/Java2D/etc. packages. Added the "which" package to the Requires Checking in F-10/389-console.spec; /cvs/extras/rpms/389-console/F-10/389-console.spec,v <-- 389-console.spec new revision: 1.3; previous revision: 1.2 done Checking in F-11/389-console.spec; /cvs/extras/rpms/389-console/F-11/389-console.spec,v <-- 389-console.spec new revision: 1.3; previous revision: 1.2 done Checking in F-12/389-console.spec; /cvs/extras/rpms/389-console/F-12/389-console.spec,v <-- 389-console.spec new revision: 1.4; previous revision: 1.3 done Checking in devel/389-console.spec; /cvs/extras/rpms/389-console/devel/389-console.spec,v <-- 389-console.spec new revision: 1.4; previous revision: 1.3 done 389-console-1.1.3-5.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/389-console-1.1.3-5.fc12 389-console-1.1.3-4.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/389-console-1.1.3-4.fc11 389-console-1.1.3-4.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/389-console-1.1.3-4.fc10 389-console-1.1.3-4.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. 389-console-1.1.3-4.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. (In reply to comment #4) > I'm not really sure if specific fonts would be the right thing. That's the > issue that I'm fighting with. Probably the best thing to do would be to just > skip this. part. Who knows what fonts Gnome or KDE will default to in the > future and we don't want to force the user to use a certain font. Furthermore, > if someone wants to use a localized version of the product, something like > bitstream vera sans might not apply anymore or might not be optimal in CJK > languages or in scripted languages like Arabic or Farsi. > > The other option would be to include a single fallback font in the JDK > implementation. Technically, it should be a requirement for the > Swing/AWT/SWT/Java2D/etc. packages. Having just run in to this same problem on a headless Fedora13 system, I'd think that instead of having the exception just barf it would be helpful to catch that exception in the java code, and fail with a more useful message. Or yes, perhaps the jdk should have had a basic font package as a dependency? The common fonts is such a small package, and unlike other packages that have package dependencies that make almost no sense, having this one depend on one of the basic font packages (liberation-fonts-common?) seems comparatively reasonable. |