Hide Forgot
Description of problem: $ npm outdated Package Current Wanted Latest Location copy-webpack-plugin 1.1.1 1.1.1 3.0.1 copy-webpack-plugin css-loader 0.23.1 0.23.1 0.25.0 css-loader eslint 2.13.1 2.13.1 3.6.0 eslint eslint-config-standard 5.3.5 5.3.5 6.0.1 eslint-config-standard eslint-plugin-promise 1.3.2 1.3.2 2.0.1 eslint-plugin-promise eslint-plugin-standard 1.3.3 1.3.3 2.0.0 eslint-plugin-standard file-loader 0.8.5 0.8.5 0.9.0 file-loader history 2.1.2 2.1.2 4.2.0 history react 0.14.8 0.14.8 15.3.2 react react-addons-update 0.14.8 0.14.8 15.3.2 react-addons-update react-dom 0.14.8 0.14.8 15.3.2 react-dom
ovirt-engine-nodejs-modules dependencies needs to be updated and depending projects like cockpit-ovirt verified.
ovirt-engine-nodejs-modules will use Yarn instead of npm to manage all dependencies, including: - downloading dependencies and generating LICENSES file during RPM build - locking down versions of all dependencies - detecting outdated dependencies and upgrading them to latest version (this must be done manually) The associated patch documents the process via README file.
OK, just realized this RFE is for cockpit-ovirt component. Please note that we're in the process of moving ovirt-engine-{nodejs,nodejs-modules} out of `releng-tools` repo and making changes to nodejs-modules package (use Yarn & rework the build script) so all consuming projects should be updated once the changes are done & std. CI makes new RPMs available.
(In reply to vszocs from comment #3) > OK, just realized this RFE is for cockpit-ovirt component. > > Please note that we're in the process of moving > ovirt-engine-{nodejs,nodejs-modules} out of `releng-tools` repo and making > changes to nodejs-modules package (use Yarn & rework the build script) so > all consuming projects should be updated once the changes are done & std. CI > makes new RPMs available. Before qa_ack, could you help to provide the steps or info about how to verify this RFE. or if you could help to verify, since QE not familiar with npm, yarn, and these dependencies? Thanks
(In reply to dguo from comment #4) > Before qa_ack, could you help to provide the steps or info about how to > verify this RFE. > or if you could help to verify, since QE not familiar with npm, yarn, and > these dependencies? Thanks Both ovirt-engine-nodejs & ovirt-engine-nodejs-modules projects now live in their dedicated git repos: https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-nodejs https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-nodejs-modules ovirt-engine-nodejs = Node.js platform binary, packaged as RPM, used to build oVirt JavaScript applications. Build time dependency. ovirt-engine-nodejs-modules = Single RPM containing all JavaScript modules needed to build all oVirt JavaScript applications. Build time dependency. The task here is to verify that cockpit-ovirt RPM can still be built with above mentioned projects, which implies that cockpit-ovirt uses Yarn instead of npm. cockpit-ovirt falls under Virt team so I'm assigning this BZ to Tomas.
According to comment above, this should be verified during build process, QE will do the sanity test after that. Thus, consider to change the QA contact as assignee. Tomas, your thought?
A couple of recent cockpit-ovirt releases were built ok. I can confirm, another dependent ovirt-web-ui package builds recently ok as well. I think this bug can be closed.
Thank you Marek, closing