gulp: remote branch not found (gulpjs/gulp#4ed9a4a3275559c73a396eff7e1fde3824951ebb)

[pablorsk]

Description

Gulp package is broken

        "gulp": "gulpjs/gulp#4ed9a4a3275559c73a396eff7e1fde3824951ebb",

Error Message & Stack Trace

npm WARN deprecated [email protected]: Use uuid module instead
npm ERR! code 128
npm ERR! Command failed: /usr/bin/git clone --depth=1 -q -b 1681/head git://github.com/gulpjs/gulp.git /home/rsk/.npm/_cacache/tmp/git-clone-33c0fdff
npm ERR! warning: templates not found /tmp/pacote-git-template-tmp/git-clone-efa14a5b
npm ERR! warning: Could not find remote branch 1681/head to clone.
npm ERR! fatal: Remote branch 1681/head not found in upstream origin
npm ERR! 

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/xxx/.npm/_logs/2017-05-31T13_45_36_763Z-debug.log
Initialized empty Git repository in /home/xxx/desarrollo/fgulp/.git/

Config

{
  "generator-fountain-angular1": {
    "version": "1.0.0",
    "props": {
      "framework": "angular1",
      "modules": "webpack",
      "js": "typescript",
      "ci": "",
      "css": "scss",
      "resolved": "/usr/lib/node_modules/generator-fountain-webapp/node_modules/generator-fountain-angular1/generators/app/index.js",
      "namespace": "fountain-angular1:app",
      "_": [],
      "sample": "todoMVC",
      "router": "uirouter"
    }
  }
}```

[pablorsk]

Temporal solution: replace, on package.json, this:

"gulp": "gulpjs/gulp#4ed9a4a3275559c73a396eff7e1fde3824951ebb",

for this:

"gulp": "gulpjs/gulp#3f5aba28718dc19e4bf600fb88f128158ff2ff83",

(Edit) Better solution:

npm install --save-dev gulpjs/gulp#4.0

[sintaa]

Is there any specific reason for mentioning gulp and gulp-hub package versions in the below format:
"gulp": "gulpjs/gulp#4ed9a4a3275559c73a396eff7e1fde3824951ebb",
"gulp-hub": "frankwallis/gulp-hub#d461b9c700df9010d0a8694e4af1fb96d9f38bf4",

All other dependency versions are in caret pattern, like ^1.2.0, Can I use caret range pattern for gulp and gulp-hub packages in my angular 1 project which is generated using fountain.js

[Protectator]

Just encountered the same problem. @pablorsk workaround works, but the solution also references a version by a commit hash. I think it's still a bad idea and is just as prone to break again as it was before. Why not use a labelled version ?

[chaosfinity]

This is being broken by npm v5. Falling back to npm v3 the hash still works as expected

[pablorsk]

@Protectator is not released yet on https://www.npmjs.com/package/gulp

But, this can be fixed running:

npm install --save-dev gulpjs/gulp#4.0