[Bug 1799152] New: antlr4: FTBFS in Fedora rawhide/f32
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1799152
Bug ID: 1799152
Summary: antlr4: FTBFS in Fedora rawhide/f32
Product: Fedora
Version: rawhide
Status: NEW
Component: antlr4
Assignee: stuart(a)gathman.org
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: cz172638(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
lef(a)fedoraproject.org, mizdebsk(a)redhat.com,
projects.rg(a)smart.ms, puntogil(a)libero.it,
stuart(a)gathman.org
Blocks: 1750908 (F32FTBFS)
Target Milestone: ---
Classification: Fedora
antlr4 failed to build from source in Fedora rawhide/f32
https://koji.fedoraproject.org/koji/taskinfo?taskID=41315802
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
Please fix antlr4 at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
antlr4 will be orphaned. Before branching of Fedora 33,
antlr4 will be retired, if it still fails to build.
For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1750908
[Bug 1750908] Fedora 32 FTBFS Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 11 months
[Bug 1754645] New: Retire elasticsearch? FTBFS since f24
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1754645
Bug ID: 1754645
Summary: Retire elasticsearch? FTBFS since f24
Product: Fedora
Version: rawhide
Status: NEW
Component: elasticsearch
Assignee: bazanluis20(a)gmail.com
Reporter: kevin(a)scrye.com
QA Contact: extras-qa(a)fedoraproject.org
CC: bazanluis20(a)gmail.com, bobjensen(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
jvanek(a)redhat.com, pahan(a)hubbitus.info,
zbyszek(a)in.waw.pl
Target Milestone: ---
Classification: Fedora
elasticsearch has failed to build since f24.
The failure is in prep/sources (the sources file wasn't updated with the last
package update), so due to never creating a koji build on mass rebuilds it's
never shown up in the FTBFS list.
With the java stack in modules now, I don't think it can be built currently.
Some options:
* retire it now and re-add it after ursa-prime lands so you can use the java
stack to build it.
* retire it and make a module for it.
* something else?
If there's not a good reason to keep it, I'd suggest we retire it in
rawhide/f31 asap.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 11 months
[Bug 1891536] New: hawtjni-1.18 is available
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1891536
Bug ID: 1891536
Summary: hawtjni-1.18 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: hawtjni
Keywords: FutureFeature, Triaged
Assignee: java-maint-sig(a)lists.fedoraproject.org
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: decathorpe(a)gmail.com,
java-maint-sig(a)lists.fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, puntogil(a)libero.it
Target Milestone: ---
Classification: Fedora
Latest upstream release: 1.18
Current version/release in rawhide: 1.17-6.fc33
URL: https://github.com/fusesource/hawtjni
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/1296/
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 11 months