Package kawa seems to contain versioned jar files in %{_javadir} (/usr/share/java). Such versioned files cause problems for automatic requires generation and violate packaging guidelines[1]. List of subpackages and contained versioned jars kawa: /usr/share/java/kawa-1.11.jar There are cases where this can be a false positive. Most likely if: * your package is compatibility version and contains only versioned jars * your package has version in the name of jars that are part of package name Thank you, [1] https://fedoraproject.org/wiki/Packaging:Java#Filenames
-rw-r--r-- 1 awk awk 2866450 06-24 23:28 kawa-1.14.jar lrwxrwxrwx 1 awk awk 13 06-24 23:28 kawa.jar -> kawa-1.14.jar
This *is* a bug, see: http://fedoraproject.org/wiki/Packaging:Java#Filenames "Versioned JAR files (*-%{version}.jar) MUST NOT be installed unless the package is a compatibility package"
(In reply to Christopher Meng from comment #1) > -rw-r--r-- 1 awk awk 2866450 06-24 23:28 kawa-1.14.jar > lrwxrwxrwx 1 awk awk 13 06-24 23:28 kawa.jar -> kawa-1.14.jar I will contact upstream and see if it makes sense.
Upstream: "I don't have strong feelings about what is right. I have been trying to following GNU conventions in the Makefile, but the Java support is homegrown rather than automake-based. .so files are installed as versioned files, with symlinks. It seems reasonable to do something similar for .jar files; they're conceptually very similar. If the packaging guidelines say that .so and .jar files should be treated differently in this respect, I'd curious to know the reason for the seeming inconsistency. Maintaining binary compatibility between Kawa has not so far been a priority, which is why leaving the version number in the filename seems reasonable. I don't know if that qualifies for the "compatibility" exception. But if it is a problem I can modify the "install-jar" rule in the top-level Makefile.am. Possibly make it conditional."
This is not an upstream issue but a packaging one. There's no reason why upstream should change to unversioned just because it doesn't make sense in Fedora.
(In reply to Stanislav Ochotnicky from comment #5) > This is not an upstream issue but a packaging one. There's no reason why > upstream should change to unversioned just because it doesn't make sense in > Fedora. Patch welcome, I don't have time now.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I tried to fix it, but app can't launch . So I revert changes : http://pkgs.fedoraproject.org/cgit/kawa.git/commit/?id=7b2336adb21f9a8f5630fc2b9bd2dd09cfe4f8a6
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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 Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Fixing
FEDORA-2020-3ac0375023 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3ac0375023
kawa-3.1.1-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3ac0375023
kawa-3.1.1-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.