ubuntu/devel: TIP. Currently this points at 24.04 noble
ubuntu/<release>-devel: is the TIP for that release. For example, ubuntu/jammy-devel would be TIP for 22.04 jammy. This includes packages currently in the -proposed repositories.
applied/<whatever>: same as above, but with all patches from debian/patches/* applied to the source tree.
Sure. For any package in ubuntu, the git repository is in:
https:/ /code.launchpad .net/ubuntu/ +source/<package>
So, for apache2 for example, it would be:
https:/ /code.launchpad .net/ubuntu/ +source/ apache2
Then, the branches. Quick intro:
ubuntu/devel: TIP. Currently this points at 24.04 noble <release> -devel: is the TIP for that release. For example, ubuntu/jammy-devel would be TIP for 22.04 jammy. This includes packages currently in the -proposed repositories.
ubuntu/
applied/<whatever>: same as above, but with all patches from debian/patches/* applied to the source tree.
In the case of unreleased packages, like my apache2 PPA packages, then it's in my own namespace. In the https:/ /code.launchpad .net/ubuntu/ +source/ apache2 page, scroll down until "Other repositories", and there will be https:/ /code.launchpad .net/~ahasenack /ubuntu/ +source/ apache2/ +git/apache2, and you can usually locate the correct branch name in there.
So for pkcs11-provider, the repo is https:/ /code.launchpad .net/ubuntu/ +source/ pkcs11- provider
And for openssl- pkcs11- sign-provider, the repo is https:/ /code.launchpad .net/ubuntu/ +source/ openssl- pkcs11- sign-provider