#2037 F30 Change: Deprecate Apache Avalon
Closed: Accepted 5 years ago by churchyard. Opened 5 years ago by bcotton.

Mark Apache Avalon software packages as deprecated.


10 is really just a handful and could probably be fixed quickly but +1

I count the vote as (+3,0,-0). Since this was submitted right before the holidays, I will wait until Thursday to process this Change proposal as accepted.

-1

Avalon is fourteen-years dead. I counter-propose that we yank it out of the release and let the FTBFS policy deal with the remaining packages that depend on it at the mass-rebuild.

It would be nice if the Change Proposal listed the packages affected, though. If it turns out that systemd or the kernel is in the list, I might reconsider that vote.

A quick repoquery later and we get:

  • apache-commons-logging-0:1.2-16.fc30.src
  • avalon-framework-0:4.3-21.fc29.src
  • fop-0:2.2-3.fc30.src
  • hadoop-0:2.7.6-5.fc29.src
  • idlj-maven-plugin-0:1.2.1-9.fc27.src
  • jacorb-0:2.3.2-3.jbossorg.5.fc27.src
  • jets3t-app-0:0.9.3-9.fc29.noarch
  • pax-logging-0:1.6.9-17.fc29.src
  • proxool-0:0.9.1-22.fc29.src

So, eight packages (not including avalon-framework, with only hadoop sending up warning flags for me. My quick guess though is that most of these packages probably don't actually depend on avalon... they likely just have old Requires that need updating.

Since there's a -1, I will hold off on processing this Change proposal until after Monday's FESCo meeting.

Avalon is fourteen-years dead. I counter-propose that we yank it out of the release and let the FTBFS policy deal with the remaining packages that depend on it at the mass-rebuild.

As I wrote in the change proposal, I am for removing Avalon from Fedora. The problem is that Avalon is a dependoncy of some valuable software packages that IMO should be kept in Fedora. In particular the following software has runtime dependency on Avalon:

  • Apache Hadoop,
  • FreeMind,
  • Publican (tool used to build official Fedora documentation),
  • Scilab,
  • Wildfly (formerly known as JBoss Application Server),
  • and many more.

And even more software has build-only dependency on Avalon. Without someone volunteering to work on removing all these dependences, removal of Avalon is not feasible.

It would be nice if the Change Proposal listed the packages affected, though. If it turns out that systemd or the kernel is in the list, I might reconsider that vote.

Listing all packages that would be affected by removal of Avalon would IMO be pointless as I am not proposing or planning to remove Avalon in Fedora 30. However, some core packages definitely have build dependency on Avalon, which can be proven by presence of both avalon-framework and avalon-logkit packages among those required to build Base Runtime and Platform modules.

https://meetbot.fedoraproject.org/fedora-meeting-1/2019-01-07/fesco.2019-01-07-15.00.log.html

This was approved in bulk:

AGREED: APPROVED (+9, 0, -0)

@sgallagh will propose a new way to deprecate packages

Metadata Update from @churchyard:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata