bicyclerepair-0.9-r1 is in the tree since about 2 months, no bugs reported. Please consider stabilising it on x86 at least.
Is there a reason why do you need that one stable? Since it's not actively maintained anymore and version 0.9 is from 2004, I guess it will become harder to maintain it with future python versions. I'd rather like to see this not stable.
(In reply to comment #1) > Is there a reason why do you need that one stable? > Since it's not actively maintained anymore and version 0.9 is from 2004, > I guess it will become harder to maintain it with future python versions. > I'd rather like to see this not stable. Sorry, but I don't get your point here. The package is functioning, and there are no open bugs. So, why should 0.7.1-r1 (which is stable on x86) be preferred over 0.9-r1?
aah, didn't see that there's one stable already. Well, then go ahead to have the new version marked stable for the archs which already have an old version stable but no others please.
x86 stable, closing as we are last one