• From: Brighton, UK
  • Registered: 2007-06-21
  • Posts: 3,079

Topic: howto: update a plugin without horribly confusing svn?

Every time i update a plugin i get into a right old mess with subversion:  i usually end up deleting the new plugin, updating back to the old one (from svn), then doing an svn delete of that plugin, then commit, then install the new one, then commit again.  Kind of horrible.

I feel like there's a nice way to do this within svn but i can't work out the protocol.  Can anyone help?

thanks, max

###########################################
#If i've helped you then please recommend me at Working With Rails:
#http://www.workingwithrails.com/person/ … i-williams
  • Registered: 2008-07-25
  • Posts: 38

Re: howto: update a plugin without horribly confusing svn?

hey max,

any news on that?

i just came along the same problem:

i installed attachment fu, which created folders and files which are not under version control.
when i try to commit using netbeans it tells me:

'/home/richard/NetBeansProjects/gidl/vendor/plugins/attachment_fu' is not a working copy
Can't open file '/home/richard/NetBeansProjects/gidl/vendor/plugins/attachment_fu/.svn/entries': No such file or directory

so i can't commit anymore...

  • From: Brighton, UK
  • Registered: 2007-06-21
  • Posts: 3,079

Re: howto: update a plugin without horribly confusing svn?

fusilaeh wrote:

hey max,

any news on that?

i just came along the same problem:

i installed attachment fu, which created folders and files which are not under version control.
when i try to commit using netbeans it tells me:

'/home/richard/NetBeansProjects/gidl/vendor/plugins/attachment_fu' is not a working copy
Can't open file '/home/richard/NetBeansProjects/gidl/vendor/plugins/attachment_fu/.svn/entries': No such file or directory

so i can't commit anymore...

Basically - no.

Where you adding attachment_fu for the first time?  If so you should just need to do an svn add.  If you were replacing it, then you might have to go back to the old 'script':

- delete it
- do an svn update to get the repos version back
- svn delete that version
- commit the change
- install latest version
- svn add it
- commit the change

Sometimes it gets confused - there's an svn folder in every folder under source control which hass files keeping track of what's in there (or what it thinks is in there).  I've got in a mess before copying something from one place to another, forgetting it had an svn folder inside.  I'm not an expert on svn by any means, i'd love to know a cleaner way to update plugins.

###########################################
#If i've helped you then please recommend me at Working With Rails:
#http://www.workingwithrails.com/person/ … i-williams
  • Registered: 2008-07-25
  • Posts: 38

Re: howto: update a plugin without horribly confusing svn?

tnx!
actually it was worse... the repo lacked the dir in question, too (it wasn versioned because svn had no permission to write to the dir)... so i had to delete the repo, import my working copy (which was ok) and then checkout again. regard, fusi