flowbot wrote:
> Has anyone got an idea of how to work around this
1. migrate to keepassx
2. recompile your own revelation
3. fix the broken package and submit the fix upstream
None are pain-free. I plan to do (1) when I can spare the time. I will
certainly find the time if an upgrade to hardy causes revelation to take
half an hour to open. Talk about motivation :-)
flowbot wrote:
> Has anyone got an idea of how to work around this
1. migrate to keepassx
2. recompile your own revelation
3. fix the broken package and submit the fix upstream
None are pain-free. I plan to do (1) when I can spare the time. I will
certainly find the time if an upgrade to hardy causes revelation to take
half an hour to open. Talk about motivation :-)
Tony