On 5/8/13 2:56 AM, Andreas K. Huettel wrote: > the deptree of kde-base has been broken for over two months now (most likely > more, it was already bad for a while when I filed bug 460532), and we cannot > really commit new KDE releases without repoman --force option. > > A package is missing keyword ~amd64-fbsd, and so far noone from that team has > responded to our repeated communication attempts. > > For the KDE team, I see two options: > 1) remove amd64-fbsd keyword everywhere. This is "within our rights to do", > but hits users badly (if there are any). > 2) downgrade the amd64-fbsd profiles from "stable" to "dev" in > profiles/profiles.desc. This has the big advantage that the impact for users > is minimal, but enables us to work normally again at the same time. Needless > to say, it's not really a usual step to take for anyone outside the > amd64-fbsd > team. > > Out of frustration I am slowly tending to just commit option 2 and take the > resulting flak.
I support anything done to unbreak the tree. If possible, masking USE flags or packages on amd64-fbsd sounds better than switching the whole profile to dev, which is likely to introduce even more breakages. Paweł
signature.asc
Description: OpenPGP digital signature
