Packaging Wireshark

Packaging wireshark... what can I say, it didn't go smoothly but then again after reading some other posts on packaging, I quickly realized how lucky I had it.

I simply used Prof. Tyler's steps to making the SPEC file:

rpmdev-setuptree

1. get tarball, put in ~/rpmbuild/SOURCES
2. Go to ~/rpmbuild/SPECS
> RUN rpmdev-newspec [name]
3. Edit name.spec
4. rpmbuild -ba name.spec

I didn't have to change much on the spec file. At first all I did was fill in the meta data and ran the rpmbuild hoping on a miracle. Everything seemed to be going surprisingly smoothly...no errors (warnings, but no errors)...A few minutes later when everything was complete, I went to check my RPM and SRPM directories...and OFCOURSE nothing was there...

BACK to the drawing board I went (aka the SPEC file). I looked at some sample SPEC files on the net and realized a lot of them had

"make DESTDIR=$RPM_BUILD_ROOT install" under %install

So I changed mine to that, ran it again...and it seemed to go better. However with that all said and done, I couldn't get rpmlint and mock to work. I will be asking Prof. Tyler in class tomorrow to see why this was happening.

Kudos to Jesse Keating!

First off I would like to say... the teleconferencing room in the TEL building has the most comfortable chairs ever!

Anyways getting back to the important stuff, during our teleconference with Fedora's Release Engineer, Jesse Keating, we had learned all about what it's like to work for the Fedora Project and specifically what it means to be a Release Engineer.

As a Release Engineer he is responsible for organizing and managing Fedora's progress throughout all the release phases....and best of all... he does it all from home! His thorough explanation of what he does exactly, makes it clear, that he not only is good at what he does but really really likes his job!

I specifically asked Jesse a couple questions.
Question 1: What kind of resources do you use? It seems like you're the go-to-guy so what happens if you can't or are unsure of how to fix a problem?

His answer (in a nutshell): The best resource is the other fedora developers/packagers, google and other redhat engineers!
(for full answer see 33:46 of the recording)

Question 2: What kind of features is fedora incorporating that are making Fedora more mainstream?

His answer (in a nutshell): Easy use features to access things that normal users care about such as web browser, email, battery life, and fast boot up time.
(for full answer see 38:25 of the recording)

Check out the link below for all the Fedora releases.
http://fedoraproject.org/wiki/Releases

Configure - Quite the learning experience.

Last week, we were assigned the task of downloading source code and using the configure function for SBR600 while in SEC520 we were asked to download a sniffer (such as wireshark). I decided to kill two birds with one stone and download the source code for wireshark.

Once, downloaded (using wget [url]), I began to extract the tar file and then ran configure. Well, just my luck things stopped after about a dozen lines where I was getting an error message stating "C compiler cannot create executables" My first instinct was to google it...ofcourse. But instead I decided to get on the seneca IRC channel where I was helped out by a few people (thanks to those people btw).

I quickly learned that I required a package called binutils. After learning how to use sudo apt-get install [tab] (which became my saviour) I installed binutils but also required to install build-essentials (ubuntu's version of binutils...I think). Other packages were required throughout this process such as libpcap (and trust me...the list goes on for a while).

Another major issue I had was with the GTK+ version that was required. But that issue was solved by install libgtk2.0.

After dealing with much struggle and a mass amount of package installations, configure was complete. (yay!) I ran make and make install with smooth sailing. Lastly, I never thought running a program would make me so happy but running ./wireshark and having the program run put a smile on my face. :)

SBR600

apvlahopoulos>	ctyler: ping
	<ctyler>	apvlahopoulos: pong
	<apvlahopoulos>	hi sir, just testing out freenode for sbr600, seems that everything is working
	<ctyler>	Cool! I was wondering who apvlahopoulos was. Suggestion: fill in your real name in your IRC client so people know who you are.
	<ctyler>	The default 'real name' in chatzilla is 'New Now Know How', which is not too informative :-)
	=-=	User mode for apvlahopoulos is now -e
	=-=	YOU are now known as Alex_Vlahopoulos
<Alex_Vlahopoulos> like that?
	<ctyler>	well, you can keep the nick, but add a real name. For example, whether I'm on here as 'ctyler' or 'DrOlgovie', my real name still shows as 'Chris Tyler'
	<ctyler>	Seen anyone else from sbr600 here?
<Alex_Vlahopoulos> not too sure
	* ctyler	sees Alex_Vlahopoulos in #fedora, great. You might also want to join #fedora-admin and #fedora-devel
<Alex_Vlahopoulos> i am using chatzilla and in the Global Settings window it allows me to change the nickname and username... is the username what i change into my real name?
<Alex_Vlahopoulos> or is the real name the name i register with?
	<ctyler>	hmm, I haven't used chatzilla in a while, sec
	<ctyler>	Alex_Vlahopoulos: Under Preferences>Identification>Description -- that's the field I meant
	<ctyler>	it shows up in a /whois
	<ctyler>	(or in most GUIs)
<Alex_Vlahopoulos> Oh perfect, thanks!

http://zenit.senecac.on.ca/wiki/index.php/User:Apvlahopoulos

https://fedoraproject.org/wiki/User:Apvlahopoulos