kiskadee

#19 Define a better way to handle kiskadee dependencies
Closed: NEXTRELEASE Opened by davidcarlos.

Closed: NEXTRELEASE
Reopen Issue

Test dependencies should not go in requirements.txt, we need to define a way to handle this dependencies separately.

Metadata Update from @davidcarlos:
- Issue set to the milestone: version 0.4
- Issue tagged with: Enhancement

Metadata Update from @davidcarlos:
- Issue assigned to davidcarlos

Metadata Update from @davidcarlos:
- Issue set to the milestone: None (was: version 0.4)

Metadata Update from @davidcarlos:
- Issue set to the milestone: version 0.4.1

This issue is done. I had moved kiskadee test dependencies to a separate file, that is used by jenkins before run kiskadee tests.

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

Enhancement

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.