<div dir="ltr"><div>I'm also in favor of doing option 1 until option 2 is possible.<br></div><div><br></div><div>I had an existing email thread with the upstream maintainer going. To work towards option (2) I've bumped that thread with him just now, identifying the PRs below and asking him to review+feedback or review+merge.</div><div><div><br></div><div><a href="https://github.com/geerlingguy/ansible-role-postgresql/pull/86" target="_blank">https://github.com/geerlingguy/ansible-role-postgresql/pull/86</a></div><div><a href="https://github.com/geerlingguy/ansible-role-postgresql/pull/92" target="_blank">https://github.com/geerlingguy/ansible-role-postgresql/pull/92</a></div><div><a href="https://github.com/geerlingguy/ansible-role-postgresql/pull/91" target="_blank">https://github.com/geerlingguy/ansible-role-postgresql/pull/91</a></div><div><a href="https://github.com/geerlingguy/ansible-role-postgresql/pull/69" target="_blank">https://github.com/geerlingguy/ansible-role-postgresql/pull/69</a></div><div><br></div><div>If there are additional things besides these PRs please identify them also.</div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 3, 2019 at 10:47 AM Dennis Kliban <<a href="mailto:dkliban@redhat.com" target="_blank">dkliban@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Combination of 1 and 2: we need to find a way to collaborate with the author more closely to get outstanding PRs merged.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 3, 2019 at 8:28 AM Matthias Dellweg <<a href="mailto:dellweg@atix.de" target="_blank">dellweg@atix.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
in the ansible-pulp role (that is meant to install pulp) we use a role<br>
to install the postgresql db-server from galaxy named<br>
ansible-role-postgres.<br>
Sadly the upstream version of this role is missing fedora30 support,<br>
and the PR for this has not been merged for a long time.<br>
This leads to ansible-pulp using a clone of this role, which is<br>
hosted on github in a personal namespace and is missing debian10 support<br>
respectively.<br>
This sounds to me like a kind of short term workaround, but it is in<br>
place for almost half a year now.<br>
<br>
I see several ways to move this forward:<br>
<br>
1)Leave it as is, wait for upstream.<br>
pros: nothing to do (now)<br>
cons: no good debian support<br>
2)Use upstream role and add fedora30 config like debian10 config [0]<br>
pros: no need to maintain a clone of the role<br>
cons: ugly workaround<br>
3)Use upstream, and drop fedora30 support for now<br>
pros: no need to maintain a clone of the role<br>
cons: seems quite obvious?<br>
4)Maintain a clone of the role in the pulp namespace with a team of<br>
committers<br>
pros: most flexibility, fedora30 & debian10 support<br>
cons: extra maintainance work<br>
<br>
(The order is random, and the numbers are only for future references. I<br>
do not want to express a personal preference this way.)<br>
<br>
Matthias<br>
<br>
[0] <a href="https://github.com/pulp/pulplift/pull/45" rel="noreferrer" target="_blank">https://github.com/pulp/pulplift/pull/45</a><br>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>