Differences between revisions 8 and 9
Revision 8 as of 2013-04-06 02:23:18
Size: 2423
Editor: ?JoeHealy
Comment:
Revision 9 as of 2013-04-06 02:27:31
Size: 2746
Editor: ?JoeHealy
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Our aims are to package salt and then the other salt tools (salt-api, salt-cloud etc) for debian and subsequently ubuntu.

Our primary aim at this point is firstly getting salt into debian unstable and hopefully being backported to wheezy and squeeze. Following this, we will be repeating this process for the other salt tools.
Line 8: Line 12:
If you wish to join part of the team, the best approach is probably to join the mailing list. If you wish to be involved, the best approach is probably to join the mailing list.

Salt Packaging Team

It is early days for the salt packaging team, but we are setting up the infrastructure.

Our aims are to package salt and then the other salt tools (salt-api, salt-cloud etc) for debian and subsequently ubuntu.

Our primary aim at this point is firstly getting salt into debian unstable and hopefully being backported to wheezy and squeeze. Following this, we will be repeating this process for the other salt tools.

Most of the information below is for the team to learn, agree and standardize on processes for setting up and working with the repository we will use for packaging. Although it contains information that may be useful for building your own salt packages, that is not the intention at this stage. For the moment, the best reference is probably http://docs.saltstack.com/topics/installation/debian.html.

If you wish to be involved, the best approach is probably to join the mailing list.

Infrastructure

Interacting with the team

Task description

Packaging of Salt (http://saltstack.com) and related projects.

HowTos

Initial Repository Setup

1) download the .tar.gz and dsc files from http://debian.madduck.net/repo/pool/main/s/salt/

2) Use git-import-dsc with madducks last 0.12.1 release:

git-import-dsc salt_0.12.1-1~bpo60+1~madduck.2.dsc --pristine-tar

3) Download and import the released 0.14.0 tar.gz from pypi:

wget -c https://pypi.python.org/packages/source/s/salt/salt-0.14.0.tar.gz#md5=0f9fa32f208356e41ac8e0976e927b41
git-import-orig ../salt-0.14.0.tar.gz -u 0.14.0 --pristine-tar

Importing a new salt release

Do we need to do something with uscan here?

wget -c https://pypi.python.org/packages/source/s/salt/salt-0.x.0.tar.gz
git-import-orig ../salt-0.x.0.tar.gz -u 0.x.0 --pristine-tar

Building the packages

Is this the best? Some people use pbuilder - should that be our standard process?

git-dch -i
git-buildpackage -us -uc

Testing the packages

1. Install on sufficiently clean system

1. Uninstall

1. Install previous version

1. Upgrade to new package

1. Test basic package functionality

Backporting

Decisions

Proposed Decisions

  1. Use of git and git-buildpackage for VCS
    • I think this is pretty likely given we are starting from scratch and the pros and cons from Andrii. 1 vote from JH