tracker - users/developers have expectations that are not implemented in urpmi correctly
the running application is irpmi.
urpmi is calling through perl bindings to rpm lib and Berkeley DB and is deadlocking between multiple erasures traversing critical regions.
All that rpm lib and Berkeley DB can do is detect the improper usage, warn and deadlock.
That is the purpose of locks on critical regions in spite of I want a pony! expectations.
tracker - users/developers have expectations that are not implemented
in urpmi correctly
the running application is irpmi.
urpmi is calling through perl bindings to rpm lib and Berkeley DB and
is deadlocking between multiple erasures traversing critical regions.
All that rpm lib and Berkeley DB can do is detect the improper usage,
warn and deadlock.
That is the purpose of locks on critical regions in spite of
I want a pony!
expectations.