Closed (fixed)
Project:
Drush
Component:
PM (dl, en, up ...)
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
21 Dec 2010 at 20:17 UTC
Updated:
18 Jan 2011 at 09:30 UTC
Jump to comment: Most recent file
$ drush dl pathauto --version-control=bzr --bzrsync --bzrcommit
gives:
Project pathauto (7.x-1.0-alpha2) downloaded to [success]
/home/USER/web/drupal-7/sites/example.com/modules/pathauto.
Problems were encountered committing your changes to Bazaar. [error]
The specific errors are below:
Committing to: /home/USER/web/drupal-7/sites/example.com/
aborting commit write group: PathsNotVersionedError(Path(s) are not
versioned: modules/pathauto)
bzr: ERROR: Path(s) are not versioned: modules/pathauto
Further details: /home/USER/web/drupal-7/sites/example.com/ is a symbolic link pointing at: /home/USER/web/example
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | drush-1004562_02.patch | 967 bytes | kdebaas |
| #6 | drush-1004562.patch | 2.83 KB | kdebaas |
Comments
Comment #1
moshe weitzman commentedI can't reproduce this with a simple setup. Could you paste the whole output using --debug?
Comment #2
kdebaas commentedComment #3
moshe weitzman commentedBzr is not a package handler
Comment #4
kdebaas commentedTrue. Woops! Correct debug output below:
Comment #5
kdebaas commenteddrush dl --version-control=bzr --bzrsync --bzrcommit --debug advanced_helpworks well when performed in Drupal root. The module is downloaded to sites/all.The problem is that my web/drupal-7/sites/postpolitikak.org dir is a symlink pointing at web/politikak.org, which is itself a bzr branch. So in the following lines 76 - 94 in bzr.inc, $root[0] is never equal to $project['full_project_path'] on line 84:
Since Bazaar is recursive anyway, can't we skip the foreach, and do a Bazaar add on the $project['full_project_path']?
Comment #6
kdebaas commentedIn the attached patch, a bzr add is performed on the $project['full_project_path'], leaving it up to bzr to figure out the bzr root. Since add is recursive, there is no need to iterate over the
bzr status --shortoutput. I leftbzr status --shortin, to be able to collect error messages.I removed the foreach loop that 'bzr removes' deleted files, since they are implicitly removed on 'bzr commit'. As I type this, though, I realize that one may want to do a bzrsync without doing a bzr commit. I can't think of a scenario yet in which one would want to have the deleted files of a drush pm-update explicitly removed from version control before bzr commit removes them, so I don't know what the consequences of this could be.
Comment #7
kdebaas commentedThe new patch is more modest: $path is not compared to $project['full_project_path'] anymore, and the option --no-recurse is added to bzr add, so that directories and files aren't added recursively anymore, but one by one. Better?
Comment #8
moshe weitzman commentedLooks pretty simple and proper to me. Maybe jonhattan has some feedback. Anyone else?
Comment #9
jonhattanI did commit #7.