Sensio mudou o nome de sua organização GitHub para ‘SensioLabs’. Isso significa que todos os URIs e locais do git foram alterados.
Observe a diferença nessas duas respostas GET?
root@me:~# wget https://api.github.com/repos/sensio/SensioDistributionBundle/zipball/v2.1.8
--2013-06-10 11:17:37-- https://api.github.com/repos/sensio/SensioDistributionBundle/zipball/v2.1.8
Resolving api.github.com... 204.232.175.74
Connecting to api.github.com|204.232.175.74|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-06-10 11:17:37 ERROR 404: Not Found.
root@me:~# wget https://api.github.com/repos/sensiolabs/SensioDistributionBundle/zipball/v2.1.8
--2013-06-10 11:17:50-- https://api.github.com/repos/sensiolabs/SensioDistributionBundle/zipball/v2.1.8
Resolving api.github.com... 204.232.175.74
Connecting to api.github.com|204.232.175.74|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/sensiolabs/SensioDistributionBundle/legacy.zip/v2.1.8 [following]
--2013-06-10 11:17:50-- https://codeload.github.com/sensiolabs/SensioDistributionBundle/legacy.zip/v2.1.8
Resolving codeload.github.com... 204.232.175.86
Connecting to codeload.github.com|204.232.175.86|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/zip]
Saving to: `v2.1.8'A correção é editar (manualmente) o arquivo composer.lock do seu aplicativo e corrigir os URIs corrompidos. Você pode testar isso removendo o pacote que está testando do diretório de fornecedores e do cache do compositor:
rm -rf vendor/sensiolabs/SensioDistributionBundle/
rm -rf ~/.composer/cache/repo/https---packagist.org/provider-sensio*Agora, quando você executar composer install, o composer irá buscar o pacote do GitHub usando seu arquivo de configuração composer.lock e não copiará aquele que você armazenou em cache.