When running build-classpath db-4.8.30 it is unable to locate the db-4.8 jar files as they are installed into /usr/lib/java/db48-4.8.30.jar instead of /usr/shared/java/db-4.8.30.jar This breaks things like being able to build Ice-3.4.2 amungst other things that require DB-4.8 support in java. A fix to this was for me to simply create as symlink by doing ln -s /usr/lib/java/db4.8-4.8.30.jar db-4.8.30.jar It would be nice if the db48 package would either create the appropriate symlink or the java packages would also search /usr/lib/java. Not sure which to file this under. All other packages such as jgoodies-forms install their jar files to /usr/share/java db48 installs its to /usr/lib/java -- not sure why. NOTE: This seems to also effect mageia 2 as well but i am currently using mageia 1. Packages: ---------- db4.8-4.8.30-5.mga1 lib64db4.8-devel-4.8.30-5.mga1 jpackage-utils-1.7.5-5.mga1
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX