Difference between revisions of "DEB-packaging"

Revision as of 09:53, 11 September 2016

Introduction

We want to be able to work on DEB packages for OpenStack create working deb packages. This will allow us to work on Ubuntu/Debian compatible packages with community and DEB packages maintainers who are already doing the same work separate.

Goals

The goal of the project is to create and develop further a central place for DEB packages specifications. Here we will maintain Linux packages for the OpenStack. This will allow to involve to development process as maintainers of Linux packages as developers of various types OpenStack projects. Together, we will do better packages.

Releasing a new upstream release package

project-config/gerrit/projects.yaml has the track-upstream option. Meaning that Gerrit should have the latest upstream tag already, and that we should be able to just merge a tag from upstream into the packaging branch. Therefore, here's the procedure. Let's take oslo.cache as an example, and let's make the assumption we want to package the latest version upstream version 1.14.0 for Newton, as per requirements/upper-constrants.txt.

git clone https://git.openstack.org/openstack/deb-python-oslo.cache
cd deb-python-oslo.cache
git checkout debian/newton
git merge -X theirs 1.14.0
dch --newversion 1.14.0-1 -m "New upstream release"
# Edit debian/control to fix (build-)dependencies and do any other packaging change needed for the release
git commit -a --amend

Note that the fix of debian/changelog and debian/control should be done in the same single commit as the merge commit, otherwise the package will fail to build.

Once the package builds successfully in OpenStack infra on all the distributions it support (as of writing, this is only Debian Jessie, but we are planning to add more later), then ask a core reviewer to approve your change request. If you are a core reviewer yourself, it's fine to self-approve your change if nobody is around in the #openstack-pkg channel to do it for you.

Once the CR is merged into the OpenStack upstream CI, it is a good moment to also upload it to Debian Experimental.

Contact

The team can be found on the Freenode IRC channel #openstack-pkg.
he PTL for the Newton Cycle is Monty Taylor (IRC nick: mordred)

Subpages

DEB-packaging/Meetings

@@ Line 15: / Line 15: @@
 project-config/gerrit/projects.yaml has the track-upstream option. Meaning that Gerrit should have the latest upstream tag already, and that we should be able to just merge a tag from upstream into the packaging branch. Therefore, here's the procedure. Let's take oslo.cache as an example, and let's make the assumption we want to package the latest version upstream version 1.14.0 for Newton, as per requirements/upper-constrants.txt.
-git clone https://git.openstack.org/openstack/deb-python-oslo.cache
+# git clone https://git.openstack.org/openstack/deb-python-oslo.cache
+# cd deb-python-oslo.cache
-cd deb-python-oslo.cache
+# git checkout debian/newton
+# git merge -X theirs 1.14.0
-git checkout debian/newton
+# dch --newversion 1.14.0-1 -m "New upstream release"
+# # Edit debian/control to fix (build-)dependencies and do any other packaging change needed for the release
-git merge -X theirs 1.14.0
+# git commit -a --amend
-dch --newversion 1.14.0-1 -m "New upstream release"
-# Edit debian/control to fix (build-)dependencies
-# and do any other packaging change needed for the release
-git commit -a --amend
 Note that the fix of debian/changelog and debian/control should be done in the same single commit as the merge commit, otherwise the package will fail to build.