#9365 Unorphan python-cassandra-driver
Closed: Get back later 4 years ago by mohanboddu. Opened 4 years ago by nyh.

  • Name of the package?
    python-cassandra-driver

  • FAS username of the new maintainer?
    nyh

  • Any extra information?
    As I understand it, python-cassandra-driver was retired because the previous maintainer lost interest, and apparently because the Cassandra server package was retired as well. However, unlike the Cassandra server which often requires complex setups involving many machines and much tweaking beyond what Fedora can offer - the client package (python-cassandra-driver) can be used on "mundane" machines that just connect to a Cassandra cluster, and it's very useful to do this from Fedora.
    Personally, I'm a developer on Scylla (https://github.com/scylladb/scylla), an open-source Cassandra-compatible server, and I am not planning to run the Cassandra server, but definitely want to run the Cassandra client which is also a Scylla client, and I want it see it remain a package on Fedora and not having to resort to extra-Fedora mechanisms like "pip".
    I think (but please correct me if I'm wrong) the "retiring" of the Cassandra client library went mostly unnoticed by the Cassandra users in the Fedora community, because this package still exists in Fedora 31, which is why you didn't see opposition to retiring this still-very-useful package.


The package is retired for 5 months, it needs a new package review.

The package is retired for 5 months, it needs a new package review.

Hi, I'm a Fedora (and before that, Redhat) user for twenty-two years, and have a lot of experience as an open-source developer on many projects, but I unfortunately have zero experience with Fedora's internal processes. So I don't know what "a new package review" entails or how to initiate it. Is it something I need to do? How? Or is the fact that I opened this issue enough, and we can "review" this package on this issue?
Thanks.

@nyh Please reopen the ticket after you become a packager.

Thanks.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Get back later
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata