How to commit on the mainrepository

From Paldo

(Difference between revisions)
Jump to: navigation, search
Revision as of 09:45, 28 August 2008 (edit)
Amnon82 (Talk | contribs)
← Previous diff
Revision as of 09:46, 28 August 2008 (edit) (undo)
Amnon82 (Talk | contribs)
Next diff →
Line 66: Line 66:
* foo-1.0-1: new test package * foo-1.0-1: new test package
-To do this first press'''i'''. Now you are in the edit mode. Write your changes to the svn in english.+To do this first press the key '''i'''. Now you are in the edit mode. Write your changes to the svn in english.
When finished press '''ESC''' to quit the edit mode. With the cmd ''':wq''' you close '''VI'''. When finished press '''ESC''' to quit the edit mode. With the cmd ''':wq''' you close '''VI'''.

Revision as of 09:46, 28 August 2008


About the tutorial

This tutorial is for our developers. I explain you how you can commit your packages to our main-repository. Read this tutorial exactly and keep our rules in mind!


Everything has to have some order. A linux distribution has rules. Otherwise it will be caos and bad publicity. Changing the main-repository might create heavy issues with our user if it is done wrong.

Commit only in branch testing/unstable. Commit only new packages which are NOT in our meta-package paldo. To check if your package is in the meta-packages go on our homepage search for paldo and click on "Show all dependencies" to see them all.

If the package is in the meta-package paldo and you still want to commit it you have to create svn diff patches and mail them to Jürg or Raffaele using this email: Also Amnon82 can look into it: You might get the permission to commit it yourself.


Maybe you get an account from Jürg/Raffaele to commit on our main-repository. To get one you've to prove your self first. Create your own repository for paldo and point Jürg, Raffaele or Amnon82 to it.


  • ssh://
  • svn co svn://

How to


All tarballs get uploaded to "ssh://". They have to be in tar.bz2-archives, so repack them if needed. To upload them us followed cmd:

  scp yourownlocalrepo/sources/packagename/tarballname.tar.bz2


  scp ~/repo/sources/foo/foo-1.0.tar.bz2


We edit the specs only locally! Later we add the new specs to the svn. First you've to get the latest specs using this cmd:

  svn co svn:// specs-svn

Next copy your modified specs into the specs-svn folder. In the terminal change into the folder specs-svn with "cd specs-svn". Before every change you have to get your local svn with svn up to the latest stand. With "svn st" all of your modified specs got displayed. "svn diff" shows you the changes in detail.

If you have a new package created the new spec-file must be added using followed cmd:

  svn add foo.xml

Re-check your changes with "svn st".

If you only update an existing spec-file you haven't to do the steps svn add and svn st.

To close the progress you've to commit your changes to the repo. Do it with: svn commit. The program VI opens. We have a format how we wrote our changes we did to the svn:

  * Packagename-Version-Revision: maybe a personal comment


  * foo-1.0-1: new test package

To do this first press the key i. Now you are in the edit mode. Write your changes to the svn in english. When finished press ESC to quit the edit mode. With the cmd :wq you close VI.

After you entered your svn account password your files got uploaded.

With "svn up" you update your local repository to the latest stand. "svn log | less" shows you the latest changes the main-repository-developer-team did.

"SVN diff"-Patches

For specs which are dependencies of "paldo" and "paldo-base" you have to have a permission from Jürg or Raffaele.

After you added your modified specs as usual you do a "svn st" followed by "svn diff > ~/specs.changes". Your changes got saved in the file "specs.changes" in your home dir. Send this file by email to Jürg and Raffaele (

After you got permission to commit your changes write into your comments by whom you got it.

Follow the log of the build server

It is always good to check the log of our build server. Even with testings and checks sometimes still some packages have build problems on this server. Open Nautilus and connect to our server Open a new terminal by mouse-right-click and choosing "Open in Terminal". Re-enter your personal svn account password. With the followed cmd you can follow the log of the build server:

   tail -f /paldo-x86/var/log/upkg-buildd/upkg-buildd.log /paldo-x86/var/log/upkg/upkg.log

Tutorial by Müller Philip (aka Amnon82) - 28.08.2008

Personal tools