Content translation/Machine Translation/Apertium/Packaging

This is temporary documentation for Apertium Service packaging by Language Engineering team. This page may be moved to elsewhere when documentation is complete.

Repository

 * Gerrit: operations/debs/contenttranslation/PROJECTNAME

Request a new project

 * Ask anyone from Ops team.

Building from tarball
0. If packaging a new package, ask Ops team to create new project else, go to #1.

1. Clone project:

2. Import upstream source:

3. Once imported (and answering question by gbp import-orig), check if branches are OK.

4. Push upstream and pristine-tar branches to Gerrit.

5. Add debian/ folder you prepared.

We're not going into debian/ documentation right now!

6. Add debian/ to git repository.

7. Commit it.

8. Now, push master branch except last commit (ie debian/ folder!)

9. Push tags.

10. And, send debian/ for review to Gerrit.

Building from upstream SVN
0. If packaging a new package, ask Ops team to create new project else, go to #1.

1. Clone project:

2. Copy project from upstream SVN repository and create tarball:

3. Import that tarball to repository:

4. Once imported (and answering question by gbp import-orig), check if branches are OK.

5. Push upstream and pristine-tar branches to Gerrit.

6. Add debian/ folder you prepared.

We're not going into debian/ documentation right now!

7. Add debian/ to git repository.

8. Commit it.

9. Now, push master branch except last commit (ie debian/ folder!)

10. Push tags.

11. And, send debian/ for review to Gerrit.

Jenkins CI for packages
Once package repository is created, add entries in  repository. Edit  and add entries at appropriate line.

Troubleshooting
1. Can't push upstream/pristine-tar to Gerrit.

A. Make sure you've necessary permission for it in Gerrit.

2. Jenkins fails to build package.

A.
 * 1) Check if upstream tag is pushed.
 * 2) Check debian/changelog debian version.