[Debian-in-commits] [SCM] Git repository for debian-in branch, master, updated. aa12553085f8125d11a41bae38f8d9a99b94e88e

Thu Feb 2 06:21:03 UTC 2012

The following commit has been merged in the master branch:
commit aa12553085f8125d11a41bae38f8d9a99b94e88e
Author: Kartik Mistry <kartik at debian.org>
Date:   Thu Feb 2 11:50:56 2012 +0530

    Updated TODO and some formatting in packaging-how-to

diff --git a/docs/TODO b/docs/TODO
index 2cba7e5..7bb2b92 100644
--- a/docs/TODO
+++ b/docs/TODO
@@ -25,7 +25,7 @@ TODO for Debian-IN Team
 
 * Package the SMC fonts in fonts-smc [Done]
 
-* Package eeyek fonts
+* Package eeyek fonts.
 
 * Package remaining fonts with no active upstream possibly as single upstream
 
@@ -54,18 +54,15 @@ TODO for Debian-IN Team
   - fonts-indic[Done]
 
 * Assign / Close bug reports on ttf-indic-fonts as new fonts packages are
-  uploaded
+  uploaded.
 
 * Move remaining packages of Debian-IN team from SVN to git:
-  - aspell-bn
-  - aspell-gu [Done: Kartik]
-  - aspell-mr
-  - aspell-ta
+  - aspell-mr [Kartik]
+  - aspell-ta [Kartik]
   - festival-hi [Kartik]
   - festival-mr [Kartik]
-  - festival-te
-  - itrans
-  - latex-sanskrit [Done: Kartik/Vasudev]
+  - festival-te [Kartik]
+  - itrans [Kartik]
 
 * Prepare udeb for following
   - ttf-kannada-fonts-udeb => fonts-knda-udeb (Done) (Do we need to
@@ -75,13 +72,11 @@ TODO for Debian-IN Team
   - ttf-telugu-fonts-udeb = fonts-telu-udeb (In which?)
 
 * Review and test all the packages for breakages replacement of old
-  packages and provide bugs and suggestion
+  packages and provide bugs and suggestion.
 
 * Triage bugs on other packages of Debian-IN (We should be bug free ;) )
 
-* Get a nice website done for Debian-IN possibly using ikiwiki
-
-* Fix CIA bot for Debian-IN [Done]
+* Get a nice website done for Debian-IN possibly using ikiwiki.
 
 * Make sure that build-fonts.sh understand relative path and document it.
 
diff --git a/docs/debian-in-git-packaging-how-to.txt b/docs/debian-in-git-packaging-how-to.txt
index c4b55cd..239a09f 100644
--- a/docs/debian-in-git-packaging-how-to.txt
+++ b/docs/debian-in-git-packaging-how-to.txt
@@ -16,17 +16,17 @@ Checking out Repository
  Host alioth.debian.org svn.debian.org git.debian.org
  User user-guest
 
-Again the username will be the same as in step 2
+ Again the username will be the same as in step 2
 
-Probably the file ~/.ssh/config won't be present, so create it If it exists
-append to it.
+ Probably the file ~/.ssh/config won't be present, so create it If it exists
+ append to it.
 
 3. Clone the debian-in repository. (Note: you will be asked to enter your
    ssh-passphrase)
 
  $git clone git+ssh://username@git.debian.org/git/debian-in/debian-in.git
 
-Here, username is you alioth username, in my case it is techmaniack-guest.
+ Here, username is you alioth username, in my case it is techmaniack-guest.
 
 4. Execute ./make-mrconfig
 
@@ -34,10 +34,12 @@ You can find this file inside debian-in/ directory created after step 2.
 
 5. Add the path to .mrconfig in ~/.mrtrust
 
-Step 4 will create ".mrconfig" inside debian-in/ Add the ABSOLUTE PATH of
-".mrconfig" to ~/.mrtrust. In my case the path was "/home/abdulkarim/projects/debian-in/.mrconfig"
-Most probably the file ~/.mrtrust won't be present, so create a new one. If it
-exists just append to it.
+ Step 4 will create ".mrconfig" inside debian-in/ Add the ABSOLUTE PATH of
+ ".mrconfig" to ~/.mrtrust.
+
+ In my case the path was "/home/abdulkarim/projects/debian-in/.mrconfig"
+ Most probably the file ~/.mrtrust won't be present, so create a new one. If it
+ exists just append to it.
 
 6. Run "mr checkout"
 
@@ -54,113 +56,116 @@ Pushing the Debianized package to Debian-in repo
 
 1. ssh into git.debian.org
 
-  `$ ssh username-guest at git.debian.org`
+   $ ssh username-guest at git.debian.org
 
-in my case it was $ssh techmaniack-guest at git.debian.org
+   in my case it was $ssh techmaniack-guest at git.debian.org
 
 2. change the directory to "/git/debian-in"
 
