Yesterday bard has removed openoffice-bin old ebuilds from portage tree but the new ebuilds are still masked(by pauldv) in packages.mask they need to be unmasked. Right now whats happening is that my emerge world -uDp is trying to downgrade openoffice-bin from 1.1 to 1.0. Reproducible: Always Steps to Reproduce: 1.try emerge world -up with ~x86 and untouched packages.mask on x86 system 2. 3. Actual Results: it tries to downgrade openoffice-bin to 1.0... Expected Results: it should install openoffice-bin-1.1....
The reasoning for this is that openoffice 1.1 is still release-candidate and it's not proper to officially provide it as 'the version to use'. If you believe it's stable enough to use anyway (I know I do), add >=app-office/openoffice-bin-1.1_beta2 >=app-office/openoffice-1.1_beta2 to /etc/portage/package.unmask.
hmm.... I could not reopen this bug :(. Thats okey as long as you guys read this :) In this case (refering to the previous comment), I think the ebuilds that were removed as being old, should not be removed. Unless ofcourse if they were considered unstable too. But from the comment I see for removing the openoffice-bin-1.1_beta ebuild to attic, it says its old ebuild, but *Theres no updated ebuild*. Some sort of confusion Hope this helps.
Move deprecated ebuild still being marked as LATER to Fixed.
