I think the workflow looks like this
(all that creating of directories and moving around is to get a git-repo.
I wouldn't bet that it is necessary, but i think so)
Don't take my word for nothing. It is late and i wrote it from the top of my head. If commands don't work assume i borked
the path somehow.
Due to the git-repo-creating voodoo we need three work-folders:
mkdir upstream git-build dh-make
download the tar.gz to upstream directory just created
go to the git-build directory and import the *tar.gz from upstream directory
git-import-orig --pristine-tar ../upstream/hexchat-2.9.4.tar.gz
got to the dh-make directory and create a debian/ folder template with dh_make
cp -a ../upstream/*tar.gz .
tar -xzf *tar.gz
mv hexchat-2.9.4.tar.gz hexchat_2.9.4.orig.tar.gz
to make sure it builds correctly
Go back to the git-build and copy the debian-folder from the dh-make directory in place
cp -a ../dh-make/hexchat-2.9-4/debian .
Edit the following files in the debian/ directory
You can remove the bigger part of the *ex files in the debian/ directory (perhaps even all)
Now add debian/ directory to git
git add debian/
git commit -m "adding debian/ directory"
To edit changelog you will need to send an ITP. Try something like this to email@example.com
ITP: hexchat -- an irc client
Owner: YourName <firstname.lastname@example.org>
*Package Name : hexchat
Version : 2.9.4
Upstream Author : I-don't-know-Sorry
*URL : http://hexchat.org/
*License : I-don't-know-Sorry
*Description : IRC client based on xchat
Add the ITP number to the file debian/changelog
Build it with git-buildpackage:
Make sure it is lintian clean
lintian -iIEcv --pedantic --color auto *.changes
Run it with pbuilder to be sure you got the right Depends: in debian/control.
sudo pbuilder create
sudo pbuilder build *dsc
(you will need to edit visudo for that)
If it succeeds test the result ( /var/cache/pbuilder/result ) once again with lintian (won't hurt).
Upload the git-build directory to a git-host, say gitorious.
git push --all
git push --tags
Now it is time to send a RFS to find a sponsor.
Make sure to mention that it is lintian clean, that it builds in pbuilder and where the git-repo is to be found.
There is more to be done, probably, and you will get the info now via email.
(Truth to be told: I am not that sure with the RFS. I am sure you will figure it out).
As you can see this is a question of time too. I guess you sure help someone who wants to upload it if you do all of the investigating work and then just ask for a sponsor.
Lots of things are difficult, sure, but a lot of that simply takes loads of time.
As far i can see this package builds nice and easy, but i only had a very quick look (and am not experienced neither)
If all you want is to use it yourself:
download the tar.gz, unpack it, rename the tar.gz to name_version.orig.tar.gz
cd to the unpacked source
dpkg-buildpackage -us -uc
Call it a day
Like said: This is just the general idea and as far i can tell. It might contain errors, and horrible ones. Else i would have used code-tags for the commands. This it _not_ a how-to. It is a bit of chat in the night (ok, ok, and a tiny wee bit of bigmouthing ...
"I am not fine with it, so there is nothing for me to do but stand aside." M.D.