dsegree

Release 0.3

dsegree — Fri, 13 Apr 2012 00:31:56 +0000

Before I begin, here is a link to my project wiki page:

For my final release of the KidsRuby package, I have made myself a checklist of things that I have completed and things that still need to be done. This will be good for the person who will be taking over my work.

Complete:

Grabbed both the KidsRuby and Rubywarrior package from their respected github page.
Created a spec file for both programs (listed below) and successfully packaged both programs.
Created desktop icon/file for KidsRuby.
Tested on Fedora 17 Alpha release. (KidsRuby needs Ruby 1.9 to run and only Fedora 17 has this package)
Successfully went through mock and koji.

Outstanding:

Must get GOSU Gem packaged up for Fedora 17 and incorporated into KidsRuby.
Probably touch up the spec files to make it 100% follow Fedora packaging guidelines.
Still receiving a few errors when running rpmlint on my Kidsruby RPM that needs to be fixed.

Below are the links to my spec files, SRPM’s, RPM’s and my project parent folder (All files are stored on my Matrix account).

Project Parent Folder

KidsRuby Spec File

KidsRuby – No Arch RPM <– Right click on link and save to computer to download

KidsRuby – Source RPM

Ruby Warrior – Source RPM

Ruby Warrior – No Arch RPM <– Right click on link and save to computer to download

Ruby Warrios Spec File

Overall this has been a great experience and I have learned a lot. If there is anymore information that is needed please feel free to email me at danielsegree@me.com.

Release 0.2

dsegree — Mon, 02 Apr 2012 17:29:48 +0000

In my 0.1 release, I successfully packaged RubyWarrior, with the help of my Prof. Chris Tyler. For this milestone I will be attempting to package KidsRuby. As stated in my previous blog ( Release 0.1), I had to grab the source code from KidsRuby website. Once downloaded, I read the README file to see how to run it. I realized that it needs a few other packages to be installed before it can be ran. Qt4-devel, ruby and rubygems are some of the additional software needed.

Once the additional files were installed I was able to run it by typing the follow command: ruby main.rb

After testing the software, its now time for me to create my spec file. I followed the spec file from my RubyWarrior package. After using rpmbuild -ba kidsruby.spec to build my package, I made sure there were no errors in my spec file and rpm files…. everything looks okay. Before uploading the newly created RPM files to my matrix account, I ran it through mock and koji and all was well.

Below are the links to my spec file, RPM’s and my project parent folder (All files are stored on my Matrix account).

Project Parent Folder

KidsRuby Spec File

KidsRuby – No Arch RPM

KidsRuby – Source RPM

When trying to install my newly created KidsRuby RPM I was getting some errors; I believe I have to make a patch file to edit one of the files needed for the program to run. Also I have to get my desktop icon to actually work and open the actual KidsRuby program. As of right now the desktop icon doesn’t do anything.

Release 0.1

dsegree — Sun, 11 Mar 2012 21:13:49 +0000

RELEASE 0.1

Well here goes nothing… I’m suppose to have a release of some sort today of my project that I am working on… KidsRuby.

I will be the first to admit that I am lost, but I am still trying to make it work. Never give up. So I have downloaded the file and tried to make it work on Fedora 16, but was unsuccessful, so now I’m trying to build it for Fedora 17 coming out in a few months.

I have realized that this isn’t as easy as I thought it was going to be. This package needs a lot of other packages just to get it up and running.

UPDATE: So they have updated the package for KidsRuby from v1.0.5 to v1.1.

I had to grab the KidsRuby software from the KidsRuby download page.
Next I have to grab the Ruby Warrior package, which is a standalone game, which also runs within KidsRuby.
Then I had to grab the required Ruby package for it to run on Fedora 17…Ruby 1.9.3.0-8

Once I had the above downloaded, it was time to start scratching my head lol…. kidding. I installed the latest ruby package and installed the Ruby Warrior game to make sure it worked. After that I then met with Chris Tyler (my professor), who helped me construct the spec file according to Fedora guidelines. Once complete I packaged it and ran it through Mock.

For this milestone I will be packaging Ruby Warrior. Below are the links to my spec file, RPM’s and my project parent folder (All files are stored on my Matrix account).

Parent Project Folder

Ruby Warrior – Source RPM

Ruby Warrior – No Arch RPM

Ruby Warrios Spec File

Using GIT

dsegree — Sat, 18 Feb 2012 01:45:31 +0000

Time to blog… Git Git Git….

Git = Git is a free & open source, distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

GitHub = GitHub is the best way to collaborate with others. Fork, send pull requests and manage all your public and private git repositories.

Resources:

http://git-scm.com/
http://github.com/

To Do:

