<div dir="ltr">> <span style="font-family:arial,sans-serif;font-size:12.800000190734863px"> if we want to build iso with custom packages, we have to add flexibility to our dependencies lists.</span><div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px">yes please, if there is no other option. It should be easy for anyone to build Fuel on custom packages, so let's target for it.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px">I do not see issues in flexible deps while we are managing our upstream packages in our own mirrors. Are there any possible issues?</span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 26, 2014 at 2:42 PM, Dmitry Pyzhov <span dir="ltr"><<a href="mailto:dpyzhov@mirantis.com" target="_blank">dpyzhov@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">It is not enough, you need to review requirements in the code of nailgun, ostf and astute.<div><br></div>
<div>I'll be happy to have our requirements files and specs as close to global-requirements as possible. It will ruin our current solid structure, where we have same versions of dependencies on production, on development and test environments. And from time to time we will face issues with updates from pypi. Development and test environments will be affected. We somewhat protected from it by maintainers of global-requirement file. And changes in production environments are protected by OSCI team.</div>
<div><br></div><div>So, if we want to build iso with custom packages, we have to add flexibility to our dependencies lists. Any objections?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">
On Mon, Aug 25, 2014 at 8:28 PM, Timur Nurlygayanov <span dir="ltr"><<a href="mailto:tnurlygayanov@mirantis.com" target="_blank">tnurlygayanov@mirantis.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div>Commit with fast fix was submitted: <a href="https://review.openstack.org/#/c/116667/" target="_blank">https://review.openstack.org/#/c/116667/</a><br>
</div>Need review :)<br><br></div>I will try to build image with this commit and will send my comments with my results.<br>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 25, 2014 at 7:55 PM, Timur Nurlygayanov <span dir="ltr"><<a href="mailto:tnurlygayanov@mirantis.com" target="_blank">tnurlygayanov@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>When I started the build of ISO from master branch, I can see the following errors:<br><a href="https://bugs.launchpad.net/fuel/+bug/1361279" target="_blank">https://bugs.launchpad.net/fuel/+bug/1361279</a><br>
<br>I want to submit the patch set and remove all hardcoded requirements and change all '==' to '>=', but I want to discuss how we can organize specs to avoid problems with dependencies before this.<br>
<br></div>Thank you.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Mon, Aug 25, 2014 at 6:21 PM, Timur Nurlygayanov <span dir="ltr"><<a href="mailto:tnurlygayanov@mirantis.com" target="_blank">tnurlygayanov@mirantis.com</a>></span> wrote:<br>
</div><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div>Hi team,<br><br></div>Today I started to build Fuel ISO from
the master branch and with packages with code from the master branches,
and have found strange errors:<br><a href="http://jenkins-product.srt.mirantis.net:8080/view/custom_iso/job/custom_master_iso/77/console" target="_blank">http://jenkins-product.srt.mirantis.net:8080/view/custom_iso/job/custom_master_iso/77/console</a><br>
<br></div>Looks like we have hardcoded versions of all required packages in specs:<br><a href="https://github.com/stackforge/fuel-main/blob/master/packages/rpm/specs/nailgun.spec#L17-L44" target="_blank">https://github.com/stackforge/fuel-main/blob/master/packages/rpm/specs/nailgun.spec#L17-L44</a><br>
<br clear="all"><div>and this is the root of problems. In the
result we can't build ISO from master branch, because we have another
versions of requirements for code from master branches.<br>Looks like it is common issue for several components.<br>
<br></div><div>Could we discuss how we can organize specs to avoid problems with dependencies?<br><br><br></div>Thank you!<span><font color="#888888"><br></font></span><br clear="all"><br>-- <br><div dir="ltr"><font color="#888888"><font color="#888888"><br>
</font></font><div style="font-family:arial;font-size:small">Timur,</div><div style="font-family:arial;font-size:small">QA Engineer</div><div style="font-family:arial;font-size:small">OpenStack Projects</div><div style="font-family:arial;font-size:small">
Mirantis Inc<br><br><a href="http://www.openstacksv.com/" target="_blank"><img alt="http://www.openstacksv.com/" src="https://lh5.googleusercontent.com/K-Qw1IhwB4AYMQsUee1RCmlztMg_obyJiBLCO4mXru_NT157r0w1YNfoe-IrLLoBJrMK6lEZ3wn0TemAYv9lEznw-a6ueWi6MNh72huHrB0qJKFqZ6z53bZn_ipCsu4tRw"></a><br>
</div></div>
</div>
</div></div></blockquote></div></div></div><div><div><br><br clear="all"><br>-- <br><div dir="ltr"><font color="#888888"><font color="#888888"><br></font></font><div style="font-family:arial;font-size:small">Timur,</div>
<div style="font-family:arial;font-size:small">
QA Engineer</div><div style="font-family:arial;font-size:small">OpenStack Projects</div><div style="font-family:arial;font-size:small">Mirantis Inc<br><br><a href="http://www.openstacksv.com/" target="_blank"><img alt="http://www.openstacksv.com/" src="https://lh5.googleusercontent.com/K-Qw1IhwB4AYMQsUee1RCmlztMg_obyJiBLCO4mXru_NT157r0w1YNfoe-IrLLoBJrMK6lEZ3wn0TemAYv9lEznw-a6ueWi6MNh72huHrB0qJKFqZ6z53bZn_ipCsu4tRw"></a><br>
</div></div>
</div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><font color="#888888"><font color="#888888"><br></font></font><div style="font-family:arial;font-size:small">Timur,</div><div style="font-family:arial;font-size:small">
QA Engineer</div><div style="font-family:arial;font-size:small">OpenStack Projects</div><div style="font-family:arial;font-size:small">Mirantis Inc<br><br><a href="http://www.openstacksv.com/" target="_blank"><img alt="http://www.openstacksv.com/" src="https://lh5.googleusercontent.com/K-Qw1IhwB4AYMQsUee1RCmlztMg_obyJiBLCO4mXru_NT157r0w1YNfoe-IrLLoBJrMK6lEZ3wn0TemAYv9lEznw-a6ueWi6MNh72huHrB0qJKFqZ6z53bZn_ipCsu4tRw"></a><br>
</div></div>
</div>
</div></div><br></div></div><div class="">_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Mike Scherbakov<br>#mihgen<br><br></div>
</div>