[wp-hackers] Plugin Upgrade Failing when using Subversion
mikeschinkel at newclarity.net
Fri Jan 16 01:56:19 GMT 2009
>> Empty your repository at svn.wp-plugins.org
I totally don't follow you. Are you assuming I'm using svn.wp-plugins.org? I'm not.
And why would I need to go to that trouble when I'm looking at an admin console that says "Upgrade me!"? My use of Subversion is orthogonal to upgrading at the admin console.
That said, the admin console really needs a "Pin the Plugin to this Version and do not ask about upgrading?" It would also be good if upgrades could be presented as bug-fix-only upgrades vs. feature upgrades. These are things I might tackle.
----- Original Message -----
From: "Mário Gamito" <gamito at gmail.com>
To: wp-hackers at lists.automattic.com
Sent: Thursday, January 15, 2009 7:45:49 PM GMT -05:00 US/Canada Eastern
Subject: Re: [wp-hackers] Plugin Upgrade Failing when using Subversion
Mike Schinkel wrote:
> Hi All:
> I've just run into a problem with plugin upgrades failing when using Subversion for version control. Subversion stores a collection of readme files and when the upgrade process tries to delete them it fails to and then fails the upgrade process. Am I the first person on this list to experience this? It fails in a very ungraceful way, i.e. basically it just says "Sorry, sux to be you." ;-)
> Potential solutions:
> 1.) Bypass deleting any .svn directory(s) and in that case don't require the plugin directory to be deleted in order to continue the upgrade process.
> 2.) Remove the read-only attribute and delete the files.
> 3.) Something else?
Sorry if I'm missing something here.
But why don't you just go the *real* SVN way ?
Empty your repository at svn.wp-plugins.org
Then create it again and do a whole commit from your computer.
If I'm not missing something here, that's just about it.
:wq! Mário Gamito
Key Fingerprint: 0x04DA9BC9
wp-hackers mailing list
wp-hackers at lists.automattic.com
More information about the wp-hackers