Drush 5.x-1.1 correctly noticed and preserved .svn directories when running pm update modulename.

After upgrading to 1.3, the warning

Note: A backup of your package will be stored to backups directory if no .svn directory is found.

Actually takes place:

Backups were saved into the directory /sites/agaric_basic_5/www/backup/modules/20080520104209.

Meanwhile, there is no .svn directory in the updated module directory, and my version control system is angry at me.

benjamin, Agaric Design Collective

Comments

moshe weitzman’s picture

moshe weitzman commented

@grugnog2 - can you look into this?

owen barton’s picture

owen barton commented

Benjamin - there are a couple of issues here. The suppression of backups is now done by drush_pm_svn module - if this module is disabled then backups will be made as normal.

* We need to fix the documentation so that this is made clear (and you don't get the" ...if no .svn directory is found." message if the module is disabled).

* If you did have this module enabled then something is functioning incorrectly. Please let us know which package handler you are using.

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Fixed

I fixed these doc issues

moshe weitzman’s picture

moshe weitzman commented

I fixed those doc issues.

mlncn’s picture

mlncn commented
Status: Fixed » Closed (fixed)

Yes, I'm sure that was my problem. Sorry for not getting back sooner to confirm that I simply needed to enable the svn module after updating. However, when I did go to test and keep using Drush, instead of things working, I have different and far more frustrating problems.