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 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. So, if we want to build iso with custom packages, we have to add flexibility to our dependencies lists. Any objections? On Mon, Aug 25, 2014 at 8:28 PM, Timur Nurlygayanov < tnurlygaya...@mirantis.com> wrote: > 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 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 dependencies before this. >> >> Thank you. >> >> >> On Mon, Aug 25, 2014 at 6:21 PM, Timur Nurlygayanov < >> tnurlygaya...@mirantis.com> wrote: >> >>> Hi team, >>> >>> 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: >>> >>> http://jenkins-product.srt.mirantis.net:8080/view/custom_iso/job/custom_master_iso/77/console >>> >>> Looks like we have hardcoded versions of all required packages in specs: >>> >>> https://github.com/stackforge/fuel-main/blob/master/packages/rpm/specs/nailgun.spec#L17-L44 >>> >>> 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. >>> Looks like it is common issue for several components. >>> >>> Could we discuss how we can organize specs to avoid problems with >>> dependencies? >>> >>> >>> Thank you! >>> >>> >>> -- >>> >>> Timur, >>> QA Engineer >>> OpenStack Projects >>> Mirantis Inc >>> >>> [image: http://www.openstacksv.com/] <http://www.openstacksv.com/> >>> >> >> >> >> -- >> >> Timur, >> QA Engineer >> OpenStack Projects >> Mirantis Inc >> >> [image: http://www.openstacksv.com/] <http://www.openstacksv.com/> >> > > > > -- > > Timur, > QA Engineer > OpenStack Projects > Mirantis Inc > > [image: http://www.openstacksv.com/] <http://www.openstacksv.com/> > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev