epel

#284 Proposing incompatible upgrade of Zeek to the latest LTS version
Closed: Rejected by salimma. Opened by salimma.

Closed: Rejected
Reopen Issue

Being discussed in

https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/TVF72GVPDFC5EPZVSGIW7YQBGVSNGKUK/

(please tag for meeting after the next meeting on July 24 as it won't have had a week of discussion before then)

TL;DR the previous version was stale due to lack of maintenance, and Zeek upstream only support LTS for a year (and feature releases for 4 months - and the previously available version in our repo was a feature release). No known dependent package in EPEL.

+1

Metadata Update from @tdawson:
- Issue tagged with: meeting

+1

Metadata Update from @salimma:
- Issue untagged with: meeting

Following up from discussions in two meetings:

  • we miss the boat for the initial proposed approach anyway, zeek 7 LTS is now out
  • the suggestion from @carlwgeorge to just package versioned zeek (so zeek7 or zeek7.0 - probably zeek7 as the LTS always has a 0 minor version) makes sense for the long term (similar to how Django is maintained in EPEL)
  • this will let us package the latest without the incompatible upgrade process, user can stay on the obsolete version if they want
  • if there is a bad security issue we can then retire the EOL version but this is decoupled from packaging the latest LTS
  • the additional proposal to package this like Python (versioned source package, unversioned binary package) is considered but rejected. It adds to the pain (needing to create a new package and getting it reviewed) without the gain (the binary packages will replace existing packages so need to go through incompat process again)

Also note: upstream is quite bad at using CVEs or noting security issues in their NEWS file, so the best listing of security fixes included is in the GitHub release page. Shocking, I know, that people choose to rely on the forge to store important information...

https://github.com/zeek/zeek/releases

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

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/284

Please continue any further discussion there.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.