Skip to main content

Posts

Showing posts from November, 2013

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 https://github.com/fedora-infra/packagedb2.git3. 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+https://github.com/fedora-infra/python-fedora.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)$ ./runtests.sh 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:127.0.0.0:5000I 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 https://github.com/fedora-infra/packagedb.git
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 setup.py 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.

https://github.com/fedora-infra/packagedb/issues/13

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/tasks.py", line 816, in main
    _launch_pavement(args)
  File "/usr/lib/python2.7/site-packages/paver/tasks.py", line 785, in _launch_pavement
    execfile(environment.pavement_file, mod.__dict__)
  File "pavement.py", line 16, in <module>
    from turbogears.finddata import find_package_data
  File "/usr/lib/python2.7/site-packages/turbogears/__init__.py", 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: http://zenit.senecac.on.ca/wiki/index.php/Signing_and_Creating_a_Repository_for_RPM_Packages

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.
less-451-1.fc18.i686.rpm:

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.
grep-2.9-1.fc18.i686.rpm:
[hitman@localhost i686]$



Here is a link to my signed RPMs:


grep-2.9-1.fc18.i686.rpm
less-451-1.fc18.i686.rpm


Created the gpg key by issuing the command

gpg --export --armour msmahmood@myseneca.ca > 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:

/usr/bin/fedora-packager-setup

Everything was properly set up to use koji.

GREP
[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: http://koji.fedoraproject.org/koji/taskinfo?taskID=6182383
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 (arm02-builder10.arm.fedoraproject.org)
  6182385 buildArch (grep-2.9-1.fc18.src.rpm, i686): open (buildvm-15.phx2.fedoraproject.org)
  6182384 buildArch (grep-2.9-1.fc18.src.rpm, x86_64): open (buildvm-21.phx2.fedoraproject.org)
  6182385 buildArch (grep-2.9-1.fc18.src.rpm, i686): open (buildvm-15.phx2.fedoraproject.org) -> 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: mock.py 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
Finis…

Installing Fedora Package Database

1.Get the package database from ·https://fedorahosted.org/releases/p/a/packagedb
2.you 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 setup.py 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…

Centos- Issue with mounting ntfs filesystems- (mount: unknown filesystem type ‘ntfs’)

Step1: su Step2: wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.3.6-1.el5.rf.i386.rpm Step3: rpm -Uhv rpmforge-release-0.3.6-1.el5.rf.i386.rpm Step4: yum install fuse fuse-ntfs-3g dkms dkms-fuse Step5: mkdir /mnt/usb final step: mount -t ntfs-3g /dev/sdc1 /mnt/usbSource:http://rajivpandit.wordpress.com/2012/10/31/mount-ntfs-on-linux-centos/comment-page-1/#comment-2727