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
Alioth Project: http://alioth.debian.org/projects/pkg-salt
Interacting with the team
Email contact: <pkg-salt-team@lists.alioth.debian.org>
Mailing list: https://lists.alioth.debian.org/mailman/listinfo/pkg-salt-team
Task description
Packaging of Salt (http://saltstack.com) and related projects.
Related
HowTos
Initial Repository Setup
1) download the .tar.gz and dsc files from http://debian.madduck.net/repo/pool/main/s/salt/
dget http://debian.madduck.net/repo/pool/main/s/salt/salt_0.12.1-1~bpo60+1~madduck.2.dsc (or another dsc filename if applicable)
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:
cd salt/
Verify new upstream version
uscan --verbose --download
Initiate a new Git directory
git init
or maybe a git clone git+ssh://userteam-guest@git.debian.org/git/pkg-salt/pkg-salt.git before all this it's a better idea (?)
Importing a new salt release
git-import-orig ../salt-0.14.0.tar.gz -u 0.14.0 --pristine-tar
Removing useless files
rm doc/_themes/saltstack/static/fonts/.DS_Store rm doc/_build/html/_static/fonts/.DS_Store
This files it's only used on Mac OS Systems and generate a lintian warning.
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
- 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 1 vote from Franklin