Submodule update error
A bug in 2.1.0, submitted by czheng on 24 July 2010
Announcement
Symphony's issue tracker has been moved to Github.
Issues are displayed here for reference only and cannot be created or edited.
Browse
Closed#366: Submodule update error
-
-
- czheng
- Comment #1
- 24 Jul 10, 3:04 am
-
-
- Alistair
- Comment #2
- 24 Jul 10, 7:05 pm
Eh, my bad. I was accidentally tracking a non-existent branch of the Export Ensemble extension.
Fixed http://github.com/symphonycms/symphony-2/commit/22906a316259ec553e2b84e03b2af7f330f09cd2
-
-
- bzerangue
- Comment #3
- 07 Aug 10, 2:21 am
I was having the same problem, but I noticed that I was using the original location of the symphony-2 code (http://github.com/symphony/symphony-2) which I guess is now the wrong url. I guess http://github.com/symphonycms/symphony-2 is now the official link now. Since http://github.com/symphonycms/symphony-2 is forked from the old repository, can you push your changes in the new one to old repository? OR is there a way to redirect people from the symphony/symphony-2 repository to the forked and new symphonycms/symphony-2 repository.
-
-
- Alistair
- Comment #4
- 09 Aug 10, 12:06 pm
There isn’t a way to automatically redirect people, unfortunately. We are attempting to keep the old repo up to date for a couple of months to avoid confusion, but strongly suggest everyone update their git config, as mentioned in the readme.
This issue is closed.
Getting the following when trying to update submodules in clones of the 2.1 repo:
Have tried this from two separate servers on three separate installs.