Description of problem: As of version 1.1.0 fig has been renamed docker-compose. Version-Release number of selected component (if applicable): fig-1.0.1-2.fc22.x86_64.rpm How reproducible: Always Additional info: A note on the www.fig.sh web site indicates that fig is deprecated and has been replaced with docker-compose, located at https://github.com/docker/compose . A brief look indicates that it is the same code base, but with a new name. The name of the executable is now docker-compose, so I suggest that the package be so named. At some point docker-compose 1.1.0 should be built for Fedora and obsolete fig.
Created attachment 1005590 [details] docker-compose.spec.patch Patch updates fig.spec to docker-compose.spec. Includes one new require from upstream (python-dockerpty), and a version requirement for python-docker-py related to bug 1197300. It probably needs a bit of cleanup, but it is working for me. Scratch builds can be found at https://copr.fedoraproject.org/coprs/error/rl/build/82903/
Created attachment 1005591 [details] remove-requires-upper-bound.patch Updated remove-requires-upper-bound.patch against 1.1.0 sources
Thanks for the patch! I'm a little busy right now, but I'll try to do something about this next week.
It would be also great to make it noarch.
(In reply to Tomas Tomecek from comment #4) > It would be also great to make it noarch. Yes, there's no reason for this to be ExclusiveArch, now that both it and Docker support a secure remote transport (https with client certificates).
changing the Name: field to docker-compose probably won't be sufficient and we'll need a new package review and a dist-git created for this. I'm ready to volunteer for this.
Just checked with Matej, I'll be retiring this package soon in favor of a new docker-compose package. Michael, you're welcome to join me in co-maintaining it. Or if you prefer, you could create docker-compose and get it approved and add me later on as co-maintainer. Let me know :)
guess it's time to retire fig now that we have docker-compose. Matej would you like to handle retiring fig? ohh also, we gotta make sure to update docker-compose to 'Provides: fig' and I think, also 'Obsoletes: fig <= %{existing_fig_version}-%{existing_fig_release}'
(In reply to Lokesh Mandvekar from comment #8) > guess it's time to retire fig now that we have docker-compose. Matej would > you like to handle retiring fig? Retired in f23+. Rest in peace.
Since fig is now retired, docker-compose provides it and I haven't heard any complaints, I'm closing this; hope you don't mind, Lokesh :)