Tag Release

[exptom]

Could you tag a release? We are having quite a few problems with checking out the repo from github via composer. (Get intermittent requests to login to github and failed checkouts).

[juriansluiman]

I tagged v0.1.0 for you. Currently I am upgrading all my modules one by one and haven't thought SlmException is already used by others.

Are you using the exception markers? It is good to know you're using it, so I can focus to keep BC towards v0.2 and perhaps ping you even to test the new release when it's done :)

[exptom]

Thanks for that, for some reason though packagist has not picked up the tag: https://packagist.org/packages/slm/exception

We have been using the module for close to a year I think across many projects. Would be happy to test future releases.

[juriansluiman]

👍 Weird since I had a Packagist hook, updated manually and Packagist shows the correct version now.

[exptom]

Hmm - I'm still getting problems with this repo and composer:

     [exec]   - Installing slm/exception (v0.1.0)
     [exec]     Downloading: connection...Failed to download slm/exception from dist: The "https://api.github.com/repos/juriansluiman/SlmErrorExceptions/zipball/408e6d87496ce71248c9f7d46703f02fa798bee8" file could not be downloaded (HTTP/1.1 404 Not Found)
     [exec] Now trying to download from source
     [exec]   - Installing slm/exception (v0.1.0)
     [exec]     Cloning 408e6d87496ce71248c9f7d46703f02fa798bee8

     [exec]   [RuntimeException]                                                                                                                                    
     [exec]   Failed to execute git clone --no-checkout 'git@github.com:juriansluiman/SlmErrorExceptions.git' '/home/jenkins/workspace/zf2-Users/vendor/slm/exception' && cd '/home/jenkins/workspace/zf2-Users/vendor/slm/exception' && git remote add composer 'git@github.com:juriansluiman/SlmErrorExceptions.git' && git fetch composer  

A month or so ago we went through a period when we couldn't check the repo out without signing into github as it thought it was marked as private?! This seemed to resolve itself.

I notice that the github clone url is: git@github.com:juriansluiman/SlmException.git not SlmErrorExceptions.git that composer seems to be trying to use. Did you rename the repo at some point?

[juriansluiman]

@exptom I now see that composer tries to download from SlmErrorExceptions. The repo has been renamed a while back to SlmException. I think that's where the root cause of the problem is. The web interface of Github performs a redirect from SlmErrorExceptions to SlmException, but apparently the API with downloads does not recognize this.

I asked packagist to update the canonical resource: https://twitter.com/juriansluiman/status/499889506196402176

You might be able to "overwrite" this by adding the SlmException as repository to your root composer.json:

{
    "repositories": [
        {
            "type": "vcs",
            "url": "git@github.com:juriansluiman/SlmException.git"
        },
    ],
    "require": {
        "slm/exception": "~0.1"
    }
}

[exptom]

If you log into packagist, browse to the package and click the "Edit" button it lets you update the repo URL, which may fix the issue.

[juriansluiman]

👍 I have never seen the edit feature of Packagist. Updated the package, does it work now?

[exptom]

It is currently still trying to use the old URL. You may need to press the 'Force Update' button?

[juriansluiman]

@exptom have done that already, don't know what's going on. Perhaps a caching issue on Packagist's side?

[exptom]

Sounds like a caching problem - will wait and see what the reply to your tweet says.

[exptom]

I think there is a composer bug - posted report here: composer/composer#3214