Skip to main content


Showing posts from 2013

Pkgdb2 fully setup on ireland - Official release 0.3

My goal for Release 0.3 in the beginning was to deploy Fedora Package Database and make it work with fedpkg. However, pkgdb was getting outdated so I worked on installing pkgdb2. I managed to deploy a development instance of it for my 0.1, 0.2 I could not do much as it was getting hard to communicate with Pierre.

Now, I have successfully deployed pkgdb2 on

It is completely functional and nothing is broken. It has a database that it is communicating with but there is no data in it as of yet, as i did not understand all the table relationships and did not have time to look into it. Nonetheless, there is no reason why it would not work when data is put into it, because the website is connecting to the right database.

I was told to deploy the pkgdb2 on ireland on a virtual host so i set it up on port 8080. I have properly configured the firewall to allow port8080.
I requested the packages list that needed to be put into the database and I haven't got…

Pkgdb2- Troubleshooting the installation and Improvement suggestions

Suggestions to the Package author:Please include a list of required packages in the instructionsSqllite database works in development version but does not work with the deployment on Fedora19. I have checked it several times on different machines. So we can either convert the data to other databases or fix the sqllite version.The package "Python Fedora" does not work properly when installed through yum. It has to be installed through github. We can include that in the instructions as well.There is this line in pkgdb2.wsgi which suggests to give a path to "pkgdb2" which is actually asking the path to the clone "packagedb2". I was really confused here :). Then I got to know how python import works to figure it out.Also, after installing python-flask from yum, it had to be uninstalled through pip for the FAS login to work, threebean told me that. I have no idea why. That's about it, thank you very much for the help.

Troubleshooting installation issues:…

How to install pkgdb2 (Fedora Package Database) from scratch

This cookbook assumes that Fedora 19 is freshly installed, with some design and development tools that the Fedora setup offers.

Install the Required Packages: $ yum install vim git python-flask \
python-flask-wtf python-wtforms \
python-kitchen python-sqlalchemy \
 postgresql-server postgresql-plpython \
python-psycopg2 mod_wsgi memcached \
 community-mysql-libs community-mysql-devel \
 community-mysqlcommunity-mysql-server \
python-dogpile-cachepython-openid-teams \
  python-openid-cla python-bugzillapython-memcached \
python-docutilspython-dateutil \
python-urllib3MySQL-python \

$ git clone

$ cd python-fedora

$ python ./ install

$ cd ~

Getting the Data from the sqllite database and installing pkgdb2 libraries:
$ git clone

$ cd packagedb2

$ python ./ build

if it works properly then say:

$ python ./ install

you may remove the build if you want.

$ python cre…

Got the database to work with pkdgb2 - \o/ -

Remember the database that I converted to mysql? yes, an innovation that I did :) I got mysql database to work with pkgdb2 so the link is not broken anymore. pkdgdb2 was not officially tested with mysql, therefore, I became the first person to do it. Although the pkgdb2 was tested with sqllite database, it was not working with it. I will update my blog with more details later on. Meanwhile, you can check the working version of pkgdb2 here:

Every Tab should work except the "login" button. That goes to FAS login, so I dont think we need to get it working.

Successfull Deployment of Fedora Package Database(pkgdb2) on ireland(could be my release 0.3 if I cannot get help to test it with a database)

As I said in my last blog post that I would try it on a new VM. I installed Fedora 19 from scratch and this time I did not install pkgdb2 under python/site-scripts, however, I ran it directly from clone to see if that makes a difference. Unfortunately, it did not make any difference. We know for sure that it is hitting the right database but somehow the connection is not opening up properly. I have left a message for Pierre on github and I am online since about 36 hours with very little sleep, waiting to catch him on IRC.

I got access to ireland on Friday, and was told by Chris to deploy the the instance on there. Therefore, however much installation was completed, I successfully set it up Fedora Package Database on Also, I set it up on virtual-host running on port 8080. If anybody wants to check out the deployment they can do so on this url:

Keep in mind, as there is no database to test with, if you click on any link…

Pkgdb2 - 5 hours of head scratching till 6 in the morning

Thursday night after I finished my exams and sat down to install pkgdb2, I made some progress but got stuck in getting a database together to test the pkgdb2 with. Luckily, I found Pierre- the package author, online 1 in the morning.

I started asking him questions and we were trying to resolve why the template database that comes with the clone, not working with this installation. We checked all the important python scripts in a spree of "fpaste" then figured out that my mod_wsgi file is pointing towards the clone and not the installed pkgdb2 directory. So we fixed that and I installed Sqlite manager to see if the database is good and it was. Then we were checking the httpd logs and it still says "table Package" not found. We know from the trouble shooting "print" statements in the script that it is pointing towards the right database but still it gave the same error. Even Pierre said "Now even I don't know what is wrong" :)

