Darrell
You found it. Deleting the config files was the answer. When I looked at the local config files they still had system@ in them, which is what causes the password problem.
Apparently if the config files already exist, they are not replaced by any later ones modified by the script "switch_all_submodules_to_head_and_clean". So even after I fixed the original problem the old scripts that still had system@ in them, kept me from being able to tell that I had fixed it.
Tomorrow, after the current download finishes, I plan on doing a bunch of testing to see if I can pin down the things that can go wrong and how to avoid them.
Thanks for your help everyone.
Keith
On Wed, Feb 29, 2012 at 7:03 PM, Darrell Anderson humanreadable@yahoo.com wrote:
The command line commands you suggested, started the download. When the first password message appeared and it stopped downloading--I Ctrl+C'd and stoped the download.
Then I edited the script "./scripts/switch_all_submodules_to_head_and_clean" and added what David suggested (i.e adding --recursive to several lines and removing --recursive from your startup script).
Then I ran the modified startup scrip you suggested.
This did NOT give me an error message and displayed "Already up-to-date." which I assume relates to what I had previously downloaded before I killed the command line startup you suggested.
Then it said:
Cloning into experimental... Password:
Hoping this was a onetime password I pressed enter. It ran for less than a minute and wanted another password.
Obviously what you and David suggested works--but the password problem did not go away.
Hmm. I never used a password until very recently when I was granted commit access. Up until then I always connected anonymously. I wonder whether entering a password just once has an effect that prevents anonymous connections.
If I recall correctly, when I first connected a few days after the GIT announcement in December, I manually created the local GIT directory (mkdir), did a cd to that directory and manually ran git clone --- without a script. Like this, but all manually:
mkdir -p /home/public/builds/slackware/trinity/zz_src_trinity_git cd /home/public/builds/slackware/trinity git clone --recursive http://scm.trinitydesktop.org/scm/git/tde zz_src_trinity_git
Notice I did a cd to the parent directory of $GIT_DIR (zz_src_trinity_git) before running the clone command.
Took a couple of hours. Thereafter I never again used git clone, instead using switch_all_submodules_to_head_and_clean, like this:
cd /home/public/builds/slackware/trinity/zz_src_trinity_git sh ./scripts/switch_all_submodules_to_head_and_clean anonymous
After a few times I automated the latter process into a script with a few bells and whistles.
I wonder whether manually deleting all of the "config" files would clean the local repository:
find $GIT_DIR -type f -name config -exec rm -f {} ;
Then perform a clone:
cd $GIT_DIR_ROOT git clone http://scm.trinitydesktop.org/scm/git/tde $GIT_DIR
I'm using GIT 1.7.1.
Now that I am using a password I wonder whether I can connect anonymously. I'll try that the next day or two when I rsync my local tree.
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting