Bug 14908 addressed this problem in the past. That bug has been closed with a implementation that does the job for us until the nsLocalFileSpec* is fully implemented. Correct version of RecursiveCopy implementation is requested to achieve this feature.
Status: NEW → ASSIGNED
Depends on: 23664
Target Milestone: M14
Making it dependent on 23664. marking M14.
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
There is no easy hack. It is not really a beta stopper. Will fix it along with 23664. Moving to M15.
Target Milestone: M14 → M15
Moving to M17. If bug 23664 gets fixed earlier, I will fix this one too.
Target Milestone: M15 → M17
Moving to M20.
Target Milestone: M18 → M20
something that need to be done for RTM. Not for beta3.
Bhuvan, M20 was essentially FUTURE since we did that before FUTURE existed. What makes this suddenly so important that we'd risk the RTM for it?
Whiteboard: [rtm need info]
OK. I was thinking that we would go upto M20 for all rtm bugs. This is not a critical RTM bug (we can live with rtm-). The impact is very minimal and the implementation work around is real simple as opposed to the real solution at least for RTM. Changing the milestone to Future.
Target Milestone: M20 → Future
rtm- since Bhuvan agrees w/future.
Whiteboard: [rtm need info] → [rtm-]
Doing a mass reassign to Conrad Carlen. Conrad is going address all current and upcoming profile manager issues. Please do not hesitate to involve me in any of the issues.
Assignee: racham → ccarlen
Status: ASSIGNED → NEW
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
This has been fixed for quite a while now.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.