Anyhow, I instal…

Some Progress FINALLY! Fedora Package Database - should have been my release 0.2

For so long I had been stuck in getting the Fedora Package Database running. I deployed the test instance for my first release but could not do much after that as I was unable to install the Fedora Package Database. I tried to get in contact with Pierre the author of pkgdb2, he was replying on github but could not get a hold of him on IRC.

Anyhow, I sat determined today to do it myself. Started to analyze the output that I was getting when I was trying to run the scritpt. It was giving me an import error flask.ext.fas_openid module not found. I researched and found some reference to it in github on python-fedora and saw the same guys who manage pkgdb1 and 2 discussing something about that module there.

I uninstalled python-fedora and rebuilt it, but this time I got the source from github because I thought they have the most update version and I was right. I installed python-fedora from there and I stopped getting that error and my beloved pkgdb2 built successfully. Here is a …

0.2 - Pending release - waiting to communicate with Package mantainers

I did not get a chance to update my blog, however, I made some progress after 0.1. I tried to install Fedora Package database but kept running into errors that I have no clue about. It has something to do with importing the existing database to be used with pkgdb2. I am waiting to catch any of the package mantainer on IRC channel so I can install pkgdb2 while I am communicating with them. This way I don't have to report all the bugs/issues on Github or bugtrackker. This is a one time shot. I just have to catch them once and the installation can be done at that time.

Release 0.1.1 - Pkgdb2 succesfful deployment of temporary instance

1. Install needed packages: sudo yum install python-virtualenv libpq*2. Get pkgdb2 git clone Go inside packagedb2 foldercd packagedb24. run virtual env$ virtualenv my-pkgdb2-env5. run this command$ source my-pkgdb2-env/bin/activate your prompt will change to my-pkgdb2-env now6. Run these commands to install dependencies:(my-pkgdb2-env)$ pip install kitchen paver urllib3 (my-pkgdb2-env)$ pip install git+ (my-pkgdb2-env)$ pip install -r requirements.txt (my-pkgdb2-env)$ pip install -r test_requirements.txt7. if everything went without errors then run this command to download a temporary database for your instance(my-pkgdb2-env)$ ./ this will take some time8. If the result came out as "OK" then start the server:(my-pkgdb2-env)$ python runserver.py9. Once started, open your favourite browser and type the following URL:http: was able to get the instance up a…

Release 0.1 - service sbrproject restart

The Main Goal My main project was to port fedpkg to pidora so fedpkg would work with Pidora packages. For that I needed to install Fedora Package Database as fedpkg communicates with it and then modify it for Pidora packages.
Release 0.1 My goal for release 0.1 was to install Fedora Package Database(pkgdb) and make walk-through of it. I stumbled upon a few issues and was communicating with the package maintainers, they said we will only be supporting pkgdb for 2 months now and we are currently working on pkgdb2 which would be ready in 2 months. The instance of pkgdb2 that they have currently has a few bugs and is not ready to work with fedpkg.

What Now? After a group meeting with Chris Tyler and package maintainers, we decided that I should proceed with the installation of pkgdb2, which, although is not ready yet, will be ready soon and maintained. It would not make sense to deploy a package which will go out of date very soon. Moreover, it would also not make sense to deploy pkgdb1 …

Fedora Package Database Installation - From Beginning to as far as I got

1.      Get the package database:
·git clone
2.      Install the needed packages:
·yum -y install python-genshi TurboGears python-turbojson postgresql-server \         postgresql-contrib python-TurboMail python-bugzilla python-fedora \         python-psycopg2 python-sqlalchemy python-feedparser koji mod_wsgi \         python-paver httpd mod_ssl babel python-cpio xz python-argparse \         python-mako python-memcached py NOTE: if you are running on fedora install python-fedora-turbogears by issuing command “yum install python-fedora-turbogears”
3.      go to packaged “cd packagedb”
·python egg_info (you will get a few warnings ignore them)            NOTE:please do a yum update before doing this.
4.     Copy paver to your current directory and renaming  it to paver.local ·cp /usr/bin/paver paver.local
5.      Run this complicated command (copy/paste it carefully so only the code gets copied) ·sed 's/__requires__ = .*/__requires__ = ["…

Fedora Package Installation - Latest update November 19th

I had issue with the paver command when I was installing so I asked it on github.

This was the problem:
paver build --install-conf=`pwd` --install-data=`pwd` --install-sbin=`pwd`
Traceback (most recent call last):
  File "/usr/bin/paver", line 9, in <module>
    load_entry_point('Paver==1.1.1', 'console_scripts', 'paver')()
  File "/usr/lib/python2.7/site-packages/paver/", line 816, in main
  File "/usr/lib/python2.7/site-packages/paver/", line 785, in _launch_pavement
    execfile(environment.pavement_file, mod.__dict__)
  File "", line 16, in <module>
    from turbogears.finddata import find_package_data
  File "/usr/lib/python2.7/site-packages/turbogears/", line 9, in <module>
    from turbogears.config import update_config
  File "/usr/lib/python2.7/site-packages/turbogears/config.…

RPM SIgning lab - SBR600

Followed the tutorial on the website:

executed the command gpg --key-gen,
it asked me a bunch of questions and at the end it created the RSA public key.
pub   2048R/FA60C533 2013-11-17 [expires: 2014-01-16]

after this, i just navigated to where I had my RPMS and signed it using this command

#rpm --addsign less-451-1.fc18.i686.rpm
Enter pass phrase:
Pass phrase is good.

here is a link to my signed RPM

[hitman@localhost i686]$ rpm --addsign grep-2.9-1.fc18.i686.rpm
Enter pass phrase:
Pass phrase is good.
[hitman@localhost i686]$

Here is a link to my signed RPMs:


Created the gpg key by issuing the command

gpg --export --armour > gpgkey.txt

gpgkey.txt can be viewed here

GPG is a very handy tool, probably the only tool i know that can encrypt files, maybe there are other…

Koji Lab SBR600

I already had fedora-packager installed so I did not need to do that.

Ran the command:


Everything was properly set up to use koji.

[hitman@localhost SRPMS]$ time koji build f18 --scratch grep-2.9-1.fc18.src.rpm
Uploading srpm: grep-2.9-1.fc18.src.rpm
[====================================] 100% 00:00:05 1019.85 KiB 177.57 KiB/sec
Created task: 6182383
Task info:
Watching tasks (this may be safely interrupted)...
6182383 build (f18, grep-2.9-1.fc18.src.rpm): free
6182383 build (f18, grep-2.9-1.fc18.src.rpm): free -> open (
  6182385 buildArch (grep-2.9-1.fc18.src.rpm, i686): open (
  6182384 buildArch (grep-2.9-1.fc18.src.rpm, x86_64): open (
  6182385 buildArch (grep-2.9-1.fc18.src.rpm, i686): open ( -> closed
  0 free  2 open  1 done  0 failed

Mock Lab SBR600

Mock creates chroots and builds packages in them. Its only task is to reliably populate a chroot and attempt to build a package in that chroot.

So I began by installing mock
yum install mock Then added my user-name to the group mock
usermod -aG mock hitman Then just ran the mock command to build grep under chroot.
mock -r fedora-18-i386 grep-2.9-1.fc18.src.rpm   Surprisingly, It build without any issues in the first shot! Maybe because I put a lot of work in my SPEC files and made sure build requires and macros are properly given.

INFO: version 1.1.32 starting...
Start: init plugins
INFO: selinux enabled
Finish: init plugins
Start: run
INFO: Start(grep-2.9-1.fc18.src.rpm)  Config(fedora-18-i386)
Start: lock buildroot
Start: clean chroot
Finish: clean chroot
Finish: lock buildroot
Start: chroot init
Start: lock buildroot
Mock Version: 1.1.32
INFO: Mock Version: 1.1.32
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled yum cache
Start: cleaning yum metadata

Installing Fedora Package Database

1.Get the package database from · will get a tarball, extract it using ·tar -xvf fedora-packagedb-0.6.0
3.Install the needed packages: ·yum -y install python-genshi TurboGears python-turbojson postgresql-server \         postgresql-contrib python-TurboMail python-bugzilla python-fedora \
        python-psycopg2 python-sqlalchemy python-feedparser koji mod_wsgi \
        python-paver httpd mod_ssl babel python-cpio xz python-argparse \
        python-mako python-memcached (you can probably copy paste this)

4.go to fedora-packagedb-0.6.0 ·run: python egg_info (you will get a few warnings ignore them) NOTE:please do a yum update before doing this. ·paver build --install-conf=`pwd` --install-data=`pwd` --install-sbin=`pwd`
5.start the postgresql service if it is not already started by issuing ·service postgresql initdb ·start the service using "service postgresql start"
6.Create postgresql users:  sudo -u postgres createuser -S…