@mak then what about

https://tracker.pureos.net/w/development/packaging_overview/

This says I should bootstrap landing. One side has to give in.

What usually happens is that you debootstrap green and then just add the landing repository (either replacing green, or on top).
Oddly though, that's not mentioned in https://tracker.pureos.net/w/development/pbuilder_environment_quick_setup/ even, so I think the docs need some update to reflect the current state of things (even if we add a landing suite to debootstrap later).

can we get rid of this hack? There will be more people contributing to pureos in the future (phone team).

There's also tools like vmdeboostrap that invoke deboostrap / pbuilder directly. It would be much simpler if they could work out of the box.

Same is true for purple.

@mak, go forward with this implementation so contributions and work of phone team becomes natural within pureos :)

Ubuntu's scripts (/usr/share/debootstrap/scripts) are also in Debian. Would be great if the same were to be true for pureos since that would tickle to all downstreams and enable many more people to contribute without hazards.

@guido Ubuntu's scripts have a less-generic name though - that's why debootstrap in Debian has "green" and the Tanglu distribution names ("chromodoris", etc.) but not "staging" (Tanglu's equivalent to "landing") - I assume the same will be true for the generic landing name.

Meanwhile though we can update the scripts in PureOS, I need to revise them anyway, and add landing.