composer update error

I've got the same error. Unfortunately this happens a lot, as Taylor is working on 5. From what I've seen we can compare our installations to https://github.com/laravel/laravel (the newest of course). And make the same changes.

I've got the same error.

L5 is a work in progress and not even beta yet... until it is ready the forums is flooded by similar questions. Hang in there. :)

Same error here after updating from 3e37cd1 to 2725ec3

Before you do a composer update of the framework, make sure you manually do the changes to your app that Taylor made to the app itself (not the framework) and keep track of your changes (write down the commit ID up until your update).

You can view all commits to the app here: https://github.com/laravel/laravel/compare/develop

And if you want to add an package to your composer.json without updating the whole framework. just run composer require vendor/package and enter the version you want to get. This will pull in the package but not update the framework. Or lock the framework on a certain commit "laravel/framework": "~5.0#commitId".

If you work on your project daily, start in the morning with updating your app structure to the new laravel structure, with all new files, next run composer update. (the morning works well if you live in Europe (Taylor is often asleep at that time :P), otherwise pick a moment when Taylor won't commit changes to the framework or app.

Hey @MThomas,

thanks a lot for your great response! How to update the main directory which is the laravel/laravel package? Is it possible via git merging or do I have to it manually? Any hints?

@bart I do it manually.

I'll write down the commit of my fresh laravel install (and the first time I forgot to do that, so I had to track down the latest changes to my install), and from that moment onward I check regularly the commit history and change my copy of laravel manually. After that I write down the commit ID up to the latest change updated by me.

Sometimes this takes a bit of time, but if you do it regularly you get the hang of it :)

One piece of advise, since L5 namespaces everything, you sometimes have to update the default App namespace to your desired namespace.

I think I will try a different way. Creating a new laravel app directory using git clone and copying new project related files inside should do the trick! What do you think?

I'm really looking forward the stable release of L5! :)

@bart, that will work fine, but be careful, depending on the commit you were working on, Controlers are once again extended by an Illuminate Controller and console commands have a different namespace for example.

So check the example controller/commands/models once you do this, this will help you in solving a lot of the error you will get.

Still, Taylor will keep updating for the coming weeks/months, so you will have to update the files one time or an other. Keep track of the changes, if you stick to a certain commit for to long you will miss out on new and fun stuff (like the recent changes in middleware, routes and events).

Yep, tried it out and worked for me. Last but not least it was still some work I had to do. I'm currently trying to automate it a little by referencing laravel/laravel as remote branch so that I can pull all changes from there.

Informed me that this was not the laravel error , but because of low memory.

I increased the memory from my server and is now functioning normally.

You can still do the following:

mkdir project-name
cd project-name
git clone --single-branch --branch=develop -o laravel --depth=1 git@github.com:laravel/laravel.git .

then

git branch -m laravel-dev
git branch master
git branch develop

then

git checkout master
composer install

You have a branch laravel-dev from where you pull updates that will come from github laravel/laravel (branch develop). You work on the branch develop where you trigger when you need git merge laravel-dev, and you manage conflicts, so your develop branch is always up to date with L5 development (laravel/laravel). When you are done with a feature, you git checkout master to the master branch where you git merge develop.

You can then smoothly git push to your remote server (test or production).

This is not a best practice, only a way to do to enjoy the use of the upcoming (fabulous) L5.

When Taylor and others do commits on laravel/laravel, check github, git checkout laravel-dev then git pull to grab the last commits.

Then merge to your develop branch by performing git checkout develop and git merge laravel-dev. You will mostly have conflicts to deal with. Don't forger to do a composer update too.

Finaly do a git checkout master and git merge develop. You are now ready to push to production.

[Important] If you used the composer app:name command don't forget to check namespaces within new updated files because Taylor and others are working with the namespace app\.... So you can have to replace app\... by YourNameSpace\... to get your Laravel install working without crapy errors.

@jrean thats what I'm doing since yesterday, too because there are so many changes in the branch currently and always merging it manually sucks. So this is is good and automated possibility having the most current version of laravel/laravel.

@jrean, if I already have a repo and want to do this... How do I pull the laravel/laravel develop branch or a local branch called laravel-dev?

Sorry, I'm a total beginner when it comes to Git... The more I search a topic, the more confused I become on it. lol I only know how to do the basics of clone, stage, commit, push, and occasionally merge. :-/

@devon

Please BACKUP your entire project/files before performing the following commands.
Better, make a copy and test before doing it on your real project.
Beware, as you already started your repo, when you will pull the develop branch from the laravel repo you will download all commits. It's why I use --depth=1 in my initial comment.

Create a new branch laravel-dev or whatever you want to call that branch.

git branch laravel-dev

Add the remote laravel and call it as you want. Here I use laravel.

git remote add laravel git@github.com:laravel/laravel.git

Checkout your new branch laravel-dev.

git checkout laravel-dev

Pull from laravel/laravel develop branch.

git pull laravel develop

Accept the merge. Your done.

Checkout to your master branch or whatever you named your master branch (or your develop branch as I describe in my initial comment) and merge.

git checkout master
git merge laravel-dev

Manage conflicts and accept the merge. Your done!

Next time Taylor and others commit.

git checkout laravel-dev
git pull
git checkout master
git merge laravel-dev

Manage conflicts and accept the merge. Your done!

I just got this today, on Laravel 5, when updating from 5.something to 5.something else. oddly, I have two different laravel projects, one of them updated fine, one did not. Is there an easier fix?