# What's the proper way to update an extension?

**URL:** <https://www.ruby-forum.com/t/whats-the-proper-way-to-update-an-extension/140011>\
**Category:** Radiant CMS\
**Created:** [June 10, 2008, 2:55am UTC](https://www.ruby-forum.com/t/whats-the-proper-way-to-update-an-extension/140011 "2008-06-10T02:55:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [June 10, 2008, 2:55am UTC](https://www.ruby-forum.com/t/whats-the-proper-way-to-update-an-extension/140011/1 "2008-06-10T02:55:30Z")

</div>

I know the Accents project is underway, but for now, how do I update my  
extensions?

For example, I need to update Gallery from 0.7.12 to 0.7.10. I tried  
‘git clone […]’ into my ‘vendor/extensions’ directory, but I get an  
error saying that the “destination directory already exists”.

I’m sure its simple, but I’m still a newbie.

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [June 10, 2008, 3:02am UTC](https://www.ruby-forum.com/t/whats-the-proper-way-to-update-an-extension/140011/2 "2008-06-10T03:02:20Z")

</div>

Did you type that correctly?

You’re going from 0.7.12 to 0.7.10? (I’m not a user of this extension)

if you’ve already cloned the git repository for the extension, cd into  
that directory:

cd vendor/extensions/gallery

and do ‘git pull’

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [June 10, 2008, 5:02am UTC](https://www.ruby-forum.com/t/whats-the-proper-way-to-update-an-extension/140011/3 "2008-06-10T05:02:14Z")

</div>

Jim G. wrote:

> Did you type that correctly? You’re going from 0.7.12 to 0.7.10? (I’m not a user of this extension)

Haha, you are correct, I accidentally swapped the version numbers.

> if you’ve already cloned the git repository for the extension, cd into  
> that directory:
> 
> cd vendor/extensions/gallery
> 
> and do ‘git pull’

Tried this, and got “You asked me to pull without telling me which  
branch you want to merge with”. Do I have to edit some settings, or  
should this be automatic?

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [June 10, 2008, 6:32am UTC](https://www.ruby-forum.com/t/whats-the-proper-way-to-update-an-extension/140011/4 "2008-06-10T06:32:55Z")

</div>

Ben,

If you did a plain clone originally, run `git pull origin master`.

Sean

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [June 10, 2008, 6:42pm UTC](https://www.ruby-forum.com/t/whats-the-proper-way-to-update-an-extension/140011/5 "2008-06-10T18:42:01Z")

</div>

Sean C. wrote:

> If you did a plain clone originally, run `git pull origin master`.

Tried this and I got a list of all the files followed by “: needs  
update”. Then the final output line was “fatal: Entry ‘README’ not  
uptodate. Cannot merge.”.

Checking my Extensions page in the admin UI, it seems Gallery is still  
at 0.7.10.

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [June 10, 2008, 12:15pm UTC](https://www.ruby-forum.com/t/whats-the-proper-way-to-update-an-extension/140011/6 "2008-06-10T12:15:39Z")

</div>

In terms of pulling down repos and updating a cloned repo, git is more  
trouble than its worth. Tolerable nonetheless.

Sean C. wrote:

> Ben,
> 
> If you did a plain clone originally, run `git pull origin master`.
> 
> Sean