Am 17.11.18 um 12:41 schrieb Adrian Bunk: > This would be a huge regression, buildds aren't the only place where > packages get built. > > It doesn't sounds right that we suddenly start declaring it "misbuilt" > when a user builds a package locally with dpkg-buildpackage as has been > working for the past 25 years. > > I am not aware of any real benefits of merged /usr for users, so let's > go back from "How can we mitigate some regressions of merged /usr?" to > "Can we make merged /usr working in buster without causing any > regressions at all?". Of course there are benefits for the users, otherwise we wouldn't be doing it. That said, I don't think this bug report is the right place to discuss this. The way I see this is, that building locally is still supported. Some few packages will be affected by this and be misbuilt a in merged-usr environment. That is not too different from packages being buggy because they have been built locally and e.g. picked up a library dependency from say experimental or some (unwanted) package features where turned on because ./configure auto-detected a locally installed libray. We can binNMU those packages in both cases to have working packages again. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature