if we want to build iso with custom packages, we have to add flexibility
to our dependencies lists.
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.
I do not see issues in flexible deps while we are managing our
It is not enough, you need to review requirements in the code of nailgun,
ostf and astute.
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
When I started the build of ISO from master branch, I can see the following
errors:
https://bugs.launchpad.net/fuel/+bug/1361279
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
Commit with fast fix was submitted: https://review.openstack.org/#/c/116667/
Need review :)
I will try to build image with this commit and will send my comments with
my results.
On Mon, Aug 25, 2014 at 7:55 PM, Timur Nurlygayanov
tnurlygaya...@mirantis.com wrote:
When I started the build of
