I think I got git

I've played around with git for a bit. Instead of using /etc, I used a directory in my user account that had a mixed collection of binary and text files.

First, I setup the git environment:

$ git config --global user.name "Rahi Parsi"
$ git config --global user.email rparsi@learn.senecac.on.ca

Then using the mockresults directory:
$ git init
$ git commit

This is where I first got a little confused. Git displays a text document using vi (or "less", not really sure). I couldn't figure out what to do at first. After some frustration, figured out that I can enter some remarks and just save.

Next I created some text files, created some zip files using the rpm's, and added to git:
$ git add stuff.zip notes.txt
$ git commit

Created a test branch:
$ git branch test
$ git checkout test

Made some changes:
$ rm root.log state.log
$ git commit -a
$ git checkout master

I made more changes by creating directories and adding files. The "vi" like popup screen that shows up after "$ git commit" takes some getting used to. It just feels odd, as I've never used a RCS that behaved like that.

Cleanup:
$ git branch -d experimental

Overall, I like git. It's not that hard to figure out and is quite versatile. Only negative I can say about it, is the "vi" popups for comments. Maybe I'm asking for too much, but I think there's a better approach somewhere.

Signing RPM packages - Done! | Creating a YUM repository - Done!

I created my yum repository on the Ireland system, and then proceeded to have a hell of a time with the gpg key generation. It so long to generate the key, thought it had frozen a few times.

I also tested distcc using the autoconf source package.

My repository is in /var/www/html/rparsi, so the URL would be http://142.204.133.26/rparsi/

It contains all RPM packages, the repo file and the public RSA key.

There's an RPM named "rahiskey" which installs the key and the repository on the system.

Distcc - shaves off 7 minutes

After trying to get gcc to build, have switched to the autoconf package.

Without distcc, it takes approximately 12 minutes to build. With distcc (Scotland as the server) the output is:

real 12m15.636s
user 7m7.141s
sys 5m16.847s

So essentially not much of a difference. I'm a bit surprised, as I expected the overhead of distcc to increase the build time.

Gcc, would you please build -- Thanks

Update regarding build of gcc package:

1. Still haven't solved the build problem. I get the same error message on Scotland, Australia and Ireland, so that rules out a Fedora version issue.

2. Testing with mock produces mixed results. "mock" completes the source and binary build in 121 minutes and 10 seconds. Running rpmlint on the resulting binary packages shows one error regarding glibc-devel.

3. Inspection of the build.log file shows a lot of "Error 1" and "Error 2" entries, which don't seem to be stopping the build.

At this point I'm not sure how to proceed.