packaging and releasing a backport from Debian is not documented
https://developer.puri.sm/Librem5/Contact/Uploading_to_PureOS.html covers upstream packages and forks from Debian, but not backports from Debian.
Page itself distinguish between upstream and downstream packaging, documents inline upstream part, and references snippet 138 for downstream part.
Snippet 138 distinguishes between upstream and forking from Debian, documents again(!) upstream part, and half documents half references PureOS packaging for forks from Debian.
I am missing how to package projects in the process of being packaged for Debian, but temporarily pulled into PureOS until it emerges in Debian. I imagine such section would be similar to Debian backports, and e.g. cover the following:
- Use version suffix
~pureos+librem5.<number>(i.e. with tilde unlike regular Librem5
pureos+librem5.<number>or regular PureOS
- Some way of declaring the origin suite (or salsa repo in cases of not yet included officially in Debian yet)
- Some mechanism of tracking if PureOS release is falling behind from the origin
- Some mechanism of tracking if origin disappears (e.g. removed from Debian testing, or rejected from NEW queue)
- Some upper limit to how long a PureOS release can be out of sync with its origin, before it is dropped from PureOS (and how dependencies and leaving users with abandoned packages is handled for those situations)
- Some mechanism of detecting when backport is obsolete (seems PureOS infrastructure require manual action to switch to pulling from Debian)