How to maintain the Ubuntu Studio Packages

This section is a step by step description on how to make changes to a Ubuntu Studio package and publish it.

Source Repositories

Ubuntu Studio package source can be found in one of two places:

• Launchpad (where our original sources are kept)
• Ubuntu archive (where the packages are built, and becomes installable)

Source at launchpad

Let's look at a typical Ubuntu Studio original package, using ubuntustudio-default-settings as an example.

Typically all Ubuntu Studio source packages belong to a launchpad project with the same name as the source package. In the case with the package ubuntustudio-default-settings, the project page is launchpad.net/ubuntustudio-default-settings, and the source can be found at code.launchpad.net/ubuntustudio-default-settings.

There may be more than one source repository for the package. The one under active development is the one with the shorthand lp:<projectname>. The real name for the package with that shorhand is trunk, which you can see from this full url to the trunk branch for ubuntustudio-default-settings: https://code.launchpad.net/~ubuntustudio-dev/ubuntustudio-default-settings/trunk.

Repository naming for bzr branches

The development branch: trunk

There's always at least one branch for each project/package called trunk. This is the branch which is under active development, and will always stay that way. So, if you ever create a new original Ubuntu Studio package, create a project for it with the same name as the package, and if you create a bzr repository you name it trunk. If it's a git repository, you may use a different naming scheme.

Stable Release branches

There's no need to create branches other than trun" usually. The situation where this might be needed is when you need to fix a bug in a stable release package, but for some reason you are not able to just build and upload the current development branch. When that happens, you'll can create a new branch which is based on the stable release code - not the trunk branch.

Creating a branch for it under the project will allow other team members to further make changes to the same source, so doing this is only valuable when many people work on the same source. Else, you can just create a personal branch, do the bugfix, and then do a merge request (but this is under the topic bug fixing, so not further explained here).

If you need to create a new branch of the stable release of a package, this is how you do it (using ubuntustudio-default-settings as an example package):

pull-lp-source ubuntustudio-default-settings trusty

Create a new branch in launchpad for it. Name it using either the codename (i.e. trusty), or the release number (14.04). For example:

bzr push lp:~ubuntustudio-dev/ubuntustudio-default-settings/14.04

Making Changes to a Package

Different packages need different kind of treatment. But, simply put, there are two kinds of packages:

• regular packages

• meta packages

Meta Package Maintenance

Meta package is special.

Other packages

bzr, debian build tools, uploading...

CategoryUbuntuStudio CategoryUbuntuStudioDev