Can we stabilize Crypt-Eksblowfish? It's a crypto package that can be used by otrs to support the optional support for bcrypt hashing. It depends on dev-perl/Class-Mix, so this needs to be stabilized as well.
And Class-Mix depends on dev-perl/Params-Classify, so we'd need to stabilize that as well.
Errm, why? otrs is not stable either.
well, I just think packages that are kind of "settled" should go stable at some point. And I wanted to point out why these packages matter. whether otrs can go stable is another question.
(In reply to Hanno Boeck from comment #3) > well, I just think packages that are kind of "settled" should go stable at > some point. And I wanted to point out why these packages matter. whether > otrs can go stable is another question. Hanno, we're trying hard to avoid unneccessary increases in the stable set at the moment. Many arch teams are effectively defunct, and the stabilization bug queues are growing and growing. Only security stabilizations are still handled timely. If you have the time, *please* consider joining an arch team of your choice and helping with testing. Even amd64 or x86 will be a lot of help. Or join the wg-stable workgroup (see also the #gentoo-wg-stable irc channel) for planning how to get out of the hole. With this background, I'm sorry, wontfix for now.
