On 2017-05-09 10:12, Rich Freeman wrote: > Why not? If an arch is considered a non-security-supported arch > then you would just ignore it in a security bug.
We dropped security coverage already for ia64 and are in the process to drop it for sparc as well. So how do you want to cleanup a package which is the last ebuild of the package and still marked stabled for ia64/sparc? You cannot. If you are lucky you would only remove a package without any rdeps. But in most cases you are breaking the tree. > Otherwise a revbump could break stage3 on those arches. Is this really a problem? What could happen: Worst case: Existing stage3 for this specific dev/exp architecture will be very old because any attempt to refresh the stage3 image will fail with a build error. However, the last working stage3 image won't go away until it was replaced by a newer working one... Also, is this different from current status? Not really: If this architecture would be capable to keep up with all the other major architectures the stage3 image would be in a current working state. Build errors would be solved in time. We wouldn't discuss dropping them. So we are only talking about architectures which have shown that they are not able to keep up. And those architectures are already lacking behind, i.e. they don't have a current stage3... -- Regards, Thomas
signature.asc
Description: OpenPGP digital signature
