Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating a single package doesn't work #782

Closed
kostiklv opened this issue Jun 9, 2012 · 11 comments

Comments

@kostiklv
Copy link
Contributor

commented Jun 9, 2012

Running composer.phar update vendor/package actually updates all the packages, not just the selected one.

@Seldaek

This comment has been minimized.

Copy link
Member

commented Jun 14, 2012

I think the problem is that it keeps the installed packages locked at their version, and if your installed packages don't match the lock file, then you update and it dumps what you had installed in the lock file, instead of following the lockfile + updating the required package. This may not be the only problem, but it's something I have noticed.

@Seldaek Seldaek closed this in 5c30fcb Jul 1, 2012
@Seldaek

This comment has been minimized.

Copy link
Member

commented Jul 1, 2012

Alright this should now work better. Please let us know if you spot a weird behavior again.

@kostiklv

This comment has been minimized.

Copy link
Contributor Author

commented Jul 1, 2012

Thanks, I'll test it and let you know. We are using it a lot to update our
own packages w/o touching third party deps, especially dev-master ones.

Konstantin Tjuterev

digitalkaoz pushed a commit to digitalkaoz/composer that referenced this issue Jul 1, 2012
digitalkaoz pushed a commit to digitalkaoz/composer that referenced this issue Nov 22, 2013
digitalkaoz pushed a commit to digitalkaoz/composer that referenced this issue Nov 22, 2013
@benschoch

This comment has been minimized.

Copy link

commented Nov 30, 2015

Is there any progress on this issue? It still doesn't seem to work, neither with composer.lock in place nor without it.

@stof

This comment has been minimized.

Copy link
Contributor

commented Nov 30, 2015

@gstoert if you have an issue, open a new issue instead of commenting on an issue closed 3 years ago. Your issue is likely to be a different one

@luis02lopez

This comment has been minimized.

Copy link

commented Jun 13, 2017

+1 still have the same problem. It update every package. This issue is in current topic.

@Jafo232

This comment has been minimized.

Copy link

commented Jul 7, 2017

I can confirm this issue is still happening.

@smalec79

This comment has been minimized.

Copy link

commented May 18, 2018

And still doesn't do it right

@smalec79

This comment has been minimized.

Copy link

commented May 18, 2018

with
Composer version 1.6.5 2018-05-04 11:44:59

@stof

This comment has been minimized.

Copy link
Contributor

commented May 18, 2018

my comment from November 2015 still holds true. If you have an issue, please open a new ticket, with details about what you expect and what happens instead, instead of telling us that you face the same bug than here, whole this one was fixed in 2012 (and so your issue is probably a different one)

@naneri

This comment has been minimized.

Copy link

commented Oct 9, 2019

Still have this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.