-  `(ssh)$ cd /git/debian-in`
+   (ssh)$ cd /git/debian-in
 
 3. setup an empty repo for 'your package'
 
-  `(ssh)$ ./setup-repository package`
+   (ssh)$ ./setup-repository package
 
-e.g. (ssh)$./setup-repository fonts-lohit-bn
+   e.g. (ssh)$./setup-repository fonts-lohit-bn
 
- - This is all that is to be done on the 'git.debian.org' server.
- - You may close the ssh connection now.
+   - This is all that is to be done on the 'git.debian.org' server.
+   - You may close the ssh connection now.
 
 4.  run "./make-mrconfig" on your local system
 
-  `$ ./make-mrconfig`
+   $ ./make-mrconfig
 
 Note: execute this inside the "debian-in/" directory on your local system.
 
 5.  Update your local debian-in repo
 
-  `$ mr update`
+   $ mr update`
 
-Note: execute this inside the "debian-in/" directory on your local system.
+   Note: execute this inside the "debian-in/" directory on your local system.
 
- - this will add the empty repo created by you in step3 to your local system.
+   This will add the empty repo created by you in step3 to your local system.
 
 6. Go to your package directory, the one created during step3.
 
 7. Import the .dsc file of 'your package' using "git-import-dsc"
 
-  `$git-import-dsc --pristine-tar /path/to/packagenameXYZ.dsc`
+   $ git-import-dsc --pristine-tar /path/to/packagenameXYZ.dsc
 
- - This should populate 'your project' directory.
- - If any modification is to be done, do it now itself.
+   - This should populate 'your project' directory.
+   - If any modification is to be done, do it now itself.
 
 8. Deleting the debian tag
 
-  `$git tag -d debian/version`
+   $ git tag -d debian/version
 
 e.g. git tag -d debian/2.4.4-1
 
 9. push 'your package' to "Debian-in" repo at git.debian.org
 
-  `$ git push --all
+   $ git push --all
    $ git push --tags
-  `
-Note: if git push doesn't work, execute the following command once 
- $git push origin master
+
+  Note: if git push doesn't work, execute the following command once 
+
+   $ git push origin master
 
 10. Inside package directory execute,
 
-  `$git-buildpackage`
+   $ git-buildpackage
 
- You may need to update your ~/.gbp.conf
- See: https://gitorious.org/personal-configuration-files/conffiles/blobs/master/gbp.conf
+  You may need to update your ~/.gbp.conf
 
- Your package will be built at: /var/cache/pbuilder/result by default.
+  See: https://gitorious.org/personal-configuration-files/conffiles/blobs/master/gbp.conf
 
- Check package for any Debian Policy violations using 'lintian' tool.
+  Your package will be built at: /var/cache/pbuilder/result by default.
 
-[Sponsor/Uploaders only]
+  Check package for any Debian Policy violations using 'lintian' tool.
+
+[for sponsor/uploaders only]
 
 11. Upload package. Make sure you run lintian tool before upload.
 
 12. Once package is uploaded, tag it:
 
-  `$ git tag debian/version
+   $ git tag debian/version
    $ git push --tags
-  `
+
 13. When new upstream version is available see below.
 
 
 Importing New Upstream version
 ==============================
 
-1. When there is a new version available for your package run following
+1. When there is a new version available for your package run following:
 
-  `$ uscan`
+   $ uscan
 
-2. This will download the new upstream tarball and create orig.tar symbolic link
-   to it
+2. This will download the new upstream tarball and create orig.tar symbolic
+   link to it.
 
-3. Run following command to import this new upstream version into git repo
+3. Run following command to import this new upstream version into git repo.
 
-  `$ git-import-orig --pristine-tar ../package_version.orig.tar.gz`
+   $ git-import-orig --pristine-tar ../package_version.orig.tar.gz
 
-4. Don't forget pristine-tar switch 
+4. Don't forget '--pristine-tar' switch.
 
-5. Additionally this import will run the git-dch for you but in case it fails due to
-   error run git-dch yourself to update the debian/changelog
-   
-6. Verify changes in new version if new files added / license changed update appropriates
+5. Additionally this import will run the git-dch for you but in case it fails
+   due to error, run git-dch yourself to update the debian/changelog.
 
-7. Once everything is done commit changes and push the changes to repository using following
+6. Verify changes in new version if new files added / license changed update
+   appropriates.
 
-  `$ git push --all
-   $ git push --tags`
+7. Once everything is done commit changes and push the changes to repository
+   using following commands:
+
+   $ git push --all
+   $ git push --tags
 
 
 TODO
 ====
 
-1. New upstream version - how-to?
-2. Prepare other format, probably HTML, MarkDown, PDF.
+1. Prepare other format, MarkDown, PDF.
 

-- 
Git repository for debian-in

