.
I think it's time to unmask this. If any package still fails, then it should fix the dependency-string. Any objections?
Please unmask this already.
I think pidgin-otr-4.0.0 needs to be also be unmasked, as the current stable version pidgin-otr-3.2.1 depends on libotr-3.2.1.
Is this getting unmasked? New bitlbee supports this, I'd like to commit it without adding masks :)
Going to unmask it now, after checking again. All packages that are not known to work with libotr-4, will receive a new dep on <libotr-4
(In reply to Manuel Rüger from comment #5) > Going to unmask it now, after checking again. All packages that are not > known to work with libotr-4, will receive a new dep on <libotr-4 That's the right approach instead of masking. * import the package straight without mask into ~arch * all packages that don't work with it have to be fixed (either by version constraint or patch) Seems to me like we are abusing package.mask because portages dependency resolver is broken.