El 16 mar. 2018 11:55 a.m., "Adrian Bunk" > sorry but we can't enforce such dependencies, specially with experimental versions of qt.
We can, and we should. And we do, +/- bugs. > The stack needs to be still fully bootstrapped and built, this is why it is in experimental. And then the stack goes piece by piece slowly into testing, breaking everything there (and in Debian derivatives using testing). Adrian: no, and the sole fact that you are stating this means to have no idea of how we handle packages. > Stuff will and should self heal in a matter of days, if not, when the qt will go in unstable, if a rebuild > will be necessary, please open a bug against qtbase, for not providing a stable ABI, and then affect this package. Non stable API is provided in -private packages, tracked and rebuilt with every transition. Each and every transition is managed to get a coordinated entry to testing, and when bugs showed up we went ahead to solve them. You are free to ask the release team about that. I'll kindly ask you two to not close or reopen our team's bugs. If you consider it's needed do mail the bug in question.