GIT Lab
Clone the repository at ssh://sbr600@scotland.proximity.on.ca/~/certs/
Add your cert using the instructions in the readme.txt file.
Blog about your experience.

Let’s start the Blogging process…. Below is the read me file of the steps that I needed to take setup my SSH public key on the GIT repo.

Clone the repository at ssh://sbr600@scotland.proximity.on.ca/~/certs/ to your computer.
Command: git clone ssh://sbr600@scotland.proximity.on.ca/~/certs/

Create a new brach in the repo.
Command: git checkout -b dsegree

Add my public ssh key to the repo.

Command: git add dsegree.pub
Command: git commit -m “add some comments”

Note: If the above commit command doesn’t work then type the below commands…..

git config –global user.name “Your Name” <– your name
git config –global user.email you@example.com <– your email

Check the Git log to make sure all looks good.

Command: git log

Push branch to repo.
Command: get push origin dsegree:dsegree

Fineto I am now able to ssh into @scotland.proximity.on.ca

Example: ssh dsegree@scotland.proximity.on.ca

Signing RPM packages

dsegree — Wed, 15 Feb 2012 23:07:58 +0000

An RPM signature, like the digital signature used on many other software-signing systems, is a private key encryption of a checksum. RPM uses the GPG libraries for signing.

My Custom Repository

Create a GPG key, by the running the following command:

gpg –gen-key

Add the e-mail address associated with your gpg key to the %_gpg_name macro in ~/.rpmmacros — the line will look like this:

%_gpg_name “e-mail-address”

Before we can sign our RPM packages, install rpm-sign first:

yum install rpm-sign

Sign one of your packages with by running the follow command:

rpm –addsign ~/rpmbuild/RPMS/i686/httptunnel-3.0.5-1.fc16.i686.rpm

You should now have a signed package that is ready to be added to a custom repo.

Creating a custom YUM Repository

Here is a link to my Repodata:

My Repodata

Create a directory (I am using http protocol to serve the directory, so I’m creating the directory within /var/www/html).

mkdir /var/www/html/yum_repo

Move the signed package into the directory we just created:

mv httptunnel-3.0.5-1.fc16.i686.rpm /var/www/html/yum_repo/

Create the repository metadata for the directory:

createrepo /var/www/html/yum_repo

This command will create a subdirectory called repodata where all the repository metadata are located.

Testing

Create a new repo file in /etc/yum.repos.d by copying and modifying an existing file in that directory. Keep gpgcheck=1 but comment out the gpgkey file.

cp fedora.repo dsegree.repo

Run the following command:

gedit /etc/yum.repos.d/dsegree.repo

Edit this file with the following information:

[insert-your-repo-name-here]
name=
baseurl=http://–put the location of repository here–
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/–the name of key you create goes here–

Now you will need to export your gpg key as a normal user.

Run the following command as normal user:

gpg –export –armor dsegree@learn.senecac.on.ca

Your new repository should be fully function now the first time you try to download from it you will be asked if you like to import the key that you have made earlier.

KOOOOOOOOJI

dsegree — Wed, 15 Feb 2012 20:27:39 +0000

OK here we go my attempt at Koji!…. a little overdue but better late then never lets start with the installation process:

Installing Koji

Installing the Koji CLI
Everything you need to use Koji (and be a Fedora contributor) can be installed in a single step:

yum install fedora-packager

fedora-packager provides useful scripts to help maintain and setup your koji environment. Additionally, it includes dependencies on the Koji CLI, so it will be installed when you install fedora-packager. The command is called koji and is included in the main koji package. By default the koji tool authenticates to the central server using Kerberos. However SSL and username/password authentications are available. You will need to have a valid authentication token to use many features. However, many of the read-only commands will work without authentication.

Fedora Account System (FAS2) Setup – Initial Fedora Setup
In order to interface with the koji server, maintainers will need to run

/usr/bin/fedora-packager-setup

Now on to the fun stuff… time to build a queue request on the Koji servers!

Use Koji to build a scratch package for each of the following architectures:
Primary architectures (submit using the “koji” command):

ARM architectures:

s390 mainframe architectures:

PowerPC architectures:

Issue the command: koji build f17 –scratch yourSRPM to start the process to build a queue request for your package. I used httptunnel. Below are the screenshots of of my request for all of the above architectures.

MOCK

dsegree — Wed, 15 Feb 2012 20:07:19 +0000

Purpose

To use and become familiar with the mock and koji tools.

Mock is used to test that the BuildRequires for a package are complete and accurate, by creating a bare-bones chroot environment containing only the basic build packages plus any packages indicated by BuildRequires lines in the spec file.

