Hi all, As I was the one wanting amd64-fbsd profiles 'stable' to ensure a sane deptree, and seeing the number of (re)keywording bugs growing and growing while I don't have time to process them and no-one else is doing it, I just switched them to 'dev' state.
For users, this means they can no longer expect packages to have a correct dependency tree with ~amd64-fbsd keywords: packages can now have missing optional, or even mandatory, deps making them uninstallable in some cases. For developers, this means broken dependencies for amd64-fbsd changed from a repoman error to an optional warning; meaning that in most cases developers won't even notice their package has broken deps on this arch. While I don't think there is any general rule, what I would recommend is the following: - If you have a package whose amd64-fbsd keywords have been dropped between version N and N+1, keep version N in tree as long as it does not annoy you, then drop it. - If you introduce a new version that would create a broken deptree (and run repoman -d to notice it), keep ~amd64-fbsd keywords if the missing dep is optional, drop keywords otherwise. - Since, from my experience, most developers will not even notice broken deps on amd64-fbsd, filling (re)keywording bugs for amd64-fbsd is optional. Anyone wanting to restore its "stable" state will have to run a full check on the entire tree anyway. If anyone is interested in taking over the arch and restoring its "stable" status, you are very welcome, but for now it is just annoying more and more fellow developers in this state. Best regards, Alexis.
