On 14.07.2018 13:01, Michael Biebl wrote: > Am 14.07.2018 um 12:28 schrieb Mattia Rizzolo: >> On Sat, Jul 14, 2018 at 11:59:37AM +0200, Michael Biebl wrote: >>> debootstrap was changed (again) in 1.0.102 to now default to >>> --merged-usr [1]. >>> >>> Systems are not forcefully upgraded to a merged-usr setup atm though. >>> buildds are regularly re-created from scratch and will thus have a >>> merged-usr setup. >>> This means, binaries that were built in a merged-usr buildd environment >>> will now run on a lot of non-merged-usr setups. >> >> Is that really so? I expect buildds to run with stable's debootstrap, >> so for now they should be using non-merged-usr chroots. > > I would have expected that buildds use debootstrap from unstable, but > I'm not a buildd admin, so I trust you to know more about that then me. > Thanks for correcting me on that and sorry if that caused confusion.
For the record: buildds usually (except new architectures) run stable and hence have no easy way of pulling in a newer debootstrap. That also makes them relatively easy to reason about. Packages we forked in the past were sbuild and sometimes schroot (although we try very hard to avoid that). > Still, in the hopefully not too distant future, we will have such a > debootstrap in stable, so it's probably a good idea to be prepared for > that by then. TTBOMK, there are no plans to forcefully upgrade systems > to a merged-usr setup on stretch → buster upgrades. I suppose this point still stands. :) Kind regards Philipp Kern