Galeon 1.0.x is no longer in development and will no longer be supported, so it would be suggested that after the next galeon release (1.2.0) it is unmasked. 1.2.0 is now string-frozen for translation, and should be avaiable "real soon now"
Think the better solution would be to only mask 1.1.0* releases, and remove them from cvs as well. Not every user use 'emerge --clean rsync'
Its a non issue... if we check in 1.2.0 ebuild and unmask it, its a higher version so it would take precendence no matter unless the user manually specified the old version. I'd recommend yanking the 1.1.x builds and keeping the last 1.0.x build for awhile... Don't really see why we have to have an open bug for this....
This is a non-issue at this point