If this get's fixed in 10.10, can the fix be back-ported to 10.04 LTS?
I am in charge of a business deployment where we are experiencing this bug but we are sticking with the LTS release for obvious reasons.
If this get's fixed in 10.10, can the fix be back-ported to 10.04 LTS?
I am in charge of a business deployment where we are experiencing this bug but we are sticking with the LTS release for obvious reasons.