You should target top of branch. Fixing the latest development release is always the first step before considering a backport to an earlier release.
Debian does not require centralized source - rather, each package is expected to contain metadata that points you to the version control system:
$ apt showsrc clevis | grep Vcs-
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Vcs-Browser: https://git.in-ulm.de/cbiedl/clevis Vcs-Git: https://git.in-ulm.de/cbiedl/clevis.git Vcs-Browser: https://git.in-ulm.de/cbiedl/clevis Vcs-Git: https://git.in-ulm.de/cbiedl/clevis.git
But you can also file a bug in the Debian bug tracker and attach a patch.
You should target top of branch. Fixing the latest development release is always the first step before considering a backport to an earlier release.
Debian does not require centralized source - rather, each package is expected to contain metadata that points you to the version control system:
$ apt showsrc clevis | grep Vcs-
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Vcs-Browser: https:/ /git.in- ulm.de/ cbiedl/ clevis /git.in- ulm.de/ cbiedl/ clevis. git /git.in- ulm.de/ cbiedl/ clevis /git.in- ulm.de/ cbiedl/ clevis. git
Vcs-Git: https:/
Vcs-Browser: https:/
Vcs-Git: https:/
But you can also file a bug in the Debian bug tracker and attach a patch.