Great #tldr of how to manage (modify & build) #debian packages with the less effort possible using #dgit
In the ongoing saga of my #debian-devel unretirement, my next step is to recreate my build daemons.
I have tooling that uses #gitpkg and #dgit that communicates to the build machine over ssh (either a KVM locally or a virt on AWS).
I used to use `bootstrap-vz` to build the kvm or AWS AMI minimal images, that had minimal barebones install + sshd + build-essential. However bootstrap-vz seems to have bit rotted. Using fai-diskimage seems to be future proofing since that is what Debian uses.
@wolf480pl
Partly historical, the #debian packaging workflow evolved from source tarball plus a .diff, the requirements for #gpl compliance suggested it was best to keep a copy of your sources to ensure you could provide them, and since then Debian as a community has developed a wide range of interesting ways to modernize packaging workflows, e.g. #VCS or #git driven (#dgit FTW!). What was your favorite VCS in the early 90s? If Debian were to start today, it would look very different.