Jelmer Vernooij

A common complaint about distribution packages - especially those that do more than just wrap the upstream build system to create a more integrated system, like Debian - is that packaging is perpetually behind on upstream releases. Over the last couple of years, the ubiquitous use of git by upstreams and various efforts in Debian ([uscan](https://qa.debian.org/cgi-bin/vcswatch "uscan"), [Vcs-Git](https://upsilon.cc/~zack/stuff/vcs-usage/), [DEP-12](https://dep-team.pages.debian.net/deps/dep12/)'s Repository field, [autopkgtest](https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html), [machine-readable copyright files](https://dep-team.pages.debian.net/deps/dep5/)) have made it easier to find the locations of upstream code and to automatically (but not just naively) import changes into packaging. This makes it possible in many cases to automatically provide updated packages of packages in the Debian archive, incorporating new upstream releases as well as daily Git snapshots. This talk will reveal how many packages can already be automatically rebuilt against fresh releases and snapshots from their upstream, and it will cover the challenges overcome and ahead to do this for more of the archive.