Description of problem: on F33 `dnf repoquery hamcrest --provides` (...) osgi(org.hamcrest.generator) = 1.3.0 osgi(org.hamcrest.integration) = 1.3.0 osgi(org.hamcrest.library) = 1.3.0 on rawhide `dnf repoquery --disablerepo='*' --enablerepo=rawhide hamcrest --provides` we don't see any provides of osgi Version-Release number of selected component (if applicable): hamcrest-0:2.2-5.fc35.noarch Expected results: osgi(org.hamcrest.generator) = 2.2.0 osgi(org.hamcrest.integration) = 2.2.0 osgi(org.hamcrest.library) = 2.2.0 Additional info:
Confirmed. Reproducer: dnf -q -C --repo rawhide repoquery --provides hamcrest | grep osgi Is hamcrest OSGi metadata needed by anything in Fedora? This will help prioritize this bug.
eclipse.spec have Requires: osgi(org.hamcrest.core)
Yes, I'm aware Eclipse was the primary user of OSGi metadata, but Eclipse is retired. I'll keep it low priority, possibly eventually close as WONTFIX unless there is a reason to re-add OSGi metadata.
(In reply to Mikolaj Izdebski from comment #3) > Yes, I'm aware Eclipse was the primary user of OSGi metadata, but Eclipse is > retired. > I'll keep it low priority, possibly eventually close as WONTFIX unless there > is a reason to re-add OSGi metadata. but I'd like bring back eclipse to Fedora , for that one of the first goals is build tycho
I see. Can you provide a patch or PR for adding OSGi metadata that will work for Eclipse? OSGi metadata is added with a downstream patch. Traditionally, Fedora Eclipse maintainers were maintaining such patches as the metadata is coming from Eclipse Orbit and Fedora package maintainers have no easy way of testing whether such patch is correct.
(*) for that one, of the first goals is build tycho the build eclipse we need bootstrap some builds which requires OSGi metadata IIRC and have OSGi metadata would be more easier to build it, that why I was interested on OSGi metadata. if we can build and all other packages associated to eclipse without OSGi metadata fine for me. Again I think now the path is build "tycho" but we have many obstacles (like OSGi metadata ...) Best regards,
Upstream hamcrest does not include OSGi metadata, but I will accept downstream patches adding it. Until then I'm closing the bug as WONTFIX, feel free to reopen it once patch or pull request with OSGi metadata is submitted.