Utile OS Debian Packages

Debian packages used in Utile OS, if you were looking for the apt repository, go there.

Note: I am certain that there must be a better way to manage this repository, I just haven't thought of one yet.

Upstream package clone instructions

1. pull-lp-source base-files {codename} {needed_version} to get the source code of the upstream package, this requires the ubuntu-dev-tools package. The needed_version must usually be the absolute latest release in a specific codename/branch. For now, the latest codename we use is resolute.
2. Rename the directory accordingly (for human understanding: base-files-14ubuntu6/ was renamed to base-files-abstract_all/) and introduce a new entry to the Debian changelog file.
   • When the package name comes from Ubuntu's upstream (Debian or original software) and therefore has an Ubuntu revision (e.g., -1ubuntu1), that revision is directly replaced with a Utile revision (e.g., -1utile1) and the .orig.tar.xz (which could either be a package from Debian or original software source code) is retrieved from the package's Launchpad page.
   • When the package name comes from Ubuntu directly and therefore doesn't have an Ubuntu revision (e.g., 3.1.0ubuntu1), Utile OS's revision is added and Ubuntu's package is used as .orig.tar.xz.
   • This is of course very TODO, I think I need to think more about this.
3. (optional) if you're doing this in an already-existing package folder that you want to merge with upstream, run git init && git add . && git commit -m "Current Utile version" to make it a Git repository.
4. git remote add ubuntu https://git.launchpad.net/ubuntu/+source/{package} to add the package's remote repository.
5. git remote update ubuntu to fetch the remote repository.
6. git merge ubuntu/ubuntu/{codename} --allow-unrelated-histories to merge the remote repository into the local repository.
7. (optional) if you did step 3., remove the .git folder from the package folder.

If the local package will undoubtedly match the upstream branch's latest package, then git clone could be used instead:

git clone -b ubuntu/{codename} https://git.launchpad.net/ubuntu/+source/{package}

Upstream package merge instructions

For now, this only means the base-files package, but this is how it should be merged with upstream:

1. git fetch ubuntu to fetch the ubuntu remote.
2. git rebase ubuntu/ubuntu/{codename} main to merge the ubuntu remote into the main branch.
3. dch -i if the updates upstream are incremental, otherwise, manually specify a version.
4. debuild && debuild -T clean to build the package*, this requires the build-essential devscripts debhelper packages.

* if your debuild commands are failing due to 'debsign', then you need to generate a GPG signing key for your package builds so that we can verify your identity as a contributor. This is currently not enforced since I (Aaser Abd-el Sabour, in case you're not aware) manually update all packages (we do not have build farms and build queues to limit package uploads to those who have permission).

However, I do have my personal GPG signing key alongside the Utile OS Debian repository key, and I will use it to upload packages once we have that kind of infrastructure.