Control: severity -1 normal On 2017, ഡിസംബർ 21 3:28:29 PM IST, Ben Finney <bign...@debian.org> wrote: >Package: node-gulp-babel >Version: 7.0.0-2 >Severity: serious >Justification: Policy 3.5 > >Attempting to run a Gulp build that uses ‘gulp-babel’ fails >immediately: > >===== > module.js:327 > throw err; > ^ > > Error: Cannot find module 'babel-core' > at Function.Module._resolveFilename (module.js:325:15) > at Function.Module._load (module.js:276:25) > at Module.require (module.js:353:17) > at require (internal/module.js:12:17) > at Object.<anonymous> (/usr/lib/nodejs/gulp-babel/index.js:7:15) > at Module._compile (module.js:409:26) > at Object.Module._extensions..js (module.js:416:10) > at Module.load (module.js:343:32) > at Function.Module._load (module.js:300:12) > at Module.require (module.js:353:17) >===== > >The dependency ‘babel-core’ needs to be packaged in Debian, and then >this package can declare a Depends relationship on that one. > >
Upstream does not declare a dependency on babel-core and I think it is reasonable as babel-core may not be enough (at the minimum it may need some babel presets or plugins) to get the build working and the dependency should be declared by packages depending on node-gulp-babel. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