Koji is a client-server system which allows you to queue builds within the Fedora build farm. This permits you to test whether your package builds on multiple different architectures, which is especially useful when you don’t otherwise have access to the machines of each architecture. For example, if you are working on a 32-bit PC, you won’t be able to directly test builds on a 64-bit PC architecture (x86_64), nor non-PC architectures such as ARM, MIPS, PA-Risc, IA64, S390, Sparc, and PowerPC.

Preparation for Mock

* Install the mock package: yum install mock
* Add yourself to the mock group: usermod -aG mock yourUserName

After the above is complete we must go ahead a use mock for the correct Fedora package and architect. We must run the below command to do this for Fedora 16 32bit edition.

* mock -r fedora-16-i386 nettle-2.4-1.fc16.src.rpm
* mock -r fedora-16-i386 httptunnel-3.0.5-1.fc16.src.rpm

Here are the screenshots after running mock successfully.

MOCK – HTTP Tunnel

MOCK – Nettle

RPM-Writing (RPM Packaging)

dsegree — Mon, 23 Jan 2012 00:22:14 +0000

RPM-Writing Lab

Let the fun begin! No to sure how to do this and it seems complicated, but I shall find out. **Fingers crossed **

I’ve finished the first part, which was moving the tarball files (package source code) in the ~/rpmbuild/SOURCES directory. I’ve also created two .spec files for my packages, by running the command rpmdev-newspec nameOfPackage. One for nettle (nettle.spec) & one for httptunnel (httptunnel.spec).

Next was to edit the two .spec files with the metadata and fill in all of the required sections. Here is a copy of my .spec files, with all the information entered:

Be back in a few……

Okay so I ran the rpmbuild -ba nettle.spec command and it ran successfully, but when I ran the rpmbuild -ba httptunnel.spec command I got some errors. Not sure what this means but I will have to google or jump on the chat rooms and ask around. Below are the errors:

Found out from a colleague that I have to edit the httptunnel.spec file and add %{_bindir}/* and %{_mandir}/man*/*. I also reached out to my prof (Chris Tyler) via IRC and he gave some great pointers and explained to me why I was getting errors. He also advised me to have a look at RPM Marcos, which explains the marcos that should be used in the spec files.

Build from Source

dsegree — Sun, 22 Jan 2012 23:40:26 +0000

Build from Source Lab

Purpose

To become familiar with the build process.
To create a foundation for later labs.

For this lab I chose http tunneling, and nettle. They were both random picks. Below are the steps I used to build software from source code.

NETTLE:

Website: http://www.lysator.liu.se/~nisse/nettle/

1. wget ftp://ftp.lysator.liu.se/pub/security/lsh/nettle-2.4.tar.gz <– Download the code.
2. time tar xvzf nettle-2.4.tar.gz <– Unpack the tarball
real 0m0.106s
user 0m0.028s
sys 0m0.039s

3. cd nettle-2.4 <– Change to the directory containing the unpacked files.
4. time ./configure <– Run a script that configures the build for our particular system.
real 0m6.118s
user 0m1.170s
sys 0m1.088s

5. time make <– Run a script to build the software
real 0m23.003s
user 0m14.116s
sys 0m4.018s

6. time sudo make install <– Installing the software
real 0m9.519s
user 0m2.881s
sys 0m0.622s

HTTPTUNNELING:

Website: http://www.nocrew.org/software/httptunnel.html

1. www.nocrew.org/software/httptunnel/httptunnel-3.0.5.tar.gz
2. time tar xvzf httptunnel-3.0.5.tar.gz
real 0m0.010s
user 0m0.000s
sys 0m0.002s

3. cd httptunnel-3.0.5
4. time ./configure
real 0m4.496s
user 0m0.911s
sys 0m0.591s

5. time make
real 0m1.696s
user 0m0.902s
sys 0m0.229s

6. time sudo make install
real 0m0.474s
user 0m0.258s
sys 0m0.056s

*** NOTE: The built-in “time” command, provided by bash, is used in front of the above commands; to determine how long a command takes to execute. The above outputs from the time command, shows three different times:

real – the actual time taken to run the command
user – the amount of time the CPU was running the command
sys – the amount of time the CPU was performing kernel operations which were initiated by this command

About Me…

dsegree — Sun, 15 Jan 2012 03:54:34 +0000

My name is Daniel Segree, I’m currently enrolled in CTY at Seneca College.

Hobbies include:

Playing videos
Going out with friends
Playing sports
Anything Apple :-)

Contact Info:

Email: dsegree@learn.senecac.on.ca
Blog: http://dsegree.wordpress.com/
Fedora Project: https://fedoraproject.org/wiki/User:Dsegree
Open Source @ Seneca: http://zenit.senecac.on.ca/wiki/index.php/User:Dsegree
IRC username: dsegree