Fix #168 Vimbadmin installation issue due to composer.json over secure http

[iam404]

Fixed.

For reference: #168

Command Error: Loading composer repositories with package information
Installing dependencies                                          
  - Installing zendframework/zendframework1 (dev-master fccf5d2)
    Downloading: 100%         

  - Installing opensolutions/oss-framework (dev-master 53dc6d8)
    Downloading: 100%         

  - Installing opensolutions/minify (1.0.0)
    Downloading: 100%         

  - Installing symfony/polyfill-mbstring (dev-master 1289d16)
    Downloading: 100%         

  - Installing symfony/console (2.8.x-dev c25e035)
    Downloading: 100%         

  - Installing doctrine/lexer (dev-master 83893c5)
    Downloading: 100%         

  - Installing doctrine/annotations (dev-master 07a9af2)
    Downloading: 100%         

  - Installing doctrine/collections (dev-master 866e100)
    Downloading: 100%         

  - Installing doctrine/cache (dev-master e0ef9e9)
    Downloading: 100%         

  - Installing doctrine/inflector (dev-master 90b2128)
    Downloading: 100%         

  - Installing doctrine/common (dev-master 773c56e)
    Downloading: 100%         

  - Installing doctrine/dbal (dev-master 61e1f86)
    Downloading: 100%         

  - Installing doctrine/orm (2.4.x-dev ea713a0)
    Downloading: 100%         

  - Installing smarty/smarty (dev-master d88168d)
    Downloading: 100%         

  - Installing komola/bootstrap-zend-framework (dev-master f81b60c)
    Downloading: 100%         

Writing lock file
Generating autoload files

[PhrozenByte]

The explicit repository definition is a temporary fix (see d91b97f, committed by @barryo) for Smarty 3.8.17 hosted on Google Code. It makes absolutely no sense to let the repository point to GitHub when Packagist does this already. Simply remove the repository and use ~3.1.18 (or ^3.1.18, don't know whether Smarty follows semantic versioning) as version constraint.

[elanfer]

I got the same problem like @iam404. His fixed worked it out. @PhrozenByte please excuse my qustion I am not familiar with Packagist. But isn't it similar whether the source points on github or on googlecode? Or do you mean that there shall be no source to any of this providers and composer is getting it from packagist?

[PhrozenByte]

Yes, composer gets the download URLs from Packagist, so there shouldn't be a source in the composer.json at all.

[barryo]

@PhrozenByte is correct - the hard coded reference was added two years ago to get around a Smarty issue. Back when Smarty was unavailable on GitHub or Packagist.

ViMbAdmin seems to work fine with ~3.1 now.