Ühel kenal päeval, T, 24.01.2017 kell 09:55, kirjutas Matthew Thode: > So, to be clear, we need to wait for an AT to mark stable for one > arch > on an ALLARCHES package. Once that is done any dev can mark the rest > of > the arches stable.
Currently this seems to be resulting in broken deptrees for arches that don't have a stable profile. arm64 in particular. But I'm not fully sure that's a bad thing yet. As a concrete example, newer setuptools was stabilized on arm64 per ALLARCHES, but the previous stable used bundled dev-python/pip still, while this newly stabilized one depends on the system one. However arm64 doesn't have any dev-python/pip stable, so that's now broken. If it had a stable profile, the stablebot would point this out at least to the maintainer to put depends in place, of course repoman would yell too. I think this is fine, we'll just need to clean up as unstable profile ourselves, but maybe this shouldn't be done, not sure. I will be working on getting some arm64 profiles stable, I just hope the breakage doesn't happen faster than I can catch up (plus ~arm64 first for me...). Anyhow, I guess the point is to not forget to run repoman when doing this ALLARCHES commit :) Mart
