<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 8 March 2017 at 07:39, Hirofumi Ichihara <span dir="ltr"><<a href="mailto:ichihara.hirofumi@lab.ntt.co.jp" target="_blank">ichihara.hirofumi@lab.ntt.co.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
<br>
On 2017/03/08 23:59, Andreas Jaeger wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On 2017-03-08 15:40, ZZelle wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi,<br>
<br>
iiuc, neutron uses a released version of neutron-lib not neutron-lib<br>
master ... So the change should depends on a change in requirements repo<br>
incrementing neutron-lib version<br>
</blockquote>
This is documented also at - together with some other caveats:<br>
<br>
<a href="https://docs.openstack.org/infra/manual/developers.html#limitations-and-caveats" rel="noreferrer" target="_blank">https://docs.openstack.org/inf<wbr>ra/manual/developers.html#limi<wbr>tations-and-caveats</a><br>
</blockquote></span>
Thank you for the pointer. I understand.</blockquote><div><br></div><div>You can do the reverse as documented in [1]: i.e. file a dummy patch against neutron-lib that pulls in both neutron's and neutron-lib changes. One example is [2]</div><div><br></div><div>[1] <a href="https://docs.openstack.org/developer/neutron-lib/review-guidelines.html">https://docs.openstack.org/developer/neutron-lib/review-guidelines.html</a> </div><div>[2] <a href="https://review.openstack.org/#/c/386846/">https://review.openstack.org/#/c/386846/</a></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-HOEnZb"><font color="#888888"><br>
<br>
Hirofumi</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
Note a depends-on requirements won't work either - you really need to<br>
release it. Or you need to change the test to pull neutron-lib from source,<br>
<br>
Andreas<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On Wed, Mar 8, 2017 at 3:16 PM, Hirofumi Ichihara<br>
<<a href="mailto:ichihara.hirofumi@lab.ntt.co.jp" target="_blank">ichihara.hirofumi@lab.ntt.co.<wbr>jp</a><br>
<mailto:<a href="mailto:ichihara.hirofumi@lab.ntt.co.jp" target="_blank">ichihara.hirofumi@lab.<wbr>ntt.co.jp</a>>> wrote:<br>
<br>
Hi,<br>
<br>
I thought that we can post neutron patch depending on neutron-lib<br>
patch under review.<br>
However, I saw it doesn't work[1, 2]. In the patches, neutron<br>
patch[1] has Depends-on tag with neutron-lib patch[2] but the pep8<br>
and unit test fails because the test doesn't use the neutron-lib patch.<br>
<br>
Please correct me if it's my misunderstanding.<br>
<br>
[1]: <a href="https://review.openstack.org/#/c/424340/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/424340/</a><br>
<<a href="https://review.openstack.org/#/c/424340/" rel="noreferrer" target="_blank">https://review.openstack.<wbr>org/#/c/424340/</a>><br>
[2]: <a href="https://review.openstack.org/#/c/424868/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/424868/</a><br>
<<a href="https://review.openstack.org/#/c/424868/" rel="noreferrer" target="_blank">https://review.openstack.<wbr>org/#/c/424868/</a>><br>
<br>
Thanks,<br>
Hirofumi<br>
<br>
<br>
<br>
_____________________________<wbr>______________________________<wbr>_______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.o<wbr>penstack.org?subject:unsubscri<wbr>be</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-<wbr>request@lists.openstack.org?<wbr>subject:unsubscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cg<wbr>i-bin/mailman/listinfo/opensta<wbr>ck-dev</a><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/c<wbr>gi-bin/mailman/listinfo/openst<wbr>ack-dev</a>><br>
<br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div></div>