[Pulp-dev] How does the Developer Ansible Playbook Identify Dependencies?
austin at redhat.com
Mon Dec 12 17:32:46 UTC 2016
I was confused about how this works recently, so I dug around to get a
better idea. I learned some things that might be helpful to you:
- The normal repo file is not created for some reason for f24:
- This is where we use rpmspec to look for Requires:
- This is where those deps are installed.
Also, I do expect the dev role to install pulp-server dependencies, but I
do not expect the pulp_server role to run on a dev system.
On Sat, Dec 10, 2016 at 1:47 PM, Brian Bouterse <bbouters at redhat.com> wrote:
> I ran into this issue  where vagrant up (master of pulp/devel) was not
> installing Kobo. Kobo is listed as a dependency in the spec file on
> 2.10-dev, and I thought the Ansible dev playbook inspected the spec file
> for each plugin and platform and dnf installed those items. I was surprised
> when it was not installed by the Ansible playbook.
> I thought this line would do it which installs pulp-server  via rpm
> which should bring in kobo as a dependency.
> * Do others expect ansible dev to install pulp-server dependencies listed
> in the pulp.spec
> * Any insight into why this didn't happen?
> * Can someone explain to me how our dependencies are supposed to be
> treated by the dev Ansible playbook?
> : https://pulp.plan.io/issues/2481
> : https://github.com/pulp/pulp/blob/60e85bf4383a8c0bc5ef054c42bfc3
> : https://github.com/pulp/devel/blob/8604223e2e23e208aa69e40d26e43c
> Thank you!
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev