Hi Johannes, there's one things that I don't understand. Why would you like to submit dlp:python-toml to your CloudStack project in place of simply doing a linkpac ? You can also pick the revision if you want stability.

Bruno Friedmann (bruno_friedmann) - almost 7 years ago

source maintainer

Also it seems (from the description of the project that you should sr to :Staging). Instead of linkpac there's also the osc copypac from project:devel:languages:python package:python-toml revision:2 way of doing it (picked from erlang)

---

Thomas Bechtold (tbechtold) - almost 7 years ago

source maintainer target maintainer

@bruno_friedmann, this is ok. That's the way we handle the Cloud:OpenStack subprojects.

Cloud:OpenStack:Pike is the latest stable OpenStack project. For stable projects our policy is to copypac -K -e because that way the package will remain in place, even if the upstream package gets deleted. For the unstable Cloud:OpenStack:Master project our policy is to linkpac to the latest revision. Until a couple of weeks ago I'd just have performed a straight copypac, but we recently restricted the number of maintainers on the stable projects project to a smaller group and I'm not part of that group...

The :Staging project is only for core OpenStack services. Everything else (e.g. dependencies or third-party services such as RabbitMQ) goes into the non-staging repository.

Thanks both for the explanations.