kompose
kompose copied to clipboard
kubernetes
Packaging Kompose for debian
Bug#874049: Acknowledgement (ITP: Kompose -- conversion tool for all things compose( namely Docker Compose) to container ochestrators (Kubernetes or Openshift))
@cdrage was looking at this one before IIRC !
@rahulkrishnanfs has filed it in Debian upstream https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874049
Hey @rahulkrishnanfs I can help and become a co-maintainer. I've been wanting to become a Debian developer for a while.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale
Unfortunately going to close this as we advise users to use binaries instead. Unfortunately we do not have the bandwidth to support a native Debian package.
do you expect revisiting your conclusion?
If you can become a maintainer of the package + distribute upstream we can revisit it, otherwise we unfortunately do not have the resources to maintain a debian package.
Johan, If you would like to join with me, we can package together.
Regards, Rahul Ra
On Mon, 15 Jan 2024, 15:07 Charlie Drage, @.***> wrote:
do you expect revisiting your conclusion?
If you can become a maintainer of the package + distribute upstream we can revisit it, otherwise we unfortunately do not have the resources to maintain a debian package.
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/kompose/issues/806#issuecomment-1892346227, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DOYMBTAS6YKOTWOKQDE3YOVA2FAVCNFSM4DZLRAQ2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBZGIZTINRSGI3Q . You are receiving this because you were mentioned.Message ID: @.***>
Cheers, cdrage.
Rahul, interesting. What would that entail? Are you already maintaining some debian packages? What's your preferred means of communication, should we want to move it outside this issue?