I use both GNUstep and libsafe on my desktop and laptop, and libsafe on my server. All 3 systems now issue complaints when I run "emerge -Du world" because the stable x86 ebuilds were deleted.
These aren't the only packages to have this happen recently. Paolo Pedroni <firstname.lastname@example.org> filed bug 117518 when the alsa-utils lost its stable x86 ebuild.
I marked this as "all platforms, all OS's" because it's a human error, not a coding error, and could happen to any ebuild on any platform.
If it were within my power, I would make it impossible to remove the last stable ebuild for a package. New packages which have never had a stable ebuild would be exempt. Once a package has a stable ebuild, it should *always* have a stable ebuild, until it is totally deleted from Portage.
I'm not sure what a proper preventative measure would be (a GLEP?), or if this is the proper place to complain about this. If I should say this in a different forum, just say so, and I'll take it there. I just had to say something.
Well, I'm sorry but sys-libs/libsafe has never been stable anywhere, and gnustep-gui has 0.9.5 stable.
Yes, you are right. It appears that I have somehow installed some ~x86 packages unwittingly. I never had libsafe or any GNUstep packages (except gorm) marked as ~x86, so I don't know how they got installed.
Complaint withdrawn. Sorry for wasting your time.