Bug 2501971

maven-doxia is one of the  dependencies required to build the antlr4-project, itself a dependency needed to build sympy in non-bootstrap mode for epel10 (https://bugzilla.redhat.com/show_bug.cgi?id=2368290) And sympy is, in its turn, a deep dependency of Ceph, which I package in CentOS Stream and someday maybe in Rocky if the Rocky folks ever get around to creating projects for me.

scratch build at https://koji.fedoraproject.org/koji/taskinfo?taskID=147955309

Wouldn't you rather skip generating documentation for the EPEL builds?

Reassigning to the EPEL maintainer.  @michel can you take care of this?

(In reply to Jerry James from comment #2)
> Wouldn't you rather skip generating documentation for the EPEL builds?

I'm open to suggestions.  I don't know what any of this stuff does, I'm just plunking through all the dependencies so I can get sympy built in non-bootstrap. If there's a shortcut, let me know.

> 
> Reassigning to the EPEL maintainer.  @michel can you take
> care of this?

This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.

> If you do not wish to maintain maven-doxia in epel10,
> or do not think you will be able to do this in a timely manner,
> I would be happy to be a co-maintainer of the package (FAS: kkeithle);

bump

WIP

this PR address the current FTBFS from koschei + adapt the spec to support epel10

https://src.fedoraproject.org/rpms/maven-doxia/pull-request/5

scratch build for epel10 => https://koji.fedoraproject.org/koji/taskinfo?taskID=149336170

@logan(In reply to Jerry James from comment #2)

> Reassigning to the EPEL maintainer.  @michel can you take
> care of this?

ah, please remove the EPEL bugzilla assignment making me the assignee. I signed up for this when it was needed to try and bootstrap the golang packages for EPEL 10, but since then the Golang SIG switched to vendoring dependencies anyway.

> If you do not wish to maintain maven-doxia in epel10,
> or do not think you will be able to do this in a timely manner,
> I would be happy to be a co-maintainer of the package (FAS: kkeithle);
> please add me through https://src.fedoraproject.org/rpms/maven-doxia/adduser

Or advise how to build maven-invoker-plugin without this.  Thanks

> If you do not wish to maintain maven-doxia in epel10,
> or do not think you will be able to do this in a timely manner,
> I would be happy to be a co-maintainer of the package (FAS: kkeithle);
> please add me through https://src.fedoraproject.org/rpms/maven-doxia/adduser

Or advise how to build maven-invoker-plugin without this as it would eliminate the need to build maven-reporting-api and maven-reporting-impl.  Thanks

I orphaned maven-doxia because no package I maintain needs it anymore. You are free to take it if you wish. It may not be possible to remove the maven-doxia dependency from maven-invoker-plugin. It seems to be needed by src/main/java/org/apache/maven/plugins/invoker/InvokerReportRenderer.java.

Filipe Rosset has already taken it.

> If you do not wish to maintain maven-doxia in epel10,
> or do not think you will be able to do this in a timely manner,
> I would be happy to be a co-maintainer of the package (FAS: kkeithle);
> please add me through https://src.fedoraproject.org/rpms/maven-doxia/adduser

successful epel10 scratch build https://bugzilla.redhat.com/show_bug.cgi?id=2497806

(In reply to Kaleb KEITHLEY from comment #14)
> successful epel10 scratch build
> https://bugzilla.redhat.com/show_bug.cgi?id=2497806

great, thanks


@michel could you please request the epel10 branches?

(In reply to Jerry James from comment #12)
> I orphaned maven-doxia because no package I maintain needs it anymore. You
> are free to take it if you wish. It may not be possible to remove the
> maven-doxia dependency from maven-invoker-plugin. It seems to be needed by
> src/main/java/org/apache/maven/plugins/invoker/InvokerReportRenderer.java.

I'm not sure why you are still the "owner" for Fedora => https://src.fedoraproject.org/rpms/maven-doxia

could you please try "orphan" the package to see what happens ?

otherwise we will need to open a ticket with the infra team to fix the package membership.

"Unable to orphan the package: You are not allowed to modify this project."

(In reply to Jerry James from comment #17)
> "Unable to orphan the package: You are not allowed to modify this project."

I added a comment to https://forge.fedoraproject.org/releng/tickets/issues/13564

There are issues with the pkg ownership + EPEL branches.

FEDORA-EPEL-2026-57413d100b (maven-doxia-2.1.0-4.el10_4) has been submitted as an update to Fedora EPEL 10.4.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-57413d100b

FEDORA-EPEL-2026-57413d100b has been pushed to the Fedora EPEL 10.4 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-57413d100b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-EPEL-2026-7a6f0e7fdb has been pushed to the Fedora EPEL 10.4 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7a6f0e7fdb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.