Comment 9 for bug 1827340

Hello,

generally, changes like this should be done in Debian first, however the 'cloud' packages can sometimes be special.

@corey.bryant, do you have an opinion on changing the swift sysv init scripts over to normal systemd services (meaning, @tkurek doing the work with me assisting him)? If you're ok with that, would you prefer it go into Debian first, or just carry it in Ubuntu (I assume Debian first, but just checking).

@tkurek, assuming Corey doesn't object to the systemd service change in general, and prefers it in Debian, there are generally two ways to get changes into Debian, either open a bug with the debdiff attached, or open a Debian Salsa merge request.

The Debian swift bug trackers shows no bugs currently:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=swift
but you could open one with the debdiff fairly easily, by using the 'submittodebian' script from the ubuntu-dev-tools package. Its manpage is not super descriptive, but essentially you just need to run the script from the package source you want to patch. If you have questions about its usage let me know.

Alternately (or additionaly) you can try opening a salsa merge request:
https://salsa.debian.org/openstack-team/services/swift
you will need to create a 'guest' salsa account, and after that it's basically the same process as github/gitlab.

I've subscribed to this bug so let me know if I can help with any further steps in the process.